Hot topics from the managed newsgroups

Hot topics from the Partner newsgroup… now if you were on the ball, you wouldn’t need the blog post to tell you what this post is all about, you would have seen this post already in the Managed partner newsgroup:


https://partner.microsoft.com/US/supportsecurity/technicalsupport/onlinesupport/newsgroups 


The following “hot topics” were posted and resolved during the month of May:


(NOTE – ANYTIME YOU SEE THESE HOTTOPIC POSTS FROM THE NEWSGROUPS, IT MEANS A MICROSOFT ENGINEER WAS ASSISTING THE PERSON.  ON A SBS BOX, REMOVING IIS WITHOUT HAVING EXPERT GUIDANCE CAN BE VERY DANGEROUS.  THESE POSTS JUST FOR AWARENESS OF ISSUES, THEY ARE NOT MEANT TO BE FOLLOWED WITHOUT HAVING EXPERT GUIDANCE ASSISTING YOU.  IF YOU SEE ONE OF THESE NASTY ISSUES AND YOU ARE A PARTNER, SIGN UP FOR THE MICROSOFT PARTNER NEWSGROUPS AND POST TO GET ASSISTANCE.  IF YOU ARE NOT A PARTNER AND JUST AN END USER/CUSTOMER, HIRE SOMEONE TO DIG YOU OUT.  REINSTALLING IIS IS NOT FOR THE FAINT OF HEART)

ISSUE
=====
Customer has SBS 2003 R2 with WSUS 2.0. He tried to upgrade to WSUS 3.0 but
failed. He observed the following event in the event log:

“The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: .NET
Runtime version 1.1.4322.2379- AutoApprove.exe – Common Language Runtime
Debugging Services: Application has generated an exception that could not be
handled.

Process id=0x1c9c (7324), Thread id=0x1ca0 (7328).

Click OK to terminate the application.
Click CANCEL to debug the application..”

- and saw the following in the WSUSSETUP.log file:

2007-05-09 10:51:57  Success   MWUSSetup          Installing ASP.Net
2007-05-09 10:53:26  Success   MWUSSetup          ASP.Net is installed
successfully
2007-05-09 10:53:26  Success   MWUSSetup          Installing wYukon…
2007-05-09 10:57:21  Success   MWUSSetup          wYukon Installed
Successfully
2007-05-09 10:57:26  Error     MWUSSetup          GetData returned error
(Error 0x800CC801)
2007-05-09 10:57:26  Error     MWUSSetup          GetWebsiteKeyList
returning error (Error 0x800CC801)
2007-05-09 10:57:26  Error     MWUSSetup          GetWebsiteKeyList returned
error (Error 0x800CC801)
2007-05-09 10:57:26  Error     MWUSSetup
CIISWebService::GetWebsites returning error (Error 0x800CC801)
2007-05-09 10:57:26  Error     MWUSSetup
CUpgradeDriver::SetWebsiteinfo: Failed to get list of websites (Error
0x800CC801)
2007-05-09 10:57:26  Error     MWUSSetup
CUpgradeDriver::PerformSetup: Failed to set website information (Error
0x800CC801)
2007-05-09 10:57:26  Error     MWUSSetup          CSetupDriver::LaunchSetup:
Setup failed (Error 0x800CC801)
2007-05-09 11:01:44  Error     MWUSSetup          DoInstall: Wsus setup
failed (Error 0x800CC801)


CAUSE
======
Error 0x800CC801 means: MD_ERROR_DATA_NOT_FOUND. This error indicates that
the WSUS installation process cannot read info from IIS database. Normally
after configuring IIS virtual directory for reporting service under a
specific web server (say the index is 6), the virtual directory should look
like that

<IIsWebServer Location=”/LM/W3SVC/6″ />
<IIsWebVirtualDir Location=”/LM/W3SVC/6/Root/Reports” AccessFlags ..>
..

But somehow in the customer’s server, the virtual directory of reporting
service was  under an IIsConfigObject node

<IIsConfigObject Location=”/LM/W3SVC/6″ />
<IIsConfigObject Location=”/LM/W3SVC/6/Root” />
<IIsWebVirtualDir Location=”/LM/W3SVC/6/Root/Reports” AccessFlags ..>

When WSUS setup traverse the metabase to detect the existence of default
Websites, it also hits <IISConfigObject> node, for which the Keytype
attribute is not of type INHERIT, thus the detection logic bailed out. Our
code could have just skipped this kind of node and continue looping, because
default website should always be a <IIsWebServer> node whose Keytype is of
INHERIT type.



WORKAROUND
=============
1. Reinstall IIS which rebuild the IIS metabase. According to Eric’s
feedback, SBS now handles IIS reinstallation only in CSS case. So you can
redirect the customer to work with CSS.

2. Manually modify metabase file. Steps are:

a. Make a backup copy of Windows\System32\inetserv\metabase.xml

b. Shutdown IIS

c. Comment out elements:

<IIsConfigObject Location =”/LM/W3SVC/6″>
</IIsConfigObject>
<IIsConfigObject Location =”/LM/W3SVC/6/Root”>
</IISConfigObject>

d. Start IIS

e. Install WSUS 3.0

f. Shutdown IIS.

g. Uncomment elements in step c.

h. Start IIS.

Note: The second solution is a case by case solution which depends on the
web site ID of the WSUS admin page and we need to analyze metabase file
first to locate the root cause, however, according to our IIS guru wen-jun
Zhang’s suggestion, metabase file checking is only supported in CSS case.

MORE INFORMATION
==================
Microsoft has confirmed this to be a problem and it is now under further
investigation.


ISSUE
=====
Customer tried to install WSS 3.0 on the SBS 2003 server with WSUS 3.0
installed but he/she received the follow error message:

Failed to create the configuration database.
An exception of type System.Data.SqlClient.SqlExecution was thrown.
Additional exception information: Could not find stored procedure
‘dbo.getObjectByClass’.

CAUSE
======
Incorrect installation order of WSUS 3.0 and WSS 3.0.

RESOLUTION
===========
1. Close the error dialog.

2. Install the SharePoint 3.0 hotfix package from KB 934790
(http://support.microsoft.com/kb/934790). You will have to call Microsoft to
obtain this hotfix package.

3. After you apply this hotfix, you must run the SharePoint Products and
Technologies Configuration Wizard. To do this, click Start, point to All
Programs, point to Administrative Tools, and then click SharePoint Products
and Technologies Configuration Wizard.

NOTE: This is the same wizard that you run in Step 3 of the WSS 3.0 white
paper
(http://www.microsoft.com/downloads/details.aspx?FamilyID=0daafc81-efff-4f5b-a28a-8265f1e99f5b&displaylang=en).
You only need to run this wizard once to completion after installing the
hotfix.

4. Complete steps 4-6 in the WSS 3.0 white paper
(http://www.microsoft.com/downloads/details.aspx?FamilyID=0daafc81-efff-4f5b-a28a-8265f1e99f5b&displaylang=en)
to complete the SharePoint 3.0 side by side installation on SBS 2003.

MORE INFORMATION
==================
One frequent question often asked of SBS 2003 server installations concerns
the order of installing the components, upgrades, and updates that have
released over the years. For the most part, the best approach is to install
the items in the order they were released. For those of you planning on
installing Windows SharePoint Services 3.0 (aka WSS 3.0, SharePoint 3.0) and
WSUS 3.0 on the same server, this guidance is no different and both
installations should go smooth if you install WSS 3.0 before installing WSUS
3.0.

How to install SharePoint 3.0 and then WSUS 3.0.

1. Install SBS R2 including WSUS 2.0.

2. Install WSS 3.0 using the side by side installation steps in the white
paper. Complete all steps.

3. Upgrade to WSUS 3.0.

To avoid the error above when installing SharePoint 3.0 after WSUS 3.0:

1. Install SBS R2 including WSUS 2.0.

2. Upgrade to WSUS 3.0.

3. Install WSS 3.0 using the side by side installation steps in the white
paper. Only perform steps 1 and 2 in the white paper at this point.

4. Before performing step 3 in the WSS 3.0 white paper, install the
SharePoint 3.0 hotfix package from KB 934790.  You will have to call
Microsoft to obtain this hotfix package.

5. Complete steps 3-6 in the WSS 3.0 white paper to complete the SharePoint
3.0 side by side installation on SBS 2003.


ISSUE
=====
Customer received the following error message on the SBS server:

Error: Microsoft Intelligent Message Filter has encountered a problem and
needs to close.  We are sorry for the inconvenience.

This error occurs when you are in Exchange manager and try to open Help.
This is basically caused by IE7 trying to use a Different DLL.

CAUSE
======
This problem occurs because of a conflict between the newer version of the
Psapi.dll file that Internet Explorer 7 uses and the older version that
Exchange System Manager uses.

RESOLUTION
===========
From:
http://support.microsoft.com/kb/932513, Exchange System Manager in Exchange
Server 2003 stops responding when you try to access Exchange Help after you
install Internet Explorer 7

Consider the following scenario. You are using Microsoft Exchange Server
2003 on a computer that is running Microsoft Windows Server 2003 Service
Pack 1 (SP1). You install Windows Internet Explorer 7 on the computer that
is running Exchange System Manager. In this scenario, when you try to access
Exchange Help in Exchange System Manager, Exchange System Manager stops
responding because of an access violation.

To work around this issue, you must rename the Psapi.dll file in the
Exchsrvr\Bin directory so that the Exchange services use the Psapi.dll file
from the %Windir%\System32 directory. To do this, follow the steps that are
appropriate for your situation.

You have installed Internet Explorer 7 on the Exchange server that also has
Exchange System Manager installed. If you have installed Internet Explorer 7
on the Exchange server that also has Exchange System Manager installed,
follow these steps:

1. Stop all Exchange and Internet Information Services (IIS) services.

a. Open the Services snap-in.

b. Stop the Microsoft Exchange System Attendant service.

Important Note: The list of dependent services that will be stopped. For
example, the list of dependent services may resemble the following:

.Microsoft Exchange Information Store

.Microsoft Exchange MTA Stacks

c. Stop the IIS Admin Service.

Important Note the list of dependent services that will be stopped. For
example, the list of dependent services may resemble the following:

.World Wide Web Publishing Service
.Simple Mail Transfer Protocol (SMTP)
.HTTP SSL
.AntigenIMC

2. Rename the Psapi.dll file. To do this, follow these steps:

a. Open a command prompt.

b. Move to the following directory:

Drive_Letter:\Program Files\Exchsrvr\bin

c. Change the name of the Psapi.dll file to Psapi.dll.old.

d. Close the Command Prompt window.

3. Restart the Exchange services and the IIS services. This includes the
dependent services that were stopped.


ISSUE
=====
Customer installed Windows 2003 SP2 on his SBS 2003 R2 server and after
that, Help and Support does not work. When he tried to launch Help and
Support, he receives the following error message:

Windows cannot open Help And Support because the service is not running. To
fix this problem start the service named Help and Support.

CAUSE
======
The root cause is unknown and the issue is now under further investigation.

RESOLUTION
===========
Run the following steps to reinstall Help and Support:

1. Open a command prompt.

2. Navigate to %windir%\PCHealth\HelpCtr\Binaries

3. Run the following command:

start /w helpsvc /svchost netsvcs /regserver /install

4. Once this command completes the Help and Support service should now
appear in services.msc.

5. Start the Help and Support service

MORE INFORMATION
=================
Windows 2003 service pack 2 known issues on Small Business Server 2003
http://support.microsoft.com/kb/555912

Help and Support service missing after installing Windows 2003 Service Pack
2
http://blogs.technet.com/sbs/archive/2007/03/20/help-and-support-service-missing-after-installing-windows-2003-service-pack-2.aspx


 

Comments are closed.

Post Navigation