What happen to OWS.CSS in WSS V3.0 site?

I have a custom develop menu control that pick up styles from OWS.CSS style sheet. I have noticed when I upgrade the WSS V2.0 site to WSS V3.0, the styles were missing from the menu control. Even the old style OWS style sheet from

C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\LAYOUTS\1033\STYLES

Copied to new location

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\STYLES

OWS style sheet is above location with all the styles, but the site is not picking it up!!!!!

There is a new style sheet in above directory called CORE.CSS. I have to copy al my custom style class to CORE.CSS file to get this working properly.

I still haven’t got to the bottom of this situation and don’t know why there is new CORE.CSS style sheet. I am sure I will find out and blog about it soon….

“Rename your object or delete the existing object”. Error

I hit another problem while I was doing the gradual upgrade. The site upgrade process was complaining that the site is already exists and stope the site upgrade process before get completed successfully with following error message.

An object of the type Microsoft.SharePoint.Administration.SPWebApplication named "RegionalServices_Pair" already exists under the parent Microsoft.SharePoint.Administration.SPWebService named "". Rename your object or delete the existing object.

I couldn’t find the object mentioned in the error message through STSADM tool. I was trying to delete it or trying to access the site through STSADM command with out any luck.

Finally I figure out the way to fix this problem through the Central Administration pages

• Open the Central Administration site
• Go to Application Manager
• Select Delete Web Application link
• Select the site mention in your error message
• Choose to delete the Content database and the IIS Web site
• Navigate to Site content upgrade status under Operation tab
• Rerun the site upgrade

Method not found: Error

Method not found: System.String Microsoft.SharePoint.Administration.
SPVirtualServerConfig.get_DefaultZoneOutgoingUrl().

I am currently working through a SharePoint 2003 upgrade to MOSS 2007 using In-Place Upgrade. I was running the Prescan tool as part of the migration and got the following error message.

The command ran

Prescan.exe /c presupgradescanconfig.xml /all

The Error Message

2/05/2007 11:12:51 Error: Exception while looping through virtual servers.
02/05/2007 11:12:51 System.MissingMethodException: Method not found: System.String Microsoft.SharePoint.Administration.SPVirtualServerConfig.get_DefaultZoneOutgoingUrl().
at Microsoft.SharePoint.PreupgradeReport.Scan.ScanOneVirtualServer(SPVirtualServer curVS)
at Microsoft.SharePoint.PreupgradeReport.Scan.Run(StringCollection argsList)
02/05/2007 11:12:51 Scan finished with failure.
02/05/2007 11:12:51 ===============================Logs==================
=============
02/05/2007 11:12:51 Log file: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\PreupgradeReport_633062707654456096_Log.txt
02/05/2007 11:12:51 Summary file: C:\DOCUME~1\ADMINI~1\
LOCALS~1\Temp\PreupgradeReport_633062707654456096
_Summary.xml
02/05/2007 11:12:51 ==============================Totals==================
============

Solution

This is due to not having service packs installed in my existing SharePoint Portal Server 2003 environments.

Windows SharePoint Services Service Pack 2 (SP2)
http://www.microsoft.com/downloads/details.aspx?FamilyId=9C552114-DC9A-43EE-9281-B080B7C280B4&displaylang=en

SharePoint Portal Server 2003 Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyId=171DC9A7-B4BA-4759-BD64-6B7D851A97EF&displaylang=en