|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Error 0x80041010 WinMgmt when launching SQL SERVER MANAGEMENT STUDEvent filter with query "select * from __InstanceModificationEvent within 10
where TargetInstance isa 'Win32_Service'" could not be (re)activated in namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error 0x80041010. Events may not be delivered through this filter until the problem is corrected. Did someone have the answer for this problem of SQL2005? Thanks in advance. Hi Pan,
Thank you for your posting! From your description, my understanding of this issue is: When you try to open the SQL SERVER MANAGEMENT STUDIO to connect to a SQL cluster, you get the following error in the event log: Event filter with query "select * from __InstanceModificationEvent within 10 where TargetInstance isa 'Win32_Service'" could not be (re)activated in namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of error 0x80041010. Events may not be delivered through this filter until the problem is corrected. If I misunderstood your concern, please feel free to let me know. Based on my research, this is a known issue that is caused by WMI and there will be a fix for this known issue on SQL Server SP2. If it has much business impact on you, I recommend that you open a Support incident with Microsoft Customer Service and Support (CSS) so that a dedicated Support Professional can work with you in a more timely and efficient manner. If you need any help in this regard, please let me know. For a complete list of Microsoft Customer Service and Support phone numbers, please go to the following address on the World Wide Web: <http://support.microsoft.com/directory/overview.asp> If you are outside the US please see http://support.microsoft.com for regional support phone numbers. If there are further questions on the issue, please feel free to let us know. Have a great day! Sincerely, Wei Lu Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi Wei Liu,
Someone suggested to replace . with the instance name in this string "\\.\root" in this "sqlmgmproviderxpsp2up.mof" file will eliminate this error. Because the . in "\\.\root" is pointed to local server. Would you please verify this work around because I don't have a test sever to test? Thanks, Judy Wei Lu [MSFT] wrote: Show quote > Hi Pan, > > Thank you for your posting! > > From your description, my understanding of this issue is: When you try to > open the SQL SERVER MANAGEMENT STUDIO to connect to a SQL cluster, you get > the following error in the event log: > > Event filter with query "select * from __InstanceModificationEvent within > 10 > where TargetInstance isa 'Win32_Service'" could not be (re)activated in > namespace "//./root/Microsoft/SqlServer/ComputerManagement" because of > error > 0x80041010. Events may not be delivered through this filter until the > problem > is corrected. > > If I misunderstood your concern, please feel free to let me know. > > Based on my research, this is a known issue that is caused by WMI and there > will be a fix for this known issue on SQL Server SP2. > > If it has much business impact on you, I recommend that you open a Support > incident with Microsoft Customer Service and Support (CSS) so that a > dedicated Support Professional can work with you in a more timely and > efficient manner. If you need any help in this regard, please let me know. > > For a complete list of Microsoft Customer Service and Support phone > numbers, please go to the following address on the World Wide Web: > > <http://support.microsoft.com/directory/overview.asp> > > If you are outside the US please see http://support.microsoft.com for > regional support phone numbers. > > If there are further questions on the issue, please feel free to let us > know. > > Have a great day! > > Sincerely, > > Wei Lu > Microsoft Online Community Support > > ================================================== > > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. Hi Judy,
Thank you for the reply. Based on my research, this known issue is caused by the SQL Object Explorer use the different component to create the ManagementScope. I don't think the replacement will resolve this issue. If it has much business impact on you, I recommend that you open a Support incident with Microsoft Customer Service and Support (CSS) so that a dedicated Support Professional can work with you in a more timely and efficient manner. Have a great day! Sincerely, Wei Lu Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi Judy,
How is everything going? Please feel free to let me know if you need any assistance. Sincerely, Wei Lu Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi We Lu,
Thank you for the quick response. I will wait for the SP2 release. Best regards, Judy Wei Lu [MSFT] wrote: Show quote > Hi Judy, > > Thank you for the reply. > > Based on my research, this known issue is caused by the SQL Object Explorer > use the different component to create the ManagementScope. I don't think > the replacement will resolve this issue. > > If it has much business impact on you, I recommend that you open a Support > incident with Microsoft Customer Service and Support (CSS) so that a > dedicated Support Professional can work with you in a more timely and > efficient manner. > > Have a great day! > > Sincerely, > > Wei Lu > Microsoft Online Community Support > > ================================================== > > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > > ================================================== > This posting is provided "AS IS" with no warranties, and confers no rights. Hi Judy,
Thank you for the update. I will inform you as soon as possible if the service pack is ready. Thank you! Sincerely, Wei Lu Microsoft Online Community Support ================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi:
SQL 2005 sp2 is already release. Just like to know if this error 0x80041010 have already been fixed in SP2 of SQL 2005. In the list of bugs fixed by SP2 the error 0x80041010 is not included, check this site http://support.microsoft.com/kb/921896 Thanks. *** Sent via Developersdex http://www.developersdex.com *** I was having the same problem on my x64 box running SQL 2005 SP1 in
cluster. What happen that somehow permissions were removed from local administrators and DBA's group. I had to login as sa and reassign the system admin permissions to local admin and dba's group and it start wotking fine. BC *** Sent via Developersdex http://www.developersdex.com *** On Apr 6, 3:37 am, Bader Cheema <bader_chee***@hotmail.com> wrote:
> I was having the same problem on my x64 box running SQL 2005 SP1 in Hi,> cluster. > What happen that somehow permissions were removed from local > administrators and DBA's group. I had to login as sa and reassign the > system admin permissions to local admin and dba's group and it start > wotking fine. > > BC > > *** Sent via Developersdexhttp://www.developersdex.com*** I tried your solution but can't understand what you mean. what do you mean by local administrators? BUILTIN\Administrators? it already has sysadmin in server roles. and I didn't find DBA's group in my SQL configuration. Please elaborate your solution for me. I didn't install SQL 2005 SP2 yet. Does it solve this problem? Thanks in advance. |
|||||||||||||||||||||||