[RESOLVED] Export to PDF Failure

I have an automated task that generates reports every couple of minutes as part of a data processing routine here and everything was working perfectly fine until last week.

The VB application generates reports and exports them to PDF. The process no longer works and luckily, the application does some logging as part of the process and I found this:

Error No: -2147190908
Description: Failed to export the report

So I'm trying to research why all of the sudden, this issue started and what I am reading online seems to think that it has to do with unregistered DLL files. The version of Crystal on the server is 8.5.0.217. The reports are also getting data from an Oracle database.

I'm thinking about reinstalling Crystal from scratch, but I don't know if that'll help. Everything was working fine a week ago. Any ideas? Also, I ran the report manually from Crystal on that server and it ran and exported to PDF perfectly fine. I'm wondering if it has to do with the scheduled task that is running.

Thanks.

Quote:

---

Originally Posted by jayplus

I have an automated task that generates reports every couple of minutes as part of a data processing routine here and everything was working perfectly fine until last week.

The VB application generates reports and exports them to PDF. The process no longer works and luckily, the application does some logging as part of the process and I found this:

Error No: -2147190908
Description: Failed to export the report

So I'm trying to research why all of the sudden, this issue started and what I am reading online seems to think that it has to do with unregistered DLL files. The version of Crystal on the server is 8.5.0.217. The reports are also getting data from an Oracle database.

I'm thinking about reinstalling Crystal from scratch, but I don't know if that'll help. Everything was working fine a week ago. Any ideas? Also, I ran the report manually from Crystal on that server and it ran and exported to PDF perfectly fine. I'm wondering if it has to do with the scheduled task that is running.

Thanks.

---

Did you try and unregister/re-register the appropriate dll's?
Check out this hotfix. It worked for me and I am using 8.5.

http://support.businessobjects.com/c...win_en.zip.asp

Try this page

Business Object KB

Maybe here:
http://support.businessobjects.com/l...s/c2012282.asp
Or here:
http://support.businessobjects.com/l...s/c2008078.asp

Google is your friend :bigyello:

Thanks. You won't believe how much time I spent on Google. I may search Dogpile next, or Yahoo.

Anyway, which solution worked for you? The unregistering/reregistering DLL files or the application of the hotfix?

I'd like to try some of the fixes, but because the problem is occurring only in our production environment, I'll have to try these fixes directly to the production environment, which worries me a lot. I guess I can try the fixes in our test environment to make sure nothing breaks, but I won't know if they really fix the issue until I apply the fix to the production environment.

So which fix did you apply to fix the issue I'm running into?

Quote:

---

Originally Posted by jayplus

Thanks. You won't believe how much time I spent on Google. I may search Dogpile next, or Yahoo.

Anyway, which solution worked for you? The unregistering/reregistering DLL files or the application of the hotfix?

I'd like to try some of the fixes, but because the problem is occurring only in our production environment, I'll have to try these fixes directly to the production environment, which worries me a lot. I guess I can try the fixes in our test environment to make sure nothing breaks, but I won't know if they really fix the issue until I apply the fix to the production environment.

So which fix did you apply to fix the issue I'm running into?

---

Unregistering/Registering and then I got a hotfix from Business Objects as described above.

hth

So which fixed it? The unregistering/reregistering the DLL files? The hotfix? Or both? And why did you do both?

Quote:

---

Originally Posted by jayplus

So which fixed it? The unregistering/reregistering the DLL files? The hotfix? Or both? And why did you do both?

---

I did both because thats what the support person suggested. Whether it was one or the other I never did find out.

Just to document why I will be doing the same, is that support person from Business Objects? Also which one did you do first, the unregister/register DLL files or the hotfix?

Quote:

---

Originally Posted by jayplus

Just to document why I will be doing the same, is that support person from Business Objects? Also which one did you do first, the unregister/register DLL files or the hotfix?

---

Yes he was from Business Object because the company I used to work for had a service contract.
In your case though since you obviously do not have a contract, I'd try to register/unregister before trying the hotfix. I'd use that as a very last resort and make sure I had a backup in case the hotfix needed to be rolled back.

Anyways thats just my opinion.

Good luck and let us know how you fixed it (Cause I know you will :D )

I think we just did fix it, but we're doing more testing, but at least our initial results are promising. The unreg/reg DLL files and the hotfix didn't work, but applying Service Pack 3 did.

Thanks for all your help.