Jump to content


pccarrick

Package Fails To Update Distribution Point

Recommended Posts

Hi i am currently having an issue with Autocad Admin package not being able to get it to update and 2 of my distribution points. The size of the package is 5gig I have 1 Primary server with 4 distribution points on other sites. I have it replicated to two of them but i am unable to get it to replicate correctly to the other 2 sites.

I have tried using the distribution Point as a pull DP but this fails, tried a normal DP which also fails and i have now tried setting it as a pre-staged DP and this is also failing when i try extracting on the server.

 

The error messages i am getting is the standard i guess for a failed Package on a Normal DP which is

 

Possible cause: Site server does not have sufficient rights to the source directory.
Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.

Possible cause: There is not enough disk space available on the distribution point.
Solution: Verify that there is enough free disk space available on the distribution point

 

For the PreStage DP i get the below error's

 

Prestangedcontent.log

 

<![LOG[CFileLibrary::GetFullName failed; 0x80070003]LOG]!><time="23:17:11.756-480" date="09-25-2013" component="PrestageContent" context="" type="3" thread="4196" file="filelibrary.cpp:862">
<![LOG[CFileLibrary::SetFileUser failed; 0x80070003]LOG]!><time="23:17:11.756-480" date="09-25-2013" component="PrestageContent" context="" type="3" thread="4196" file="filelibrary.cpp:935">
<![LOG[CContentBundle::ExtractContentBundle failed; 0x80070003]LOG]!><time="23:17:11.761-480" date="09-25-2013" component="PrestageContent" context="" type="3" thread="4196" file="contentbundle.cpp:1378">
<![LOG[ArchiveFile::ExtractFile failed; 0x80070003]LOG]!><time="23:17:11.770-480" date="09-25-2013" component="PrestageContent" context="" type="3" thread="4196" file="archivefile.cpp:3280">
<![LOG[ArchiveFile::ExtractContent failed; 0x80070003]LOG]!><time="23:17:11.770-480" date="09-25-2013" component="PrestageContent" context="" type="3" thread="4196" file="archivefile.cpp:2551">
<![LOG[End ====> Wed Sep 25 2013 23:17:11]LOG]!><time="23:17:11.774-480" date="09-25-2013" component="PrestageContent" context="" type="1" thread="4196" file="log.cpp:86">

 

 

I have done a validation of the pre-staged package using the extract to

 

No prestaging content has been done.
The content prestaging file has been succefully verified.
Nothing found that prevents prestaging of content on this system
.

 

 

I am really out of idea's on this and can't understand why it works for for some and not others. The only thing i can think is that the path is to deep but i guess if this was the case it would be the same for all servers.

Any help and advise is really welcome to help me get around this problem

 

Thanks In Advance

 

 

Share this post


Link to post
Share on other sites

I have since found using process monitor that when it fails it appears to fail with path not found. It appears to be converting the path to chinese char's for some reason. Both distribution point i am having trouble with is located in Asia but has no settings configured with these char's.

Can anyone shed any light on why this would happen ???? Please see attached screenshot of what is happening.

 

 

post-19969-0-88284200-1380698240_thumb.jpg

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.