Troubleshooting Software Distribution Issues
Updated: August 1, 2010
Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2
This topic provides information to help troubleshoot software distribution issues in Microsoft System Center Configuration Manager 2007. This content might have been updated. For the most recent version, see Software Distribution Troubleshooting http://go.microsoft.com/fwlink/?LinkId=93052.
Processing Delays in Binary Delta Replication
The processing time for large packages can take an extended period of time (20–30 minutes in some cases or even longer, depending on the size of the package). During this package compression/decompression and hashing/signature-creating process, the distmgr.log might appear to be idle even though the process is continuing.
Settings That Are Changed During a Maintenance Window Are Not Immediately Effective
If settings (such as Restart Countdown) that use or affect the maintenance window are changed while the maintenance window is open, those changes will not be considered until the next applicable maintenance window. For example, if a maintenance window is currently open and has 4 minutes remaining in it, and the Restart Countdown is changed from 5 minutes to 1 minute, a queued program will not run in that maintenance window even if it would otherwise have run with the new Restart Countdown.
Packages Are Not Replicated to a Branch Distribution Point After an Extended Wait
Occasionally, when provisioning a branch distribution point, packages might not be replicated properly even after waiting for an extended period of time. A typical symptom of this can be the branch distribution point continuing to remain in "downloading" status for an extended period of time. This can occur because the job thread has failed before the main process thread, causing a known issue between the content transfer manager and the branch distribution point agent.
Retry the branch distribution point by refreshing (updating) the package. This should solve the issue.
Advertising Option "Run only when a user is logged on" Does Not Work Reliably on Windows XP Embedded
That the Run only when a user is logged on option does not work reliably when advertising a program to a Windows XP Embedded (Windows XPe) operating system is a known issue.
The recommended course of action is to use Run whether or not a user is logged on to make sure the advertisement is executed by the Windows XPe clients.
Creating a Package from Definition via Remote Configuration Manager Console Results in an Incorrect Source Directory by Default
When creating a package from a package definition file located on the local computer, the Source Directory page might display the path to the .msi file on the local drive, but it will not work on the site.
This is because the Create Package from Definition Wizard attempts to set the source directory to where the package definition is located, but when creating the package, Configuration Manager uses the directory on the site server itself. As a result, Configuration Manager attempts to use the displayed path (which is appropriate only to the remote computer) as if it exists on the site server.
When creating packages from definition by using a remote Configuration Manager console, administrators must define the source directory as the path on the site server (rather than the remote computer running the Configuration Manager console) where the package file or files exist.
Packages Are Stuck in the "Pending" State on a Branch Distribution Point After Deleting and Re-adding Them
When deleting a package and re-adding the same package to a branch distribution point within a short period of time (such as less than one hour or before the next branch distribution point policy cycle has occurred, whichever is shorter), the package will be stuck at the pending state for this branch distribution point.
After deleting and re-adding a package to a branch distribution point, if the branch distribution point seems to be staying in a "Pending" state for a very long time, one of the following options can be tried:
On the Configuration Manager console, on the Package node, update the distribution points for this package. This causes the most recent version of the package to be sent to all distribution points to which this package is assigned. For more information, see How to Update Package Data on Distribution Points.
Delete this package from the branch distribution point, wait for one hour (or a length of time sufficient for the next branch distribution point cycle to have occurred), and then add the package back to the branch distribution point.
Restart the client SMS Agent Host service.
New Advertisement Wizard Gives Incorrect Summary Information
When you run the New Advertisement Wizard, the summary page might say that the advertisement was not assigned, even though it was configured to run as soon as possible, and that the assignment will ignore maintenance windows. However, when you check the resulting advertisement, the assignment and maintenance window settings are configured correctly.
This is a known issue in Configuration Manager 2007. When the advertisement is configured with the assignment schedule setting Assign immediately after this event, the summary page does not report this as an assignment, and settings for maintenance windows and Wake On LAN are not verified in the summary information. The summary information is incorrect, and the advertisement requires no additional configuration.
Additionally, if you configure an optional advertisement with the setting Always rerun program, the summary page incorrectly displays the program rerun behavior as "never rerun advertised program."
Cannot Create Advertisement Using Distribute Software Wizard from a Folder Under Advertisements
Under the Advertisements node, if you create a folder, right-click the folder, and then click Distribute Software, the Distribute Software Wizard appears to complete successfully but no advertisement is created. This is a known issue.
Parcel Created in Courier Sender Manager Fails on SMS 2003 Site
When you create a parcel in Configuration Manager 2007 Courier Sender Manager, you cannot import that parcel into Courier Sender Manager on the SMS 2003 child sites. You get the error message "The parcel was read but there were no objects for this site." This is a known issue. There is no workaround.
The Network Access Account Fails After Changing Account Name
You change the user account configured for the Network Access Account but use the same password as the old account. In this case, the Network Access Account cannot access package content.
When changing the Network Access Account, you must also enter a password for the new account, even if the new account uses the same password as the old account.
Cannot Multi-Select and Delete More Than 479 Advertisements
If you select a large number of advertisements, usually more than 479, you delete the advertisements, confirm the deletion, and find that the advertisements have not been deleted. This is a known issue.
Delete fewer than 479 advertisements at a time.
Advertisements Fail to Run on the Internet
Advertisements fail to run on the Internet when you are using the Internet-based client management feature. However, other features, such as hardware inventory and software updates, succeed on the Internet.
Cannot Create Branch Distribution Point Because the Option Is Disabled
Configuration Manager automatically detects some scenarios that would prevent a branch distribution point from working. In these circumstances, the option Enable as a branch distribution point cannot be selected in the distribution point properties.
These scenarios include the following:
The Configuration Manager client is not installed on the site system and assigned to the site.
The site system is not confirmed to be a member of an Active Directory domain.
The site system is running the Windows 2000 operating system.
The Configuration Manager client is configured for Internet-based client management.
Verify and correct the conditions that prevent the branch distribution option from being selected:
Ensure that the Configuration Manager client is installed and displays in the Configuration Manager console with Yes in the Client column and Yes in the Assigned column. If necessary, troubleshoot client installation and site assignment.
Verify that the computer is joined to a domain in the site server forest. Also confirm that the Name for the site system is correctly entered as the computer name and that this name can be resolved on the network.
Select a computer that is not running the Windows 2000 operating system.
If the client has been configured for Internet-based client management by using the CCMHOSTNAME client installation property, follow these steps:
Remove this configuration by deleting the Internet-based management point (FQDN) value in the Internet tab in the Configuration Manager client properties, and then click OK.
In the Configuration Manager console, use the Collections node to locate the client object, and delete it.
On the computer running the Configuration Manager client, restart the client service, SMS Agent Host.
On the computer running the Configuration Manager client, initiate a discovery data collection cycle by performing the following steps:
In the Configuration Manager properties, click the Actions tab.
Click Discovery Data Collection Cycle, click Initiate Action, and then click OK to close the pop-up dialog box.
Click OK to close Configuration Manager Properties.
- In the Configuration Manager properties, click the Actions tab.
- Remove this configuration by deleting the Internet-based management point (FQDN) value in the Internet tab in the Configuration Manager client properties, and then click OK.
If none of these solutions resolve the issue, check for the following:
Confirm that the selected computer does not have a conflicting record. Check the Conflicting Records node to ensure that there are no unresolved conflicting records for this computer.
Verify that the selected computer does not have any errors reported for the client or site system components. Check for errors in the status messages and log files, and if necessary, uninstall and reinstall to correct any problems.
Try closing and reloading the Configuration Manager console to ensure that it is not a timing display error.
Branch Distribution Point Fails to Install Packages in a Native Mode Site
Although Configuration Manager does not support branch distribution points on clients that are configured for Internet-based client management, Configuration Manager cannot always detect this combination and can let you select the option Enable as a branch distribution point in the distribution point properties when the client is configured for Internet-based client management. In this scenario, the branch distribution point will successfully install but packages will not install on it. The package status will remain as Install Pending, and the status message ID 11377 will be reported by the Peer DP Agent component. On the client, the log file PeerDPAgent.log will contain the following text:
The client is internet enabled, therefore cannot be marked as a Branch DP
Decide whether this client should be a branch distribution point or configured for Internet-based client management, and then reconfigure the client accordingly:
If the client should be managed over the Internet, delete the branch distribution point role, and then delete the site system.
If the client should be a branch distribution point, follow these steps:
In the client Configuration Manager properties, click the Internet tab, delete the Internet-based management point (FQDN) value, and click Apply.
Click the Actions tab, click Branch Distribution Point Maintenance Task, click Initiate Action, and then click OK to close the pop-up message. Packages will now start to install.
Click OK to close Configuration Manager Properties.
- In the client Configuration Manager properties, click the Internet tab, delete the Internet-based management point (FQDN) value, and click Apply.
Virtual Application Package Does Not Run After Restarting Computer
Virtual applications packages that have been configured for streaming do not run after you restart the computer.
This can occur when applications that are configured to run at startup run before the SMS Agent Host service (Ccmexec.exe) is started. When this occurs, virtual application packages configured to stream will not successfully run unless the package has been fully downloaded to the Microsoft Application Virtualization Desktop Client cache. You can configure the virtual application package advertisement with the setting Download content from distribution point and run locally or wait until the package has been completely downloaded to the client cache.
Advertisements Created by Using Rerun Advertisement Might Run at the Wrong Time
When you use the Rerun Advertisement action to create a new mandatory schedule for an advertisement, the advertisement might not run at the expected time. Advertisement schedules created by the Rerun Advertisement option are created by using Coordinated Universal Time (UTC) while new advertisement schedules are set to local time. There is no visual identification in the mandatory assignment display which indicates a schedule has been set to UTC.
To validate or change settings for any mandatory assignment schedule, select the desired mandatory assignment schedule, and then click the Properties icon to open the Assignment Schedule dialog box.
Distribution Manager (a Server Component) Fails When Creating a Share with a Long File Name
Distribution Manager fails and cannot create a custom share when you specify a shared folder name that contains more than 64 characters.
When you create a shared folder on a standard distribution point, specify a shared folder name that contains 64 characters or less.
ConceptsTroubleshooting Software Distribution Using Custom Error Codes
Other ResourcesSoftware Distribution Overview
For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.