Collection job collection_set_1_noncached_collect_and_upload failing sometimes - by Alvaro Mosquera

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


11
0
Sign in
to vote
ID 644099 Comments
Status Closed Workarounds
Type Bug Repros 6
Opened 2/15/2011 12:14:43 AM
Access Restriction Public

Description

Hello,

I'm running Sql Server 2008 R2 enterprise edition (10.50.1753.0) on Windows Server 2008 R2 Enterprise x64.The job collection_set_1_noncached_collect_and_upload  fails sometimes. The job have default shedules and run every 6 hours. If fails smoetimes, no so much. After the fail if I run from SSMS it always runs OK.  

The job fails with the next error: (job history)

Executed as user: domain\user. Failed to log package begin event for package: "TSQLQueryCollect". Inner Error ------------------>  Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "SERVER" Procedure: "sp_syscollector_event_onpackagebegin" Line#:   35 Error Number:  14262 Error State:   1 Error Severity:  16 Error Message: "Se especific¾ @parent_log_id ('151120'), que no existe." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}.  OLE DB Error Record dump end.  Failed to get a package log id for package: TSQLQueryCollect, previous messages should explain the reason for the failure. The package will use log id: 151119 instead.  Failed to log package begin event for package: "TSQLQueryCollect". Inner Error ------------------>  Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "SERVER" Procedure: "sp_syscollector_event_onpackagebegin" Line#:   35 Error Number:  14262 Error State:   1 Error Severity:  16 Error Message: "Se especific¾ @parent_log_id ('151120'), que no existe." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}.  OLE DB Error Record dump end.  Failed to get a package log id for package: TSQLQueryCollect, previous messages should explain the reason for the failure. The package will use log id: 151119 instead.Failed to log package end event for package: "TSQLQueryCollect". Inner Error ------------------>  Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "SERVER" Procedure: "sp_syscollector_verify_event_log_id" Line#:   22 Error Number:  14262 Error State:   1 Error Severity:  16 Error Message: "Se especific¾ @log_id ('151119'), que no existe." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}.  OLE DB Error Record dump end.Failed to log package end event for package: "TSQLQueryCollect". Inner Error ------------------>  Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "SERVER" Procedure: "sp_syscollector_verify_event_log_id" Line#:   22 Error Number:  14262 Error State:   1 Error Severity:  16 Error Message: "Se especific¾ @log_id ('151119'), que no existe." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}.  OLE DB Error Record dump end.  Failed to log package end event for package: "Set_{7B191952-8ECF-4E12-AEB2-EF646EF79FEF}_Master_Package_Collection". Inner Error ------------------>  Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "SERVER" Procedure: "sp_syscollector_verify_event_log_id" Line#:   22 Error Number:  14262 Error State:   1 Error Severity:  16 Error Message: "Se especific¾ @log_id ('151120'), que no existe." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}.  OLE DB Error Record dump end.  The master package exited with error, previous error messages should explain the cause.  Process Exit Code 5.  The step failed.

Windows Log Application Error:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="SQLISPackage100" /> 
  <EventID Qualifiers="16385">12291</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2011-02-15T05:00:02.000000000Z" /> 
  <EventRecordID>72489</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>server.domain.cag</Computer> 
  <Security UserID="S-1-5-21-1494506204-1709601483-925700815-19601" /> 
  </System>
- <EventData>
  <Data>Set_{7B191952-8ECF-4E12-AEB2-EF646EF79FEF}_Master_Package_Collection</Data> 
  </EventData>
  </Event>


Sign in to post a comment.
Posted by Santosh Heranjal on 12/24/2014 at 3:39 AM
Hi Sethu,

We are also seeing similar symptoms

We are running Microsoft SQL Server 2008 R2 10.50.1753.0 (X64) on Enterprise Edition (64-bit) on Windows NT 5.2 <X64>Service Pack 2

The job collection_set_1_noncached_collect_and_upload is seen to fail intermittently. Below pasted is the message registered to the job log:

Failed to log package begin event for package: "TSQLQueryCollect". Inner Error ------------------> Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "MCJS-BIBSQL2" Procedure: "sp_syscollector_event_onpackagebegin" Line#: 35 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @parent_log_id ('1617331') does not exist." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Failed to log package begin event for package: "TSQLQueryCollect". Inner Error ------------------> Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "MCJS-BIBSQL2" Procedure: "sp_syscollector_event_onpackagebegin" Line#: 35 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @parent_log_id ('1617331') does not exist." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Failed to get a package log id for package: TSQLQueryCollect, previous messages should explain the reason for the failure. The package will use log id: 1617330 instead. Failed to get a package log id for package: TSQLQueryCollect, previous messages should explain the reason for the failure. The package will use log id: 1617330 instead.Failed to log package end event for package: "TSQLQueryCollect". Inner Error ------------------> Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "MCJS-BIBSQL2" Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @log_id ('1617330') does not exist." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end.Failed to log package end event for package: "TSQLQueryCollect". Inner Error ------------------> Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "MCJS-BIBSQL2" Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @log_id ('1617330') does not exist." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. Failed to log package end event for package: "Set_{7B191952-8ECF-4E12-AEB2-EF646EF79FEF}_Master_Package_Collection". Inner Error ------------------> Row#:    0 Source: "Microsoft SQL Server Native Client 10.0" Instance: "MCJS-BIBSQL2" Procedure: "sp_syscollector_verify_event_log_id" Line#: 22 Error Number: 14262 Error State: 1 Error Severity: 16 Error Message: "The specified @log_id ('1617331') does not exist." Help File: "(null)", Help context:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. OLE DB Error Record dump end. The master package exited with error, previous error messages should explain the cause. Process Exit Code 5. The step failed.

In one of the updates '6/26/2012 at 4:34 PM' you have mentioned that is a fix for this issue and the next update on ' 3/4/2014 at 6:49 AM' says that this issue is addressed in SQL 2012 SP1.

We currently do not have a plan as such to move to SQL 2012 SP1. Wanted to understand if there is a way to workaround this issue in the current version.

Regards,
Santosh
Posted by Alvaro Mosquera on 3/5/2014 at 12:16 AM
Hi Sethu,

We are in Sql Sver 2008 R2... when we move to 2012 I'll test it.

Thanks
Posted by Sethu Srinivasan on 3/4/2014 at 6:49 AM
We have addressed this issue in SQL 2012 SP1. Let us know if you see this issue after applying SQL 2012 SP1 on your SQL 2012 instances -
You can download SQL 2012 SP1 from http://www.microsoft.com/en-us/download/details.aspx?id=35575

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Posted by Ben Seaman on 10/17/2012 at 1:13 AM
Hello,

I am also seeing this problem on build 10.50.2500. Can you post details of the fix please?

Many thanks,
Ben Seaman
Posted by Microsoft on 6/26/2012 at 4:34 PM
We have a fix for this issue. If you would like to help us validate the fix, Please email us at sethu.srinivasan@microsoft.com

Thanks
Sethu Srinivasan[MSFT]
SQL Server
Posted by Microsoft on 4/11/2012 at 12:18 PM
Hello Alvaro,
We are working on a fix to resolve this issue. Would you be willing to test this fix? Please email us at sethu.srinivasan.microsoft.com

Thanks
Sethu Srinivasan[MSFT]
SQL Server
Posted by Gunter G_ on 12/18/2011 at 10:59 PM
I am facing a similar problem on a 2008 R2 system (10.50.2789). Even though I can only provide details in German (system language), the similarity of the issue with the one mentioned in the main article is pretty obvious:
"
12/16/2011 07:00:00,collection_set_3_upload,Fehler,2,SQL-08,collection_set_3_upload,collection_set_3_upload_upload,,Ausgeführt als Benutzer: ''[domain\username]''.

Fehler beim Protokollieren des Paketanfangsereignisses f³r Paket: 'QueryActivityUpload'.
    Interner Fehler ------------------> Zeilennr.:    0 Quelle: 'Microsoft SQL Server Native Client 10.0' Instanz: 'SQL-08' Prozedur: 'sp_syscollector_event_onpackagebegin'
        Zeilennr.: 35 Fehlernummer: 14262 Fehlerstatus: 1 Fehlerschweregrad: 16 Fehlermeldung: 'Das angegebene @parent_log_id-Objekt ('53707') ist nicht vorhanden.'
        Hilfedatei: '(null)'<c/> Hilfekontext:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. Ende des OLE DB-Fehlerdatensatzspeichers.

Fehler beim Abrufen einer Paketprotokoll-ID f³r Paket: QueryActivityUpload<c/> vorherige Meldungen sollten den Grund f³r den Fehler erlõutern.
Das Paket wird stattdessen die Protokoll-ID: 53706 verwenden.Fehler beim Protokollieren des Paketendeereignisses f³r Paket: 'QueryActivityUpload'.
    Interner Fehler ------------------> Zeilennr.:    0 Quelle: 'Microsoft SQL Server Native Client 10.0' Instanz: 'SQL-08' Prozedur: 'sp_syscollector_verify_event_log_id'
        Zeilennr.: 22 Fehlernummer: 14262 Fehlerstatus: 1 Fehlerschweregrad: 16 Fehlermeldung: 'Das angegebene @log_id-Objekt ('53706') ist nicht vorhanden.'
        Hilfedatei: '(null)'<c/> Hilfekontext:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. Ende des OLE DB-Fehlerdatensatzspeichers.

Fehler beim Protokollieren des Paketendeereignisses f³r Paket: 'Set_{2DC02BD6-E230-4C05-8516-4E8C0EF21F95}_Master_Package_Upload'.
    Interner Fehler ------------------> Zeilennr.:    0 Quelle: 'Microsoft SQL Server Native Client 10.0' Instanz: 'SQL-08' Prozedur: 'sp_syscollector_verify_event_log_id'
        Zeilennr.: 22 Fehlernummer: 14262 Fehlerstatus: 1 Fehlerschweregrad: 16 Fehlermeldung: 'Das angegebene @log_id-Objekt ('53707') ist nicht vorhanden.'
        Hilfedatei: '(null)'<c/> Hilfekontext:    0 GUID: {0C733A63-2A1C-11CE-ADE5-00AA0044773D}. Ende des OLE DB-Fehlerdatensatzspeichers.

Das Masterpaket wurde mit einem Fehler beendet<c/> vorherige Fehlermeldungen sollten die Ursache erlõutern. Prozessexitcode 5. Fehler bei Schritt.,00:00:14,0,0,,,,0
"
The error occurs not every time the job is running, but when it appears, the log entries are always similar to the one above.

I hope this helps and we will see a fix for this soon.

Thanks,

Gunter
Posted by Microsoft on 4/6/2011 at 3:45 PM
I have added Auditing, XEvent session defenition to capture logs that can help us narrow down this issue
http://blogs.msdn.com/b/sqlagent/archive/2011/04/06/auditing-changes-done-to-syscollector-execution-log-internal-amp-tracking-root-cause-of-error-14262.aspx

If you can send us gathered logs, it would be really helpful for us

Thanks
Sethu Srinivasan[MSFT]
Posted by MG Support on 3/11/2011 at 3:53 PM
For me it normally either fails on the 12:00 PM or 12:00 AM run, but at least once has failed on a 6:00 PM run. (This happens on both of our 2008 R2 servers (Prod and Dev.)

The most recent failure was shortly after updating Dev to CU6 (10.50.1765)
Posted by Microsoft on 2/28/2011 at 1:11 PM
Hello Alvaro,

Thank you for reporting this issue - we are investigating and we will get back to you shortly.

Thanks,

Alex Grach