Re: WSS3 on SBS install problems step 5 of Configuration Wizard.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Is this the first time you try to install WSS 3.0 on that box?

Did you installed it before and then uninstalled it? If that's the case, it's possible the instance of the database has to be manuall removed before the new installation

Costas

"Rickuk99" <rickuk999@xxxxxxxxx> wrote in message news:Ouvj0m6wHHA.4652@xxxxxxxxxxxxxxxxxxxxxxx
I am trying to install WSS3 onto an SBS server.

The SBS server is windows windows 2003 SP2 and already has WUS 3 install and running. I have followed the white paper for installing WSS3 onto SBS leaving WSS 2 in place and run the hotfix for SBS however the install fails, please see attached extract from log file

07/11/2007 11:18:53 9 ERR Task services has failed with an unknown exception
07/11/2007 11:18:53 9 ERR Exception: System.ArgumentException: The object with id e43c45d9-1342-4b3b-9a91-3c4c544c18b9 does not exist in the configuration store. The object may have been deleted by another operation.
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.DeleteObject(Guid id)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.DeleteObject(SPPersistedObject obj)
at Microsoft.SharePoint.Administration.SPPersistedObject.Delete()
at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.ProvisionDatabase()
at Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject)
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject)
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo)
at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()


There are other errors around the same message,

I also get these events in the application log,

SharePoint Products and Technologies Configuration Wizard error 3759
Database 'WSS_Search_SERVER' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' is not empty and does not match current database schema.


Relevant Pages

  • How to build a VAX/VMS emulator on Fedora Core 3 Linux
    ... make install the libpcap for ethernet support on VAX emulator ... Is the OpenVMS media ready to be mounted? ... * Do you want to install the MSGHLP database? ... Message from user AUDIT$SERVER on NEWBB ...
    (alt.os.linux.redhat)
  • Re: Need technique to programatically update back end structure / relationships
    ... Yes, that should work, Bob. ... Install the new one. ... > have the user rename the current production database (after taking a ... > final step of the installation process, I would ask the user to execute ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Error: Cannot find a valid Windows XP Embedded database installed
    ... Both the database and tools are Eval or Retail? ... Microsoft Windows XP Embedded Test Team ... Well, in fact it has a network connection, and it's working without any ... if I install everything in the same computer (tools and ...
    (microsoft.public.windowsxp.embedded)
  • Re: DBD::Informix -- Error Installing On Mac OSX
    ... the environment correctly, as long as the module reasonably clearly ... working Informix environment than to test for things that might not be ... use either the sysmaster database or the informix user to install ...
    (comp.databases.informix)
  • Re: User Rights Assignment - not available - Resolved
    ... Then copy the security file from the \windows\repair ... If none of that works I would try an upgrade/repair install ... shows user rights and use the Resource Kit command line tool NTrights to ... This operation may find that this database is corrupt ...
    (microsoft.public.windowsxp.security_admin)