locked
Unable to backup SCCM with SCCM SP1 R2 and SQL 2008 all on Server 2008 with SP2. RRS feed

  • Question


  • I have two servers.
    Server 1
        Server 2008 with SP2   
        SCCM 2007 with SP1 and R2
        SCCM Updates Applied, KB956578, KB961105, KB969113, KB969529, KB970093

    Server 2
        Server 2008 with SP2
        SQL 2008 (all patches applied)


    I receive this message from my SMSBKUP.LOG

    Initializing the status message reporting system... SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
        The path to the "Status Manager" inbox is "D:\Program Files (x86)\Microsoft Configuration Manager\inboxes\statmgr.box\statmsgs". SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
        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 8/24/2009 6:10:14 PM 7828 (0x1E94)
    Registered this process as a source of "SMS Server" events. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    Registered this process as a source of "SMS Client" events. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    Registered this process as a source of "SMS Provider" events. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    Status message reporting system initialized successfully. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    Locale set to OS value (English_United States.1252). SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    SMS site backup service 4.00 started. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    STATMSG: ID=500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:10:14.737 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    08/24/09 18:10:14 - starting backup. SMS_SITE_BACKUP 8/24/2009 6:10:14 PM 7828 (0x1E94)
    BackupDir = E:\CONFIGMGRBACKUP. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    Installation RootDir = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    Site SQL Dir = \\SQL02\C$\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL10.MSSQLSERVER\MSSQL\. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    Site Backup Location = \\sccm01\configmgrbackup SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    SQL Backup Location = \\sccm01\configmgrbackup SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    STATMSG: ID=5055 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:10:15.284 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,879) SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    Starting VSS initialization... SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    Starting Asynchronous GatherWriterMetadata. SMS_SITE_BACKUP 8/24/2009 6:10:15 PM 7828 (0x1E94)
    Number of writers that responded: 10. SMS_SITE_BACKUP 8/24/2009 6:10:18 PM 7828 (0x1E94)
    Reading SMS Writer metadata... SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Number of FileIncludes: 0. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Number of FileExcludes: 0. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Number of Components: 7. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 0 - PC2Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\INBOXES\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 1 - PC2Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\LOGS\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 2 - PC2Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\DATA\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 3 - PC2Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    FileGroupFile = D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\SRVACCT\* [Recursive: yes] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 4 - PC2Backup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    FileGroupFile = D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat [Recursive: no] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 5 - PC2Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    FileGroupFile = D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat [Recursive: no] SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Volume D:\ (that contains the file(s)) is marked as a candidate for snapshot. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Component 6 - PC2Backup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Dependency On SQL Writer , LogicalPath:\\SQL02, ComponentName:SCCM_PC2 SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_BACKUP. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Starting to clean and prepare the backup location. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Cleanup and/or preparation done. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Info: Sending message to start the SQL Backup... SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Starting to create the snapshot set. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Added volume containing D:\ to the snapshot set. SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Info: Starting Asynchronous PrepareForBackup... SMS_SITE_BACKUP 8/24/2009 6:10:19 PM 7828 (0x1E94)
    Info: Asynchronous PrepareForBackup finished... SMS_SITE_BACKUP 8/24/2009 6:10:20 PM 7828 (0x1E94)
    Info: Waiting for SQL to PrepareForBackup. SMS_SITE_BACKUP 8/24/2009 6:10:20 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:20 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:25 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:30 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:35 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:40 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:45 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:50 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:10:55 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:00 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:05 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:10 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:15 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:20 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:25 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:30 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:35 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:40 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:45 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:50 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:11:55 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:00 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:05 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:10 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:15 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:20 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:25 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:30 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:35 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:41 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:46 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:51 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:12:56 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:01 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:06 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:11 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:16 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:21 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:26 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:31 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:36 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:41 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:46 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:51 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:13:56 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:01 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:06 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:11 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:16 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:21 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:26 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:31 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:36 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:41 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:46 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:51 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:14:56 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:01 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:06 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:11 PM 7828 (0x1E94)
    Sleeping for 5 seconds... SMS_SITE_BACKUP 8/24/2009 6:15:16 PM 7828 (0x1E94)
    Error: Sql Server could not prepare for the Backup. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    Aborting the backup process. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    Error: CreateSnapshotSet failed... SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    STATMSG: ID=5047 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:15:21.615 2009 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    SMS site backup service is stopping. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:15:21.647 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    SMS site backup service stopped. SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)
    STATMSG: ID=501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=SCCM01 SITE=PC2 PID=10064 TID=7828 GMTDATE=Mon Aug 24 23:15:21.647 2009 ISTR0="SMS site backup" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 8/24/2009 6:15:21 PM 7828 (0x1E94)


    This is from my SMSWRITER.LOG

    OnIdentify event triggerred. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    SMS Writer 08/24/09 18:10:17 - starting to build the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\INBOXES into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\LOGS into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\DATA into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    Successfully included D:\PROGRAM FILES (X86)\MICROSOFT CONFIGURATION MANAGER\SRVACCT into to the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    Successfully included \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\NAL - D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat into the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    Successfully included \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS - D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat into the metadata. SMS_SITE_VSS_WRITER 8/24/2009 6:10:17 PM 1012 (0x03F4)
    OnPrepareBackup event triggerred. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    The backup task has selected the components in the Sms Writer. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteServer\SMSServer\inboxes. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteServer\SMSServer\Logs. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteServer\SMSServer\data. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteServer\SMSServer\srvacct. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    ComponentName = PC2Backup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:19 PM 1012 (0x03F4)
    Successfully exported the \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\NAL to D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:20 PM 1012 (0x03F4)
    Successfully exported the \\SCCM01\HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\SMS to D:\Program Files (x86)\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat. SMS_SITE_VSS_WRITER 8/24/2009 6:10:20 PM 1012 (0x03F4)
    Tuesday, August 25, 2009 12:01 AM

Answers

  • Robert Williams a Co Worker of mine, found the fix.

    SCCM Site Backup Failure

    Failed component installation on the SQL Server

    Typically only seen if the current Site Database server was not the original site database server

    1.       Look for SMS_SITE_SQL_BACKUP under services on the SQL Server

    2.       If the service is not listed, the Site Server may not have admin permissions on the SQL Server

    3.       Correct the permissions, and check the SMS_SITE_COMPONENT_MANAGER status for errors

    SCCM SP1 SMS_SITE_SQL_BACKUP component issue

    Frequently seen if the SCCM Site Database server is a separate server from the SCCM Site Server, and SCCM is upgraded to SP1

    1.        Query the SMS_SITE_SQL_BACKUP component in SCCM Service Manager

    2.       If you receive “Error Communicating with Component”, see if this hotfix may apply to you:

    a.       http://support.microsoft.com/kb/957879

    VSS Writer Failures

    Occurs in various scenarios

    1.       On the Site Server, run command:  vssadmin list writers

    a.       The command should return ‘SMS Writer’ in a stable state

    b.      The command will probably return many more VSS writers

    2.       On the SQL Server, run command:  vssadmin list writers

    a.       The command should return ‘SqlServerWriter’ in a stable state

    b.      The command will probably return many more VSS writers

    3.       If the VSS writers are not in a stable state, or the command does not return any results:

    a.       Review this article:  http://support.microsoft.com/kb/940184

    b.      The registry key deletion will likely be required

    c.       The server may need to be rebooted

    d.      The VSS Writer services will need to be restarted (if attempting to avoid a reboot)

     

    • Marked as answer by JamesAvery Tuesday, August 25, 2009 5:04 PM
    Tuesday, August 25, 2009 5:04 PM

All replies

  • Is the computer account for your primary site server a local admin on the SQL server?

    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Tuesday, August 25, 2009 12:13 AM
  • Yes, we went so far to give full rights to each machine account to each other. Then we also opened up the rights for SQL 2008 to accept any request from the SCCM server.

    One of my coworkers also asked me to review the KB940184 article. This article describes the issues with the VSS writers on both SQL and SCCM. I tested the VSS Writers as requested and I recieved NO ERRORS on either of the servers and writers on both servers are showing correct.

    We have turned off Firewalls on both servers.

    We have tested Kerberos and SQL is seeing the Kerberos coming from SCCM server.

    Tuesday, August 25, 2009 2:04 PM
  • Robert Williams a Co Worker of mine, found the fix.

    SCCM Site Backup Failure

    Failed component installation on the SQL Server

    Typically only seen if the current Site Database server was not the original site database server

    1.       Look for SMS_SITE_SQL_BACKUP under services on the SQL Server

    2.       If the service is not listed, the Site Server may not have admin permissions on the SQL Server

    3.       Correct the permissions, and check the SMS_SITE_COMPONENT_MANAGER status for errors

    SCCM SP1 SMS_SITE_SQL_BACKUP component issue

    Frequently seen if the SCCM Site Database server is a separate server from the SCCM Site Server, and SCCM is upgraded to SP1

    1.        Query the SMS_SITE_SQL_BACKUP component in SCCM Service Manager

    2.       If you receive “Error Communicating with Component”, see if this hotfix may apply to you:

    a.       http://support.microsoft.com/kb/957879

    VSS Writer Failures

    Occurs in various scenarios

    1.       On the Site Server, run command:  vssadmin list writers

    a.       The command should return ‘SMS Writer’ in a stable state

    b.      The command will probably return many more VSS writers

    2.       On the SQL Server, run command:  vssadmin list writers

    a.       The command should return ‘SqlServerWriter’ in a stable state

    b.      The command will probably return many more VSS writers

    3.       If the VSS writers are not in a stable state, or the command does not return any results:

    a.       Review this article:  http://support.microsoft.com/kb/940184

    b.      The registry key deletion will likely be required

    c.       The server may need to be rebooted

    d.      The VSS Writer services will need to be restarted (if attempting to avoid a reboot)

     

    • Marked as answer by JamesAvery Tuesday, August 25, 2009 5:04 PM
    Tuesday, August 25, 2009 5:04 PM
  • Jason, 

    I have SCCM 2007 R2 with a remote SQL 2005.

    I have problem with backup, too. It looks like my SQL server need to have a Service name "SMS_Site_SQL_Backup". I looked in the Services list it is not there. So, that mean I need to install the SMS_Site_SQL_Backup component on my remote SQL server? Is there an instruction set for the installation? Thanks.

    Friday, March 25, 2011 4:09 PM
  • Have you added it as a site server in the ConfigMgr console and does the ConfigMgr site server account have local admin privileges on the system hosting the DB (as well as sysadmin privilileges in the DB)?
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Friday, March 25, 2011 9:32 PM
  • The "ConfigMgr Site System" properties of the db server was not fully configured. I added the FQDN for the intranet. The ConfigMgr site server account have local admin privileges on the system hosting the DB and sysadmin privilileges in the DB.

    So, far I have not seen any changes. I still don't see the "SMS_Site_SQL_Backup" service in the db server. Is there a specific log to check for errors.

    Monday, March 28, 2011 2:52 PM
  • Have you checked the component status area in the console?
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Monday, March 28, 2011 6:30 PM
  • Configman is trying to reinstall

    Component name: SMS_Site_SQL_Backup_<cfgm-server>,

    Description: SMS Site Component Manager detected that this component should be reinstalled on this site system. SMS Site Component Manager will attempt to install the component every 60 minutes until the installation succeeds.

    configman retried many time but never install sucessfully.

    This is what I get in the backup log,

    ~Info: Sending message to start the SQL Backup...  $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:22.417 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    Starting to create the snapshot set.   $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:22.463 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    Added volume containing C:\ to the snapshot set.  $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:24.491 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    ~Info: Starting Asynchronous PrepareForBackup...  $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:24.491 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    ~Info: Asynchronous PrepareForBackup finished...  $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:25.209 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    ~Info: Waiting for SQL to PrepareForBackup.  $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:25.209 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    Sleeping for 5 seconds...  $$<SMS_SITE_BACKUP><Mon Mar 28 11:38:25.225 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
       .
       .
       .
    Error: Sql Server could not prepare for the Backup.  $$<SMS_SITE_BACKUP><Mon Mar 28 11:43:25.684 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    Aborting the backup process.  $$<SMS_SITE_BACKUP><Mon Mar 28 11:43:25.684 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
       $$<SMS_SITE_BACKUP><Mon Mar 28 11:43:25.684 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>
    Error: CreateSnapshotSet failed...  $$<SMS_SITE_BACKUP><Mon Mar 28 11:43:25.700 2011 Eastern Daylight Time><thread=8096 (0x1FA0)>

    when I run the command: "VSSadmin list writers" on db server, all writers are stable. However, when I run that on cofigman server, it shows "SMS writer" is the only one that failed.

     

    Monday, March 28, 2011 8:20 PM
  • If the component is not installed properly, then backups are not going work.

    Have you reviewed sitecomp.log?


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Tuesday, March 29, 2011 1:00 AM
  • checked the sitecomp.log. I don't know if the following make any sense to you. At the red text, my SQL-Server is an x32 machine an I don't know why it try to install an x64 software,

    Thread "SiteComp server polling Thread #0" id:7976 terminated normally  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.063 2011 Eastern Daylight Time><thread=7976 (0x1F28)>

          Bootstrap operations aborted.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.032 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    LogEvent(): Successfully logged Event to NT Event Log (4, 77, 1073742842, (null)).  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.094 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          The server already contains some of the required files for this component.  A disk space check will not be made.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.094 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          Installed file \\SQL-SERVER\C$\SMS_CFGM-SERVER\bin\x64\smssqlbkup.exe.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.141 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    Disabling Wow64FsRedirection...  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    Revert Wow64FsRedirection...  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          All files installed.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          Starting bootstrap operations...  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

            Component file list item in the install map for component SMS_SITE_SQL_BACKUP does not contain srvboot.exe.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          Bootstrap operations aborted.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

        Reinstallation failed and will be retried in the next polling cycle.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    LogEvent(): Successfully logged Event to NT Event Log (1, 77, -1073740804, (null)).  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    STATMSG: ID=1020 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_SQL_BACKUP_CFGM-SERVER" SYS=SQL-SERVER SITE=GTP PID=3404 TID=8052 GMTDATE=Wed Mar 30 05:43:12.157 2011 ISTR0="60" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          Releasing current connection to server.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

          Releasing Abstract Network object.  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

      Finished polling server SQL-SERVER...  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    Thread "SiteComp server polling Thread #1" id:8052 terminated normally  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    CSiteCompThreadManager::ThreadTerminating - All threads have stopped running  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=8052 (0x1F74)>

    CSiteCompThreadManager::WaitForThreadsToFinish - All threads have stopped  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=4376 (0x1118)>

    Finished polling all servers  $$<SMS_SITE_COMPONENT_MANAGER><Wed Mar 30 01:43:12.157 2011 Eastern Daylight Time><thread=4376 (0x1118)>

     

    Wednesday, March 30, 2011 8:35 PM
  • If you do a web search for srvboot.exe you'll find a handful of hits including some possible solutions. There is also an older KB for SMS2003 with the same issue that recommends contacting CSS: http://support.microsoft.com/kb/227010. This is advice I would also recommend; it is probably a known, but rare, issue that they can help you walk through fixing in short order.
    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Wednesday, March 30, 2011 10:13 PM
  • Jason,  it is fixed! Thank you much for your help to troubleshoot this. 

    Your suggestion led me to the thread "SMS_SITE_SQL_BACKUP component failed to reinstall". there I found the solution. After the component reinstalled successfully on my db server, it added a new servive "SMS_Site_SQL_Backup_<SiteServer>" there. I ran a test backup and it worked.

    Thursday, March 31, 2011 3:40 PM