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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to connect erro

Status
Not open for further replies.

ShortyA

MIS
Feb 20, 2002
363
CH
Hi,
I am using CE 9 on Windows 2003 Server running against SQL Server.

Any reports that are migrated for a single SQL datasource always fail when run. I have run them via Schedule to see if it was the Report Job Server. They failed with :
Code:
Status: Failed 
Printer: The instance is not printed. 
External Destination: None 
Creation Time: 8/17/2005 9:06:08 AM 
Start Time: 8/17/2005 9:06:08 AM 
End Time: 8/17/2005 9:06:08 AM 
Server Used: MyServerName.report 
Error Message: Unable to connect: incorrect log on parameters. File D:\Crystal Decisions\Enterprise9\Data\procSched\MyServerName.report\~tmp15d03f5ff409b50.rpt.
When I run the reports using View On Demand I keep getting prompted for logon information to the database even though there are no subreports. I have also run the reports via the CMC to see if it was the CSP code. However, this also fails.

Does anyone have any thoughts as all of the existing reports run both as scheduled instances and on demand?

Thanks for your assistance.
ShortyA
 
Hi,
The usual suspect:
Are the CE servers running under an account that has access/permissions to the Database location?




[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Odd one this. They are all running under the local system account which should be fine as I am not exporting the reports anywhere beyond the CE server itself (the output FRS). I changed the account on the Report Job Server to use an account with local admin and they run fine. Oddly enough I didn't need to change the account on the Page Server.

Anyway, I would have thought that the Local System Account would have had sufficient privileges to run reports. I will delve deeper to try and find out why this account wasn't sufficient.

ShortyA
 
Hi,
It is not the report that needs the admin rights, it is the database that demands it - the file system has to allow read/write access to the database's location..The servers are the ones that access that location, so they need permission to do so..



[profile]

To Paraphrase:"The Help you get is proportional to the Help you give.."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top