ScottGill
Posts: 31
Score: 0
Joined: 3/1/2007
Status: offline
|
OK this is a new one for me. Yesterday while I was attempting to make an update to one of my WinPE boot images the site server took a dump on me. After going through the painstaking process of rebooting it getting the network working again, and then reinstalling WDS and PXE (On a second server which had other issues, not responding etc...). I got everything up again and started to redistribute the PE image... Everything seemed fine at first, but now I'm getting errors distributing this package. (BTW, this system is not in production yet, just deploying it and in some ways using it for test/learning purposes).
At first I thought there was a server issue (I had also done some other config changes regarding NTFS permissions and IIS config to fix issues with WSUS). So thinking there was some kind of server issue I proceeded to undo some of the changes I had done, which of course did not resolve the problem and just ended up breaking WSUS again. Then I thought there was permissions issues with the DP's, so I tried a different package and everything worked fine.
Fast forward to now, and only this one package is having this problem, all other packages can distribute just fine. The part I can't figure out is how it distributes to one distro point just fine, but won't go out to any of the others. I'm completely stumped, I've never seen anything like this before. Anybody have any ideas?
This is the error showing up in the status:
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone *** 7/10/2008 4:43:07 PM SITESERVER SMS_DISTRIBUTION_MANAGER 2328 SMS Distribution Manager failed to copy package "***00001" from "D:\Program Files\Microsoft Configuration Manager\osd\boot\i386\boot.***00001.wim" to "MSWNET:["SMS_SITE=***"]\\SERVER\SMSPKGD$\***00001\". Possible cause: SMS Distribution Manager does not have sufficient rights to read from the package source directory or to write to the destination directory on the distribution point. Solution: In the SMS Administrator console, verify that the site system connection accounts have sufficient privileges to the source and destination directories. 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 package files on the distribution point, disconnect the users first. 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 distribution points" box in the Data Access tab of the Package Properties dialog box. Possible cause: The distribution point does not have enough free disk space to store the package. Solution: Verify that there is enough free disk space. 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.
Oh, and here's what my console looks like (with server names removed):
http://img84.imageshack.us/my.php?image=consolehu8.jpg
< Message edited by ScottGill -- 7/10/2008 8:15:07 PM >
|
Printable Version
Weird issue with package - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread