Crystal reports viewer error in XI: Unable to connect:

[ramkrish11]

Hi,

I have a report in the Enterprise XI Server which I schedule to run. It gives me a Success status after about 15 minutes. When I click on the instance to view it, it gives me the following error

Crystal Report Viewer

Error in File ReportName.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 1005 ]

Unable to retrieve Object.
Error in File ReportName.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 1005 ]

User trying to view has FullControl on the Folder and Object.

I am using a Oracle Server connection to Oracle 9i database.

Has anyone encountered this error before ?

Thanks
Ram

 

[techie2]

Did you try to run this report from Designer. If possible, run it from the Enterprise XI Server.

Open the file straight from Input repository path, verify teh DB / Dependecy Check, save it and run again from BOE XI and see what happens.

 

[ramkrish11]

thanks.

The report runs fine in Enterprise. It is when we try to view it, that I get the above error message.

Also, this report has Sub Reports.

Ram.

 

[kskid]

Have you tried running it in CMC using the Preview button? If you are being prompted for a database logon then click to the process tab and complete the database section.

You might also check to see if the username used to start up the CrystalViewer service has administrative rights

 

[ramkrish11]

kskid,

Crystalviewer is running under a username that has admin rights. From CMC when I tried Preview, it asked for parameter and went to retrieve rows but I guess this is at the main report level, which does not have an issue.

thanks guys for the suggestions.

 

[Ridyen]

Did you ever find a true resolution to this problem? I have this same error off and on and cannot seem to find a way to solve it other than chaning the db connection from OLE DB to ODBC. I don't want to put DSNs on my Crystal Enterprise server so I don't consider this a solution.

 

[jyoti05]

I had a server name with a '_' in it . I was told to use same link and with localhost instead of servername. That resolved my problem..