Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2008 Management Data Warehouse problem Expand / Collapse
Author
Message
Posted Tuesday, May 26, 2009 8:12 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, March 23, 2014 9:54 AM
Points: 142, Visits: 557
Hi All,

We have set up sql server 2008 management dataware house (mdw) a month ago, it was working correctly for some time, our configuration is two 2-node SQL Server 2008 failover cluster (4 machine at total) as :

Cluster1:
Node 1 : Instance A
Node 2 : Instance B + Instance C

Cluster2:
Node 1 : Instance D
Node 2 : Stand by

so 4 instance at total. This was the configuration, our problem is:

MDW collection sets are working well for all instances except "Server Activity" collection set on instances B and C; server activity collection set is not working on this node.

When I looked at the "view log" the main error is:

The thread "ExecMasterPackage" has timed out 3600 seconds after being signaled to stop. on upload step of collection (its a cached collection)

By using dbo.sp_syscollector_update_collection_set i have set logging_level to 2 for the collection I went deeper in the error:

At performance counters part there is a warning which is repeated multiple times (not an error):

The output column "collection_time" (703) on output "Raw File Source Output" (40) and component "RAW - Read current tempoary storage - purpose - obtain counter paths" (36) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.

As far as i see the error is the job cannot be finished in one hour and error comes:

The thread "ExecMasterPackage" has timed out 3600 seconds after being signaled to stop. on upload step of collection (its a cached collection).

- All instances works with the same MDW.
- I have setup a new MDW but problem is same
- I have tried different schedules up to 6hours for uploading for Server activity, but the errors comes and job fails,

Any ideas will be appreciated,

Thanks
Serter






Post #723272
Posted Wednesday, July 08, 2009 8:15 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, April 04, 2014 9:05 AM
Points: 336, Visits: 766
I'm also experiencing a similar issue. Anyone know how to fix this?
Post #749274
Posted Thursday, August 26, 2010 6:27 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, June 11, 2012 1:11 PM
Points: 60, Visits: 172
Any solution to this ..even I am facing the same issue. Any pointer would be very helpful
Post #976078
Posted Friday, August 27, 2010 12:40 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Sunday, March 23, 2014 9:54 AM
Points: 142, Visits: 557
SP1 has resolved some of the errors for me, now there is arithmetic overflow error, as I searched the internet, it is said SP1 CU8 is the cure, but I haven't applied the CU yet..
Post #976179
Posted Tuesday, September 21, 2010 1:24 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 09, 2013 3:50 PM
Points: 1, Visits: 220
I had similar issue in my environment. I had restarted each collection set seperately. After then the job ran successfully and performance data has got collection in the Warehouse database.
Post #990697
Posted Thursday, November 25, 2010 3:37 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, August 29, 2011 3:51 PM
Points: 1, Visits: 13
I am also getting this timeout error sporadically. Keen to get this resolved. Will keep investigating & advise if I find a fix.
Post #1026585
Posted Thursday, May 05, 2011 5:58 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 17, 2012 11:29 PM
Points: 138, Visits: 236
I am facing similar issue only for Server Activity Collection Set. IT upload job runs for more than 1hr it fails with below error message
the thread "ExecMasterPackage" has timed out 3600 seconds after being signaled to stop.

I have also applied SP2 on the server.
Post #1103771
Posted Thursday, May 12, 2011 6:06 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 17, 2012 11:29 PM
Points: 138, Visits: 236
I am now trying to have upload job for server activity run 3 times a day every 8 hr. Also I have given retry attempts and retry interval to 1 and 5 respectively in the job. Let's C how it is going and will update accordingly within 1 day.
Post #1107624
Posted Wednesday, July 27, 2011 9:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, March 08, 2013 8:10 AM
Points: 30, Visits: 135
I have made a lot of changes to fix this issue, but think I finally [serendipitously] figured out how to resolve this yesterday.

I actually did two things yesterday. 1. I capped SQL Server memory so that 2GB were free for the OS. 2. I turned off all data collectors [I had 7 managed instances] and added them back one at a time. There is one more important note: I was monitoring the server that the Utility was running on in addition to six other servers. I have not turned data collection back on for that instance.

I think it was change 2. that actually made the difference, but include both for your information. Since that time, I have only had one "The thread "ExecMasterPackage" has timed out" error on the busiest server. I was getting them ALL the time on several servers.

I suspect the problem is related to the these failures causing the log on the utility server to get backed up and rendering it unable to carry the backlog. Our utility server is lightly horse-powered, since this is a relatively new technology. I think "the Utility" [which is a totally dumb name] requires quite a bit of IO throughput in order to avoid problems. I suspect I increased the conflict by monitoring the local system. I also suspect that the problem is related to DCEXEC executions and stops.

Good luck. Hope this helps!





Post #1149292
Posted Wednesday, August 29, 2012 1:10 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, April 04, 2014 9:05 AM
Points: 336, Visits: 766
I noticed this was happening on one of my SQL instances.

In order to fix the problem I followed these steps:
1) right click Data Collection and select Disable Data Collection (this disables the SQL Agent jobs)
2) stop the SQL Server Agent service
3) opened task manager and killed all DCEXEC.exe processes (I think these were hung)
4) start the SQL Server Agent service
5) right click Data Collection and select Enable Data Collection

All pending cache files were processed and new ones were being re-created again after doing this.
Post #1351866
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse