I am having a problem with Enterprise Manager. The server is SQL
Server 2000, SP 2, with the hotfix (the server is used for an ePiphany
application, which does not support sp3).
Anyway, when you try to "double-click" a job, it flashes up once, then
disappears. The same can be said for the alerts, and it does not list
any operators (if you query sysoperators, you see all the operators).
In addition, if you try to display the SQL Agent properties,
Enterprise Manager locks up.
This problem has been narrowed down to only inflict the items under
Management>SQL Server Agent. It does not affect viewing current
activity, maint plans, backup devices, or the SQL Error log.
Their is a KB article about the same type of problem with maintenance
plans, and the fix is to alter the path for the log file of SQL Agent.
This is not possible with this problem because you cannot get to the
properties to alter the log file location for the agent.
Anybody seen this problem?
HGHumphreyThis has been fixed. It was because we had an entry in the
Sysoperators table that was blank. Once this was deleted, and the
services were restarted, it was fine.
Thanks,
HGHumphrey
hhumphrey@.hrblock.com (HGHumphrey) wrote in message news:<188b70ac.0402101354.6b1ffbcb@.p
osting.google.com>...
> I am having a problem with Enterprise Manager. The server is SQL
> Server 2000, SP 2, with the hotfix (the server is used for an ePiphany
> application, which does not support sp3).
> Anyway, when you try to "double-click" a job, it flashes up once, then
> disappears. The same can be said for the alerts, and it does not list
> any operators (if you query sysoperators, you see all the operators).
> In addition, if you try to display the SQL Agent properties,
> Enterprise Manager locks up.
> This problem has been narrowed down to only inflict the items under
> Management>SQL Server Agent. It does not affect viewing current
> activity, maint plans, backup devices, or the SQL Error log.
> Their is a KB article about the same type of problem with maintenance
> plans, and the fix is to alter the path for the log file of SQL Agent.
> This is not possible with this problem because you cannot get to the
> properties to alter the log file location for the agent.
> Anybody seen this problem?
> HGHumphrey
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment