THE OFFICIAL BLOG OF THE SBS "DIVA"

I will say it again, as I've said it before.... if you are someone that supports/sells to small businesses ...you need to be a Microsoft Partner.... if you are you get access to the managed services newsgroup and get info like this: 

 RECENT ISSUES AND TROUBLESHOOTING TIPS
-----------------------------------------------------------

ISSUE
-----------
How to install slipstreamed Outlook 2003 SP2 to the SBS Set Up Computer
wizard.

RESOLUTION
---------------
1. Download Office2003SP2-kb887616-fullfile-enu.exe from Microsoft Download
website:

   http://www.microsoft.com/downloads/details.aspx?FamilyID=57E27A97-2DB6-4654-9DB6-EC7D5B4DD867&displaylang=en

2. Save it as C:\Office2003SP2-kb887616-fullfile-enu.exe.
3. Run the following command to extract the files from the .exe file:

   C:\Office2003SP2-KB887616-FullFile-ENU.exe /C /T:C:\O2003SP2

4. Run the following command to slipstream SP2 into the installation
package:

   C:\O2003SP2\mainsp2ff.msp /a C:\ClientApps\Outlook2003\OUTLS11.msi

5. Follow the instruction to complete the process, and click OK.
6. Use Notepad to open %sbsprogramdir%\ClientSetup\apps.dat.
7. Change "Microsoft Office Outlook 2003 (Service Pack 1)" to "Microsoft
Office Outlook 2003 (Service Pack 2)"
8. Open C:\O2003SP2 in Explorer, and rename mainsp2ff.msp to
Office2003_SP2.msp.
9. Create a folder Office2003_SP2 under C:\ClientApps, and copy
Office2003_SP2.msp in step 8 to this folder.
10. Delete these files/folders:
    a) C:\Office2003SP2-KB887616-FullFile-ENU.exe
    b) C:\O2003SP2
    c) C:\ClientApps\Office2003_SP1

SBS has an C:\ClientApps\Office2003_SP1 folder and C:\ClientApps\Outlook2003
folder.
At the very beginning, the SBS client will first install Outlook 2003
without SP1 from C:\ClientApps\Outlook2003 folder, and then install Office
SP1 from C:\ClientApps\Office2003_SP1 folder.


After doing the above steps, Set Up Computer Wizard can deploy Outlook 2003
with Service Pack 2 to new clients join SBS domain.
For existing clients, run
\\<SBSServerName>\ClientApps\Office2003_SP2\Office2003_SP2.msp to install
Office 2003 SP2.



ISSUE
-----------
After turning on Success auditing for Object Access on the SBS 2003 Server,
the security event is fills up with:

Event ID: 562
Source: System
Category: Object Access
Type: Success A
Description:
Handle Closed
Object Server: Microsoft Exchange
Image File Name: C:\Program Files\Exchsrvr\bin\store.exe


CAUSE
--------
Temporary objects created/opened while routing mail are audited when
closed/deleted.
The auditing is not based on SACL on these objects; all these operations are
audited just because they turned on auditing for Store.


RESOLUTION
---------------
Add the following registry setting to disable the store auditing without
impacting the audit for other objects.

On the SBS Server, please open the below registry key:

  HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem

Please add the following DWORD value

Value name: Disable Close Object Audit
Value Type: DWORD
Value Data: 1


ISSUE
-----------
ActiveSync does not work on SBS 2k3 with either http or https but OMA works.

Http://FQDN/Microsoft-server-activesync or
https://FADN/microsoft-server-activesync gives out expected 501/505 not
implemented

WM 5.0 Device Report 0x85010014
Event Error 3031 on ActiveSync report error HTTP 409.
You may alsoalso see same event report HTTP 415 - Media type is not
supported

nextagslog shows
...
11/17/06 06:31:19 Dump of HTTP response for ConnId [0x00DCB4F8] User
[test@domain.com]
            HTTP/1.1 409 Conflict
            Connection: close
            Date: Fri, 17 Nov 2006 06:31:19 GMT
...
You may also see 0x80840001 in the Nextag log

CAUSE
-------
Trend virus scanner software is blocking the access. The exact root cause is
unknown.

RESOLUTION
---------------
We perform a clean boot by disabling all items and services related with
Trend software, the problem is resolved.
If you install a stand-along device simulator on SBS 2k3 directly, it may
sync fine and you may not be able to reproduce this issue.


ISSUE
-----------
SBS 2003 network, when the user deletes the outbound messages from the "Sent
Items" folder in Fax Console on client workstation, the messages also are
deleted from the SBS server.

CAUSE
--------
This is a by-design behavior.
What you see in you're the "Sent Items" folder in Fax Console on client
computers is the view of server.
There is no separate client copy of faxes.
So, if you delete faxes from sent items, they do get deleted from the
server.

The setting "Archive all successfully sent Faxes" mean after the fax is sent
successfully, it will be saved in the folder location mentioned. If you don't
have this checkbox turned ON, the fax will not be saved in the folder in
server. However, even when fax service saves the fax in the archive folder,
post that, it has no control on deletion of the message if the user deletes
from his sent items.

RESOLUTION
--------------
One way to solve this problem would be to run an application on the server,
which periodically monitors the archive folder and copies over the faxes
from that folder to some other folder store.


ISSUE
-----------
When you run the R2 Setup of the SBS 2k3 server, the wizard errored out with
following message

setup encountered an error during the configuration of the update services.
For more Information, see the log file at: C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs\R2_setup.log

When you review the logs, you will see the following error

11/27/2006 6:58:14 PM  !Error!         ForceAllDefaultSettings: An exception
occured while configuring Wsus defaults.
Information about the exception: System.Data.SqlClient.SqlException: Timeout
expired.
The timeout period elapsed prior to completion of the operation or the
server is not responding.
   at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException
e)
   at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
   at
Microsoft.UpdateServices.Internal.NoResultSPHandler.ExecuteStoredProcedure(DBConnection
connection)
   at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
spName, DBParameterCollection args, IExecuteSPHandler handler, Int32
queryTimeoutInSeconds)
   at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
spName, DBParameterCollection args, IExecuteSPHandler handler)
   at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPNoResult(String
spName, DBParameterCollection args)
   at
Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPDeleteTargetGroup(Guid
id)
   at Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.Delete()
   at
Microsoft.SBS.UpdateServices.WsusDefaults.WsusConfigurationDefaults.CreateWsusComputerGroups()
   at
Microsoft.SBS.UpdateServices.WsusDefaults.WsusConfigurationDefaults.ForceAllDefaultSettings(Boolean
isCleanInstall, Boolean configureAutomaticDownloads)
11/27/2006 6:58:14 PM                  ConfigureUpdateServices: An exception
occured while setting WSUS defaults: System.Data.SqlClient.SqlException:
Timeout expired.  The timeout period elapsed prior to completion of the
operation or the server is not responding.
   at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException
e)
   at
Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
   at
Microsoft.UpdateServices.Internal.NoResultSPHandler.ExecuteStoredProcedure(DBConnection
connection)
   at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
spName, DBParameterCollection args, IExecuteSPHandler handler, Int32
queryTimeoutInSeconds)
   at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String
spName, DBParameterCollection args, IExecuteSPHandler handler)
   at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPNoResult(String
spName, DBParameterCollection args)
   at
Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPDeleteTargetGroup(Guid
id)
   at Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.Delete()
   at
Microsoft.SBS.UpdateServices.WsusDefaults.WsusConfigurationDefaults.CreateWsusComputerGroups()
   at
Microsoft.SBS.UpdateServices.WsusDefaults.WsusConfigurationDefaults.ForceAllDefaultSettings(Boolean
isCleanInstall, Boolean configureAutomaticDownloads)
   at R2_SetupWizard.R2WI_ConfigureUpdateServices.DoWork(StringDictionary
sd)
11/27/2006 6:58:14 PM  !Error!         WorkItemExecutor:
ComponentMessageException occured in DoWork() for work item
ConfigureUpdateServices: R2_SetupWizard.ComponentMessageException: Exception
of type R2_SetupWizard.ComponentMessageException was thrown.
   at R2_SetupWizard.R2WI_ConfigureUpdateServices.DoWork(StringDictionary
sd)
   at R2_SetupWizard.WorkItemExecutor.ExecuteWorkItems(StringDictionary sd,
ExecutorCallback beforeWork, ExecutorCallback afterWork)

CAUSE
--------
The system index for the SQL database was missing.

RESOLUTION
---------------
Sometimes, the reinstallation of the R2 package does not resolve the issue.
After investigating, the "Timeout Expired" error on
"DrainObsoleteConnections" was seen when the system index for the SQL
database was missing. To resolve this issue, please consider the following
solution


1. Make sure, we remove all R2 and WSUS component from the SBS machine
2. We need to use the steps to install the WSUS into your system manually

<CDDRIVE>:\WSUS_20\WSUSSetup.exe /v "CONTENT_DIR="<WSUSDRIVE>:\WSUS" /d
"INSTANCE_NAME=WSUS"


Note, you can remove the quotes if the command does not work

3. Create a txt document and copy the following lines to it

USE SUSDB
GO
BEGIN TRAN
IF NOT EXISTS (SELECT * FROM sysindexes where name='nc7DeploymentRevision')
   BEGIN
        CREATE NONCLUSTERED INDEX nc7DeploymentRevision ON
dbo.tbDeployment(RevisionID, TargetGroupID, ActionID)
   END
   COMMIT TRAN
   GO

4. Rename the file to "addDeploymentIndex.sql" and save the files to the
C:\Program Files\Microsoft SQL Server\80\Tools\Bin.
5. Open a Command prompt and go to C:\Program Files\Microsoft SQL
Server\80\Tools\Bin. Then, please execute the following command

   osql -E -S SBSServerName\WSUS -n -b -i addDeploymentIndex.sql

6. If the command completed successfully, please continue the SBS R2 setup.


ISSUE
-----------
Receive event 11010 on one ISA 2000 node every hour:

  Event Type: Error
  Event Source: Microsoft ISA Server Control
  Event Category: None
  Event ID: 11010
  Date:  xx/xx/2006
  Time:  5:04:54 PM
  User:  N/A
  Computer: xxxx
  Description:
  Microsoft ISA Server Control failed.
  The storage of the current array {3CC7537D-D5B9-4BE0-8A27-E520B9B2EE59}
(or server {4E9B5993-3258-43C5-85D9-20E00CE5A354}) could not be accessed
during Log files sweeping.
  The error code in the event viewer indicates the source of the failure.
Use the source location 1.1044.3.0.1200.166 to report the failure.
  If your server is a stand-alone ISA Server, try to restore the ISA Server
configuration, otherwise, check the connectivity to domain controller (DC),
and the DNS configuration.
  The error description is: An operations error occurred.

CAUSE
--------
There are several DCs in the domain and the ISA server does not have a
secure channel with the PDC.

RESOLUTION
---------------
Re-configure the ISA to establish the secure channel with the correct DC:
1. Open the ISA MMC ->Servers and arrays ->Select the array the ISA server
(the problematic node) is in -> computers -> look for your server (which
Domain controller is it using?)

2. On the command line using nltest (nltest.exe is on the w2k install CD
under the support\tools folder and in the support.cab file ):
   a. nltest /DSGETSITE
      (what site is this machine in?)
   b. nltest /SC_query:%your domain% (for example: domain.local)
      (which DC is given back? Is the secure channel successfully
established?)
   c. nltest /DClist:%your domain%
      (this displays all DCs available in this site.)
   d. nltest /SC_RESET:%your domain%
      (A new secure channel should be established to another DC seen in c)

Note: (You may need to run this command multiple times)

3. After that reboot the ISA Server and the event no longer triggers.



ISSUE
-----------
SBS 2003 with ISA 2004 installed. LAN clients receive 403 access denied when
accessing http://companyweb. They can browse https://companyweb and
http://companyweb.domain.local without issues.

CAUSE
--------
"Require all users to authenticate" option was enabled on the ISA's Internal
network.
All the LAN clients are configured as Web Proxy client and the "Bypass proxy
server for local addresses" option is ticked.
The problem occurrs because ISA requires authentication for all HTTP traffic
from the internal network.
When the "Bypass proxy server for local addresses" option is selected, IE
will bypass the proxy when accessing resources considered locally (whose URL
doesn't contain a period) and leverage either the Firewall client and the
SecureNAT client to send the traffic.
If Firewall Client is not installed, the SecureNAT will handle the traffic.
As the SecureNAT cannot pass the user credential to the ISA, the access
failed.
As you install the third party web filter on the ISA, the "Require all users
to authenticate" option should be enabled.

RESOLUTION
---------------
Two options:

1. Uncheck the "Bypass proxy server for local addresses" option in IE.

Or:

2. Install the Firewall Client on all the workstations.