Advertised programs may not finish successfully in Systems Management Server 2003 (886156)
The information in this article applies to:
- Microsoft Systems Management Server 2003
SYMPTOMSWhen you run an advertised program on a computer that is running the Microsoft Systems Manager (SMS) 2003 Advanced Client, the program may not finish successfully. If this behavior occurs, you may receive entries in the %Windir%\System32\CCM\Logs\Execmgr.log file that are similar to the following: Rolling over to network access account to check content location $$<execmgr><DateTime><ThreadID>
ConnectNetResource failed with error code 0x000004c3 $$<execmgr><DateTime><ThreadID> CAUSEThis problem may occur when the following conditions are true: - The client computer that is running the program is also running the Microsoft Systems Management Server (SMS) 2003 Advanced Client.
- The advertised program uses the Network Access account to connect to a distribution point.
- The advertised program runs immediately after another advertised program that is designed to start and then finish in less than one second.
WORKAROUNDTo work around this problem, use one of the following methods: Method 1: For programs that are chained- If only one member of the program chain starts and then finishes in less than one second, and the sequence of the programs is not important, move the member of the program chain that starts and finishes in less than one second to the end of the chain.
- If the members of a program chain that start and then finish in less than one second can run independently of the rest of the chain, remove those members from the chain, and then advertise them separately.
- Try to introduce a one-second delay into the chain immediately after the members of the program chain that start and then finish in less than one second.
Method 2: For programs that are not chained togetherCreate another advertisement for the program to the same collection with a new assignment time that is later than the original assignment time. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
---|
Keywords: | kbSMSDistribution kbwinservperf kbMgmtServices kbprb KB886156 kbAudITPRO |
---|
|