Hi All,

In my SCCM 2012 environment, we have SCCM 2012 SP1 (CAS & PRI). Database for CAS and PRI is on different server(SQLDATABASESERVER) with SQL 2008 R2 SP1 CU6. Backup is getting failed on CAS and PRI both.

SCCM 2012 backup is getting failed with the below error message.

Warning: SQL installation root directory is empty.The registry key "SOFTWARE\Microsoft\MSSQLServer\Setup\SQLPath" (populated by ConfigMgr setup) was found empty.

After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_BACKUP.

Error: VSS_E_WRITERERROR_TIMEOUT. Error Code = 0x80,042,3f2.

ERROR: SQL Backup task failed. Error message - Error: SQL Writer not found.

STATMSG: ID=5052 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=CASSERVER.gk.world.pmpi.com SITE=HM0 PID=1436 TID=11636 GMTDATE=Sat Apr 27 21:15:46.827 2013 ISTR0="\\SQLDATABASESERVER" ISTR1="CM_HM0;" ISTR2="Error: SQL Writer not found." ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Error: Sql Server could not prepare for the Backup.

Current state of SQL backup: [failed]. Aborting it.

SMS_SITE_BACKUP failed. Please see previous errors.

STATMSG: ID=5060 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=CASSERVER.gk.world.pmpi.com SITE=HM0 PID=1436 TID=11636 GMTDATE=Sat Apr 27 21:15:47.097 2013 ISTR0="Error: Sql Server could not prepare for the Backup." ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Raised backup task failure alert.

Troubleshooting done below:

Service checked on CASSERVER:

SMS_SITE_VSS_WRITER service is in started mode.

Volume Shadow Copy is manual and stopped.

SQL Server VSS Writer service is started.

Services checked on SQLDATABASESERVER:

SMS_SITE_SQL_BACKUP_CASSERVER.gk.world.pmpi.com service is started.

SQL Server VSS Writer service is started.

Volume Shadow Copy is manual and stopped.

NT AUTHORITY\SYSTEM and gk\CASSERVER accounts are sysadmin on SQL Server.

What else I can check to resolve this issue.

Stop using the built-in configMgr backup and use SQL backup instead. That's all you need for restore, and it's less complex to troubleshoot the backup process.

Kent,

Nice recommendation to reduce backup size but how can we manage site server information backup which is included in the configuration manager build in backup . do you have any recommendation for this or is this something which we can ignore ?

Regards,

Vinu

You do not need any additional information.

As per Kent's earlier statement you can restore from a database backup - this is fully supported.

Thanks Tim

Regards,

Vinu