Being a generic error message, this event can be recorded with several types of errors and each error type will imply a different approach in trying to troubleshoot it. Additional events may be found in the event log that can help narrowing down the source of the problem.
Common combinations of error codes and error messages:
Error code 0x80040e4d
, error message: Login failed for user 'NT AUTHORITY\SYSTEM' - As per Microsoft, this could be an authentication problem. See ME919023
for a troubleshooting methodology of this type of error. The 0x80040e4d error code indicates an authentication failure.
Error code 0x80004005
, error message: [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied. The 0x80004005 error code is used for "generic" failures (that is, the system does not have enough information about it, just that the program failed). In many cases this indicates a failure inside the program itself, not related to a process performed by standard Microsoft APIs. In this case, the failure occured inside the DB Network programming libraries).
Error code 0x80004005
, error message: [DBNETLIB][ConnectionOpen (SECDoClientHandshake()).]SSL Security error.
Volume Shadow Copy service was enabled on our system but there was a SQL instance for our payroll system that would still produce the error. I simply scheduled a "NET STOP" and "NET START" to stop the instance during the backup window.
I found that adding "NT Authority\System" to the SharePoint Admin group in Site Settings allowed the VSS to work properly.
This error appeared due to insufficient permissions to query the system tables or the catalog views that contain the information about the databases and the files that belong to the database. Therefore, Volume Shadow Copy stopped itself at that point. To correct this, open SQL 2000 Enterprise Manager, expand Microsoft SQL Servers, expand SQL Server Group, expand SERVERNAME\SHAREPOINT, expand Security, click Logins, right click NT AUTHORITY\NETWORK SERVICE, click Properties, click Database Access, click to select the appropriate database(s) (e.g., master), and in the Database Roles for “master” click to select the appropriate roles (such as dbdatareader). See ME919023
for details (Authentication problems / SQL Server 2000).
I made sure the Volume Shadow Copy service was started in the services management console. In my case, it was set to manual. Setting it to automatic and starting it made the backup work fine after that.
Open the Client Network Utility and go to the Alias tab. Now, make sure that you have an alias for the server and that the connection type is correct for your server. If you use TCP you have to have one for TCP and so forth. For some reason mine was set to Named Pipes although I do not use it. Changing it to TCP solved my problem.
This problem will occur when the MSDE writer cannot connect to SQL Server. The MSDE writer must connect to SQL Server to send the required data to the Volume Shadow Copy Service. See ME913360
for a hotfix applicable to Microsoft Windows Server 2003, Microsoft Windows XP and Microsoft SQL Server 2000 Desktop Engine (Windows).
This problem can occur when you configure the instance of MSDE to use the shared memory protocol only. See ME913100
for a hotfix applicable to Microsoft SQL Server 2000.
This event will show in the logs if authentication problems occur. See ME919023
This error can also be caused by a SQL instance that is locked, such as ACT!. ACT! can only be accessed by purchasing the SDK from Sage Software. The best workaround is to shutdown the ACT! SQL instance during a backup and turn it back on afterwards.
for the Volume Shadow Copy Service (VSS) update-2 package for Windows Server 2003.
Salford Software Support Document ID: SKB0315 provides information on this event.
for a Volume Shadow Copy Service (VSS) update package for Windows Server 2003.