Jump to content


rotem

SMS Distribution Manager failed to process package

Recommended Posts

hello, i installed a new DP for my sccm site, i had few problems but i fixed them (PXE,share...) i manage to copy my boot images into the dp just fine...

but im having a problem that i cant solve , im trying to transfer one of my win7 images and im keeping getting failure events..

here is the major one i think , from the SMS_DISTRIBUTION_MANAGER query status messgae viewer:

 

SMS Distribution Manager failed to process package "ver 5.6_220810_1330" (package ID = IL00004E).

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.

 

 

and here is the 2nd error that it shows:

 

Failed to create virtual directory on the defined share or volume on distribution point "["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\".

 

Possible cause: Distribution Manager requires that IIS base components be installed on the local SMS Site Server in order to create the virtual directory. Distribution Manager also requires that IIS Web Services be installed on the Distribution Point Server that needs to support Background Intelligent Transfer Service (BITS).

Solution: Verify that IIS base components are installed on the local SMS Site Server, and IIS Web Services are installed on the Distribution Point Server.

 

i installed BITS on the DP (running on server 2003 r2)..

 

thanks for the help!

Share this post


Link to post
Share on other sites

well IIS is installed , i think its configured correctly ...im not sure 100% what is need to be config ...

the DP is standard not a branch, and its a standard server not a share (i didnt config it as a share , but he use one for the PXE role)

dismgr gave me a weird error..but now its gone and another one replaced it:

 

for ["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\, machine account is to be used SMS_DISTRIBUTION_MANAGER 3/10/2011 1:24:57 PM 4060 (0x0FDC)

STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=ILTLV0010 SITE=IL0 PID=2376 TID=4060 GMTDATE=Thu Mar 10 11:24:57.056 2011 ISTR0="Win 7 Unattended" ISTR1="["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="IL000037" AID1=404 AVAL1="["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\" SMS_DISTRIBUTION_MANAGER 3/10/2011 1:24:57 PM 4060 (0x0FDC)

Established connection to ["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\ SMS_DISTRIBUTION_MANAGER 3/10/2011 1:25:39 PM 4060 (0x0FDC)

Signature share exists on distribution point path MSWNET:["SMS_SITE=IL0"]\\ild529\SMSSIG$\ SMS_DISTRIBUTION_MANAGER 3/10/2011 1:27:18 PM 4060 (0x0FDC)

The distribution point ["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\ doesn't point to an existing path. SMS_DISTRIBUTION_MANAGER 3/10/2011 1:27:18 PM 4060 (0x0FDC)

Edited by rotem

Share this post


Link to post
Share on other sites

well IIS is installed , i think its configured correctly ...im not sure 100% what is need to be config ...

the DP is standard not a branch, and its a standard server not a share (i didnt config it as a share , but he use one for the PXE role)

dismgr gave me a weird error..but now its gone and another one replaced it:

 

CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

CWmi::Connect() failed to connect to \\ild529\root\MicrosoftIISv2. error = The RPC server is unavailable. SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

ERROR DPConnection::ConnectWMI() - Failed to connect to ILD529. error = 0x800706ba SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

STATMSG: ID=2344 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=ILTLV0010 SITE=IL0 PID=2376 TID=2484 GMTDATE=Thu Mar 10 07:23:24.422 2011 ISTR0="["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\" SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

ERROR CheckDPforDrizzle: Could not find the desired DP ["Display=\\ild529\"]MSWNET:["SMS_SITE=IL0"]\\ild529\ in the SCF SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

Cannot set the current Drizzle Role status for the DP. SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

Error occurred. SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 01/01/1601 12:00:00 AM 2484 (0x09B4)

Share this post


Link to post
Share on other sites

Hi,

 

Just had the same problem. All worked fine until we implemented Firewall rules via policies last week. I found this link "http://scug.dk/blogs/configurationmanager/archive/2009/09/22/hmmm-the-firewall-once-again.aspx". I only changed this FW rule on the DP server, not the primary site server and everything started working again.

 

Very strange because I can not find any documentation (yet) from MS which states that we need this rule.

 

Hope this helps.

 

Rgds, Ton

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

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.