Erroneous job status display in Enterprise Manager

From: Scott Ashby (Scott.Ashby@SMNA.com)
Date: 10/29/02 

From: Scott.Ashby@SMNA.com (Scott Ashby)
Date: 29 Oct 2002 13:53:00 -0800

Enterprise Manager is reporting false job status information in some
cases on our Windows 2000 SQL Server (running Service Pack 2) on
Windows 2000 Service Pack 3. When you define a SQL login (using
SQL-based security, rather than integrated security), and you set a
login name of mixed case (i.e., Temp_SysAdmin), create a job to be run
by SQLAgent that is owned by this ID, then run the job, come back and
check on the job, Enterprise Manager shows it is running.

If you disconnect from Enterprise Manager, connect as some other
combination of upper and lower case characters other than the correct
case (i.e., temp_sysadmin), then check the job, Enterprise Manager
will erroneously report the job is not running. You can verify this
by disconnecting, reconnecting as the case-correct login id, and
you'll find the Enterprise Manager does tell you that the job is
indeed running.

Does anyone have any explanation for why this behavior occurs? It has
caused us to stop and restart the SQLAgent at times when we shouldn't,
resulting in killed jobs... I'd love to have a fix for it.

Scott Ashby
DBA
Swedish Match, North America
scott.ashby@smna.com

O/S: Win 2000 SP3
SQL Server: 2000 SP2
SQL Collating sequence: SQL_Latin1_General_CP1_CI_AS

Relevant Pages

  • Connecting to SQLServer 2000 from ASP.NET
    ... I have an ASP.NET application that connects to a SQL Server database. ... Windows XP SP2 on development PCs which host the ASP.NET application. ... I managed to add MyDomain\AUser as a SQL user in Enterprise Manager. ... Computer: MachineName ...
    (microsoft.public.sqlserver.server)
  • Connecting to SQLServer 2000 from ASP.NET
    ... I have an ASP.NET application that connects to a SQL Server database. ... Windows XP SP2 on development PCs which host the ASP.NET application. ... I managed to add MyDomain\AUser as a SQL user in Enterprise Manager. ... Computer: MachineName ...
    (microsoft.public.dotnet.framework.aspnet)
  • invalid value specified for STOPAT parameter
    ... I too had problems when trying to perform a Point in Time restore ... Enterprise Manager, I receive a error message "Invalid value specified ... "YDM" by SQL Server where as the value supplied by the SQL Server ... Select "British English", then hit OK. ...
    (microsoft.public.sqlserver.server)
  • Re: Tools with/for Express
    ... Enterprise Manager does not work with SQL Server 2005. ... Analyzer is pretty dumb and just passes on what you type, ... But Enterprise Manager tries to write it's own code and it doesn't use SQL ... I then attempted to use Query Analyzer. ...
    (microsoft.public.sqlserver.tools)
  • Re: Problems with trusted sharing
    ... Access 2002 doesnt come with enterprise manager, ... >The security setting of your SQL Server has been set to ... >and Windows logins. ...
    (microsoft.public.access.adp.sqlserver)