Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Failed to create a folder to which to publish the package

Created: 13 Mar 2010 | 12 comments
anthonymel's picture
0 0 Votes
Login to vote

We just replicated our old End Point Protection Manger server (11.5) over to our new Windows 2008 R2 server.  We assigned all our polices over to the new server and took down the old server.  We removed the old server from the replication lists and policy lists.  All client now use the new server for policy and updates.

However, the new server can't proccess any liveupdates.  All attempts come back with a return code of 1.  At the same time liveupdate is running I also see this error "Failed to create a folder to which to publish the package" which to means that it can't save the updates to publish to clients.  I gave the Authenticated users full control over the symantec  end point protection manager folder under Program Files (x86) as well.

Anyone have ideas on resolving this?  I rather have my clients protected.

Comments

anthonymel's picture
13
Mar
2010
0 Votes 0
Login to vote

Ok so apprantly the new

Ok so apprantly the new server needed that 2010 patch.  After applying it, it looks like it got the new defs. However I still think that other problem still exsist with "Failed to create a folder to which to publish the package" 

Does any of this make sense to anyone out there?

pete_4u2002's picture
13
Mar
2010
0 Votes 0
Login to vote

check that the following

check that the following directory exists, if it does not then this might the error message you might see.

SEPM installed drive:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\ClientPackages

anthonymel's picture
14
Mar
2010
0 Votes 0
Login to vote

Yes the folder exists.  Still

Yes the folder exists.  Still getting those errors.  I'm pretty sure its attempting to download some old client software.  Probably just something I need to clean out of the database.

anthonymel's picture
13
Mar
2010
0 Votes 0
Login to vote

So I'll just continue to

So I'll just continue to update my own problem.  The server is now updating virus def correctly however my original problem is still there.  I also noticed the following error now in my windows logs.

" LiveUpdate returned a non-critical error.  Available content updates may have failed to install."

Also every now and then I see a message about a binary file with a long GUID show up as not being found.

I'm pretty sure someone out there know hows I can clean out my packages or something similar.

anthonymel's picture
13
Mar
2010
0 Votes 0
Login to vote

 This is the other message

 This is the other message that I'm seeing

"The binary file[5FD4C2B2C52AC7CB8591454F941A22F8] referred at the physical file[170F16BD7F7C09E448967BCF346E04A7], which is referred at the software package[4209DCACED66213A52DB822FCD5D1C80,Symantec Endpoint Protection (version 11.0.4000.0) for WIN32BIT], does not exist.  [Site: PVRHS Site]  [Server: citadel]":

AravindKM's picture
14
Mar
2010
0 Votes 0
Login to vote

Whether MR4 package is

Whether MR4 package is present in the server (Admin--->install packages)?
Whether your clients are able to receive the updates? 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

HappyAdmin's picture
14
Apr
2010
0 Votes 0
Login to vote

Having same 'failed to create a folder' issue

I have trie all the options I can find on the net, mind you they're aren't many. 
-The folder for the packages exists
- all permissions are wide open
- its a new install of SEP 11 on Server 2003
I'm pulling out my hair as to what this issue is and how to fix it, no one seems to know.  Any new information out there?

Citlali's picture
14
Apr
2010
0 Votes 0
Login to vote

Delete the MR4 package

Since you replicated one SEPM to the other, my guess is that you didn't replicate over the installation packages.  So your old SEPM had an MR4 package in the database but the new one doesn't since it was a fresh RU5 installation.  Since the SEPMs are no longer replicating, you won't be able to get that package.  You probably just need to delete the MR4 package referenced under Install Packages and the messages will go away. 

Citlali's picture
14
Apr
2010
0 Votes 0
Login to vote
HappyAdmin's picture
15
Apr
2010
0 Votes 0
Login to vote

I personally did not

I personally did not replicate.  As stated this is a new install of server 2003 and a new install of SEP 11.  I have no additional packages under Admin - Install other than the original two, which I cannot delete as they state 'latest package'.  But every 5 minutes I get 'failed to create a folder' followed by 'ziputil.unzipfile returned false'. What folder is this trying to create or look for? I think I'm about to give up on this package and go back to good 'ol Corp. SAV.

zerofai's picture
04
Aug
2010
0 Votes 0
Login to vote

Wired way to fix

On a 2003 R2 SP2 server, I face the same problem too.
How I resolve is redownload the source (the original source is from a Laptop > USB > Server), the new source is download the source from server directly.
And the server works.
Hope this help.

BSharpe's picture
24
Aug
2010
0 Votes 0
Login to vote

Had the same issue. You will

Had the same issue. You will notice when you get the error message symantec is trying ot update 2 folders. Both folders load a "full.zip" file and a "full.zip.sig" file in the locations "78648e9d1817017948dc9cc600823543" and "1b42208a6dc8ff67b9a65370351a0457" .

This file then normally would make a "full" folder to extract the file into. From what I saw is the LiveUpdate would fail to make the folder then it reports this error message. To resolve the issue this is what I did.

Created a folder called: "full"   in the following locations

C:\Program Files\Symantec\Symantec Protection Center\Inetpub\ClientPackages\1b42208a6dc8ff67b9a65370351a0457

C:\Program Files\Symantec\Symantec Protection Center\Inetpub\ClientPackages\78648e9d1817017948dc9cc600823543

After doing this the zip file would extract to the location and work.

Hope this helps.