Forum Discussion

Sahap_Yuzer's avatar
18 years ago

SQL Errors followed by termination of the BackupExec Remote Agent

We recently upgraded from 10 to 11D and when the backup server starts to backup local Volume Shadow Copy Service (VSS),
we get below errors and then unexpected termination of the Backup Exec Remote Agent. Any ideas what the problem is?
---------------------
EVENT # 67907
EVENT LOG Application
EVENT TYPE Error
SOURCE Backup Exec
EVENT ID 57860
COMPUTERNAME   BUPSERVER
TIME 4/30/2007 11:34:52 PM
MESSAGE An error occurred while attempting to log in to the following server: "BUPSERVER".
SQL error number: "4818".
SQL error message: "Login failed for user 'DOMAIN\backupexec'".
----------------
EVENT # 67908
EVENT LOG Application
EVENT TYPE Error
SOURCE VSS
EVENT ID 6013
COMPUTERNAME   BUPSERVER
TIME 4/30/2007 11:34:52 PM
MESSAGE Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80040e4d. SQLSTATE: 42000, Native Error: 18456
Error state: 1, Severity: 14
Source: Microsoft OLE DB Provider for SQL Server
Error message: Login failed for user 'NT AUTHORITY\SYSTEM'.
 
BINARY DATA   0000: 2D 20 43 6F 64 65 3A 20 53 51 4C 43 4F 4E 4E 43
0010: 30 30 30 30 30 34 39 31 2D 20 43 61 6C 6C 3A 20
0020: 53 51 4C 43 4F 4E 4E 43 30 30 30 30 30 33 39 37
0030: 2D 20 50 49 44 3A 20 20 30 30 30 30 34 35 34 38
0040: 2D 20 54 49 44 3A 20 20 30 30 30 30 34 36 34 38
0050: 2D 20 43 4D 44 3A 20 20 43 3A 5C 57 49 4E 44 4F
0060: 57 53 5C 53 79 73 74 65 6D 33 32 5C 76 73 73 76
0070: 63 2E 65 78 65 20 20 20 2D 20 55 73 65 72 3A 20
0080: 4E 54 20 41 55 54 48 4F 52 49 54 59 5C 53 59 53
0090: 54 45 4D 20 20 20 20 20 2D 20 53 69 64 3A 20 20
00A0: 53 2D 31 2D 35 2D 31 38 

-----------------------
EVENT # 491974
EVENT LOG System
EVENT TYPE Error
SOURCE Service Control Manager
EVENT ID 7032
COMPUTERNAME   BUPSERVER
TIME 4/30/2007 11:38:18 PM
MESSAGE The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Backup Exec Remote Agent for Windows Systems service, but this action failed with the following error:
An instance of the service is already running.
 
 

Message Edited by Sahap Yuzer on 05-01-200710:11 AM

  • Hi Sahap -
     
    It appears to me you may have an environmental issue. To check and see if your VSS List Writers are stable do the following:
     
    1. Open a command window by clicking Start | Run, typing cmd, and then clicking OK
    2. Type VSSADMIN LIST WRITERS at the command prompt and press the ENTER key
     
    This will return a list of writers currently running on the system. If any errors are returned, the you will need to contact Microsoft for assistance.
     
    There is a hotfix out from Microsoft that has assisted our customer's experiencing the same issue when dealing with VSS associated errors.
     
    Here is a hotfix provided by Microsoft regarding VSS:
     
    A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
     
    I hope this helps!
     
    - Jared
     
     
     
     
     
  • Thank you for your reply. I run the VSSADMIN LIST WRITERS and returned no errors.
    But I did see 4 of the the below entries in the EventLog as soon as I run it. So it is some how
    related to VSS but no indication on where this is coming from. Any ideas?
     
    EVENT # 68157
    EVENT LOG Application
    EVENT TYPE Error
    SOURCE VSS
    EVENT ID6013
    COMPUTERNAME  BACKUPSERVER
    TIME 5/1/2007 4:21:58 PM
    MESSAGE
    Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80040e4d. SQLSTATE: 42000, Native Error: 18456
    Error state: 1, Severity: 14
    Source: Microsoft OLE DB Provider for SQL Server
    Error message: Login failed for user 'NT AUTHORITY\SYSTEM'.

    BINARY DATA  0000: 2D 20 43 6F 64 65 3A 20 53 51 4C 43 4F 4E 4E 43
    0010: 30 30 30 30 30 34 39 31 2D 20 43 61 6C 6C 3A 20
    0020: 53 51 4C 43 4F 4E 4E 43 30 30 30 30 30 33 39 37
    0030: 2D 20 50 49 44 3A 20 20 30 30 30 30 35 33 31 32
    0040: 2D 20 54 49 44 3A 20 20 30 30 30 30 37 34 32 38
    0050: 2D 20 43 4D 44 3A 20 20 43 3A 5C 57 49 4E 44 4F
    0060: 57 53 5C 53 79 73 74 65 6D 33 32 5C 76 73 73 76
    0070: 63 2E 65 78 65 20 20 20 2D 20 55 73 65 72 3A 20
    0080: 4E 54 20 41 55 54 48 4F 52 49 54 59 5C 53 59 53
    0090: 54 45 4D 20 20 20 20 20 2D 20 53 69 64 3A 20 20
    00A0: 53 2D 31 2D 35 2D 31 38
     
     
  • I googled the 18456 error on Microsoft and came up with a lot of information regarding VSS. I would search through the Microsoft knowledge base to develop a solution or contact Microsoft support to see what they think.
     
    - Jared
  • There is one third-party SQL Express database that we have no access rights to
    running on the backup server. I'm suspecting that's the culprit for the VSS errors.
    I don't know how to add [NT AUTHORITY\SYSTEM] as Admin to this database
    or if there is a workaround to this issue. Anyone knows?
     
    But the beremote.exe started to crash after the 11D upgrade. We never had this before.
    We've been seeing the VSS erros but they were not effecting the backups. (See below)
     
    EVENT # 68295
    EVENT LOG Application
    EVENT TYPE Error
    SOURCE Application Error
    CATEGORY 100 (no category messagefile registered)
    EVENT ID 1000
    COMPUTERNAME  BACKUPSERVER
    TIME 5/1/2007 11:36:48 PM
    MESSAGE Faulting application beremote.exe, version 11.0.7170.0, faulting module bedsshadow.dll, version 11.0.7170.0, fault address 0x0006bafd.
    BINARY DATA  0000: 41 70 70 6C 69 63 61 74 69 6F 6E 20 46 61 69 6C
    0010: 75 72 65 20 20 62 65 72 65 6D 6F 74 65 2E 65 78
    0020: 65 20 31 31 2E 30 2E 37 31 37 30 2E 30 20 69 6E
    0030: 20 62 65 64 73 73 68 61 64 6F 77 2E 64 6C 6C 20
    0040: 31 31 2E 30 2E 37 31 37 30 2E 30 20 61 74 20 6F
    0050: 66 66 73 65 74 20 30 30 30 36 62 61 66 64
  • for SQL2005, Open "SQL Server Management Studio", RCklick on the top of the tree > "New Query", paste
     
    EXEC sp_grantlogin [NT Authority\System]
    EXEC sp_addsrvrolemember @loginame = [NT Authority\System]
    , @rolename =  'sysadmin'
     
    press F5 or Query>Execute, you should see in query results:

    Granted login access to 'NT Authority\System'.

    'NT Authority\System' added to role 'sysadmin'.

     
    as for crash, i looked into my bedsshadow.dll  876 624 bytes, x32 11.0.7170.0 version
    there is no machine instruction at 0x0006bafd. The neares one at 0x0006baf6 and then 0x0006bafc
    weird, weird, weird