Top issues with SBS 2003 sp1

On August 8, 2005, in SBS 2k3 sp1, by

Now if you were a Microsoft partner…. you’d be able to visit the Partner newsgroups and find these answers to top issues:


…now then…if you install SBS servers…why aren’t you a partner? Better yet…why not a Small Business Specialist?


1. Store.exe memory consumption alerts

SYMPTOMS
After installing SBS 2003 SP1, a performance monitoring program that you run
may generate an alert or a report to indicate that the Store.exe process
uses much more memory than it did before you installed SP1. Typically, the
monitoring program reports that the Store.exe process uses more “private
bytes” memory than it used before you installed SP1.

CAUSE
This is actually the same issue described here:

867628 Monitoring programs report that the Store.exe process consumes
http://support.microsoft.com/?id=867628

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
If you re-run the Monitoring Configuration Wizard, the alert is going to be
disabled. Or disable the alert manually from the Monitoring page.

2. CEICW fails with error 0x800725ec in the CEICW log (ICWLOG.TXT)

SYMPTOMS
When running the CEICW after installing SBS SP1 and ISA 2004, the wizard may
fail with the following errors in the ICWLOG.TXT:

Error 0x800725ec returned from call to Creating A record for publishing().
Error 0x800725ec returned from call to
CStingrayCommit::CreateWebPublishingRules().
Error 0x800725ec returned from call to Creating ISA2k4 Web publishing
rules().
Error 0x800725ec returned from call to
CStingrayCommit::CommitWebPublishingRules().
Error 0x800725ec returned from call to Creating Web publishing rules().
Error 0x800725ec returned from call to CStingrayCommit::CommitEx().
[..]
*** Enabling SSL with ISA returned ERROR 8000ffff
*** CCertCommit::EnableSSL returned ERROR 8000ffff
*** CCertCommit::CommitEx returned ERROR 8000ffff
The Firewall Configuration and the Secure Web Configuration will fail in the
wizard.

CAUSE
The error 0x800725ec means:

DNS_ERROR_NODE_IS_CNAME

The problem here is that the PUBLISHING record in DNS is a CNAME instead of
the expected A record.

RESOLUTION
Remove the CNAME Publishing record in DNS and create a new A record for
Publishing pointing to the proper internal IP.

3. CEICW may fail with error c0040393 in the CEICW log (ICWLOG.TXT)

SYMPTOMS
When running the CEICW after installing SBS SP1 and ISA 2004, the wizard may
fail with the following errors in the ICWLOG.TXT:

Saving changes and restarting services returned ERROR c0040393
Publishing CompanyWeb through ISA2k4 returned ERROR c0040393
CCertCommit::EnableSSL returned ERROR c0040393
CCertCommit::CommitEx returned ERROR c0040393

The Firewall Configuration and the Secure Web Configuration will fail in the
wizard.

CAUSE
This issue may occur if  the following  policy settings are not assigned to
the Network Service account on the domain controller:

– Adjust memory quotas for a process
– Generate security audits
– Log on as a service
– Replace a process level token

The Network Service account must be added to the policy settings in the
list. This issue may occur if Group Policy settings that were applied at the
domain level have modified the policy settings for the Network Service
account on the domain controller. This issue may occur after you promote a
member server to a domain controller, or on a migration from a Windows 2000
network where SBS 2003 was joined to the 2000 domain.

RESOLUTION
To resolve this issue, make sure that the Network Service account is added
to the following policy settings on the domain controller:

– Adjust memory quotas for a process
– Generate security audits
– Log on as a service
– Replace a process level token

4. SP1 reports error when Outlook 2003 files are missing from clientapps

SYMPTOMS
When trying to setup SBS 2003 SP1, we may see the following symptoms:

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

CAUSE
Outlook deployment files were not installed, uninstalled, moved, or just
deleted.

RESOLUTION
1.  Install the client apps Outlook deployment.

2.  Correct the reg path to point to the proper location.

3.  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

5. Be prompted to insert CD with SBS 2003 SP1 when trying to reinstall a SBS
component

SYMPTOMS
When trying to reinstall a SBS component, you are prompted to insert CD with
SBS 2003 SP1 and the original SBS 2003 CDs do not work.

CAUSE
SBS 2003 SP1 setup was downloaded from the web.

RESOLUTION
Check to see if the HKLM\Software\Microsoft\SmallBusinessServer\IsRunFromWeb
= 0x2 and if so, extract the SBS 2003 SP1 package and point it to the
folder.

6. Clients unable to get DHCP address after installing ISA 2004

SYMPTOMS
Clients may no longer be able to get DHCP addresses assigned by SBS’s DHCP
server after ISA 2004 is installed.

CAUSE
The broadcast address for the subnet is not included in the Internal network
range.

RESOLUTION
Check in the ISA MMC/ServerName/Configuration/Networks then on the Networks
tab, look at the Name Internal Address Ranges. If it’s not there, for
example range is up to .254 instead of .255, right click and select
Properties/click on the Addresses tab to change/correct the entries.

 

Comments are closed.