Event IDs 6013 (VSS) and 57860 (BE) with SQL error 4818 on remote server

[Hugh_Martin]

The following error is appearing in the App Event Log of a remote server. However, the backups are not indicating an error and appear to be backing up the database successfully.

Event Log Details for Event ID 57860
------------------------------------------------------
Event Type:Error
Event Source:Backup Exec
Event Category:None
Event ID:57860
Date:1/8/2006
Time:8:06:08 AM
User:N/A
Computer:HDAJTERM
Description:
An error occurred while attempting to log in to the following server: "HDAJTERM\PROFXENGAGEMENT".
SQL error number: "4818".
SQL error message: "Login failed for user 'HDAJCPA\Beanc0unter$'.
".

For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Data:
0000: 18 48 00 00 00 00 00 00 .H......
0008: 00 00 00 00 00 00 00 00 ........


Event Log Details for Event ID 6013
------------------------------------------------------
Event Type:Error
Event Source:VSS
Event Category:None
Event ID:6013
Date:1/8/2006
Time:7:38:06 PM
User:N/A
Computer:HDAJTERM
Description:
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'.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20 - Code:
0008: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0010: 30 30 30 30 30 34 39 31 00000491
0018: 2d 20 43 61 6c 6c 3a 20 - Call:
0020: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0028: 30 30 30 30 30 33 39 37 00000397
0030: 2d 20 50 49 44 3a 20 20 - PID:
0038: 30 30 30 30 31 30 38 30 00001080
0040: 2d 20 54 49 44 3a 20 20 - TID:
0048: 30 30 30 30 33 37 32 34 00003724
0050: 2d 20 43 4d 44 3a 20 20 - CMD:
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 53 79 73 74 65 WS\Syste
0068: 6d 33 32 5c 76 73 73 76 m32\vssv
0070: 63 2e 65 78 65 20 20 20 c.exe
0078: 2d 20 55 73 65 72 3a 20 - User:
0080: 4e 54 20 41 55 54 48 4f NT AUTHO
0088: 52 49 54 59 5c 53 59 53 RITY\SYS
0090: 54 45 4d 20 20 20 20 20 TEM
0098: 2d 20 53 69 64 3a 20 20 - Sid:
00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18


Job Log Details (abridged)
---------------------------------------------------
Family Name: "Media created 1/6/2006 10:00:04 PM"
Backup of "HDAJTERM\PROFXENGAGEMENT "
Backup set #9 on storage media #1
Backup set description: "Fri and Sat Incremental Backup Job"
Backup Type: DATABASE - Back Up Entire Database
Microsoft SQL Server Agent: Started

Backup started on 1/8/2006 at 7:46:13 AM.

Backed up 5 databases
Processed 72,275,333 bytes in 35 seconds.
Throughput rate: 118 MB/min

[shweta_rege]

Hello,

Kindly refer the following document:

http://seer.support.veritas.com/docs/264616.htm

A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003

http://support.microsoft.com/default.aspx?kbid=833167

*******************************************************************
*****************************************************************

Note : If we do not receive your reply within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.


Thanks.

[Hugh_Martin]

Thanks for the response. I tried renaming the DLL as described in the Veritas 264616, but this resulted in a failed backup (note that the SQL error number in the article is different than what I'm getting. Regarding the MS article, it also describes errors that do not match mine. Are you confident that this hotfix is appropriate for my situation or is this a troubleshooting step? These by-request-only hotfixes often cannot be uninstalled. Thanks.

[Sharvari_Deshmu]

Hello,


What version of BE are you using if it is not 10.1 please upgrade to 10.1
Please see the technote:

http://support.veritas.com/docs/279332

Thanks,

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

[Hugh_Martin]

We are currently running 10.0. I am downloading the 10d software and will perform the installation this weekend. I will provide feedback as to whether this resolves the problem at that time. Thanks.

[Hugh_Martin]

The upgrade to 10.1 (10d) has been completed successfully. The errors are still occurring.

[tejashree_Bhate]

Hello,

As this seems to be a microsoft issue we request you to please contact microsoft in getting the issue resolved.

Note:- if we do not receive your reply within two business days, this post would be assumed answered and archived.

[Hugh_Martin]

How is it that this is now a Microsoft issue? And why did I have to wait this long just to be told to call Microsoft? I would like this issue escalated to a manager, please.

[Rick_Olson]

Hello Hugh,

I too am having the exact same problem you are having, though our backups are failing every night. It took me several days of searching online for anyone with similar issues.

The renaming of the .dll file is no good for users that have the SQL Agent installed, as renaming the .dll file is for users who are wishing to use BE to backup the database "files" and not backup the "database" itself (if that makes sense).

I've not found a solution yet either, and would absolutely abhor calling Microsoft for this, since it is not a Microsoft problem (our databases are running just fine) but rather this is a Veritas problem (BE is unable to backup a database as it says it should).

When I go in to modify my backup job, then select the database I want, I get the "resource credentials" window popping up (basically the username/password I've given it won't work, but I know for a fact I'm typing it in correctly). That's when I receive Event ID 57860, exactly as you have.

I do hope this thread is examined by someone who can help.

[Hugh_Martin]

Hi Rick,

I also sent a separate email to Customer Service on 2/13, but have not yet gotten a response. I'll keep you posted if something happens outside this forum.

Hugh

[Mayan_Nath]

I have been having trouble with this error as well. As a last resort, I even called Microsoft (really didn't have to) and was redirected back to Symantec Veritas Support as a resolution. Reason for that is because, this error relates directly to Backup Exec. and Microsoft does not support it. Hopefully, someone here is able to help us out.

[Rick_Olson]

Hugh,

I once again got on the phone with Veritas support and this time was able to resolve my issue. This time around they initiated a "WebEX" session, where the support person could see my desktop. This proved far more useful than trying to explain the situation (he could not control the session, he could just see). Fortunately (or unfortunately) in my case it ended up being an extremely simple solution.

SQL databases have a super user account "SA" instead of "Administrator". In the Backup Exec Login Management screen, I needed to add the user "SA" with the password (the default for SQL databases is apparently a blank password). It was not a restricted account, nor should it be the default account. This gave me the appropriate permissions to access that specific database.

I'm quite relieved to say that we're now fully able to backup our accounting databases. I'll be sleeping better tonight, and hoping that this solution can be of some help to your situation as well. Take care.Message was edited by:
Rick Olson

[Hugh_Martin]

Rick,

Thanks for the follow-up. Unfortunately, our situation is a little different. We are also using the SA account, but have the password. In our case, the database backups are succeeding, so our issue is a little less pressing, but we continue to see the errors in the event log.

Sadly, Veritas (Symantec) support has been of no help whatsoever. As you can see here, they have not responded to this case in quite awhile. Also, I've gotten no response to my 2-3 emails to Customer Service (despite their auto-reply which promises a response within 48 hours. I suspect I'll be lookng for a new backup solution soon. Before Symantec bought Veritas, support was much better! I am, however, glad to hear that they were able to help you. -Hugh

[William_Triplet]

We are having the same issue as described. We even went a little further and added the System Logon Account to the SQL server with the appropriate rights. Everything tested fine in the backup job and the backups are 100% complete. However, we still get the SQL logon error. This has to be a SQL agent issue.

[Hugh_Martin]

Agreed. I did finally get a response from Customer Service. Here it is:

==============================
Thank you for contacting Symantec,

Unfortunately, Americas Customer Care can not assist you with your issue.

For installation and technical issues, please contact Symantec Technical Support at 800-342-0652, option #0 or visit http://support.veritas.com.
==============================

If Symantec wants to kill the Veritas products, they're off to a great start with me! I won't be renewing support next time if support does not significantly improve soon.