Unable to connect - incorrect logon parameters

[janchan]

Hi, i am getting the following error whle trying to run a report. this report was running sucessfully until last friday and i have been getting this error from last night. i removed and re-created the DB2 database connection. the connection tested successfully. i opened the report from the BO server and entered the same pwd and it runs successfully. i am not sure what else i am missing. i even tried removing this report and re-exporting it from development. please help!! we are using BOE - XI. i went to the link in the error and could not find the .rpt file


Error in File C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Data\procSched\m3ngdm01.reportjobserver\~tmp13442ddaf701a69.rpt: Unable to connect: incorrect log on parameters.

 

[synapsevampire]

You need to clarify what is failing, you say there's an error and also state that you can run it...

A report can't be exported from development, so that's confusing as well.

Crystal Reports alllows you to Save to (or overwrite) within a CE folder, and CE allows you to Add in new reports.

The error seems descriptive enough, however your posting appears to contradict itself, or doesn't explain what you are doing when the report fails.

Do you mean that a scheduled report is failing, or?

-k

 

[janchan]

yes, a scheduled report is failing. it waits for a scheduled event, but its been failing from last night.when i looked at the failed instance, i got the above message. i tried to run it on-demand by clicking on run now, and i still get the same error.

 

[Durango122]

hi
you can check looks like there something wrong with your odbc

http://support.businessobjects.com/...x_ver=&index_lang=&indexq2=&indexq3=&indexq4=

good luck

Durango122

 

[synapsevampire]

Sounds straightforward to me, something has changed about that connectivity, what it is will require some detective work.

I often place Crystal Reports itself on the CRS box because it gives better error messages, and you can confirm the connectivity.

-k

 

[janchan]

I think the problem was with our network. the windows AD logon was locking me out every 5 minutes.