Jack of all that is Microsoft, Master of None

September 22, 2006

MOSS 2007 Beta 2 Technical Refresh Install Fail – Roll Back… Sort of!

First, I must preface this blog post by saying that if you follow what I write, I take absolutely no responsibility for your environment getting all screwed up (even though technically you’re following what I wrote because you’re environment is all screwed up).  You better make sure you backup everything possible! This is a beta product, and it should be installed in a development environment, so that if need be, you can perform crazy things like what I’m about to write…

So about 12 hours ago, I started a MOSS 2007 B2 TR upgrade on a standalone server.  Everything went exactly as planned, until I ran the ‘SharePoint Products & Technologies Configuration Wizard’.  The wizard took a long time to run, and eventually it got to step 8 of 9… but then boom!  All hell broke out… I got an error and the damn setup couldn’t continue.  So I tried to run the Wizard again, thinking that maybe the error was a fluke, and this time, I got the following error:

Exception: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPConfigurationDatabase Name=SharePoint_Config Parent=SPDatabaseServiceInstance is being updated by WEB\myaccountname, in the psconfigui process, on machine SERVERNAMEHERE.

I did some searches, and I couldn’t find anything that really helped with this error.  My thougth was that maybe the installer thought that the database was in use by another user, and couldn’t gain exclusive access to perform the upgrade.  I tried rebooting, dropping all db connections, changing dbo… you name it.  And yet every time, I kept getting this error.

So I did some digging further through the logs, and I found a line mentioning that an upgrade was ‘already in progress’… but I wasn’t running any upgrades at this time – I just had a botched MOSS Beta 2 server with some portion of the TR installed.  So the thought that came across my mind was that somewhere on the system, the Wizard was looking at a version number, and saw 12.0.0.4407 – the TR version number, and therefore thought that the upgrade was running or already installed.  So I did something dangerous – dug through the registry and changed any references to this version number back to the previous version (12.0.0.4017)… and then in the config db’s Versions table, deleted the record that was inserted by the installer also referencing the newer version number.  I rebooted the server, and ran the Config Wizard again – and wow, what a suprise – it still thought the upgrade was running.

So now I was not a happy camper… what am I going to do… I’ve got what was a good Beta 2 server now completely broken (I did test opening every site and got all kinds of errors), and TR is there partially installed – and can’t be rolled back.  So I took it upon myself to perform the following to try and get Beta 2 back up and running.  Just to preface this, my thought was that I could uninstall / reinstall Beta 2 and overwrite everything to get back to some type of usable state:

1. Restored all of the Beta 2 pre-upgrade databases to SQL (Because I had no idea what state the databases were in after the failed TR upgrade attempt).
2. Uninstalled .NET Framework 3.0
3. Uninstalled & reinstalled IIS
4. Repaired the .NET Framework 2.0 (because IIS wasn’t showing .NET 2.0 as an available web server extension)
5. Attempted to uninstall SharePoint Server 2007 from Add/Remove program. This was great – when I clicked Remove & told it to uninstall, the uninstall screen would completely disappear after about 10 seconds… nothing was touched!  Craziness!

So I was still up the creek without a paddle… until I did the following:

1.  Deleted the folder C:\Program Files\Common Files\Microsoft Shared\SERVER12
2.  Went back into add/remove programs and removed SharePoint – only it’s that ‘fake remove’ – where it removes it from the list because it can’t find the program files.
3.  Stopped / disabled all of the Services related to SharePoint & Office.
4.  Rebooted & prayed.

After the reboot, I installed the Windows Workflow Foundation Beta 2, then ran the MOSS 2007 Beta 2 installer… and voila… it worked!  It actually went through the entire installer & configuration wizard without any issues.  So I then reconfigured everything through Central Admin, and then recreated my Web Applications… but when I recreated them, I pointed them to the already existing Beta 2 databases that I had previously restored.  And each and every time I created the new web app and attached it to the correct content database – it worked!

So… the moral of the story is… this worked for me, and I wanted to throw it out there for you.  If you’re completely stuck with a half-installed TR upgrade and don’t know what to do, maybe I’ve given you some ideas.  Just one other thing – it’s almost 6am here on the East Coast and I haven’t slept… so I will review & update this post when I’m functional & can think.

I wish you good luck, and hope you do not run into anything like the problems I hit.  But if you did, know that you are not alone!

-Chris

Advertisements

6 Comments »

  1. Thanks ! Same problem, same solution ! 🙂

    Comment by Von — October 13, 2006 @ 9:59 am

  2. to remove MOSS after a failed Beta 2 TR install:

    Using add remove programs remove the following in this order –

    1. .Net Framework 3.0
    2. SQL Server main service (I forget exactly what this was called)
    3. SQL Analysis Services
    4. SQL Native Client
    5. SQL Setup files
    6. Report Redistributable
    7. MSXML 6

    Sharepoint Server will now uninstall.

    Next, Uninstall IIS from the windows components

    Finally, use MSICUU2.exe to clean up all Sharepoint and SQL uninstall entries.

    Your machine should now be clean and allow for a Beta 2 reinstall.

    Now for the final question – how does one install the TR???

    Comment by Blair Allen Stark — October 18, 2006 @ 1:01 am

  3. whoo-hooo got it now!!!

    DO NOT RUN THE CONFIGURATION WIZARD AT THE END OF THE REFRESH! UNCHECK THE BOX BEFORE CLICKING CLOSE

    INSTEAD, RUN THE COMMAND LINE VERSION OF THE CONFIG TOOL WITH THE FORCE OPTION:

    “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin\psconfig.exe” -cmd upgrade –force

    GO THROUGH THE ERROR FIXES OUTLINED IN THE KNOWN ISSUES SECTION OF:

    http://technet2.microsoft.com/Office/en-us/library/f49862ab-e067-4723-bb90-7eb1182c65ce1033.mspx?mfr=true

    I HAD TO RUN THE FARM TOPOLOGY WEB CONTROL REPLACE. I ALSO HAD TO REBUILD THE SEARCH DATABASE.

    After this, you can continue on your merry way, or if like me you understand the process and want to have non default names for SSP/Apps, Sharepoint now uninstalls cleanly via Add remove programs.

    Cheers!

    Comment by Blair Allen Stark — October 18, 2006 @ 1:55 pm

  4. Here you go. . . complete walk through:

    1. create a windows 2003 server
    2. configure IIS
    3. Install .Net framework 2.0
    4. Edit IIS Web extensions to allow ASP.NET 2.0
    5. Run all updates to your server
    6. create a local domain user, add to BUILTIN\Administrators (I did this to allow other users to easily administer the Sharepoint Server, if need be)
    7. log off and log in as user created in step 6
    8. install Windows Workflow Foundation Runtime Components Beta 2_2(EN) for x86.exe
    9. install Sharepoint 2007 Server Beta 2 using defaults
    10. At the end of the install, leave the checkbox checked and close, this will kick off the configuration wizard. Let that run (It takes a good bit of time)
    11. Open the Sharepoint 3.0 Sharepoint Administration Site and Create a new Web Application
    12. Using Add/Remove Programs Uninstall Windows Workflow Foundation
    13. Install DotNet version 3.0.4506.3 or later
    14. Install the WSS Beta 2 Technical Release Refresh (WSSv3b2tr-kb000000-x86-fullfile-en-us.exe). You can safely ignore the non-error messages.
    15. Verify these folder permissions and states:

    C:\Program Files\Microsoft Office Servers\12.0\
    \WSS_WPG: Read & Execute, List, Read
    \WSS_ADMIN_WPG: Full Control
    \Administrators: Full Control
    SYSTEM: Full Control
    Users: Read & Execute, List, Read

    C:\Program Files\Microsoft Office Servers\12.0\WebServices
    click advanced and check “Allow Inheritable permissions. . . ”

    C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root
    NETWORK SERVICE: Read & Execute, List and Read
    Users: Read & Execute, List and Read
    click advanced and check “Allow Inheritable permissions. . . ” and “Replace permission entries”

    16. Install the Server Portal Beta 2 Technical Release Refresh (officeserver2007b2tr-kb000000-x86-fullfile-en-us.exe)
    NOTE: DO NOT RUN THE SHAREPOINT PRODUCTS AND TECHNOLOGIES CONFIGURATION WIZARD AT THE END OF THIS REFRESH –
    CLICK CANCEL AND THEN CLICK YES TO EXIT THE WIZARD
    17. Open a command prompt window and execute the following:

    cd “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN”
    psconfig.exe -cmd upgrade -force

    this will take a little while

    18. from start ->Control Panel|Adminstrative Tools, run Component Services.
    Drill down to Components Services|Computers|My Computer|DCOM Config.
    Find IIS WAMREG admin Service,
    right click and select properties.
    on the security tab select customize for “Launch and Activation Permissions” and click Edit.
    Add NT Authority\Network Service and allow ‘Local Launch’ and ‘Local Activation’.
    Click Ok
    Click Ok

    repeat for OSearch and SPSearch

    close Component Services

    For the most part, the refresh is complete, but here we had a couple of problems that were easily fixed.
    I will outline the particular issues we had, but bear in mind, your mileage may vary!!!

    PROBLEM: Web Part Error in SharePoint 3.0 Central Administration
    When browsing the SharePoint 3.0 Central Administration site, the Web Farm Topology Web Control fails to load.
    To resolve this issue, reset the Farm Topology Web Part by doing the following:
    1. On the Site Actions menu, click Edit Page.
    2. On the Farm Topology Web Part, on the toolbar, click Edit, and then click Delete.
    3. In the Left Web Part Zone, click Add a Web Part.
    4. In the Add Web Parts to Left dialog box, select the check box next to the Farm Topology Web Part, and then click Add.
    This resets the Web Part to its proper state.

    PROBLEM: SPAdmin not started
    Application Event log reported SPADmin not running
    1. Open services, right click “Windows SharePoint Services Administration” and select properties
    2. Change Startup to “automatic” and click “Apply”
    3. Click start and close services

    PROBLEM: Multiple Errors regarding Search Services reproted in Application Event Log
    The Search Service database needs to be rebuilt. to fix:
    1. from a command prompt execute:
    “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\stsadm.exe” -o spsearch -action stop
    2. Open Central Sharepoint Administrator and Navigate to the Search Settings page on the SSP home page.
    3. Click Reset all crawled content.
    4. Click OK.
    5. Start Office SharePoint Server Search by using the Services on Server page.

    Comment by Blair Allen Stark — October 18, 2006 @ 5:14 pm

  5. Hi guys,

    I had to stop all SQL services, SP services, stoped all the SharePoint sites & have managed to uninstall successfully.

    Comment by Rany — November 29, 2007 @ 11:55 pm

  6. 3aThank’s.5i I compleatly agree with last post. bva
    ламинированный паркет 1c

    Comment by ламинат — August 25, 2008 @ 2:33 am


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Blog at WordPress.com.

%d bloggers like this: