Jump to content


  • 0
wiggum123

System Center 2012 DPM Permissions error NO_PARAM

Question

Hey Guys

I've got an odd problem with System Center 2012 Data Protection Manager. When trying to protect a machine if you select the C:\ drive the following error appears;

dpm_error.JPG
I have tried this on the following OS's;

2003 x86, 2008, 2008 R2, 2012 R2, Windows 7 x64

This also occurs on the DPM server itself, it cannot access its own C:\ to backup

Other drives are fine, as is system state and SQL backups (which are stored on C:\)

I have tried;

  • Removing Antivirus
  • Restarting both DPM server and client machine
  • Reinstalling DPM agent and installing agent on a machine which has never been managed by DPM (account used to install is domain admin). Every time the agent comes back as OK
  • Removed all GPO's from the DPM server
  • Used psexec to run a cmd.exe as system to check file permissions

  • Installed all updates to windows and DPM, running v 4.2.1297.0

Have tried these technet articles;

Its installed on a Windows 2012 R2 Server with SQL 2012. There is nothing else installed on the machine and has been built from scratch for this purpose.

No amount of googling has brought me any joy... I do hope someone has seen this before and can help me out!!

Thanks

Ben 

 

Share this post


Link to post
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

Join the conversation

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

Guest
Answer this question...

×   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.