Error 27763. Failed to open existing Office Communications Server database.
Hi!
I'm trying to install the standard edition of Microsoft Communications Server 2007. I think the server might have had this sever installed previously and then uninstalled.
When I run through the deployment setup I get to the point where the setup attempts to the create configuration database. An error occurs telling me: "Failed to open existing Office Communications Server database."
Is there any way to remove the entry for the existing database (I want a clean install, not using the exisiting database)?
I can't seem to find out where the setup is looking for the existing database (ip/fqdn)?
Below is an extract of the installation log file.
Any help greatly appreciated!
I'm trying to install the standard edition of Microsoft Communications Server 2007. I think the server might have had this sever installed previously and then uninstalled.
When I run through the deployment setup I get to the point where the setup attempts to the create configuration database. An error occurs telling me: "Failed to open existing Office Communications Server database."
Is there any way to remove the entry for the existing database (I want a clean install, not using the exisiting database)?
I can't seem to find out where the setup is looking for the existing database (ip/fqdn)?
Below is an extract of the installation log file.
Any help greatly appreciated!
Action 08:55:20: CA_CheckSQLServiceReady. Checking whether SQL service is ready to accept database connections
MSI (s) (94:1C) [08:55:20:031]: Executing op: CustomActionSchedule(Action=CA_CheckSQLServiceReady,ActionType=1089,Source=BinaryData,Target=CheckSQLServiceReady,)
MSI (s) (94:08) [08:55:20:046]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIF3A.tmp, Entrypoint: CheckSQLServiceReady
Info 29038. Error 0x80070002 (The system cannot find the file specified) trying to check whether SQL service is ready to accept connections
MSI (s) (94:1C) [08:55:20:062]: Executing op: ActionStart(Name=CA_CreateConfigDB,Description=Creating Configuration database. This can take a while to complete depending upon the computer configuration.,)
Action 08:55:20: CA_CreateConfigDB. Creating Configuration database. This can take a while to complete depending upon the computer configuration.
MSI (s) (94:1C) [08:55:20:062]: Executing op: CustomActionSchedule(Action=CA_CreateConfigDB,ActionType=1025,Source=BinaryData,Target=ExecuteCommand,CustomActionData=CScript.exe //U //Nologo PoolCfgDBSetup.wsf /clean /dbsize:32 /dbpath:"D:\LC Data\" /logsize:32 /logpath:"D:\LC Log\" /lcsvcgroup:"domain\RTC Server Local Group;domain\RTC Component Local Group" /srvadmingrp:"domain\RTC Local Administrators" /usradmingrp:"domain\RTC Local User Administrators;domain\RTC Local Read-only Administrators" /serverrole:"HS" /verbose|C:\WINDOWS\system32\CScript.exe|C:\Program Files\Common Files\Microsoft Office Communications Server 2007\DBSetup\|1)
MSI (s) (94:C8) [08:55:20:093]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIF3B.tmp, Entrypoint: ExecuteCommand
MSI (c) (1C:24) [08:55:22:859]: Note: 1: 2731 2: 0
Error 27763. Failed to open existing Office Communications Server database.
MSI (s) (94!70) [08:55:27:406]: Product: Microsoft Office Communications Server 2007, Standard Edition Server -- Error 27763. Failed to open existing Office Communications Server database.
Action ended 08:55:27: InstallFinalize. Return value 2.
The easiest way to do it is to uninstall SQL express from that server. Then go into program files and delete any folders that reference Micrsoft SQL. Then try reinstalling again
ASKER
OK, I guess I should uninstall SQL Server 2005 then? I think my WSS 3.0 Sharepoint sites use Windows Internal Database, My Project Server created an "Office Servers" SQL server, I guess this server instance will have to be uninstalled too (when I start the uninstall I have to remove three servers: Office Server, Backup Exec and RTC)?
As mentioned i know the Office Server is used by MS Project Server 2007 and the Backup Exec was created by Symantec Backup Exec but what is the RTC database used for?
As mentioned i know the Office Server is used by MS Project Server 2007 and the Backup Exec was created by Symantec Backup Exec but what is the RTC database used for?
If other services that run on that server I would not uninstall them. OCS is really meant to be installed on a standalone box. Even with you install std edition which installs SQL it should not reside with other services. Even if OCS install doesn;t use SQL and SQL is installed I have seen the error you have received.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your suggestions!
I've now removed the RTC database. This time the SQL setup started when I tried to deploy OCS. SQL server installs just fine, creates a new database instance (server\RTC) and proceeds to deploy OCS.
However, I get the same error when setup attempts to create the configuration database. It seems to me that there's still some entries left from the previous OCS install.
Is there any way to clear all registry entries concerning the old OCS installation?
I've now removed the RTC database. This time the SQL setup started when I tried to deploy OCS. SQL server installs just fine, creates a new database instance (server\RTC) and proceeds to deploy OCS.
However, I get the same error when setup attempts to create the configuration database. It seems to me that there's still some entries left from the previous OCS install.
Is there any way to clear all registry entries concerning the old OCS installation?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you remove the old database files?
Removing the RTC database using the management studio does not remove the actual files, you should remove them manually after you remove them from the management studio.
Removing the RTC database using the management studio does not remove the actual files, you should remove them manually after you remove them from the management studio.