TOP SUPPORT ISSUES [remember as a Microsoft partner you get access to all of these resources, log into the Partner web site, into the Support section.
Please keep in mind, I've just put these here for Google purposes and to showcase what level of support you get, it's much better to get CSS support for such issues.
ALWAYS, WHEN IN DOUBT...CALL FOR SUPPORT
How to - reinstall config database, reinstall WSS, without removing content database
Problem Symptom
After applying Small Business Server 2003 SP1, the service MSSQL$SHAREPOINT stops immediately after starting it manually. http://companyweb displays "cannot connect to the config database"
Resolution
Get a new configuration database in place by doing the following.
1.Run the stsadm.exe command to back up the current http://companyweb:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN\stsadm.exe -o
backup -url http://companyweb -filename
c:\backups\companyweb.dat -overwrite
2. Go into http://localhost:8081 and Remove WSS from companyweb, without
deleting the content databases:
1) Virtual Server Configuration à Configure Virtual Server Settings, and
then choose Companyweb.
2) Choose 'Remove Windows SharePoint Services from virtual Server' under
'Virtual Server Management'.
3) Select 'Remove without deleting content databases', and then click OK.
3. Set the Configuration database server and change the name of
configuration database to STS_Config2:
1) Get back to the main page of 'Central Administration', and then click
'Set configuration database server' under 'Server Configuration'.
2) Change the 'SQL Server database name' to 'STS_Config2', and then click
OK.
4. Extend and create a content database:
1) Get back to the main page of 'Central Administration', and then click
'Extend or upgrade virtual server' under 'Virtual Server Configuration'.
2) Click to choose Companyweb under 'Virtual Server List'.
3) Click 'Extend and create a content database' under 'Provisioning
Options'.
5. Go to http://companyweb and choose the blank site template.
6.Restore the companyweb using stsadm.exe: C:\Program Files\Common
Files\Microsoft Shared\web server
extensions\60\BIN\stsadm.exe -o restore -url http://companyweb -filename
c:\backups\companyweb.dat - overwrite
How to - Reinstall Companyweb after the SBS 2003 SP1 setup
Problem Description
After SBS 2003 SP1 installation, one uninstalls the Companyweb by using the
'Remove' feature in SBS Integrated setup; when they try to reinstall the Intranet component through 'SBS Integrated Setup', they are prompted to insert the CD 3: Insert Windows Small Business Server 2003 Disc 3 or point to location where Windows Small Business Server Setup files may be found.
However, after the original SBS CD3 is inserted and 'OK' is clicked, the
wizard then gives the error: The drive contains a disc for Windows Small Business Server 2003 with no service packs. When the prompt appears, insert a disc for Windows Small Business Server 2003 with Service Pack 1.
Since the Companyweb (Intranet) installation part is in the SBS SP1 CD2,
The installation cannot proceed.
Resolution
I. Please DO NOT uninstall/reinstall WSS/Companyweb in the first place,
instead, we should try to figure out why the SP1 failed to install and give valid suggestions.
II. If you have to reinstall WSS as the last resort and you run into the
problem described below, you just need to change the value of 'isrunfromweb' to '2', under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer. That will make
the SBS Integrated setup program recognize the original SBS RTM CD2.
How To - Troubleshoot the issue that Backup doesn't work after the
installation of SBS 2003 SP1
Problem Description
We've seen some issues that the Backup fails after the installation of SBS
2003 SP1, the problem symptom is like the following:
1. SBS Backup fails with event 5634.
2. Backup log may be blank or not.
3. Backup did succeed before the installation of SBS 2003 SP1.
The problem could be caused by any of the following:
· Driver not compatible with Windows 2003 SP1.
· RSM database corruption.
· Backup tape needs to be cleaned.
Suggestion
1. Can the backup be successfully performed by Ntbackup (utilizing the BKS
file created by the wizard)?
2. Disable the Exchange writer by editing the registry under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
MSExchangeIS\ParametersSystem:
http://support.microsoft.com/?kbid=838183 , does the backup work?
3. Clean the tape, and then go to RSM to mark the tape as 'Clean'. Can the
backup run successfully then?
We've seen some issues that the Windows service pack 1 does not recognize
the media until the tape drive was "cleaned" (or marked as clean).
4. Uninstall the tape drive and remove it from the libraries, and then scan
the computer for the hardware changes. Once the hardware is detected, reinstall the latest driver.
5. Check if there's an updated driver and firmware for the device, if so,
apply it.
6. Rebuild the RSM database by calling product support serivces.
7. Can you successfully access the Backup snap-in in the SBS Management
console, if not, repair the backup web page by using the steps outlined in
http://support.microsoft.com/?kbid=842693 .
Issue - SBS 2003 SP1 reports error when Outlook 2003 files are missing from
clientapps
Problem Description
SBS 2003 SP1 appears to fail because the Outlook deployment files were not
installed, uninstalled, moved, or just deleted.
1. You will see the following service pack install error - "Windows Small
Business Server Service Pack 1
Setup has encountered an error. For more information, review the most
Recent entry in the setup error log in C:\Program Files\Microsoft Inetgration\Windows Small Business Server 2003
\logs\setup.log. Then correct the error and run the Service pack 1 setup again."
2. Setup.log will show all successes / no failures
3. Errorlog.txt will show "Microsoft Office outlook 2003 (ServicePack1):
[2] : Error applying outlook sp1
MSP file to AIP
(C:\CLientApps\Office2003_sp1\office2003_sp1.msp/c:\Client~1\outlook2003\OUTLS11.msi),
(3)
4. Could be a slight variant of the errorlog.txt message depending on the
initial cause (not installed, removed, etc)
5. You will also see the following in the KB885918.log
109.468: ---- Old Information In The Registry ------
109.531: Source:C:\ClntApps\ClientApps5\Office2003_SP1\SETC.tmp
109.609:
Destination:C:\ClntApps\ClientApps5\Office2003_SP1\OFFICE2003_SP1.MSP
109.609: ---- New Information In The Registry ------
109.609: Source:C:\ClntApps\ClientApps5\Office2003_SP1\SETC.tmp
109.609:
Destination:C:\ClntApps\ClientApps5\Office2003_SP1\OFFICE2003_SP1.MSP
109.609: DoInstallation: A reboot is required because RebootRequired=1 was
specified in the inf.
109.609: DoInstallation: A reboot is required because the
ProcessesToRunAfterReboot inf section was non- empty.
109.609: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
error 0x2
109.609: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
error 0x2
109.609: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
751.656: RebootNecessary = 1,WizardInput = 0 , DontReboot = 1, ForceRestart
= 0
Solutions
1. Install the client apps Outlook deployment
2. Correct the reg path to point to the proper location
Safely ignore the error and verify SP1 did install properly by a) All
successes in the setup.log, b) The registry value states
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer]\
ServicePackNumber=dword:00000001
Issue - Store.exe memory consumption alerts
Problem Description
After the SBS 2003 SP1 installation, you still receive the memory
Allocation alert to indicate that store.exe is using an abnormal amount of memory. This is actually the same issue described here:
867628 Monitoring programs report that the Store.exe process consumes
http://support.microsoft.com/?kbid=867628
Analysis
The problem is that the SBS Sp1 package is not disabling the alert as
expected. So, when a customer goes through the process of installing Exchange SP1 as a requirement for SBS SP1, it will start triggering these errors that are not taken care by the SBS SP1.
Resolution
· In the SBS SP1 scenario, you can also re-run the Configure Monitoring
Wizard and it will also disable the store alert. Note that you need to choose 'Reinstall Monitoring features' when running MCW.
· Or disable the alert manually from the Health Monitoring page.
Issue - The MSSQL$SHAREPOINT service fails to start after the installation
of SBS 2003 SP1
Problem Description
Small Business Server 2003\SharePoint not working after installing the SP1
(CD1 only: Windows SP1, SharePointAP1, Exchange 2003SP1), MSSQL$SHAREPOINT service fail to start.
Following information is in the mssql$sharepoint error.log file:
Starting up database 'master'.
Database 'master' has invalid schema.
Run the following command:
C:\Program Files\Microsoft SQL Server SP4\WMSDE>setup /upgradesp SqlRun
DISABLENETWORKPROTOCOLS=1
DISABLEAGENTSTARTUP=1 DISABLETHROTTLE=1 BLANKSAPWD=1
INSTANCENAME=Sharepoint REINSTALL=ALL
REINSTALLMODE=VEMUS /L*v "C:\Program Files\Microsoft Integration\Windows
Small Business Server 2003
\Logs\Sharepoint_MSDE2.Log" REBOOT=ReallySuppress /qn
MSSQL$SHAREPOINT is still not running. Even you manually try to start
it, it will stop without obvious error logged. And you will end up failing to access http://companyweb, and failing to connect to the configuration
database.
When you try to view the properties of sts_config db in SQL enterprise mgr,
you will probably get an 'invalid schema' error as listed below:
Microsoft SQL-DMO (ODBC SQLState: 42000)
Error 954: Database 'STS_Contents' has invalid schema.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Error 954: Database 'STS_Config' has invalid schema.
Resolution
1. Detach the companyweb databases from the WMSDE Sharepoint instance and
attach them to the Default SQL 2000 instance.
2. Point the companyweb site to the Default SQL 2000 instance for the
Config and content databases.
3. Restart the MSSQLServer service.