I am running SQL2000 sp3 with 819 hotfix on a 2003
Cluster. When I am on one of the database servers in the
cluster I can select from a table and get data returned.
When I am on the webserver and use EnterPrise I can see
the tables but when I try to select I get 'Unknown Error'.
The same select works from ISQL/W GUI and isql at the
command line while on the webserver.
Any ideas on what to look for would be helpful, nothing is
being logged in the eventlog or the sql log.
Thanks
Check the following;
- The MDAC version on the good and the bad machine. If possible upgrade to
the latest version of MDAC
- Capture the T-SQL command from profiler while you are try to retrieve the
data and see if you can identify the issue.
- Permissions
- The client configuration options by comparing them to the good machine.
HTH
SQL Server Support
Agnes Panosian
Showing posts with label hotfix. Show all posts
Showing posts with label hotfix. Show all posts
Wednesday, March 21, 2012
Enterprise Manager Unknown Error
Enterprise Manager Stops Responding
I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?
"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database

Cheers,
harry
|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>
|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?
"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?
|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
Cheers,
harry
|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>
|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
Enterprise Manager Stops Responding
I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
:)
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> > Manager
> > on the server via RDP, the server stops responding. At this time, when
> > IRDP
> > another session I dont get the windows login screen...all I get is grey
> > screen and mouse pointer....it is as if the server is hung. Most of the
> > times, I have no other option than hard rebooting the server.
> >
> > What is wrong here?
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> When you reboot the server, do you see anything in the event log or SQL
>> Server error logs?
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
>> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187)
>> > on
>> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
>> > Manager
>> > on the server via RDP, the server stops responding. At this time, when
>> > IRDP
>> > another session I dont get the windows login screen...all I get is grey
>> > screen and mouse pointer....it is as if the server is hung. Most of
>> > the
>> > times, I have no other option than hard rebooting the server.
>> >
>> > What is wrong here?
>>sql
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
> on the server via RDP, the server stops responding. At this time, when IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
:)
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> > Manager
> > on the server via RDP, the server stops responding. At this time, when
> > IRDP
> > another session I dont get the windows login screen...all I get is grey
> > screen and mouse pointer....it is as if the server is hung. Most of the
> > times, I have no other option than hard rebooting the server.
> >
> > What is wrong here?
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
--
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>> When you reboot the server, do you see anything in the event log or SQL
>> Server error logs?
>> --
>> Aaron Bertrand
>> SQL Server MVP
>>
>>
>> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
>> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>> > I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187)
>> > on
>> > Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
>> > Manager
>> > on the server via RDP, the server stops responding. At this time, when
>> > IRDP
>> > another session I dont get the windows login screen...all I get is grey
>> > screen and mouse pointer....it is as if the server is hung. Most of
>> > the
>> > times, I have no other option than hard rebooting the server.
>> >
>> > What is wrong here?
>>sql
Enterprise Manager Stops Responding
I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) o
n
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manage
r
> on the server via RDP, the server stops responding. At this time, when IRD
P
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database

Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manager
on the server via RDP, the server stops responding. At this time, when IRDP
another session I dont get the windows login screen...all I get is grey
screen and mouse pointer....it is as if the server is hung. Most of the
times, I have no other option than hard rebooting the server.
What is wrong here?"Rajan" wrote:
> I'm running SQL 2000 Server Enterprise Edition, SP4 (hotfix - 8.00.2187) o
n
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise Manage
r
> on the server via RDP, the server stops responding. At this time, when IRD
P
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||When you reboot the server, do you see anything in the event log or SQL
Server error logs?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
> I'm running SQL 2000 Server Standard Edition, SP4 (hotfix - 8.00.2187) on
> Windows 2003 Server Standard x64 bit. Whenever I run SQL Enterprise
> Manager
> on the server via RDP, the server stops responding. At this time, when
> IRDP
> another session I dont get the windows login screen...all I get is grey
> screen and mouse pointer....it is as if the server is hung. Most of the
> times, I have no other option than hard rebooting the server.
> What is wrong here?|||This can happen on SQL 2000 servers with lots of (large)tables (it has to
load all tables in memory) in combination with minimal availability of
resources and a very bussy database.
This can lead to a time- out in enterprise manager.
after you made the rdp session.Use query analyzer to connect to the database
Cheers,
harry|||Nope...nothing reported in either logs.
"Aaron Bertrand [SQL Server MVP]" wrote:
> When you reboot the server, do you see anything in the event log or SQL
> Server error logs?
> --
> Aaron Bertrand
> SQL Server MVP
>
>
> "Rajan" <Rajan@.discussions.microsoft.com> wrote in message
> news:E79E49FB-AEC5-42ED-A296-96DBB92A9944@.microsoft.com...
>
>|||Well, it might just be that you are not waiting long enough, as another
poster suggested. Can you use Query Analyzer instead? Can you use
Enterprise Manager remotely instead of only within an RDP session?
Aaron Bertrand
SQL Server MVP
"Rajan" <Rajan@.discussions.microsoft.com> wrote in message
news:8D2F17A5-2A89-418F-9980-38796783319C@.microsoft.com...[vbcol=seagreen]
> Nope...nothing reported in either logs.
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Monday, March 19, 2012
Enterprise Manager problem : jobs and alerts flash, while Agent properties lock-up
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?
HGHumphreyYou can change the location of sql agent log file in the
registry, go to
SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent
under My Computer\HKEY_LOCAL_MACHINE
and change the file path in ErrorLogFile
Alternatively if you have another pc with Enterprise
Manager you can use it to manage your server.
hth.
>--Original Message--
>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
>.
>|||That does not work either. Any other clues?
HGHumphrey
<anonymous@.discussions.microsoft.com> wrote in message news:<ebd201c3f0b2$60ca6e30$a601280a@.phx.gbl>...
> You can change the location of sql agent log file in the
> registry, go to
> SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent
> under My Computer\HKEY_LOCAL_MACHINE
> and change the file path in ErrorLogFile
> Alternatively if you have another pc with Enterprise
> Manager you can use it to manage your server.
> hth.
>
> >--Original Message--
> >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
> >.
> >|||This 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@.posting.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
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?
HGHumphreyYou can change the location of sql agent log file in the
registry, go to
SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent
under My Computer\HKEY_LOCAL_MACHINE
and change the file path in ErrorLogFile
Alternatively if you have another pc with Enterprise
Manager you can use it to manage your server.
hth.
>--Original Message--
>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
>.
>|||That does not work either. Any other clues?
HGHumphrey
<anonymous@.discussions.microsoft.com> wrote in message news:<ebd201c3f0b2$60ca6e30$a601280a@.phx.gbl>...
> You can change the location of sql agent log file in the
> registry, go to
> SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent
> under My Computer\HKEY_LOCAL_MACHINE
> and change the file path in ErrorLogFile
> Alternatively if you have another pc with Enterprise
> Manager you can use it to manage your server.
> hth.
>
> >--Original Message--
> >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
> >.
> >|||This 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@.posting.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
Sunday, March 11, 2012
Enterprise Manager problem : jobs and alerts flash, while Agent properties lock-up
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
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:
Posts (Atom)