Discussion:
SQL2000 shown as not monitored in SCOM 2007
(too old to reply)
JP GUTTON
2007-05-17 13:30:02 UTC
Permalink
Hello

I setup the SCOM agent on different SQL2000 server and on the monitoring tab
under sql computer view they are shown as not monitored, the agent run under
a run as account which has SA and DBO rights on all DB (we are in test env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
Anders Bengtsson
2007-05-17 19:48:48 UTC
Permalink
Hi JP,

Try run your agent with local system as action account.

---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se

JG> Hello
JG>
JG> I setup the SCOM agent on different SQL2000 server and on the
JG> monitoring tab
JG> under sql computer view they are shown as not monitored, the agent
JG> run under
JG> a run as account which has SA and DBO rights on all DB (we are in
JG> test env.)
JG> I have a SQL2005 which is shown as monitored.
JG> Do you have an idea ?
JG> Thanks
JG> JP
GD
2007-05-21 12:44:16 UTC
Permalink
JohnR posted this in the SQL group a while back - sounds like it may be the
issue.

"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor via the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."

That might be your problem.

Cheers

Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the monitoring tab
under sql computer view they are shown as not monitored, the agent run under
a run as account which has SA and DBO rights on all DB (we are in test env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
JP GUTTON
2007-06-13 15:48:01 UTC
Permalink
OK I did it and it change nothing but I get alert, I think it's just a
cosmetic things.
I have a pb on a SQL cluster, both node are set as acting as proxy, in
agentless agent I see my virtual resource (cluster, SQL and TC) but all of
them are marked as not monitored, and no rules seems to be applied to the
Virtual SQL server. I don't see specific errors in the log
Any ideas ?
Post by GD
JohnR posted this in the SQL group a while back - sounds like it may be the
issue.
"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor via the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the monitoring tab
under sql computer view they are shown as not monitored, the agent run under
a run as account which has SA and DBO rights on all DB (we are in test env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
Anders Bengtsson
2007-06-14 04:21:31 UTC
Permalink
Hi,

If it is a cluster you might need to right-click on it and choose to start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se

JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG> "GD" wrote:
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it may
be the issue.
"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor via the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
JP GUTTON
2007-06-14 13:48:01 UTC
Permalink
but in SCOM 2007 I don't have the choice to start monitoring it, I put my 2
node as acting as proxy, it discovers all the network name resource but don't
monitor them, I did the same steps on a 3 node Exchange cluster and it works
perfectly.
Post by Anders Bengtsson
Hi,
If it is a cluster you might need to right-click on it and choose to start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it may
be the issue.
"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor via the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
Anders Bengtsson
2007-06-14 20:49:57 UTC
Permalink
Hi JP,

After installing agents to them they should be shown under Windows Server
Cluster Computers, where you can choose start managing. If you do some global
changes you might need to restart opsmgr services, also on the cluster agents.

---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se

JG> but in SCOM 2007 I don't have the choice to start monitoring it, I
JG> put my 2 node as acting as proxy, it discovers all the network name
JG> resource but don't monitor them, I did the same steps on a 3 node
JG> Exchange cluster and it works perfectly.
JG>
JG> "Anders Bengtsson" wrote:
JG>
Post by Anders Bengtsson
Hi,
If it is a cluster you might need to right-click on it and choose to start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it
may be the issue.
"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor
via
the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
J
Kamal Hassan
2007-06-27 19:50:04 UTC
Permalink
Wondering if you resolved the issue of "NOT MONITORED" for SQL 2000 computer?

I am also UNABLE to resolve/fix the issue of "NOT MONITORED"

Regards,

Kamal
Post by Anders Bengtsson
Hi JP,
After installing agents to them they should be shown under Windows Server
Cluster Computers, where you can choose start managing. If you do some global
changes you might need to restart opsmgr services, also on the cluster agents.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> but in SCOM 2007 I don't have the choice to start monitoring it, I
JG> put my 2 node as acting as proxy, it discovers all the network name
JG> resource but don't monitor them, I did the same steps on a 3 node
JG> Exchange cluster and it works perfectly.
JG>
JG>
Post by Anders Bengtsson
Hi,
If it is a cluster you might need to right-click on it and choose to start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it
may be the issue.
"Here is the solution for this problem. The SQL 2000 state will be 'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor
via
the
Authoring tab. For some reason health role up is disabled for SQL 2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide. If ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not enable via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
Anders Bengtsson
2007-06-27 21:54:28 UTC
Permalink
Hi Kamal,

There is a thread about this in the microsoft.public.general.opsmgr.general
news group, search for the thread named "Problem monitoring SQL 2000 DB".
it will explain how to enable all needed rules and monitors.

---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se

KH> Wondering if you resolved the issue of "NOT MONITORED" for SQL 2000
KH> computer?
KH>
KH> I am also UNABLE to resolve/fix the issue of "NOT MONITORED"
KH>
KH> Regards,
KH>
KH> Kamal
KH>
KH> "Anders Bengtsson" wrote:
KH>
Post by Anders Bengtsson
Hi JP,
After installing agents to them they should be shown under Windows
Server Cluster Computers, where you can choose start managing. If you
do some global changes you might need to restart opsmgr services,
also on the cluster agents.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> but in SCOM 2007 I don't have the choice to start monitoring it, I
JG> put my 2 node as acting as proxy, it discovers all the network name
JG> resource but don't monitor them, I did the same steps on a 3 node
JG> Exchange cluster and it works perfectly.
JG>
JG>
Post by Anders Bengtsson
Hi,
If it is a cluster you might need to right-click on it and choose
to
start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it
may be the issue.
"Here is the solution for this problem. The SQL 2000 state will
be
'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor
via
the
Authoring tab. For some reason health role up is disabled for
SQL
2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide.
If
ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not
enable
via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
J
Kamal Hassan
2007-06-28 14:28:03 UTC
Permalink
Thanks Anders. much appreciated.. I am unable to locate/find it but wil keep
looking.

Kamal.
Post by Anders Bengtsson
Hi Kamal,
There is a thread about this in the microsoft.public.general.opsmgr.general
news group, search for the thread named "Problem monitoring SQL 2000 DB".
it will explain how to enable all needed rules and monitors.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
KH> Wondering if you resolved the issue of "NOT MONITORED" for SQL 2000
KH> computer?
KH>
KH> I am also UNABLE to resolve/fix the issue of "NOT MONITORED"
KH>
KH> Regards,
KH>
KH> Kamal
KH>
KH>
Post by Anders Bengtsson
Hi JP,
After installing agents to them they should be shown under Windows
Server Cluster Computers, where you can choose start managing. If you
do some global changes you might need to restart opsmgr services,
also on the cluster agents.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> but in SCOM 2007 I don't have the choice to start monitoring it, I
JG> put my 2 node as acting as proxy, it discovers all the network name
JG> resource but don't monitor them, I did the same steps on a 3 node
JG> Exchange cluster and it works perfectly.
JG>
JG>
Post by Anders Bengtsson
Hi,
If it is a cluster you might need to right-click on it and choose
to
start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it
may be the issue.
"Here is the solution for this problem. The SQL 2000 state will
be
'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor
via
the
Authoring tab. For some reason health role up is disabled for
SQL
2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide.
If
ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not
enable
via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
Jonathan Hambrook
2007-07-02 12:20:04 UTC
Permalink
Funny I have just writen alittle step by step on my blog after getting the
same question from a colleage. Check it out.

However, I have been talking with MS about monitoring SQL 2000 32bit on a
x64 Windows 2003 Cluster. They have told me its not supported, SCOM doesnt
seem to even discover the SQL.

I know that not what you were after but a little extra info
--
Jonathan Hambrook

http://opsmgr.wordpress.com
Post by Kamal Hassan
Thanks Anders. much appreciated.. I am unable to locate/find it but wil keep
looking.
Kamal.
Post by Anders Bengtsson
Hi Kamal,
There is a thread about this in the microsoft.public.general.opsmgr.general
news group, search for the thread named "Problem monitoring SQL 2000 DB".
it will explain how to enable all needed rules and monitors.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
KH> Wondering if you resolved the issue of "NOT MONITORED" for SQL 2000
KH> computer?
KH>
KH> I am also UNABLE to resolve/fix the issue of "NOT MONITORED"
KH>
KH> Regards,
KH>
KH> Kamal
KH>
KH>
Post by Anders Bengtsson
Hi JP,
After installing agents to them they should be shown under Windows
Server Cluster Computers, where you can choose start managing. If you
do some global changes you might need to restart opsmgr services,
also on the cluster agents.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> but in SCOM 2007 I don't have the choice to start monitoring it, I
JG> put my 2 node as acting as proxy, it discovers all the network name
JG> resource but don't monitor them, I did the same steps on a 3 node
JG> Exchange cluster and it works perfectly.
JG>
JG>
Post by Anders Bengtsson
Hi,
If it is a cluster you might need to right-click on it and choose
to
start
monitor it.
---
Regards
Anders Bengtsson, MCSE:Security
http://www.contoso.se
JG> OK I did it and it change nothing but I get alert, I think it's just
JG> a
JG> cosmetic things.
JG> I have a pb on a SQL cluster, both node are set as acting as proxy,
JG> in
JG> agentless agent I see my virtual resource (cluster, SQL and TC) but
JG> all of
JG> them are marked as not monitored, and no rules seems to be applied
JG> to the
JG> Virtual SQL server. I don't see specific errors in the log
JG> Any ideas ?
JG>
Post by GD
JohnR posted this in the SQL group a while back - sounds like it
may be the issue.
"Here is the solution for this problem. The SQL 2000 state will
be
'Not
Monitored' until you enable the SQL 2000 "Health Role Up" monitor
via
the
Authoring tab. For some reason health role up is disabled for
SQL
2000 and
has a different role up structure to SQL 2005. Enabling SQL 2000 roll up
does not seem to be mentioned in the SQL Management pack guide.
If
ever you
see "Not Monitored" and no obvious errors are in the Operations Manager
event log then check whether the rule is enabled and if not
enable
via an
override."
That might be your problem.
Cheers
Graham
Post by JP GUTTON
Hello
I setup the SCOM agent on different SQL2000 server and on the
monitoring
tab
under sql computer view they are shown as not monitored, the agent
run
under
a run as account which has SA and DBO rights on all DB (we are in
test
env.)
I have a SQL2005 which is shown as monitored.
Do you have an idea ?
Thanks
JP
Loading...