Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Again 0x80004005 - Unspecified error

Created: 08 Jul 2013 • Updated: 10 Jul 2013 | 5 comments
This issue has been solved. See solution.

Running Backup 2012 on w 2k8R2 64bit with followin

patches: SP1, Hotfix 180964, 199866, 200433, 199190.

no internet-access, no live-update.

Article:TECH53004 is not applicable, because already done so. Still receive this error,

but sometimes the bakcup is fine, next day backup failed. Is there any other solutions

availabel? Can't believe I'm the only one recieving this error.

Operating Systems:

Comments 5 CommentsJump to latest comment

Colin Weaver's picture

0x80004005 actually translates as Access Denied and can be directly linked to what you get back if you type

NET HELPMSG 5

into a command prompt

Access Denied does not however always mean a credentials issue it can mean something no longer exists in the specified location, so when we try and access it the file system returns a generic access denied error code because it is not that to give access to.

To fix this issue you will probably have ot start looking into debug logging and a formal support case for us to assist you.

BTW Hotfix 199190 was withdrawn due to technical issues and replaced by Hotfix 201596. We have also released Hotfixes 203574 and 205111 since then

bandit61's picture

Downloaded these hotfixes and will install them today before backup. Annoying is, during the night job fails with "unspecified error", in the morning I rerun the failed job and it finish successful. 

So let's see what happens tonight.

thanxs

lmosla's picture

Are your jobs still failing?  If they are check in Windows events to see if there is anything running during the backup times that are causing a conflict.

Gurvinder Rait's picture

Check if Checkpoint Restart is enabled for the jobs. Try unchecking CPR and then restart the services and retest the job.

bandit61's picture

Installed the 3 patches 201596, 203574, 205111 on the cas-server and on the managed server. updated the agents on the failing servers and that did it. All backups went thru like expected. Hope it stays like that for the future, because this behaviour appeared and disappeared befor. 

SOLUTION