locked
DTExec and VSS errors on Win2k8/64 with SQL2k5/64 RRS feed

  • Question

  • Environment:

    Windows 2008 SP2 Standard 64 bit

    SQL Server 2005 Standard 64 bit

    DTExec fails and gives following errormessage in Eventlog, every hour (presuming the same time as the transaction log job runs in SQL)

    Application Error, Event ID 1000:

    "Faulting application DTExec.exe, version 2005.90.5000.0, time stamp 0x4d028be, faulting module kernel32.dll, version 6.0.6002.18327, time stamp 0x4cb74dd3, exception code 0xc0000142, fault offset 0x00000000000b6f08, process id 0x26d4, application start time 0x01cc7f4f55a965c1."

    and following SQLSERVERAGENT warning Event ID 208: [naturally]

    "SQL Server Scheduled Job 'Transactionlog backup.Subplan_1'
    (0x..[omitted]..) - Status: Failed - Invoked on: 2011-09-30 10:00:00 - Message: The job failed. The job was invoked by Schedule 3 (Transactionlog backup.Subplan_1). The last step to run was step 1 (Subplan 1)

    Of 40 attempts, it works for approx 2-4 attempts, randomly.

    SQL Server Agent (MSSQLSERVER) uses Local System Account.

    On the same server, following error occures for the VSS-system:

    Application Error Event ID 1000:

    Faulting application vssvc.exe, version 6.0.6002.18005, time stamp 0x49e02c5c, faulting module credui.dll, version 6.0.6002.18327, time stamp 0x4cb74dd3, exception code 0xc0000142, fault offset 0x00000000000b6f08, process id 0x2484, application start time 0x01cc7ef692b177c7.

     vssvc.exe is set to run manual in local system account.

    1. Since the exception code is the same for both the DTExec error and the vssvc error, might the source be the same ?

    2. What causes the 0xc0000142 error ?

    2. Is there any known issues referencec to VSS, DTExec and 64 bit SQL2005 on 64 bit Win2k8 (SP2)

     


    RemoteGryphon39

    Friday, September 30, 2011 1:16 PM

Answers

  • Well, I've solved it, with a little twist.

    Referenced this article:

    http://msdn.microsoft.com/en-us/library/ms191543.aspx

    Well, i know it is not SQL2k5 but SQL2k8R2, but there is a hint that Local System account might be not so preferable in many circumstances. I created a SQLAdminUser with Administrator rights. And let the vssvc.exe and SQLSERVERAGENT use this user. Suddenly it works like charm. Still I am not sure why it so. 


    RemoteGryphon39
    Tuesday, October 4, 2011 6:30 AM

All replies

  • Hi,

    You have errors on Your Registry, 

    I recommended thay You Download a registry cleaner like ccleaner or registry winner, to clean Your registry.

    Please Don't Forget take backup of a Registry File, before make any changes.

    I hope You resolve this issue.

     

    Regards,

     

    Carlos Augusto.

     


    Si la respuesta le ayudó, por favor márquela como útil.
    Friday, September 30, 2011 8:16 PM
  • Well, I've solved it, with a little twist.

    Referenced this article:

    http://msdn.microsoft.com/en-us/library/ms191543.aspx

    Well, i know it is not SQL2k5 but SQL2k8R2, but there is a hint that Local System account might be not so preferable in many circumstances. I created a SQLAdminUser with Administrator rights. And let the vssvc.exe and SQLSERVERAGENT use this user. Suddenly it works like charm. Still I am not sure why it so. 


    RemoteGryphon39
    Tuesday, October 4, 2011 6:30 AM