Prev: Error #50071: Unable to connect to the database <ConfigurationDB>
Next: Permissions Inherited Despite Being Set Otherwise
From: waxhead on 5 May 2007 01:09
Take a look at this page for resuming upgrade.

http://technet2.microsoft.com/windowsserver/WSS/en/library/b72b7ebc-2916-4aec-83e6-b7a6776d1c241033.mspx?mfr=true


"Dave Slinn" wrote:

> From my experience - and I had to perform the upgrade a few times because of
> issues I encountered with the upgrade - the only way to do this was
> uninstall Version 3, reinstall version 2, restore the site from a backup
> using STSADM and then rerun the upgrade for Version 3.
>
> Not a trivial task...
>
>
> "Naga" <Naga(a)discussions.microsoft.com> wrote in message
> news:2FC9C668-9959-497D-A514-72BB82FA9D9B(a)microsoft.com...
> > Hi,
> >
> > By seeing this thread, I had a doubt on im-place migration.
> >
> > 1) Upgrade Database
> > 2) Upgrade Searches
> > 3) Upgrade User Profiles
> > 4) Upgrade site collections
> >
> > If the Upgrade fails in middle of any of the above in-place upgrade steps,
> > how to revert back to previous version of the Sharepoint server.
> > Is it only by uninstalling the installed components and re-installing? Are
> > there any processes/automated scripts to revert back to previous version?
> >
> > Regards
> > Naga
> >
> > "Bryce White" wrote:
> >
> >> Thanks, Dave! Very nice of you to dig this for me.
> >>
> >> Happy Holidays,
> >> Bryce
> >>
> >>
> >> "Dave Slinn" wrote:
> >>
> >> > I just had a thought. Why don't I just cut and paste the info here:
> >> >
> >> > Frustrated because WSS v3-Beta sometimes leaves an orphaned install
> >> > Embedded
> >> > Edition of SQL 2005 (SSEE) on your machine ?
> >> >
> >> > Now you can get rid of it ;)
> >> >
> >> > a.. Start Registry Editor, and then locate the following registry
> >> > key:
> >> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
> >> > a..
> >> > In the left pane, click each GUID. For each GUID that you click, look
> >> > for a
> >> > display name in the right pane that matches "Microsoft SQL 2005
> >> > embedded
> >> > Edition.". When you see a display name that matches the name, copy the
> >> > value
> >> > of the Key named "UninstallString"
> >> > a.. Open a Command-Window (Start->run->cmd)
> >> > a.. Paste the Copied string.
> >> > a.. Append " CALLERID=OCSETUP.EXE" eg "MsiExec.exe
> >> > /X{BDD79957-5801-4A2D-B09E-852E7FA64D01} CALLERID=OCSETUP.EXE"
> >> > a.. There you go Don't forget to reboot.
> >> >
> >> >
> >> > "Bryce White" <BryceWhite(a)discussions.microsoft.com> wrote in message
> >> > news:E0510AD8-8496-4FAC-9F69-EA9CA70E44A8(a)microsoft.com...
> >> > > Thanks for posting this because I'm in the same boat. However, I
> >> > > can't
> >> > > find
> >> > > any articles about removing SQL Embedded. Do you remember where you
> >> > > found
> >> > > it?
> >> > >
> >> > > Thx,
> >> > > Bryce
> >> > >
> >> > >
> >> > > "Dave Slinn" wrote:
> >> > >
> >> > >> Update - 5 hrs later. Success! I have succesfully upgraded our
> >> > >> test
> >> > >> sharepoint site to version 3 and everything seems to be hunky dory
> >> > >> (so
> >> > >> far).
> >> > >> Nothing like doing something 3 times to become really good at it.
> >> > >> :)
> >> > >>
> >> > >> Now, I'll describe the steps I have had to take to get to this
> >> > >> point.
> >> > >> First
> >> > >> off, I had to uninstall version 3 of WSS, which didn't want to go
> >> > >> willingly.
> >> > >> I would click "Remove" in the Add/Remove control panel application,
> >> > >> and
> >> > >> it
> >> > >> would begin the uninstall, but the uninstall window would just
> >> > >> disappear
> >> > >> at
> >> > >> about 20% complete on the progress bar. It never actually
> >> > >> uninstalled
> >> > >> anything, and remained as an entry in the Add/Remove applet. Then,
> >> > >> I
> >> > >> found
> >> > >> an obscure blog entry describing how to remove the SQL 2005 Embedded
> >> > >> Edition, which I followed and managed to remove it. Once gone, I
> >> > >> reattempted to uninstall Windows Sharepoint Services 3.0, and now it
> >> > >> completed without any problems. Once both SQL and WSS3 were
> >> > >> removed, I
> >> > >> ran
> >> > >> the WSS2 uninstall and there weren't any problems with that.
> >> > >>
> >> > >> Now that I had a "sharepoint-free" system, I reinstall WSS2,
> >> > >> installed
> >> > >> service pack 2 for it, and then ran the restore of the backup I took
> >> > >> before
> >> > >> this long journey began. Once I was able to get the original site
> >> > >> back
> >> > >> up
> >> > >> and running, and went to the top-level site and attempted to delete
> >> > >> the
> >> > >> sub-web that caused an issue during the first upgrade. I got a
> >> > >> really
> >> > >> weird
> >> > >> error message "Site not found" or something like that. Then, I
> >> > >> tried
> >> > >> view
> >> > >> all the Sites and Collections, and got another error message, "File
> >> > >> not
> >> > >> found". I opened up SQL manager, viewed the contents of the "Webs"
> >> > >> table,
> >> > >> and sure enough, that problem web entry contained a "NULL" value in
> >> > >> the
> >> > >> title field. I ended up just deleting that record out of the Web
> >> > >> table.
> >> > >> I
> >> > >> went back to the Sites and Collections manager of the top-level
> >> > >> site, and
> >> > >> this time it came up without any problems. My guess is that I had
> >> > >> removed a
> >> > >> "problematic" web from the database, so I figured I'd give the
> >> > >> upgrade
> >> > >> one
> >> > >> more shot.
> >> > >>
> >> > >> I launched the WSS3 install, went through all the steps, ran the
> >> > >> prescan
> >> > >> tool and the config tools, just as I had before, and again, there
> >> > >> were no
> >> > >> problems. Once the Central Administrator launched and displayed the
> >> > >> Upgrade
> >> > >> Status page, everything was running smoothly. After a short time,
> >> > >> it
> >> > >> reported back that it completed and there were no jobs scheduled.
> >> > >> This
> >> > >> was
> >> > >> different than the other times, where the In-Place upgrade Failed
> >> > >> and it
> >> > >> reported to look at the Upgrade log. I finalized the upgrade and
> >> > >> viewed
> >> > >> the
> >> > >> new site, and everything looks good.
> >> > >>
> >> > >> Hopefully this detailed description will help other individuals in
> >> > >> their
> >> > >> upgrades of WSS3.
> >> > >>
> >> > >> Thanks to all!
> >> > >>
> >> > >> "Dave Slinn" <CougarDave(a)noemail.noemail> wrote in message
> >> > >> news:OJrOt5ADHHA.1224(a)TK2MSFTNGP04.phx.gbl...
> >> > >> >I have a attempted to upgrade our current sharepoint install (WSS 2
> >> > >> >w/SP2)
> >> > >> > with WSS 3.0 using the In-place upgrade. This is a fairly simple
> >> > >> > deployment, since there is only one sharepoint server, using the
> >> > >> > MSDE
> >> > >> > instance (SHAREPOINT) of SQL 2000. It contains about 10 webs, all
> >> > >> > with
> >> > >> > a
> >> > >> > single content database.
> >> > >> >
> >> > >> > I have tried to run the in-place upgrade twice now, and get the
> >> > >> > same
> >> > >> > error
> >> > >> > both times. The prescan tool reported no issues (included in
> >> > >> > attached
> >> > >> > file: logs.zip) and the config tool
> >> > >> > finished without any problems. The web-based
> >> > >> > central admin starts without problem and the Upgrade Status page
> >> > >> > displays
> >> > >> > that it is running. Eventually, it fails with a message to check
> >> > >> > the
> >> > >> > Upgrade Log (see file: Upgrade.log in logs.zip file). The lines
> >> > >> > of
> >> > >> > note
> >> > >> > are:
> >> > >> >
> >> > >> > [SPContentDatabaseSequence] [ERROR] [11/18/2006 3:42:19 PM]:
> >> > >> > Action
> >> > >> > 3.0.12.4000 of
> >> > >> > Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence
> >> > >> > failed.
> >> > >> > [SPContentDatabaseSequence] [ERROR] [11/18/2006 3:42:19 PM]:
> >> > >> > Cannot
> >> > >> > insert
> >> > >> > the value NULL into column 'ScopeId', table
> >> > >> > 'STS_test.gmsnet_37252947.dbo.Webs'; column does not allow nulls.
> >> > >> > UPDATE
> >> > >> > fails.
> >> > >> > The statement has been terminated.
> >> > >> > [SPContentDatabaseSequence] [ERROR] [11/18/2006 3:42:19 PM]: at
> >> > >> > System.Data.SqlClient.SqlConnection.OnError(SqlException
> >> > >> > exception,
> >> > >> > Boolean
> >> > >> > breakConnection)
> >> > >> >
> >> > >> > After doing a bit of digging, it appears there is one entry in the
> >> > >> > Webs
> >> > >> > table that has a NULL value. Given that this column (ScopeID) is
> >> > >> > new
> >> > >> > to
> >> > >> > V3,
> >> > >> > it must be a problem during the upgrade of the database schema
> >> > >> > that
> >> > >> > prevents
> >> > >> > a uniqueidentifier from getting generated for this row.
> >> > >> >
> >> > >> > I uninstalled WSS 3 and WSS 2, reinstalled version 2 and then
> >> > >> > restore
> >> > >> > the
> >> > >> > site prior to attempting the upgrade. I then re-tried the upgrade
> >> > >> > to
> >> > >> > version 3.0, but the same error occurred. I will, once again,
> >> > >> > roll
> >> > >> > back
> >> > >> > to
> >> > >> > the previous version of WSS and restore our original v2 site.
> >> > >> >
> >> > >> > One other item of note - the first attempt, I had upgrade the SQL
> >> > >> > MSDE
> >> > >> > instance to 2005, and the WSS upgrade had left that instance
> >> > >> > alone.
> >> > >> > However, after uninstalling WSS versions 3 and 2, I also
> >> > >> > uninstalled
> >> > >> > the
> >> > >> > 2005 db instance, and reinstalled WSS v2, which recreated an MSDE
> >> > >> > 2000
> >> > >> > instance. I left this one and the WSS v3 upgrade seems to have
> >> > >> > moved
> >> > >> > the
> >> > >> > databases out of there into a new SQL 2005 Embedded Edition
> >> > >> > install,
> >> > >> > called
> >> > >> > MICROSOFT##SSEE, which I can't seem to connect to with SQL
> >> > >> > Management
> >> > >> > Studio
> >> > >> > for some reason. It also left the 2000 instance, with nothing in
> >> > >> > it.
> >> > >> >
> >> > >> > I will attempt one more upgrade, only this time I will configure
> >> > >> > v2 to
> >> > >> > use
> >> > >> > my own SQL instance, rather than MSDE, and it will be SQL 2005. I
> >> > >> > will
> >> > >> > post
> >> > >> > the status once I have tried it.
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >>
> >> > >>
> >> > >>
> >> >
> >> >
> >> >
>
>
>
 | 
Pages: 1
Prev: Error #50071: Unable to connect to the database <ConfigurationDB>
Next: Permissions Inherited Despite Being Set Otherwise