Re: WSS 3.0 question

Thanks for the continued help.

It fails at Step 5 of the configuration wizard, gives the error: Failed to Register Sharepoint Services
This time, this is what Event Viewer shows:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3759
Date: 6/11/2007
Time: 2:45:15 PM
User: N/A
Computer: SBSServer
Description:
Database 'WSS_Search_SBSServer on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' is not empty and does not match current database schema.

the Second Event Viewer error is:
Event Type: Error
Event Source: SharePoint Products and Technologies Configuration Wizard
Event Category: None
Event ID: 104
Date: 6/11/2007
Time: 2:45:16 PM
User: N/A
Computer: SBSServer
Description:
Failed to register SharePoint services.
An exception of type System.ArgumentException was thrown. Additional exception information: The object with id 45510848-24f9-4d1d-9841-1d77691156b2 does not exist in the configuration store. The object may have been deleted by another operation.
System.ArgumentException: The object with id 45510848-24f9-4d1d-9841-1d77691156b2 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()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


"Costas" <cpstechgroup@xxxxxxxxx> wrote in message news:98044A28-EC5E-48BD-A0FB-9EB2BBD33E9D@xxxxxxxxxxxxxxxx
When do you get the error? During installation or during configuration? Configuration follows installation. If it's during installation at what point does it fails? (look at the screen and see which step it fails at). Did you accept the default parameters or did you provide any custom ones?

Costas


"Barnabas" <gcsokai@xxxxxxxxx> wrote in message news:1CD8B9F3-D04F-4235-B1BA-9DA3F7EE3906@xxxxxxxxxxxxxxxx


Thanks for the help. I found the following article referencing hotfix KB 934790 which I applied http://blogs.technet.com/sbs/archive/2007/05/22/trouble-installing-sharepoint-3-0-after-wsus-3-0.aspx. THe installation still fails, but with a different error. It appears it is rejecting the username/password which is the domain admin user account.
Does this help?
-A

Here what Event Viewer logged when the install failed after the hotfix:
Event Type: Failure Audit
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (4)
Event ID: 18456
Date: 6/11/2007
Time: 2:07:02 PM
User: Domainname\username
Computer: SBSServer
Description:
Login failed for user 'Domainname\username'. [CLIENT: <named pipe>]

#2
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3760
Date: 6/11/2007
Time: 2:07:04 PM
User: N/A
Computer: SBSServer
Description:
SQL Database 'WSS_Search_SBSServer on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below.
Cannot open database "WSS_Search_SBSServer" requested by the login. The login failed.
Login failed for user 'Domainname\username'.



"Costas" <cpstechgroup@xxxxxxxxx> wrote in message news:CE61D386-1EC9-419B-AAE5-B85396CDEBD9@xxxxxxxxxxxxxxxx
Something must have gone wrong during installation. By default WSS 3.0 installs SQL Server Embeded Edition which is similar to SQL Server Express edition.

Costas


"Barnabas" <gcsokai@xxxxxxxxx> wrote in message news:AE2ECCE8-B5DD-4F87-8951-50A9C62C7A0A@xxxxxxxxxxxxxxxx
I have SBS 2003 Premium, but no SQL Server installed as I had no need for it. I went to install WSS 3.0 following the MS documentation, followed the no upgrade option etc..
However when building the database, it fails referencing SQL xyz.
I assume that this likely because I don't have SQL server installed, but then again, WSS 2.0 works just with the MSSQL Desktop Engine. If I do need SQL server installed that's fine but the documentation did not state that.

THanks,
-A




.

Relevant Pages

  • Re: SharePoint Services 3.0 unable to display content
    ... looking at the database table information, ... Microsoft Windows SharePoint Services 2.0 ... Can we asume you mean SQL Server 2005? ... The upgrade identified that there was a previous ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Cannot Enable full-text search and index component
    ... WSS FAQ at http://wss.collutions.com ... >I receive the following error from the Windows SharePoint Services: ... On your computer running SQL Server, open a command prompt and run the ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: SharePoint Services 3.0 unable to display content
    ... Microsoft Windows SharePoint Services 2.0 ... Can we asume you mean SQL Server 2005? ... The upgrade identified that there was a previous ...
    (microsoft.public.sharepoint.windowsservices)
  • Cannot Enable full-text search and index component
    ... I receive the following error from the Windows SharePoint Services: ... Administration site when I attempt to enable full-text search and index ... I upgraded my WSS installation to a SQL Server 2000 and am attempting ...
    (microsoft.public.sharepoint.windowsservices)
Loading