- 02 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Pharos Database Service fails to start with Event log Error: Caught a general error with message 'Cannot open database requested in login 'pharos'. Login fails.
- Updated on 02 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
When I attempt to start the Pharos Database Service, it fails to start and I receive the following error in the event log:
Event Type: Error
Event Source: PSDatabaseSvr
Event Category: None
Event ID: 4000
Date: 6/15/2006
Time: 2:47:48 PM
User: N/A
Computer: SHIPPRINT02
Description:
Caught a general error with message '[CConnectionAllocator::CreateAndOpenConnection] COM -- ADO error: Unspecified error. Description: Cannot open database requested in login 'pharos'. Login fails.'
Event Type: Error
Event Source: PSDatabaseSvr
Event Category: None
Event ID: 4000
Date: 6/15/2006
Time: 2:47:48 PM
User: N/A
Computer: SHIPPRINT02
Description:
Caught a general error with message 'Cannot open database requested in login 'pharos'. Login fails.'
There are two possible reasons why this may appear:
SQL Database Account Name or Password Change
OR
The Installation of the Principal Service included a password with special characters
SQL Database Account Name or Password Change Resolution Instructions
An update to the SQL Account name or Password, if it is not also changed in the Pharos Registry entries, will cause the Database Service to fail on startup. Customers should re-check the SQL Username and Password on the Database Server. If this does not resolve the issue, the Pharos account may no longer have access or dbo permissions on the Pharos Database. Please call your Pharos Reseller or Pharos Technical Support for instructions on how to set DBO account permissions to the Pharos Database user. Reference Knowledge Base Article: 859 and the instructions on setting the Pharos user to assume DBO permissions
Special Character Password Resolution Instructions
During the installation of the Principal Server, a special character or space may have been included in the initial admin user password setup. To correct the problem you must do the following:
Open Enterprise Manager from Microsoft Sequel Server.
In the tools menu select the query analyzer.
Once open select the Pharos Database from the database drop down at the top of the query window.
Run the following query.
exec user_insert_jit 'admin'
Click the green execute button.
Run the following query.
update people
set access_level = 'Administrator'
where user_id = 2
Manually start the Pharos Database Server and log on to the Pharos Administrator.
Change the password for the newly created admin account.
Restart the server.
This will resolve the issue of a default user not being present in the Pharos Database and the Pharos Database Server failing as a result.