Re: WSS 3.0 question

Can you do a NET START and check for existing MSSQL$XXXX services? This will
tell you if your MSDE is working fine

"Barnabas" <gcsokai@xxxxxxxxx> wrote in message
news:0A907F55-EB89-4F81-A7DB-C91AF30919CB@xxxxxxxxxxxxxxxx
I do think the MSDE is corrupted, it can no longer connect to services, and
I cannot generate and do not receive reports anymore. Once I square this
away, I'll take a stab at WSS 3 again. At least WSS 2 is still working.
THanks for the help.


"Costas" <cpstechgroup@xxxxxxxxx> wrote in message
news:B2B32B85-09CB-4BC8-9F67-94786005490D@xxxxxxxxxxxxxxxx
MSDE has nothing to do with WSS 3.0 and it should remain installed on the
server because there are services that use it (such as Monitoring and
Reporting).

If you feel that by accident the MSDE configuration got corrupted you
have to reinstall it otherwise you will start having errors with the
services that use it. Even if you decide to install SQL Server, the MSDE
instance that is used by Monitoring and Reporting has to remain
installed.

Many things can go wrong during an upgrade. Sometimes it better to bring
everything to a point where you don't get any kind of errors and start
from the beginning.

Costas

"Barnabas" <gcsokai@xxxxxxxxx> wrote in message
news:B982260B-24C2-40BE-9AA1-4D0EC76F5E4B@xxxxxxxxxxxxxxxx
I followed the advise given in removing WSS 3.0 etc, but no use. Now when
reboot, the server is complaining that the SQL service(?) was tempered
with or corrupt.
As for the standalone insall - I followed the blog to the teeth (thanks
bass_player!). So next, I will probably reinstall/fix MSDE.
Altenatively, I may just instal the SQL server as I was going eventuall
use it anyway. Thanks for the tips, though Im still not sure what went
wrong.

-A

"Costas" <cpstechgroup@xxxxxxxxx> wrote in message
news:A5E159D3-4408-4D40-9A91-C0FBD51CDACD@xxxxxxxxxxxxxxxx
Indeed it was :)

Costas

"bass_player [SBS-MVP]" <bass_player@xxxxxxxx> wrote in message
news:%23QWZrtLrHHA.3380@xxxxxxxxxxxxxxxxxxxxxxx
During the installation, did you chose a Stand-alone server option?

Was that my blog? ;-)

"Costas" <cpstechgroup@xxxxxxxxx> wrote in message
news:F0659F49-55E3-4D16-BA44-E8688E494DD8@xxxxxxxxxxxxxxxx
Try the following steps:

a. Uninstall WSUS 3.0
b. Uninstalll WSS 3.0 (if it appears under the installed programs)
c. Goto 'Services' and see if there is an entry for
'MSSQL$Microsoft##SSEE' (this is the database that WSS 3.0 installs
and unfortunately does not uninstall when you remove WSS).
d. If the above database exist, remove it following the instructions
in the following link( http://bassplayerdoc.spaces.live.com/ ) . Look
for the April 09 entry
e. Reboot.
f. Check that under 'Services' there is no entry for
'MSSQL$Microsoft##SSEE'
g. Reinstall WSS 3.0

Hopefully that will fix it

Costas


"Barnabas" <gcsokai@xxxxxxxxx> wrote in message
news:9FBEC628-2139-473B-ABF1-43F1C43CD46E@xxxxxxxxxxxxxxxx
Ok, I uninstalled WSUS 3.0 and still getting the following in EV. I
reinstalled WSS 3.0 and the hotfix, rebooted but no go. Thanks for
the tips though.

Event Type: Error
Event Source: SharePoint Products and Technologies Configuration
Wizard
Event Category: None
Event ID: 104
Date: 6/11/2007
Time: 5:05: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
8c34450c-3f23-45aa-a249-e5e8f5f61001 does not exist in the
configuration store. The object may have been deleted by another
operation.
System.ArgumentException: The object with id
8c34450c-3f23-45aa-a249-e5e8f5f61001 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.

"Barnabas" <gcsokai@xxxxxxxxx> wrote in message
news:BB36E359-397E-4C7F-B45C-AD0F8B961BEE@xxxxxxxxxxxxxxxx
WSUS 3.0 is installed (uninstalling now per your recommendation),
not runing SBS 2003 R2, just plain 2003 Premium. SP2 is not
installed.


"Costas" <cpstechgroup@xxxxxxxxx> wrote in message
news:8E2C4E6C-A3EB-43D1-8F61-29AD1C57566E@xxxxxxxxxxxxxxxx
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: 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: WSS 3.0 question
    ... I followed the advise given in removing WSS 3.0 etc, ... the server is complaining that the SQL service(?) was tempered with or corrupt. ... I may just instal the SQL server as I was going eventuall use it anyway. ... If WSUS 3.0 is installed, I would suggest you uninstall it and then you install WSS 3.0. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS 3.0 question
    ... I'll take a stab at WSS 3 again. ... Even if you decide to install SQL Server, the MSDE instance that is used by Monitoring and Reporting has to remain installed. ... SharePoint Products and Technologies Configuration ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS 3.0 question
    ... Uninstalll WSS 3.0 ... Goto 'Services' and see if there is an entry for 'MSSQL$Microsoft##SSEE' (this is the database that WSS 3.0 installs and unfortunately does not uninstall when you remove WSS). ... 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. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQL Service Manager ##SSEE
    ... Upgrading the default SharePoint site to version 3.0 is not supported in SBS 2003. ... Here is the link to the document that describes how to install WSS 3.0 on SBS ... It is the default database that is using (Microsoft SQL Server Embedded Edition). ...
    (microsoft.public.windows.server.sbs)