PEStartPrintJob : Cannot open SQL server Error...

[bessebo]

At one point during the day I got the above message with every report that was scheduled. Seagate Info was running perfectly up until the time I started getting this message. I rebooted the Info APS server and Seagate Info started perfectly but I was still getting failed instances. There was nothing in the Event Viewer on the Info APS machine related to a problem with Seagate Info. We ended up repairing and compacting the CINFO.MDB and then the problem went away. I thought that the CINFO.MDB was only associated with security, users, etc. Does it make sense that repairing and compacting it corrected the problem?

thanks in advance,
Bessebo

 

[rhinok]

This message means that Seagate Info cannot connect to the database server (Oracle, SQL Server, etc...). Generally, I'd perform the following troubleshooting first:[ol][li]If a single report failed with this message, I'd doublecheck that the database password was:

[ul][li]entered when scheduled[/li][li]entered correctly when scheduled[/li][/ul][/li]
[li]If this occurred on every single report, I'd find out if the database was down. This is the most likely cause in your scenario[/li][/ol]Only after the above troubleshooting, would I look to the Info System Database as the possible culprit. It is possible that the database became corrupt, however, it is unlikely. It is more probable that your database became available around the same time, coincidentally, that you finished compacting and repairing your Info System Database.

 

[bessebo]

Our database, which is our production ERP database, was accessible and was being used by our entire user community entering sales orders, shipping product, etc at the same time that we were getting these Seagate Info errors with reports. There was nothing wrong with our ERP database. Every report was getting this same error. Once the CINFO.MDB database was repaired and compacted the reports ran perfectly.

 

[AndrewBaines]

How big is your CINFO.mdb? If you've got more than a few users you need to migrate it to a proper database - mdb's are slow and limited to 2GB in size.
Every instance has a reference in the system db, when the instance is deleted on the desktop, the entry in the db is deleted but the space is not regained until the system database is compacted. This is a 'feature' of Access, not Info. The CINFO.mdb is only for small systems or test sites.