Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Logon information is incorrect or incomplete CE10

Status
Not open for further replies.
Dec 22, 2004
2
US
I have a set of reports created in CR 8.5 and 9 that were subsequently modified and saved in CR 10. They are hosted on a CE 10 web server running IIS. The problem is that I can open the reports and run them in CR but when I try to view them through the browser on the report server or a client machine I get the error "Unable to retrieve Object.
The database logon information for this report is either incomplete or incorrect."
The Data Source is ODBC System DSN connecting to an Access DB stored on a network share (mapped drive). The Access Database logon parameters are input into CE under process/database. All CE services are running on domain accounts with rights to the DB. The Access DB is part of a Replica set distributed to other locations and updated via scripted synchroniization. I have scrutinized many threads in this forum with similar errors and have tried many of the posted suggestions. I have had no success thus far. I am at my wits end. HELP!
 
I have come up with a solution for my problem. In troubleshooting Last night I copied the Access DB to the machine that CE 10 runs on. I created a new system DSN pointing to the DB and reset the data source location in CR to point to that DSN and it worked. So, for some reason it does not like the network drive. I know UNC is supposed to work, so I tried that and it gave me a litany of errors and wouldn't even run in CR. So as a work around I created a new share on the CE server, dumped the Access DB in it, than renamed the original network location of the DB. I then set up a DFS link to the CE Server from the old Network location, so that my users that open the DB for data entry didn't have to map a new drive. I know this is more of a work around than a solution, but I am happy that this is working now. Perhaps others who encounter this problem will find it easy to apply the same fix.

Cheers!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top