Publication failing with error Unable to connect: incorrect log on parameters. (FBE60502)

[Former Member]

Hi,

we are publishing the crystal reports for multiple BO users which are under a single BO group.

For few users we are getting below error,

Scheduling document job "<report name>" (ID: report id) failed: Error in File ~tmp123.rpt:

Unable to connect: incorrect log on parameters.

Details:  [Database Vendor Code: 3135 ]

(FBE60502)

For same user it is failing for the first run and it is succeeding in the second  or third run.

So what could be the issue and how to debug this

[former_member619182]

Hi All ,

We are facing same issue . Publication fails in first attempt and runs in second attempt .

Can someone tell us what is the issue with this and resolution for the same

[former_member182521]

Could you please share your environment details?

[Former Member]

We are using BO 3.1 SP5

Crystal reports -2008

Oracle is the Database

Let me know if you need any more information.

The publication is failing intermittently, for the first time if it fails then if we run again then it is successful.

How to debug this?

Thanks for reply

[former_member191664]

The scheduled job failure due to "Failed to retrieve data from the database. Details: [Database Vendor Code: 3135 ]" error, which is ORA-03135: connection lost contact Oracle error, should contact your Oracle DBA team and IT networking team to find out why Oracle connection is lost at the time when the Publication job ran. It means the connection to your Oracle reporting database was lost or disconnected.

Regards,

Jin-Chong

[Former Member]

Thanks,

We understood Ora 3135 error but why it giving incorrect logon credentials message as well is the question...?

[former_member191664]

Your Publication seems to have Crystal Report as its SOURCE report, can you please check the Properties of this Publication and look for "Database Logon" of that Crystal Report?

Update the Database user and/or password.

Regards,

Jin-Chong

[Former Member]

Yeah. They are correct and it is failing randomly. It fails for the first time by giving this error but if we re run the same publication without any changes then it will run successfully. I think this is a  bug

[Former Member]

Hi, Anyone has any clue on this error?

please reply me.

Thanks