![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#3
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#4
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#5
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#6
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#7
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#8
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#9
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
#10
| |||
| |||
|
|
I've researched a lot about the namespace error that some people get when connecting to a cluster with Object Explorer from SSMS, however, no answer is generally proposed that encompasses my particular situation. We have a two node failover cluster that we recently upgraded to 2005. Any time someone connects the Object Browser to our virtual server, we get the ole 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. All my research has been that this would be addressed in SP2. Well we're on version 9.00.3042.00, meaning we've already got SP2 on our cluster. I was wondering if anyone has any insight into what may be causing this issue. Thanks in advance, O. |
![]() |
| Thread Tools | |
| Display Modes | |
| |