RE: SPS WSS SQL 2000 same machine

"Fysh1" wrote:

<snip>
This error can be caused by one or more issues. The most common
issue, which is explained in Microsoft Knowledge Base Article #833183, is
that the MSSQL$SHAREPOINT SQL Service instance is not running. (The correction
is to set the service, start it through the services in the Administrative
Tools, and manually start it.)

I guess that is a pretty obvious thing to check. Why didn't I think of it? :)

Another common problem is that Windows SharePoint Services is
installed before SharePoint Portal Server, the configuration database, or
both are installed on the SQL Server Default instance.

I don't understand. You MUST install WSS before SPS. SPS will not install
without WSS aready installed. The order I install (learned from trial and
error) is:

1. Windows 2003
2. Windows 2003 SP1 (yours may be included on Windows 2003)
3. SQL Server (I use 2005, but I don't think there's a difference
install-wise)
4. SharePoint Portal Server 2003 (I believe this is where your error
happens)
5. Windows SharePoint Services Service Pack 2
6. SharePoint Portal Server 2003 Service Pack 2

Doing any one of these in any different order caused me problems. I don't
know how to insert a link to a thread here, but you can search for "Service
Packs and the Order of Installation" for my detailed rant. (Well, it made me
feel better!)

This problem can usually
can be corrected by removing the extensions from the site and running
the extension process again. However, when selecting the Database
options, select the SQL Default Instance (just the server name) instead of
the <server>\SHAREPOINT instance.

I looked up the article, but it is geared towards MSDE. Alos, I am using
the default (local) instance How do I remove the extensions in the second
solution suggested? I prohibited the extensions on the IIS and then allowed
them again, is this what they are talking about?

I think "removing the extensions" means removing (or un-extending) the
extended virtual server(s). One was extended automatically when you installed
WSS. You may or may not have extended others by hand. I have never figured
out how to "un-extend" a virtual server reliably -- I just reinstall WSS.

I believe the reference to 'SQL Default Instance" means the "Database
server" field on the "Specify Configuration Database Settings for MYSERVER"
page that appears after the SPS install wizard finishes (and where you're
having your problem, if I'm not mistaken). I also use the SQL default
instance, and I type just the name of the server here, since I had problems
when I typed DOMAIN\SERVER or attempted to use a named instance.

One last thing if I create a database in SQL Server 2000 and then during the
config database in the SharePoint Admin screen it will tell me that the
database already exist and then offers to delete it and recreate it, but it
does not recreate it only deletes it. So I am confused on why the program
can delete a database, but can not create a database even if I use myself and
with the domain\username and assign the correct permissions in SQL Server
2000.

If this confuses you, then you are well on your way to being a SharePoint
guru! If it didn't, I would be worried about you. I was stuck on this page
for days, and one thing I tried was creating a database first and then
attaching to it. Even following some web advice about scripts to run to
configure the db properly, I never got it to work. I think your best bet is
to create from scratch.

Oh, one more thing. Your SharePoint administrator account should be a member
of local groups STS_WPG and SPS_WPG.

Hope there's something here that triggers a fix.
Chris
.

Relevant Pages

  • RE: Backups have Shadow Copy Problems
    ... and restarted the server. ... suggested and changed the recovery model to simple on the one database called ... I understand the issue to be: the backup task failed ... You back up data from a volume that contains a Microsoft SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Self Contained SQL Database
    ... Server, so it can work with the full version or SQL Express, MSDE, etc... ... way to just include a database file in my installation, ... Any great install products that can manage a self contained ...
    (microsoft.public.sqlserver.msde)
  • Re: upsizing to sql 2005
    ... the word SERVER in it, ... You can access to the database by multiple means (Access, ... and how does it update the SQL database with the new records in Access? ... Query Name: Arcadia - ARC ...
    (microsoft.public.access.queries)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... What's the error message you see when installing SQL? ... the easier way is to restore the server from recent backup. ... Screen shot of the error when you install SQL 2005 Workgroup edition. ... <The server-based applications that were running fine are: McAFee EPO, ...
    (microsoft.public.windows.server.sbs)