Microsoft Knowledge Base Email Alertz

(888937) - Describes a problem where programs appear to stop responding on client computers after you apply the SMS 2.0 SP4 version of the 813847 hotfix.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 888937 - Last Review: October 27, 2006 - Revision: 1.2

Programs stop responding after you install the Systems Management Server 2.0 Service Pack 4 813847 hotfix

On This Page

SYMPTOMS

After you install the Microsoft Systems Management Server (SMS) 2.0 Service Pack 4 (SP4) version of the hotfix that is described in Microsoft Knowledge Base Article 813847, you experience one or more of the following symptoms:
  • Some SMS 2.0 client components become unresponsive. Typically, the unresponsive programs are the SMS Available Programs Manager (Smsapm32.Exe) and Advertised Programs Monitor (Smsmon32.exe).
  • After you enable verbose client logging, the Smsapm32.log file contains log entries that are similar to the following entry:
    IPC SERVER : Received IPC_CS_MESSG_REQUEST_PROGRAM_CAPICON message
    IPC PIPE : ~WRITING MESSAGE HEADER :
    IPC PIPE : Message Header: ID: SMS_IPC~Type:
    TypeID~Length: 10138~Cookie:
    CookieID~Chunks:
    ChunkCount
    Additonally, the Smsmon32.log file contains log entries that are similar to the following entry:
    IPC UI : Sending message IPC_CS_MESSG_REQUEST_PROGRAM_CAPICON
    IPC PIPE : ~WRITING MESSAGE HEADER :
    IPC PIPE : Message Header: ID: SMS_IPC~Type:
    TypeID~Length: 4~Cookie:
    CookieID~Chunks: ChunkCount
    IPC PIPE : ~READ MESSAGE HEADER : IPC PIPE : Message Header: ID: SMS_IPC~Type:
    TypeID~Length: 10138~Cookie:
    CookieID~Chunks:
    ChunkCount
    Note The size of these messages is larger than 8,192 bytes. For example, in the Smsmon32.log file that appears earlier in this article, the size of the message is 10,138 bytes.
  • If you double-click the Advertised Programs icon in Control Panel, the Advertised Programs Wizard does not start.
  • If you double-click the Advertised Programs icon in the notification area at the far right of the taskbar, the Advertised Programs Wizard does not start.
  • Other programs that you run on the SMS 2.0 SP4 client stop responding.

CAUSE

This problem occurs if an SMS 2.0 SP4 client tries to use a program icon file (.ico) that is larger than 8,192 bytes.

WORKAROUND

To work around this problem, use one of the following methods.

Method 1: Replace icon files that are larger than 8,192 bytes with smaller icon files

To replace icon files that are larger than 8,192 bytes with smaller icons, follow these steps:
  1. Right-click Start, and then click Explore.
  2. Examine each subfolder of the driveletter:\Sms\Inboxes\Pkginfo.box folder.
  3. When you find an icon file that is larger than 8192 bytes in a subfolder, modify the package to use an icon file that is smaller than 8,192 bytes. To do this, follow these steps:
    1. Click Start, point to All Programs, point to Systems Management Server, and then click SMS Administrator Console.
    2. Expand Site Database (SiteCode - SiteName), expand Packages, and then expand the package that you want to change the icon for.
    3. Expand the Programs folder of the package.
    4. Right-click a program that is listed in the right pane, and then click Properties.
    5. On the General tab, click Change Icon.
    6. Click Browse, and then click an icon file that is smaller than 8,192 bytes.
    7. Repeat steps d to f for each program that is listed in the right pane.
    8. Repeat steps b to g for each package that you want to change the icon file for.

Method 2: Apply SMS 2.0 Service Pack 5, and then apply the SMS 2.0 Service Pack 5 version of the 813847 hotfix

For additional information about how to obtain and apply SMS 2.0 Service Pack 5, click the following article number to view the article in the Microsoft Knowledge Base:
288239  (http://kbalertz.com/Feedback.aspx?kbNumber=288239/ ) How to obtain the latest Systems Management Server 2.0 service pack
For additional information about how to obtain and apply the SMS 2.0 Service Pack 5 version of the 813847 hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
813847  (http://kbalertz.com/Feedback.aspx?kbNumber=813847/ ) Clients stop working if a package has many advertisements

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Before you applied the SMS 2.0 SP4 version of the hotfix, SMS 2.0 would ignore icons that are larger than 8,192 bytes. After you apply the SMS 2.0 SP4 version of the hotfix, SMS 2.0 tries to use icons that are larger than 8,192 bytes, but cannot do so.

The SMS 2.0 Service Pack 5 version of the 813847 hotfix limits the icon size to 8,192. Any icons that are larger than 8,192 are ignored and the default icon is used instead.

This problem does not occur if the client is installed with the SMS 2003 Legacy Client. The SMS 2003 Advanced Client does not support program icons.

For additional information about related issues, click the following article number to view the article in the Microsoft Knowledge Base:
813847  (http://kbalertz.com/Feedback.aspx?kbNumber=813847/ ) Clients stop working if a package has many advertisements
For additional information about how to enable verbose client logging, click the following article number to view the article in the Microsoft Knowledge Base:
327999  (http://kbalertz.com/Feedback.aspx?kbNumber=327999/ ) SMS: Client logging improvements in APM and ODP to help with troubleshooting

APPLIES TO
  • Microsoft Systems Management Server 2.0 Service Pack 4
Keywords: 
kbprb kbtshoot kbsmsupdates kbsmsclients KB888937
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate