March 8, 2015 at 11:40 pm
I’m having a fight with a MDW on SQL ENT 2012 SP2.
It was working fine for a bit, then for some reason it stops with the following error.
Failed to create kernel event for collection set: {2DC02BD6-E230-4C05-8516-4E8516-4E8C0EF21F95}. Inner Error-
Cannot create a file when that file already exits.
Now the file does not exist, not in the cache folder anyway. I have tried reconfiguring both the MDW and the data collection sets, disabling/enabling, completely removed it using SP__SYSCOLLECTOR_CLEANUP_COLLECTOR. Set it back up again, but the exact same problem exists.
I read that it could be a rogue DCEXEC command and, at the command prompt ran…
TASKLIST /SVC /FI “IMAGENAME EQ DCEXEC.EXE”
Which returned…
Image NamePIDServices
DCEXEC.EXE988N/A
DCEXEC.EXE2432N/A
As the disk collector and utility are actually working, I thought this must be them, but I went to processes , but could not see any DCEXEC entries or any PIDs with those numbers.
Next I tried...
Kill ‘2DC02BD6-E230-4C05-8516-4E8516-4E8C0EF21F95’;
...this has made no difference at all.
I’m at the end of my tether on this. Is there anybody that could provide an answer? The only thing I have not tried is a server reboot. Even if it worked, there must be a way to deal with this without rebooting the server!
I cant think of anything else I can try.
Thank you for any suggestions you may have, I have nowhere left to turn.
Regards,
D.
November 18, 2015 at 9:04 am
Good luck. I have a call into Microsoft on this issue this very moment. Please familiarize yourself with SQL 2012 SP2 CU7. There is supposed to be a fix in this CU, but it did not fix it for me. https://support.microsoft.com/en-us/kb/3072100. Specifically this article: https://support.microsoft.com/en-us/kb/3062001 (a link from the CU).
I'll update this thread if I learn anything that can help, but right now I'm getting frustrated with their lack of urgency.
November 18, 2015 at 9:10 am
Also, if you manually stop the MDW collection jobs, those DCEXEC processes should also close themselves.
November 18, 2015 at 9:50 am
Also found this:
Posted by ChrisAllenNC on 6/15/2015 at 12:11 PM
We've been able to resolve the issue by taking the SSIS packages off of an instance that wasn't updated yet and reloading them after the update. Comparing the XML data of the old/new packages it appears that the package built for 2008/2008 R2 ended up in the 2012 update. In 2008/2008 R2 the command column is only 16 characters. Also if you look at the XML the connection was dropped from SQLCLI11 to SQLCLI10.
The above was at the bottom of this Microsoft page: https://connect.microsoft.com/SQLServer/feedback/details/1138283/data-collection-query-statistics-collection-set-not-working-anymore-after-upgrade-to-sql-server-2012-sp2
I've not seen any 'admission' that MS used the wrong xml in their 2012 update, but it would sure explain a lot. I'll be sharing this with MS Support when they get around to calling me back.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply