Re: WSS 3.0 question

Is WSUS 3.0 installed? Are you on SBS 2003 R2? Did you install SP2?

I should have asked all these questions earlier in order to get an undertanding of your environment. If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0 (as the blog indicates). The error you get is on named pipes, a protocol for interprocess communication. I haven't seen named pipes errors since the days I was developing database applications in the mid-90s so I'm not sure what exactly causes it. But let's take it one step at a time.

Let me know if removing WSUS 3.0 and reinstalling WSS 3.0 solves the problem

Costas



"Barnabas" <gcsokai@xxxxxxxxx> wrote in message news:80C5A6CE-D4A8-47D1-A34C-519AA6A5212A@xxxxxxxxxxxxxxxx
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: Installing SP4 on SQL 2000
    ... SQL Server 2000 SP3a, x86 ... It seems like there is issue on your install. ... MCITP: Database Administrator ... "David G" wrote: ...
    (microsoft.public.sqlserver.setup)
  • Re: WSS 3.0 question
    ... SharePoint Products and Technologies Configuration Wizard ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ... It fails at Step 5 of the configuration wizard, gives the error: Failed to Register Sharepoint Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Installing SP4 on SQL 2000
    ... As you said this is a fresh install, so it should not be an issue. ... If you are installing are installing a fresh version of SQL Server 2000, ... MCITP: Database Administrator ... "David G" wrote: ...
    (microsoft.public.sqlserver.setup)
  • Re: Why do I need to restart the SQL service?
    ... > I use Wise Installation utility to install MSDE 2000A. ... what I do within the app is: ... Check to see if the database exists. ... > SQL Server does not exist or access denied. ...
    (microsoft.public.sqlserver.msde)
  • Re: SQL SERVER 2008 Express + SP1
    ... Again there are three service pack setups which are provided by Microsoft. ... Are u sure you are using correct version for your install? ... DB Dev SQL Server 2005 ... Script level upgrade for database 'master' failed because upgrade step ...
    (microsoft.public.sqlserver.setup)