After moving our sql database from a clustered to an non-clustered environment we are unable to successfully execute the database backup task. We receive among the noteable errors is one stating "Couldn't connect to \\SQLServer registry". Below please find the full contents of the log. Thanks for your help and time.

****LOG START HERE****

Initializing the status message reporting system...          SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

  The path to the "Status Manager" inbox is "E:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".          SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

   SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.           SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Registered this process as a source of "SMS Server" events.    SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Registered this process as a source of "SMS Client" events.      SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Registered this process as a source of "SMS Provider" events. SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Status message reporting system initialized successfully.          SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

Locale set to OS value (English_United States.1252).     SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

SMS site backup service 4.00 started.   SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:14.158 2013 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

05/21/13 17:33:14 - starting backup.      SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

BackupDir = Q:\BACKUPS.      SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

Installation RootDir = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER.  SMS_SITE_BACKUP     5/21/2013 5:33:15 PM      2536 (0x09E8)

Site SQL Dir = .SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

Site Backup Location = \\matl20\backups$        SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

SQL Backup Location = \\matl20\backups$       SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:15.345 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0     SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879)SMS_SITE_BACKUP     5/21/2013 5:33:15 PM      2536 (0x09E8)

Starting VSS initialization...       SMS_SITE_BACKUP     5/21/2013 5:33:16 PM   2536 (0x09E8)

Starting Asynchronous GatherWriterMetadata.   SMS_SITE_BACKUP     5/21/2013 5:33:16 PM   2536 (0x09E8)

Number of writers that responded: 10.   SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Reading SMS Writer metadata...           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Number of FileIncludes: 0.        SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Number of FileExcludes: 0.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Number of Components: 7.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Component 0 - KS1Backup\SiteServer\SMSServer\inboxes.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM      2536 (0x09E8)

Component 1 - KS1Backup\SiteServer\SMSServer\Logs.           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 2 - KS1Backup\SiteServer\SMSServer\data.SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 3 - KS1Backup\SiteServer\SMSServer\srvacct.        SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 4 - KS1Backup\SiteServer\SMSbkSiteRegNAL.dat.  SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 5 - KS1Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 6 - KS1Backup\SiteDBServer\SMSbkSQLDBsite.dat.          SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Dependency On SQL Writer , LogicalPath:\\DATLCL19SQLI3\I3, ComponentName:SMS_KS1      SMS_SITE_BACKUP           5/21/2013 5:33:22 PM    2536 (0x09E8)

After GatherWriterMetadata SMS Writer status = STABLE.          SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Starting to clean and prepare the backup location.         SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Cleanup and/or preparation done.         SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Info: Sending message to start the SQL Backup...         SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Couldn't connect to \\DATLCL19SQLI3 registry  SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

STATMSG: ID=5049 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:23.220 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0     SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Error: Failed to send start message to the SqlBackup.   SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Error: CreateSnapshotSet failed...         SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:23.455 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0     SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

SMS site backup failed. Please see previous errors.      SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Steven RUshin

I have 3 primary servers all running Windows 2008 R2 64 bit with SCCM 2007 SP1 R2. All have local databases on SQL server 2008 64 bit.

The internal SCCM backup routine has been running perfectly on all three for weeks. Now, for reasons unknown, one of them is failing every time with the following error written in the log: "SMS Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. Please verify that the SMS Writer service is up and running."

If I list the VSS writers, SMS Writer is indeed missing. I can manually add it back in, or restarting the VSS Writer component adds it back in too - but the backup still fails with the same error next time round.

There have been no changes to this one server that could affect it, and the other two servers are still backing up fine. Any ideas please??

Hi Team,

we are facing the Issue during the Central Server SCCM Backup. SQL Backup is failing. Please help us on this.

Error Details.

ERROR: SQL Backup task failed. Error message - Failed to copy the database files to the backup location. Please ensure that the SMS_SITE_SQL_BACKUP component has access to the backup location.

STATMSG: ID=5052 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=XXXXXXX SITE=CEN PID=3528 TID=1924 GMTDATE=Tue Jan 08 06:20:15.633 2013 ISTR0="\\SQLCLUSTER" ISTR1="SMS_CEN" ISTR2="Failed to copy the database files to the backup location. Please ensure that the SMS_SITE_SQL_BACKUP component has access to the backup location." ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Error: SQL Backup failed...

Error: Backup Failed  for Component - CENBackup\SiteDBServer\SMSbkSQLDBsite.dat.

Recently we have moved our DB from local server to seperate server after that we are facing this problem kinldy help me on this

Regards,

Prabhaharan

I'm new to SMS/SCCM and have a few questions. We have a new SCCM install with 1 Central and 1 primary server with 8000 workstation.

My understanding is the only supported way of recovering from a SCCM failure is from the Backup Maintenance task within SCCM. Is there any maintenance that needs to be done within the SQL server? The reason I'm asking is my trans logs were growing out of control and I put in a SQL maintenance plan to backup and truncate.

Am I missing something? I assumed that if SCCM was doing the maintenance that it would take care of this also...

What is the proper way to keep this under control but still fully supported.

Thanks

Hi

i am getting the below error on primary site server smsbkp.log

Dependency On SQL Writer , LogicalPath:\\SQL-SERVER\DB02, ComponentName:CM_PS1  $$<SMS_SITE_BACKUP><02-22-2013 04:06:34.521+300><thread=4660 (0x1234)>
After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_BACKUP.  $$<SMS_SITE_BACKUP><02-22-2013 04:06:34.662+300><thread=4660 (0x1234)>
~Error: VSS_E_WRITERERROR_TIMEOUT. Error Code = 0x80,042,3f2.  $$<SMS_SITE_BACKUP><02-22-2013 04:06:34.662+300><thread=4660 (0x1234)>
~Info: Sending message to start the SQL Backup...  $$<SMS_SITE_BACKUP><02-22-2013 04:06:34.662+300><thread=4660 (0x1234)>
Starting Prepare for backup.   $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.037+300><thread=4660 (0x1234)>
The System Provider VSS ID is 0,000,000,000,364,F68  $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.084+300><thread=4660 (0x1234)>
Added volume containing C:\ to the snapshot set.  $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.412+300><thread=4660 (0x1234)>
~Info: Starting Asynchronous PrepareForBackup...  $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.412+300><thread=4660 (0x1234)>
~Info: Asynchronous PrepareForBackup finished...  $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.803+300><thread=4660 (0x1234)>
After PrepareForBackup SMS Writer status = STABLE.  $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.943+300><thread=4660 (0x1234)>
~Info: Waiting for SQL to PrepareForBackup.  $$<SMS_SITE_BACKUP><02-22-2013 04:06:35.943+300><thread=4660 (0x1234)>
Sleeping for 5 seconds...  $$<SMS_SITE_BACKUP><02-22-2013 04:06:36.115+300><thread=4660 (0x1234)>
ERROR: SQL Backup task failed. Error message - Error: Backup folder \\PRISITESERVER\Backup does not exist or backup service does not have permission to access the folder.   $$<SMS_SITE_BACKUP><02-22-2013 04:06:41.178+300><thread=4660 (0x1234)>
STATMSG: ID=5052 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=PRISITESERVER SITE=PS1 PID=10980 TID=4660 GMTDATE=Fri Feb 22 09:06:41.193 2013 ISTR0="\\SQL-SERVER" ISTR1="CM_PS1;" ISTR2="Error: Backup folder \\PRISITESERVER\Backup does not exist or backup service does not have permission to access the folder. " ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_SITE_BACKUP><02-22-2013 04:06:41.193+300><thread=4660 (0x1234)>
StateTable::CState::Handle - (5052:3 2013-02-22 09:06:41.193+00:00) >> (5035:1 2013-01-02 09:20:01.533+00:00)  $$<SMS_SITE_BACKUP><02-22-2013 04:06:41.225+300><thread=4660 (0x1234)>
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='EF736CF9-7214-4796-9C85-2549A9056D8D' SID=5052 MUF=0 PCNT=2, P1='PS1' P2='2013-02-22 09:06:41.193+00:00' P3='' P4='' P5=''  $$<SMS_SITE_BACKUP><02-22-2013 04:06:41.240+300><thread=4660 (0x1234)>
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\se4yf11w.SMX   $$<SMS_SITE_BACKUP><02-22-2013 04:06:41.334+300><thread=4660 (0x1234)>
Successfully send state change notification EF736CF9-7214-4796-9C85-2549A9056D8D  $$<SMS_SITE_BACKUP><02-22-2013 04:06:41.334+300><thread=4660 (0x1234)>
Error: Sql Server could not prepare for the Backup.

i have verified the following things found ok

verified the site server system account is part of local admin grp of SQL server

verfied that the SQL server has necessary permission on site server bakup folder share

also i am seeing the below error related to vss writer

Writer name: 'SMS Writer'
   Writer Id: {03ba67dd-dc6d-4729-a038-251f7018463b}
   Writer Instance Id: {7246d834-8601-4c17-aedb-c47dbacc8a3a}
   State: [7] Failed
   Last error: Timed out

can some help me out to resolve the backup issue

MSB

I'm upgrading five site servers to new hardware and 64 bit Server 2008.

I've got some excellent documentation that covers everything but the SQL server part.

Moving SCCM server to new hardware:

http://kobile.wordpress.com/2010/10/10/moving-sccm-server-to-new-hardware/

Is it possible to upgrade to a newer version of SQL at the same time.  From SQL 2005 sp4 32bit to SQL 2008 64 bit?

If not how about from SQL 2005 sp4 32 bit to SQL 2005 sp4 64 bit?

Thanks for any help or redirection.

Good morning,

We have SCCM 2007 SP2 with R3 installed on Windows Server 2008 R2 Enterprise x64.  This system has been running since Oct 2008 and we have not updated it since installing R3 in 2010.

Once, in 2009, the "Backup ConfigMgr Site Server" task failed and I found "Error: SMS Writer not found." in the smsbkup.log.  I found a post in this forum which suggested restarting "SMS_SITE_VSS_WRITER."  I did that and the backups started working again.  Yesterday, I found the same issue - "Error: SMS Writer not found." in the smsbkup.log.  vssadmin list writers also did not show the writer.  Again, I restarted the "SMS_SITE_VSS_WRITER" service and checked vssadmin.  The following was listed:

Writer name: 'SMS Writer'
   Writer Id: {03ba67dd-dc6d-4729-a038-251f7018463b}
   Writer Instance Id: {63cdb7e1-a819-4c4f-ab69-304aa4ec6f90}
   State: [1] Stable
   Last error: No error

This morning, I checked the backup and it failed again, again with "Error: SMS Writer not found." in the smsbkup.log.  Again, I checked vssadmin and the writer was not listed.  I restarted the SMS_SITE_VSS_WRITER service, but don't have a lot of confidence the backup will be successful tonight.

Any suggestions on what I can check?

Thanks,

Terence Durning

Thanks & Regards,

Prabhaharan

I have setup a Windows 2008 R2 server and installed SQL Server 2008 application files in C drive. The Windows server is used to store SCCM 2007 DB, it has C, D, E (CD-ROM) and F drives.

The SCCM 2007 DB is located in D drive and I have enabled the "Backup ConfigMgr Site Sever" in SCCM. I checked that the SCCM Site backup was successful. However, I noticed that SCCM have created theF:\SMS_<SCCM Host Name> folder in the server with the following files:

F:\SMS_<SCCM Host Name>\bin\x64\smssqlbkup.exe

F:\SMS_<SCCM Host Name>\Logs\smssqlbkup.lo_

F:\SMS_<SCCM Host Name>\Logs\smssqlbkup.log

F:\SMS_<SCCM Host Name>\srvacct\srvacct.XXX (XXX is the site name)

How do I relocate this F:\SMS_<SCCM Host Name> to C or D drive ? I checked the "Backup ConfigMgr Site Sever" in SCCM and I have not reference F drive at all and I don't know how SCCM will "find out" the F drive by itself.

Hi everyone,

I have an SCCM 2007 issue, I cannot manually start a backup as the log says :

"SQL Backup is already in the running state. You must wait till the backup is completed before you can start off another backup.SMS_SITE_BACKUP"

has anyone seen this before? what do I need to do to allow this to continue? So far I have tried restarting services on the local box and the remote SQL box with no luck, I am now checking event logs..

Thank you

Hi All,

We are already taking SCCM site backup using Maintenance Task. As we know the backup includes SMS_XXX database, my question is - do we still need to take backup of that SMS_XXX database using SQL backup functionality? If yes then please help me by providing any document or link that help me to understand the requirement.

Hi SCCM Admins,

I just finished a SCCM primary site recovery on another hardware with x64 OS following backup\restore steps here"http://kobile.wordpress.com/2010/10/10/moving-sccm-server-to-new-hardware/".

But, i went through the issue that reporting role was not restored and to add this role again the wizard finishes successfully but there is no directory (SMSReporting_SiteCode) is created. Noting that ASP and webdav publishing roles are added and all configuration required for IIS7.5 is done as in Microdoft's articles.

By Conpying the folder SMSReporting_SiteCode from old SCCM and pasting it in the required directory i just got this:





any Help??????

thanks

Hi friends, I am having trouble restoring my BKF files. They are created by Symantec Backup Exec 12.0. The files are split into multiple parts, for example: 4 GB each. These files contain around 240 GB of data. Whenever I try to restore any of them, I just can't. I have no idea how to restore my BKF files. Please help me. It's urgent.

Many thanks in advance. 

Hi

I am trying to install the secondary site from primary site console.  The secondary site installation is not ontinuing.bootstrap.log is:
******************************************************************************** SMS_BOOTSTRAP 1/1/160112:00:00 AM 778 (0x030A)
Starting SMS_BOOTSTRAP. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Microsoft System Center Configuration Manager v4.00 (Build 6487) SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Copyright (C) 2005 Microsoft Corp. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Set current directory to C:\. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Successfully read C:\SMS_BOOTSTRAP.ini. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Started for the first time. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Current time: Tue Jan 29 06:07:59 2013 SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Looking for the .PKG file... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Found C:\SMS_BOOTSTRAP.pkg. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Elapsed time since startup: 0 days, 00 hours, 00 minutes, 00 seconds. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Processing the .PKG file... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Validating C:\SMS_BOOTSTRAP.pkg... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
C:\SMS_BOOTSTRAP.pkg passed validation check. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
There is enough disk space: 516MB required, 19918MB available. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Temp directory is C:\lo3rpm1n.TMP. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Decompressing C:\SMS_BOOTSTRAP.pkg... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Decompression successful. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Elapsed time since startup: 0 days, 00 hours, 03 minutes, 16 seconds. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Running SMS Setup... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Successfully parsed C:\lo3rpm1n.TMP\SMSSETUP\install.map. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
C:\lo3rpm1n.TMP\SMSSETUP\install.map build number "6487" is correct. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Started "C:\lo3rpm1n.TMP\SMSSETUP\bin\i386\setup.exe /script C:\SMS_BOOTSTRAP.ini /nouserinput" as PID 3008. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Waiting for PID 3008 to terminate... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
PID 3008 exited with code 1. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
FATAL ERROR: SMS_SITE_COMPONENT_MANAGER is not running, setup must have failed, bootstrap procedure aborted! SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deinstalling myself... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deleted temp directory C:\lo3rpm1n.TMP. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deleted C:\SMS_BOOTSTRAP.pkg. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deleted C:\SMS_BOOTSTRAP.ini. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deleted C:\SMS_BOOTSTRAP.EXE. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deinstalled the SMS_BOOTSTRAP service. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Deinstallation complete. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Bootstrap procedure unsuccessful. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
Stopping SMS_BOOTSTRAP... SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
SMS_BOOTSTRAP stopped. SMS_BOOTSTRAP 1/1/1601 12:00:00 AM 778 (0x030A)
***************************************************************

configmgrsetup.log

===================== << Starting SMS V4 SP2 Setup >> =====================
<01-29-2013 06:11:24> Commandline :
 /script C:\SMS_BOOTSTRAP.ini /nouserinput
<01-29-2013 06:11:24> This is 64 bit.
<01-29-2013 06:11:24> Verifying the Reg for AssetIntelligence Installation
<01-29-2013 06:11:24> Setting the default CSV folder path
<01-29-2013 06:11:24> SMS Build Number = 6487
<01-29-2013 06:11:24> SMS Version = 4.0
<01-29-2013 06:11:24> SMS Minimum Build Number = 800
<01-29-2013 06:11:24> Verifying SMS Active Directory Schema Extensions.
<01-29-2013 06:11:26> DS Root:CN=Schema,CN=Configuration,DC=sec,DC=co
<01-29-2013 06:11:27> Verifying SMS Active Directory Schema Extensions.
<01-29-2013 06:11:27> DS Root:CN=Schema,CN=Configuration,DC=sec,DC=co
<01-29-2013 06:11:27> The command line options are /SCRIPT C:\SMS_BOOTSTRAP.INI /NOUSERINPUT
<01-29-2013 06:11:27> Setup has detected an incomplete secondary site installation on this computer.  You can remove the incomplete secondary site installation, and run Setup again.
<01-29-2013 06:11:27> Checking download options...
<01-29-2013 06:11:27> Use ones on the site - secondary site push.
<01-29-2013 06:11:27> Setup path is C:\lo3rpm1n.TMP\SMSSETUP\bin\i386\setup.exe.
<01-29-2013 06:11:27> Cannot find C:\lo3rpm1n.TMP\SMSSETUP\redist. This could be secondary site push with no local media option.
<01-29-2013 06:11:27> This is a secondary site push without local media.
<01-29-2013 06:11:27> Validating characters in path from Program Files (x86)
<01-29-2013 06:11:27> IsValidNetBIOSName validation of 'SCCM' succeeded
<01-29-2013 06:11:29> VC redist is already installed.
<01-29-2013 06:11:29> Stopping service SMS_SITE_COMPONENT_MANAGER
<01-29-2013 06:11:29> Service SMS_SITE_COMPONENT_MANAGER is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_SQL_MONITOR
<01-29-2013 06:11:29> Service SMS_SQL_MONITOR is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_EXECUTIVE
<01-29-2013 06:11:29> Service SMS_EXECUTIVE is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_SERVER_BOOTSTRAP_SECON
<01-29-2013 06:11:29> Service SMS_SERVER_BOOTSTRAP_SECON is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_REPORTING_POINT
<01-29-2013 06:11:29> Service SMS_REPORTING_POINT is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_SERVER_LOCATOR_POINT
<01-29-2013 06:11:29> Service SMS_SERVER_LOCATOR_POINT is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS Remote Control Agent
<01-29-2013 06:11:29> Service SMS Remote Control Agent is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_SITE_BACKUP
<01-29-2013 06:11:29> Service SMS_SITE_BACKUP is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_SITE_SQL_BACKUP
<01-29-2013 06:11:29> Service SMS_SITE_SQL_BACKUP is not installed, skip it.
<01-29-2013 06:11:29> Stopping service SMS_SITE_VSS_WRITER
<01-29-2013 06:11:29> Service SMS_SITE_VSS_WRITER is not installed, skip it.
<01-29-2013 06:11:29> Attempting to stop WMI, and all dependent services.
<01-29-2013 06:11:30> Stopping iphlpsvc.
<01-29-2013 06:11:32> Stopping CcmExec.
<01-29-2013 06:12:16> Stopping WMI.
<01-29-2013 06:12:30> Creating SMS Logs directory ...
<01-29-2013 06:12:30> Creating SMS Inbox Source registry key ...
<01-29-2013 06:12:30> SMS Setup full version is 4.00.6487.2000
<01-29-2013 06:12:30> Successfully set security on Setup registry key.
<01-29-2013 06:12:30> Failed to set security on SQL Server registry key. Error: 2
<01-29-2013 06:12:30> Successfully set security on Identification registry key.
<01-29-2013 06:12:30> Creating SMS Inbox Source registry key ...
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Updating MPType and MPDefault for Secondary Site with default value.
<01-29-2013 06:12:30> Failed to set permissions on C:\Program Files (x86), GetLastError() = 5
<01-29-2013 06:12:30> Setup has encountered fatal errors while performing file operations.

I have added the site server computer account in local admins group on the secondary site and added secondary sever computer account in the site serversitetositeconnection_box but no luck can some plz help me out

Satya

james simons

After moving our sql database from a clustered to an non-clustered environment we are unable to successfully execute the database backup task. We receive among the noteable errors is one stating "Couldn't connect to \\SQLServer registry". Below please find the full contents of the log. Thanks for your help and time.

****LOG START HERE****

Initializing the status message reporting system...          SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

  The path to the "Status Manager" inbox is "E:\Program Files\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs".          SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

   SMS_STATUS_MANAGER is not running as part of this process, the SMS_EXECUTIVE to SMS_STATUS_MANAGER in-memory status message queue will not be used.           SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Registered this process as a source of "SMS Server" events.    SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Registered this process as a source of "SMS Client" events.      SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Registered this process as a source of "SMS Provider" events. SMS_SITE_BACKUP     5/21/2013 5:33:13 PM   2536 (0x09E8)

Status message reporting system initialized successfully.          SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

Locale set to OS value (English_United States.1252).     SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

SMS site backup service 4.00 started.   SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:14.158 2013 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

05/21/13 17:33:14 - starting backup.      SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

BackupDir = Q:\BACKUPS.      SMS_SITE_BACKUP     5/21/2013 5:33:14 PM   2536 (0x09E8)

Installation RootDir = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER.  SMS_SITE_BACKUP     5/21/2013 5:33:15 PM      2536 (0x09E8)

Site SQL Dir = .SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

Site Backup Location = \\matl20\backups$        SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

SQL Backup Location = \\matl20\backups$       SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:15.345 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0     SMS_SITE_BACKUP     5/21/2013 5:33:15 PM   2536 (0x09E8)

LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879)SMS_SITE_BACKUP     5/21/2013 5:33:15 PM      2536 (0x09E8)

Starting VSS initialization...       SMS_SITE_BACKUP     5/21/2013 5:33:16 PM   2536 (0x09E8)

Starting Asynchronous GatherWriterMetadata.   SMS_SITE_BACKUP     5/21/2013 5:33:16 PM   2536 (0x09E8)

Number of writers that responded: 10.   SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Reading SMS Writer metadata...           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Number of FileIncludes: 0.        SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Number of FileExcludes: 0.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Number of Components: 7.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Component 0 - KS1Backup\SiteServer\SMSServer\inboxes.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:21 PM      2536 (0x09E8)

Component 1 - KS1Backup\SiteServer\SMSServer\Logs.           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:21 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 2 - KS1Backup\SiteServer\SMSServer\data.SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 3 - KS1Backup\SiteServer\SMSServer\srvacct.        SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 4 - KS1Backup\SiteServer\SMSbkSiteRegNAL.dat.  SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 5 - KS1Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

FileGroupFile = E:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no]           SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Volume E:\ (that contains the file(s)) is marked as a candidate for snapshot.       SMS_SITE_BACKUP     5/21/2013 5:33:22 PM      2536 (0x09E8)

Component 6 - KS1Backup\SiteDBServer\SMSbkSQLDBsite.dat.          SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Dependency On SQL Writer , LogicalPath:\\DATLCL19SQLI3\I3, ComponentName:SMS_KS1      SMS_SITE_BACKUP           5/21/2013 5:33:22 PM    2536 (0x09E8)

After GatherWriterMetadata SMS Writer status = STABLE.          SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Starting to clean and prepare the backup location.         SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Cleanup and/or preparation done.         SMS_SITE_BACKUP     5/21/2013 5:33:22 PM   2536 (0x09E8)

Info: Sending message to start the SQL Backup...         SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Couldn't connect to \\DATLCL19SQLI3 registry  SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

STATMSG: ID=5049 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:23.220 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0     SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Error: Failed to send start message to the SqlBackup.   SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Error: CreateSnapshotSet failed...         SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=MATL20 SITE=KS1 PID=2484 TID=2536 GMTDATE=Tue May 21 21:33:23.455 2013 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0     SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

SMS site backup failed. Please see previous errors.      SMS_SITE_BACKUP     5/21/2013 5:33:23 PM   2536 (0x09E8)

Steven RUshin

I have 3 primary servers all running Windows 2008 R2 64 bit with SCCM 2007 SP1 R2. All have local databases on SQL server 2008 64 bit.

The internal SCCM backup routine has been running perfectly on all three for weeks. Now, for reasons unknown, one of them is failing every time with the following error written in the log: "SMS Site Backup could not find the SMS Writer in the list of writers provided by the VSS. Aborting the backup operation. Please verify that the SMS Writer service is up and running."

If I list the VSS writers, SMS Writer is indeed missing. I can manually add it back in, or restarting the VSS Writer component adds it back in too - but the backup still fails with the same error next time round.

There have been no changes to this one server that could affect it, and the other two servers are still backing up fine. Any ideas please??

Hi Team,

we are facing the Issue during the Central Server SCCM Backup. SQL Backup is failing. Please help us on this.

Error Details.

ERROR: SQL Backup task failed. Error message - Failed to copy the database files to the backup location. Please ensure that the SMS_SITE_SQL_BACKUP component has access to the backup location.

STATMSG: ID=5052 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=XXXXXXX SITE=CEN PID=3528 TID=1924 GMTDATE=Tue Jan 08 06:20:15.633 2013 ISTR0="\\SQLCLUSTER" ISTR1="SMS_CEN" ISTR2="Failed to copy the database files to the backup location. Please ensure that the SMS_SITE_SQL_BACKUP component has access to the backup location." ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

Error: SQL Backup failed...

Error: Backup Failed  for Component - CENBackup\SiteDBServer\SMSbkSQLDBsite.dat.

Recently we have moved our DB from local server to seperate server after that we are facing this problem kinldy help me on this

Regards,

Prabhaharan

Hi All

I am facing a peculiar problem with my SCCM server database backup. we have scheduled a backup task that runs and backup gets collected at a path but that is only a few MB's. But when i restart the server and run the backup . the back takes place at it is 23 Gb in size.

I have not observed anything suspicious in evet logs of SCCM server and SQl server logs. BOTH sccm and SQL server are installed on the same server.

It would be great if some one suggest me with a solution. After restart i understand the system resources of the server gets free. but how to find at that time the system resources are full as in task manager memory utilisation is still not that much

Regards\Sushain