WSS 2.0 -> WSS 3.0 installation Problem

Discussion in 'Windows Small Business Server' started by Mike in Nebraska, Mar 26, 2008.

  1. Running this on SBS 2003 Premium SP2.
    ================
    I am trying to install WSS 3.0 over WSS 2.0 as an upgrade, following the
    instructions for SBS, but it fails while trying to create the configuration
    database. The error is:
    03/25/2008 13:49:35 8 INF debugMessage for task configdb is
    An exception of type System.Data.SqlClient.SqlException was thrown.
    Additional exception information: Could not find stored procedure
    'dbo.proc_getObjectsByClass'.
    System.Data.SqlClient.SqlException: Could not find stored procedure
    'dbo.proc_getObjectsByClass'.
    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
    Boolean breakConnection)
    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
    exception, Boolean breakConnection)
    at
    System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
    stateObj)
    at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
    SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
    bulkCopyHandler, TdsParserStateObject stateObj)
    at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
    at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds,
    RunBehavior runBehavior, String resetOptionsString)
    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior
    cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
    cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method,
    DbAsyncResult result)
    at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior
    cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
    behavior, String method)
    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
    behavior)
    at Microsoft.SharePoint.Utilities.SqlSession.ExecuteReader(SqlCommand
    command, CommandBehavior behavior)
    at
    Microsoft.SharePoint.Administration.SPConfigurationDatabase.FetchId(QualifiedObjectName
    qName)
    at
    Microsoft.SharePoint.Administration.SPConfigurationDatabase.GetObject(String
    name, Guid parentId, Type type)
    at
    Microsoft.SharePoint.Administration.SPConfigurationDatabase.Initialize(SqlConnectionStringBuilder
    connectionString, Boolean enableCaching)
    at
    Microsoft.SharePoint.Administration.SPConfigurationDatabase.RegisterDefaultDatabaseServices
    SqlConnectionStringBuilder connectionString)
    at
    Microsoft.SharePoint.Administration.SPConfigurationDatabase.Provision(SqlConnectionStringBuilder
    connectionString)
    at
    Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder
    configurationDatabase, SqlConnectionStringBuilder
    administrationContentDatabase, IdentityType identityType, String farmUser,
    SecureString farmPassword)
    at
    Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
    at
    Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
    at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
    =========
    Nothing of note in the Application log; any ideas on how to correct this?

    Mike Webb
    Platte River Whooping Crane Maintenance Trust, Inc.
    a conservation non-profit
     
    Mike in Nebraska, Mar 26, 2008
    #1
    1. Advertisements

  2. Mike,
    You shouldn't be getting those errors however

    Well the instructions for SBS Tell you NOT to do an Upgrade of WSS 2.0 to
    3.0
    You need to do a side by side installation.

    Installing Windows SharePoint Services 3.0 on a Server Running Windows Small
    Business Server 2003
    http://technet2.microsoft.com/Windo...1421-4052-acc2-d2898afc0d951033.mspx?mfr=true

    Are those the Instructions you are following?

    Russ
    --

    SBITS.Biz
    Microsoft Gold Certified Partner
    Microsoft Certified Small Business Specialist.
    MCP, MCPS, MCNPS, (MCP-SBS)
    North America Remote SBS2003 Support - http://www.SBITS.Biz
    Information on Small Business Server 2008 - http://www.sbs2008.com
    Information on Essentials Business Server - http://www.ebs2008.com



    -
     
    Russ \(SBITS.Biz\), Mar 26, 2008
    #2
    1. Advertisements

  3. Mike in Nebraska

    David Lozzi Guest

    Hi Mike,

    I've done a few SharePoint upgrades on SBS boxes. Well, installs of WSS3.
    You cannot upgrade the WSS2 on SBS because the monitoring and management
    tools on SBS require WSS2. What you can do is install WSS3 next to WSS2, the
    migrate the database. This works great each time. There should be plenty of
    whitepapers on migrating from WSS2 to WSS3. Let me know if you need more
    assistance.

    Thanks,

    David Lozzi
    Delphi Technology Solutions
    www.delphi-ts.com
     
    David Lozzi, Mar 26, 2008
    #3
  4. Okay, I've uninstalled WSS 3.0, re-booted, did a repair on WSS2.0,
    re-booted. Re-applied SQL 2000 SP4, rebooted, treied to re-install WSS 3.0
    and get the same error, about step 9 or 10 of the Configuration Wizard
    process.

    Any ideas out there?
    Mike
     
    Mike in Nebraska, Mar 27, 2008
    #4
  5. Got the answer on a Sharepoint Forum site. I needed to install WSS 3.0
    w/SP1 as part of it. Installation went smooth once I had the right
    executable.

    Mike
     
    Mike in Nebraska, Mar 29, 2008
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.