RE: WSS install locked into MSDE DB - Can not install for SQL Serv

From: shawnk (shawnk_at_discussions.microsoft.com)
Date: 02/02/05 

Date: Wed, 2 Feb 2005 09:53:04 -0800

Jim,

We did set up a new 'WSS_admin' account on the server with
membership in Groups Administrators (for now), IIS_WPG, STS_WPG.

We then gave the WSS_Admin account SQL roles
   - Security Administrators
   - Database Creators
For the MASTER database (to be changed after STS_CONFIG is created)

We downloded the SharePoint Configuration Analyzer [sca.exe] and
verifed the following items which initially confused us.

1. Althought we change the Configuration Application pool several times
to our handrolled IIS application pool the WSS service continued to use
its original STSAppPool1_2 (on our machine) application pool. This is
why we were getting the 'error code 1801'.

2. We set the Identity of the STSAppPool1_2 (the orginal app pool for the
WSS worker process) to WSS_Admin (again - our handrolled account). This
removed
the error code 1801. Now we are able to create databases using the WSS Web
interface BUT they appear to be MSDE databases and not SQL Server databases.

3. All the ahem 'new' configuration databases are being created in directory.

   Directory of C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data

      02/02/2005 12:11 AM 1,179,648 STS_Config_WSS.mdf
      02/02/2005 12:11 AM 1,048,576 STS_Config_WSS_log.LDF

Since these database DO NOT come up in SQL Server Enterprise Manager we
assume (only for the moment) that they exist in MSDE. We want to verify
MSDE databases but have no tool right now to look at the MSDE environment.
We are using sca.exe as we move along to verify everything. We are also
using stsadmn.exe utility as well.

4. It appears (from the WSS documentation in *.CHM format - we have the
latest)
that the WSS WEB interface only creates WMSDE databases. You (evidentally)
must
create SQL databases with stdadm.exe utility to create SQL Server databases
using;

stsadm -o setconfigdb -ds <database server> -dn <database name>
-du <database user> -dp <database user password>

We are not sure about -ds <database server> input. Do we use;

-ds MY-COMPUTER-NAME

or

-ds MY-COMPUTER-NAME\SharePoint

This is where we are at right now.

5. We are doing this is 'real project time' along with our other tasks
including
downloading WSS articles, tools, etc. Our key problem was not finding
STS_CONFIG
(our name for our project is STS_CONFIG_WSS) in the SQL Server Enterprise
Manager.
The text 'SQL Server Database Name' on the WSS Admin Web page 'Set
Configuration Database Server'
has caused us no end of grief and pain.

6. Since we want to understand WSS configuration issues prior to the install
of BizTalk server
we will try to move the default application pool for the WSS service to our
own 'handrolled'
application pool.

Just to note - we use some tools that can take prefix/postfix tags in
various log files
and config files to generate reports (awk/grep/etc). This is the reason for
the renaming
of the default configuration artifacts.

I'll let you know how it goes in trying to create the new SQL Server version
of STS_CONFIG
via the stsadm.exe utility.

Thanks again for all of your help and I hope this post becomes helpful to
others.

PS.

Should we use

-ds MY-COMPUTER-NAME?

or

-ds MY-COMPUTER-NAME\SharePoint?

We are going to go with the later (-ds MY-COMPUTER-NAME\SharePoint) unless
directed otherwise. We expect the new STS_CONFIG database to come up in
SQL Server Enterprise Manager along with NorthWind and other SQL Server
databases.

"Jim Buyens" wrote:

> The WSS application pool account needs the Security Administrators and
> Database Creators rols in SQL Server. Have you granted those?
>
> Are you following the instructions at
>
> http://www.microsoft.com/
> resources/documentation/wss/2/all/adminguide/en-us/stsc02.mspx
>
> Jim Buyens
> Microsoft MVP
> http://www.interlacken.com
> Author of:
> *----------------------------------------------------
> |\---------------------------------------------------
> || Microsoft Windows SharePoint Services Inside Out
> || Microsoft Office FrontPage 2003 Inside Out
> ||---------------------------------------------------
> || Web Database Development Step by Step .NET Edition
> || Microsoft FrontPage Version 2002 Inside Out
> || Faster Smarter Beginning Programming
> || (All from Microsoft Press)
> |/---------------------------------------------------
> *----------------------------------------------------
>
>
> "shawnk" wrote:
>
> > Jim,
> >
> > I looked through the documentation, used the admin page for configuring a
> > new configuration database and kept getting the following error message;
> >
> > Followed the SQL server set up instructions and got this
> >
> > Input
> >
> > 1 Database Server
> > MY-COMPUTER\Sharepoint
> >
> > 2 SQL Server Database Name
> > STS_Config
> >
> > 3 Database Connection Type
> > Use Windows Authentication
> >
> > Output
> >
> > 1 Database 'STS_Config' already exists. (Error code: 1801).
> >
> > Note that this error code is for the WSS Configuration database and not for
> > a Context database. I also downloaded the Sharepoint Configuration Analyzer
> > as well to check the config as I go along.
> >
> > I'll go through the documentation regarding error code 1801, try the fixes
> > and see if that solves our problem. As far as we know no STS_CONFIG database
> > is in SQL Server. Note the 'SQL Server Database Name' above indicates its
> > targeting SQL Server. We saw some permission and account problems noted in
> > the documentation so we will look into the account settings.
> >
> > Thanks much for you input so far.
> >
> >
> >
> > The STS_CONFIG file
> >
> > "Jim Buyens" wrote:
> >
> > > Right. The remotesql=yes option sets the default Type Of Installation choice
> > > to Server Farm, and then Server Farm installs the WSS software with NO
> > > databases. The setup program does, however, launch a series of Web pages that
> > > provide options for you to create configuration and content databases exactly
> > > where you want them.
> > >
> > > If for some reason setupsts.exe isn't displaying those Web pages, you can
> > > browse the WSS Central Administration site and configure your databases from
> > > there. First you create a configuration database, and then you extend a
> > > virtual server and create a content database.
> > >
> > > Jim Buyens
> > > Microsoft MVP
> > > http://www.interlacken.com
> > > Author of:
> > > *----------------------------------------------------
> > > |\---------------------------------------------------
> > > || Microsoft Windows SharePoint Services Inside Out
> > > || Microsoft Office FrontPage 2003 Inside Out
> > > ||---------------------------------------------------
> > > || Web Database Development Step by Step .NET Edition
> > > || Microsoft FrontPage Version 2002 Inside Out
> > > || Faster Smarter Beginning Programming
> > > || (All from Microsoft Press)
> > > |/---------------------------------------------------
> > > *----------------------------------------------------
> > >
> > >
> > > "shawnk" wrote:
> > >
> > > > I've uninstalled/reinstalled WSS 2.0 (with SP1) serveral times. As per the
> > > > *.chm admin file for WSS I'm trying to get WSS to install with a ST_CONFIG
> > > > database created in SQL Server on a WIN 2003 Server machine. The command
> > > > sequence for installing WSS to use SQL Server is;
> > > >
> > > > setupsts.exe remotesql=yes
> > > >
> > > > With the following dialog input (during the install)
> > > >
> > > > 8. On the Type of Installation page, click Server Farm, and then click Next.
> > > >
> > > > 9. On the Summary page, verify that only Windows SharePoint Services will be
> > > > installed, and then click Install.
> > > >
> > > > On my installs (on Win 2003 Server) the install goes right to the summary
> > > > page and never prompts for the 'Server Farm' option. In addition to this it
> > > > never creates the ST_CONFIG in SQL Server.
> > > >
> > > > Can someone help me out with the problem. Its holding up an effort to review
> > > > Biztalk server.
> > > >
> > > > Thanks in advance.
> > > >
> > > > Shawn
> > > >
> > > >
> > > >
> > > >

Relevant Pages

  • Config for OLTP system
    ... extrenal disks fo the 60GByte database server. ... IBM Informix Dynamic Server Configuration Parameters ... # BUFFSIZE - OnLine no longer supports this configuration parameter. ...
    (comp.databases.informix)
  • Re: How to Replicate an SQL Server 2000 Database
    ... actual server name) enterprise manager should associate the database with the ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: SQL 2005 Best Practice vs SQL 2000: Application Files Separate from data (and log) files
    ... I have had quite a number of clients that used a SAN for a database server and suffered significant performance problems because their underlying SAN infrastructure was a huge stripe across many drives. ... By application files I mean the binn folder which contains the sql server executable among other things. ...
    (microsoft.public.sqlserver.setup)
  • Re: Access 2007 adp and SQL Server Express
    ... tab SQL Native Client Configuration / Alias in the SQL Server Configuration ... When configuring the server with the SQL Server Configuration Manager, ... Database Engine in the SQL Server 2005 Surface Area Configuration utility. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... Check the database connection information and make sure that the database ... Uninstall SQL Server; ... Reinstall Monitoring and Sharepoint and make sure they work; ...
    (microsoft.public.windows.server.sbs)