| Message ID | Severity | Message |
|---|---|---|
|
2300 |
Informational |
SMS Distribution Manager is beginning to process package %1 (package ID = %2). |
|
2301 |
Informational |
SMS Distribution Manager successfully processed package %1 (package ID = %2). |
|
2302 |
Error |
SMS Distribution Manager failed to process package %1 (package ID = %2). Solution: Review the previous status messages for further clarification about this problem. |
|
2303 |
Informational |
SMS Distribution Manager refreshed package %1 on distribution point %2. |
|
2304 |
Informational |
SMS Distribution Manager is retrying to distribute package %1. Solution: Wait to see if the package is successfully distributed on the retry. |
|
2305 |
Error |
SMS Distribution Manager failed to process package %1 without a source directory. Possible cause: The source directory is not specified. Solution: Verify that you have specified the package source directory on the Data Source tab in the package’s Properties dialog box in the SMS Administrator console. |
|
2306 |
Error |
The source directory %1 for package %2 does not exist. Solution: Make sure you have specified a valid package source directory on the Data Source tab in the package’s Properties dialog box in the SMS Administrator console. If you specify a local path, it must be a local path on the site server. If you specify a path on a network drive, verify that the path exists and that the path is typed correctly. |
|
2307 |
Error |
SMS Distribution Manager failed to access the source directory %1 for package %2. Possible cause: SMS Distribution Manager does not have sufficient rights to the package source directory. Solution: Verify that the SMS Service account has at least Read access to the directory you specify as the package source directory. |
|
2308 |
Error |
SMS Distribution Manager failed to remove the previously compressed copy for package %1 located at %2. Solution: Try to manually delete the file. |
|
2309 |
Error |
SMS Distribution Manager failed to compress package %1 from %2. Possible cause: The file that failed the compression is %3. This might have occurred because the files are corrupt. Solution: Replace the files and retry. |
|
2310 |
Informational |
SMS Distribution Manager compressed package %1 from %2 to %3. |
|
2311 |
Informational |
SMS Distribution Manager successfully created or updated package %1. |
|
2312 |
Error |
SMS Distribution Manager failed to update the distribution source for package %1. Possible cause: SMS Distribution Manager cannot update the package data in the SMS site database. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. Possible cause: Low disk space on the drive containing the package source files. Solution: Make more space available on that drive. Possible cause: The package source files are being written to a remote computer that is not accessible. Solution: Ensure that the remote computer is running and accessible. Possible cause: The package source files exist, but something other than SMS has changed the permissions or attributes of the files or the directory containing them. Solution: Restore the files’ permissions or attributes so that this SMS service can access the files. Possible cause: The package source files exist, but they are corrupt. Solution: Delete the files and replace them with backup copies. If you ignore this problem, SMS will probably fix it and complete this operation later. If this error occurs repeatedly, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
2313 |
Error |
SMS Distribution Manager failed to remove package %1 from %2. Possible cause: The share type or the share name have been changed since the package was created. Solution: Verify that the share defined for this package is accessible to SMS Distribution Manager running on the site server and that the name of the share has not been changed. If users are currently accessing the share, disconnect them before making any changes to the share. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the “Disconnect users from Windows NT distributions points” box in the Data Access tab of the package’s Properties dialog box. |
|
2314 |
Informational |
SMS Distribution Manager removed package %1 from %2 due to changes in the share type or the share name. |
|
2315 |
Informational |
SMS Distribution Manager deleted the compressed image of package %1 at %2. |
|
2316 |
Error |
SMS Distribution Manager failed to delete the compressed image of package %1 at %2. Solution: Try to manually delete the compressed image. |
|
2317 |
Informational |
SMS Distribution Manager is refreshing package %1 on distribution point %2. |
|
2318 |
Error |
SMS Distribution Manager failed to distribute package %1. Possible cause: The specified share is a hidden Windows NT drive share or a hidden Windows NT admin share. Solution: Specify a different share name on the Data Access tab of the package’s Properties dialog box in the SMS Administrator console. |
|
2319 |
Error |
SMS Distribution Manager failed to decompress package %1. Possible cause: The compressed image %2 is either missing or corrupt. Solution: Recompress the package using the Data Access tab of the Package Properties dialog box in the SMS Administrator console. Then, resend the package using the “Update distribution points on a schedule” feature on the Data Source tab of the package’s Properties dialog box. |
|
2320 |
Error |
There is not enough free disk space on the site server to decompress package %1. Possible cause: At least %2 megabytes of free disk space are required. Solution: Allocate more free disk space for the site server. |
|
2321 |
Error |
SMS Distribution Manager failed to decompress package %1 from %2 to %3. Possible cause: The file that failed to decompress is %4. Solution: Recompress the package using the Data Access tab of the package’s Properties dialog box in the SMS Administrator console. Then, resend the package using the “Update distribution points on a schedule” feature on the Data Source tab of the package’s Properties dialog box. |
|
2322 |
Informational |
SMS Distribution Manager decompressed package %1 from %2 to %3. |
|
2323 |
Error |
SMS Distribution Manager failed to initialize the network abstraction layer (NAL). Possible cause: SMS Distribution Manager cannot access the NAL. Solution: Use the SMS Service Manager to enable logging for SMS Distribution Manager. Then, investigate the log file for specific NAL errors. Refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. |
|
2324 |
Error |
SMS Distribution Manager failed to find or create the defined share or volume on distribution point %1 for distributing package %2. Possible cause: Windows NT distribution points might not have at least one available NTFS drive. Solution: Verify that there is at least one NTFS drive with enough free disk space to store the package. Then, verify that the distribution point directory exists, has the proper permissions, and is accessible. |
|
2325 |
Error |
SMS Distribution Manager failed to create subdirectories on distribution point %1 for distributing package %2. Possible cause: SMS Distribution Manager does not have sufficient rights to create subdirectories on the distribution point. Solution: In the SMS Administrator console, create a new site system connection account or verify that an existing account has sufficient privileges. |
|
2326 |
Error |
SMS Distribution Manager failed to save package status for package %1 to the SMS site database. Possible cause: SQL Server problem. Solution: 1. Review the immediately preceding status messages from this component about SQL Server errors. 2. Verify that this computer can reach the SQL Server computer. 3. Verify that SQL Server services are running. 4. Verify that SMS can access the SMS site database. 5. Verify that the SMS site database, transaction log, and tempdb are not full. 6. Verify that there are at least 50 SQL Server user connections, plus 5 for each SMS Administrator console. If the problem persists, check the SQL Server error logs. |
|
2327 |
Error |
SMS Distribution Manager failed to update the package properties on distribution points for package %1. Solution: Verify that there is enough free disk space on the site server to update the package. |
|
2328 |
Error |
SMS Distribution Manager failed to copy package %1 from %2 to %3. Solution: In the SMS Administrator console, verify that SMS Distribution Manager has the necessary rights to copy the package to the distribution point. Also, verify that there is enough free disk space for the destination distribution point to store the package. |
|
2329 |
Informational |
SMS Distribution Manager copied package %1 from %2 to %3. |
|
2330 |
Informational |
SMS Distribution Manager successfully distributed package %1 to distribution point %2. |
|
2331 |
Informational |
SMS Distribution Manager successfully removed package %1 from distribution point %2. |
|
2332 |
Error |
SMS Distribution Manager failed to remove package %1 from distribution path %2. Possible cause: The distribution point might not be accessible to SMS Distribution Manager running on the site server. Solution: If users are currently accessing the share, disconnect them before making any changes to the share. If the package distribution point is located on a Windows NT computer, you can force users to disconnect by clicking on the “Disconnect users from Windows NT distributions points” box in the Data Access tab of the package’s Properties dialog box. |
|
2333 |
Informational |
SMS Distribution Manager is preparing to send the compressed image of package %1 to child site %2. |
|
2334 |
Informational |
SMS Distribution Manager created a 1.x style instruction to send package %1 to 1.x child site %2. |
|
2335 |
Informational |
SMS Distribution Manager instructed SMS Scheduler and Sender to send package %1 to child site %2. |
|
2336 |
Error |
SMS Distribution Manager failed to create a 1.x style instruction to send package %1 to 1.x child site %2. Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. |
|
2337 |
Error |
SMS Distribution Manager failed to instruct SMS Scheduler to send package %1 to child site %2. Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. |
|
2338 |
Informational |
SMS Distribution Manager created a 1.x style instruction to send package definition for package %1 to 1.x child site %2. |
|
2339 |
Informational |
SMS Distribution Manager instructed SMS Scheduler and Sender to send the package information for package %1 to child site %2. |
|
2340 |
Error |
SMS Distribution Manager failed to create a 1.x style instruction to send the package definition for package %1 to 1.x child site %2. Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. |
|
2341 |
Error |
SMS Distribution Manager failed to send the package information for package %1 to child site %2. Solution: Verify that the site server has available memory and that there is enough free disk space to create the instruction file. |
|
2342 |
Informational |
SMS Distribution Manager is starting to distribute package %1 to distribution point %2. |
|
2343 |
Error |
There is not enough free disk space to copy package %1 to %2. Solution: Verify that %2 has at least %3 KB of free disk. |