Re: WSS 3.0 question

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: Cluster will not fail over.
    ... > As far as the TCP/IP issue goes, you had to rebuild the cluster and were ... > able to restore the master database. ... > a cluster installation you'll have to revisit. ... >> This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)
  • Re: installing help for sql 2005
    ... you have database users that are not mapped correctly to logins. ... SQL Server Documentation Team ... installation help with snap shots because i installed the sql server ... remote connections are disabled by default. ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL SERVER 2008 Express + SP1
    ... I installed the SQLXPR_X64, and before I attempted the SP1, SQLEXPRESS database was 64bit for the configuration, better yet the repair do work anymore because SP1 changed them somehow to 32 and the original install was 64 ... If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. ... And regarding your sql server installation, ...
    (microsoft.public.sqlserver.setup)
  • Re: End User Requirements
    ... running MS-Access and not needing the full access installation, ... you are considering running a local copy of SQL server database. ...
    (microsoft.public.sqlserver.programming)
  • Re: Cluster will not fail over.
    ... As far as the TCP/IP issue goes, you had to rebuild the cluster and were not ... able to restore the master database. ... the entire installation configuration just as if nothing was running on it. ... > This worked bringing up the sql server in minimal mode. ...
    (microsoft.public.sqlserver.clustering)