Support Tip: A Backup Site Server maintenance task may fail to run in ConfigMgr 2012

toolsignUPDATE: This issue has been fixed beginning with System Center 2012 Configuration Manager Service Pack 1 (ConfigMgr 2012 SP1).


In System Center 2012 Configuration Manager, the ‘Backup Site Server’ maintenance task may fail if the Backup Destination is set to a network share. An example is below:


When this happens, the following errors are logged:


Error: Backup folder \\MachineName\1234 does not exist or backup service does not have permission to access the folder.



Error: Backup folder \\MachineName\1234 does not exist or backup service does not have permission to access the folder.

If you look at the network share you see that the folder does exists and permissions are correct. So why does it fail? To know more, please download Procmon tool from here and capture a trace on both SQL and ConfigMgr site server with following filters while running the backup:

Process Name is ‘SMSSQLBkup.exe’
Process Name is ‘SMSBkup.exe’



Once you see the error(s) mentioned at the start of this post, please stop the trace and look at the result.


If you look closely enough at Path column the backup task triggers a CreateFile operation on \\MachineName\123 which doesn’t exist. The correct path is \\MachineName\1234 . It drops the last character ‘4’ and as a result the backup task fails to complete successfully.

At the moment you can choose to use any of the following three workarounds to get the backup task to work.

1. Create a sub-folder under existing folder and configure the backup task accordingly. For example:


2. Save the files on local drive.

3. Create and use a network share on SQL Server instead.

NOTE This issue is schedule to be addressed in Service Pack 1

Additional information on Backup Site Server task can be found here.

Other links of interest:

The System Center 2012 Configuration Manager Survival Guide (en-US):

System Center 2012 Configuration Manager SDK:

Karan Rustagi

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog:
ConfigMgr Support Team blog:
DPM Team blog:
MED-V Team blog:
Orchestrator Support Team blog:
Operations Manager Team blog:
SCVMM Team blog:
Server App-V Team blog:
Service Manager Team blog:
System Center Essentials Team blog:
WSUS Support Team blog:

The Forefront Server Protection blog:
The Forefront Endpoint Security blog :
The Forefront Identity Manager blog :
The Forefront TMG blog:
The Forefront UAG blog:

Comments (15)
  1. Anonymous says:

    I have this issue …and now solved 🙂 thank you people

  2. Anonymous says:

    This is still true within SCCM 2012 R2. Creating a subfolder fixed the issue. It’s still removing the last character of the share (\servershare looks like \servershar in procmon)

  3. Anonymous says:

    SQL server running on another server. Had the same error but creating the sub-folder didn't work. Procmon was showing access denied for System account to UNC share for smssqlbkup.exe process. Fixed by granting change share permission to System account for UNC share.

    Also, before I was getting SMS Writer does not exist. vssadmin list writers didn't show it.  Fixed by grating sql sysamin role to System login. Hope this helps someone!

  4. This is insane. We’re running 2012 R2 latest updates etc and this is still an issue.

    Remote SQL backup fails to connect to the UNC share. Eventually I remembered this issue from *years* ago but initially dismissed it thinking there was no way it would still be a problem, but when I noticed recent comments from people still having it I tested anyway and yes, a subdirectory fixes it.

  5. king says:

    Why would adding a sub folder fix the dropping of the last character?  Is there a bug where it only checks the first 3 letters?

  6. nandfred says:

    Even with SP1 this is still an issue. after creating the subfolder in the share, sitebackup worked.

    Ofcause i had to let the sql and site server/users have write access.

  7. Robert Marshall says:

    If the shares called XYZ and ConfigMgr truncates to XY, then just call the share XY as another work-around.

  8. ArturG says:

    I want to kick that person who is responsible for that one. It is SCCM 2012 R2 and that issue is still in place.

  9. Anonymous says:

    Pingback from SCCM 2012 SP1 Site Backup and Afterbackup.bat ← Stephan Wibier

  10. Annoyed says:

    Two years later and an R revision and this isn’t fixed? Seriously?

  11. Rick says:

    Are there any benefits to running the built in maintenance task in ConfigMgr 2012 vs using the SQL backup which gives you compression? Are any extra files backed up with the built in task?

  12. ed.daivs says:

    This has got to be the silliest thing I have ever seen. Create a share on dpm F:sccmm then in site maintenance in sccm \dpmsccmm -.- Anyway…on to the next sccm “fix” \THANKS!!

  13. Richard says:

    Yep, this is still an issue in ConfigMgr 2012 R2. Backup issue is resolved when creating a subdirectory as described above.

    PS: Will try installing CU4 over the weekend and report back if the issue this resolves the backup issue without need for subdirectory.

  14. Steve Hobday says:

    I would like to thank the author. I had this issue with *some* servers on my SCCM 2012 R2 CU5 installation. I spent a lot of time (or wasting) thinking I had access rights issues (I have my SCCM administrators and server infrastructure in 2 AD groups where
    are add to NTFS share permissions). The share name of \serversmsbackup was specified but the using Process Monitor showed that the last "p" was being dropped. Add the sub-folder resolved this issue. Obviously the problem STILL exists in R2 CU5. How disappointing.
    Hope this sheds some light for others.

  15. Anon2 says:

    CM 2012 R2 SP1 CU3

    Just ran into the same problem as one of the commenters.
    If you are running SQL on a separate server make sure you give the domain/server$ account write access to your backup directory.

    Thank you for original post.
    Following your process using procmon gave me the answer.
    Much appreciated.

Comments are closed.

Skip to main content