Hello everyone, I got handed our SCCM enviornment until we get a new guy to fill in and have been trying to keep things in running order, but had some trouble as of lately. I am getting 1000s of error 2302 and 2348 events everyday and am trying to fix them, below is one example:
2302:
SMS Distribution Manager failed to process package "Java 6" (package ID = SSS000B7).
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
2348: SMS Distribution Manager failed to decompress package "SSS000B7" from "F:\SMSPKG\SSS000B7.PKG".
Possible cause: The compressed image "F:\SMSPKG\SSS000B7.PKG" is either missing or corrupt. SMS Distribution Manager will not attempt to recover the package. Please update the package to repair the compressed image
In this case I tried the following troubleshooting steps:
Locate the package, SSS000B7, it is an older version of Java, I right click on it, update distribution points, at the prompt that asks me to conform update distribution points I click yes. No dice.
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point.
I have tracked down the folder that it is part of and made sure that the server (computer object) has full control under NTFS permissions.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
The full path even down to the file.exe or .msi in other cases is under 256 characters long and in most instances under 100 characters long.
Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Both the primary site and the distribution point have plenty of disk space (in excess of 100GB).
I have tried changing the UNC path to the local path on the server as suggested here: http://social.technet.microsoft.com/Forums/en-US/87d35966-9f12-455e-854f-d3d07760acb3/having-dp-issues-event-2302?forum=configmgrsum, however I noticed that when I tried to set it to the local path on the server instead of UNC it reverts back. I removed the program in this instance and recreated it, unfortunately it produced same result where it reverts back to the UNC path instead of the local path. The packages I have created lately have no issue they point to the local path.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Hello everyone, I got handed our SCCM enviornment until we get a new guy to fill in and have been trying to keep things in running order, but had some trouble as of lately. I am getting 1000s of error 2302 and 2348 events everyday and am trying to fix them, below is one example:
In this case I tried the following troubleshooting steps:
Locate the package, SSS000B7, it is an older version of Java, I right click on it, update distribution points, at the prompt that asks me to conform update distribution points I click yes. No dice.
Possible cause: Distribution manager does not have access to either the package source directory or the distribution point.
Solution: Verify that distribution manager can access the package source directory/distribution point.
I have tracked down the folder that it is part of and made sure that the server (computer object) has full control under NTFS permissions.
Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system.
Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility.
The full path even down to the file.exe or .msi in other cases is under 256 characters long and in most instances under 100 characters long.
Possible cause: There is not enough disk space available on the site server computer or the distribution point.
Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point.
Both the primary site and the distribution point have plenty of disk space (in excess of 100GB).
I have tried changing the UNC path to the local path on the server as suggested here: http://social.technet.microsoft.com/Forums/en-US/87d35966-9f12-455e-854f-d3d07760acb3/having-dp-issues-event-2302?forum=configmgrsum, however I noticed that when I tried to set it to the local path on the server instead of UNC it reverts back. I removed the program in this instance and recreated it, unfortunately it produced same result where it reverts back to the UNC path instead of the local path. The packages I have created lately have no issue they point to the local path.
I saw someone else on this forum previously getting event 2302, http://www.windows-noob.com/forums/index.php?/topic/2423-sms-distribution-manager-failed-to-process-package/?hl=2302 and tried to turn off bits last night to see if this would help alleviate this issue, however it didn't.
Has anyone run into this before, if so can you shed some light on how to fix it?
Share this post
Link to post
Share on other sites