Job status in EM shows wrong info
-
Hi everyone, I have a user who cannot see the true job status in EM. He is a member of the TargetServersRole in msdb and I temporarily made him a sysadmin to see if he is able to see the correct status, but he still sees the wrong status after refreshing the view. When he runs sp_help_job, he gets the wrong set of info in the result set...his results show that there no jobs are running, whereas mine show that one job is running (currect_execution_status and current_execution_step columns). What to do? Thanks for your help.
-
1) You could try changing EM connection string to use SA (or a different SQL user just so you are not using NT Auth) and see if that effects the results.
2) What is the version of SQL server you are running and what version is the SQL server tools the user is using?
3) If the user logs in using the same user name a password from a different computer does it work?
4) Just for questions sake: Is he connecting the correct instalation of SQL Server?
-
Hi J,
I am not sure how to do step 1.
We are running sql 2000 SP4 on Win 2000 SP4. User is running MMC 2.0 whereas I am running MMC 1.2. He is running it on XP, I am on 2000 Pro.
The user tried looking at the jobs from another computer and he was still unable to see the correct job status.
Yes is the answer to your last question.
I am thinking that it's either a bug or a permissions issue. This user and I just tried again to test his permissions and I gave him sysadmin and he was able to see the correct job status by restarting EM, but he was not able to see the right job status by disconnecting/reconnecting to the database server, which has to be a bug. So the user is able to see the job status if he is sysadmin, so perhaps he needs some other permission(s) to be able to see the correct job status?
-
Try creating a stored procedure that the user does have permission to. The procedure could access MSDB..sp_help_jobs or the system tables directly (although I do not suggest accessing the system tables since they can change with new releases of sql server or new service packs.
The alternative would be, find out what jobs they want to know about and send them an email when the job starts and finishes (send a different email depending on if it fails or suceeds. This is usal the best option since you do not need the grant access to any system tables or stored procedures.
-
I don't think there is way other than hacking and modifying system procs...
SQL code will check the uses athentication with job ownership or sysadmin...so that you don't get the status..
MohammedU
Microsoft SQL Server MVP
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply