SQLAgent - Generic Refresher
-
We have a DTS package that we can run from EM, but not as a scheduled job. It had been running successfully as a scheduled job, but then it failed on a bad input file, and hasn't run as a scheduled job since. Of course, it doesn't fail as a scheduled job, it hangs.
We thought we'd cleaned up all the wreckage from having to cancel the scheduled job, but because it still won't run, I'm still looking for a solution. I know that 999 times out of 100, when a job will run thru EM but not as a scheduled job, it's an issue of permissions, but as near as I can tell (and as near as anyone else will admit) the account under which SQL Agent is running has the necessary permissions on all of the servers it accesses. (And I quote, "nothing has been changed.")
So totally unrelated to this problem, I ran sp_who2 on the server where the job is located. And to my surprise, there's an entry with the following information.
53 marginal\Administrator CMDB9 . msdb AWAITING COMMAND 125 43 06/08 13:51:12 SQLAgent - Generic Refresher 53
And 06/08 is about the time we started having problems with this job. So my question is
Can I just try to kill this SPID?
Thanks for your input.
Mattie
-
This particular SPID is for your agent to run. Whenever you start your agent in SQL Server it makes a connection to the server with the program naem SQL generic Refreshner. You can stop the agent and see that this program will not be there. But check what is the problem the job is not running. Post the log output of the job to have solutions.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
Thank you Sugesh for your response. Are you saying that instead of killing the SPID, I should just stop and restart the SQL Agent Service?
As for the problem with the job, there is no log, but I don't need one to tell you why the job is hanging. The step it hangs on is an executable created from a Cobol program. And that program displays a screen to the user when an exception is encountered.
What user, you may ask? Well, that was my question, but I'm just the person trying to get the job up and running again, not the person with any authority to require that batch processes write to a flat file or database table when they encounter a problem instead of displaying a screen to a non-existent user.Thanks again.
Mattie
-
Hey now i have found what the problem is. You are trying to invoke a exe from sql server. Remember that SQL Server is non interactive and you when you try to invoke the exe it will and you can see the same in task manager but the same will not be available interactively and when the exception occurs you get the message.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
Sugesh,
Yup, we know what the fix needs to be for the future. But back to my current problem, seeing as the job it's running against isn't an issue, should I kill the SPID, or should I just stop and restart the SQL Agent Service?
Thanks,
Mattie
-
Just stop and start the services that enough. Once the agent service is started you will have the generic refresher in the sysprocesses may be with a diff spid.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com -
Just stop and start the services that enough. Once the agent service is started you will have the generic refresher in the sysprocesses may be with a diff spid.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply