Edit the vmx and add this line if the VM uses a scsi-disk
scsi0:0.mode = "independent-nonpersistent"
or this if the VM uses an IDE-disk
ide0:0.mode = "independent-nonpersistent"
Techie bits-n-tips mainly on Microsoft Technologies -.NET, SharePoint, SQL Server, Design Patterns, RUP/Scrum techniques and other latest MS technologies
Edit the vmx and add this line if the VM uses a scsi-disk
scsi0:0.mode = "independent-nonpersistent"
or this if the VM uses an IDE-disk
ide0:0.mode = "independent-nonpersistent"
12.0.0.6535 MOSS 20071 or WSS 3.0 SP2 + December 09 cumulative Update (KB960010 + KB960011)
12.0.0.6524 MOSS 20071 or WSS 3.0 SP2 + 15th December Update (KB977027 + KB977026)
12.0.0.6520 MOSS 20071 or WSS 3.0 SP2 + October 09 cumulative Update (KB974989 + KB974988)
12.0.0.6514 MOSS 20071 or WSS 3.0 SP2 + August 09 cumulative Update (KB973400 + KB973399)
12.0.0.6510 MOSS 20071 or WSS 3.0 SP2 + June 09 cumulative Update (KB971538 + KB971537)
12.0.0.6504 MOSS 20071 or WSS 3.0 SP2 + April 09 cumulative Update (KB968850 + KB968851)
12.0.0.6421 MOSS 20071 or WSS 3.0 SP2 (KB953338 + KB953334) [Updated 1st Aug 09: SP2 download now includes the hotfix (KB971620) that corrects the activation issue more information on the Microsoft SharePoint team blog]
12.0.0.6341 MOSS 20071 or WSS 3.0 February 09 cumulative Update (KB961755 + KB961756)
12.0.0.6335 MOSS 20071 or WSS 3.0 December 08 cumulative Update (KB960010 + KB960011)
12.0.0.6331 MOSS 20071 or WSS 3.0 October 08 cumulative Update (KB957691 + KB957693,KB958567 and KB958569)
12.0.0.6327 MOSS 20071 or WSS 3.0 August 08 cumulative update (KB956056 & KB956057)
12.0.0.6318 MOSS 20071 or WSS 3.0 Infrastructure Update (KB951695 & KB951297)
12.0.0.6303 MOSS 20071 or WSS 3.0 post-SP1 hotfix (KB948945)
12.0.0.6301 MOSS 20071 or WSS 3.0 post-SP1 hotfix (KB941274)
12.0.0.6300 MOSS 20071 or WSS 3.0 post-SP1 hotfix (KB941422)
12.0.0.6219 MOSS 20071 or WSS 3.0 SP1
12.0.0.6039 MOSS 20071 or WSS 3.0 October public update
12.0.0.6036 MOSS 20071 or WSS 3.0 August 24, 07 hotfix package
12.0.0.4518 MOSS 20071 or WSS 3.0 RTM
12.0.0.4407 MOSS 20071 or WSS 3.0 Beta 2 TR
12.0.0.4017 MOSS 20071 or WSS 3.0 Beta 2
12.0.0.3111 Office 12 (PDC image - pre-beta) - This version of Office does not have a support link in the Add/Remove programs dialog box.
Recreating a Shared Service Provider
SSP and MySite is not working and displaying Page Cannot be displayed error. Previously It was working fine and suddenly it stopped working. Web application pool is working properly. When click on SharedServices1 it display the error “Page Cannot be displayed” same is happening with MySite.
Find out old Database name
Open Central Administration Site and click on Shared Services Administration. Go to SharedServices1–>Edit Properties. Copy the old content database name & search database name.
Create Dummy SSP
Open Central Administration Site and click on Shared Services Administration. Click on New SSP to create a new one.
Make default SSP
Click on Shared Services Administration–>Change Default SSP (from the Shared Services Administration) and choose your new SSP (SharedServices2).
Delete old SSP
Delete the original SSP (SharedServices1) by choosing delete from its context menu. DO NOT DELETE ITS ASSOCIATED DATABASES! This might take a second to complete.
Restore the SSP
Now we’re going to click on Restore SSP and restore the original SSP with a brand new Administration site. Name it SharedServices1 and fill out fields. Create a new web application and when it comes time to fill out the fields for Search Database and but this time fill out the two databases for the SSP. This will include the databases that we identified in step 1. This will ensure that you don’t lose all your data from the SSP like Search Content Sources, Excel Services Settings, Audiences, and BDC etc.
Delete Dummy SSP
Now we should have two working SSPs, SharedServices1 and SharedServices2. Click Change Default SSP and change it back to SharedServices1. After that delete SharedServices2 (this might take a while).
Now reboot the machine and check your SSP.