MS SQL Server DTS - DTS Error 22022

Author

DTS Error 22022

2006-01-20, 8:24 pm

Dear knowledgeable ones:

For some reason, out of the blue, I am unable to schedule or run new jobs.
However, old scheduled tasks continue to run.

When I attempt to run a new job, I receive the following error:
Microsoft SQL-DMO(ODBC SQLState: 42000)
Error 22022: SQLServerAgent is not currently running so it cannot be
notified of this action.

By the way, the SQLServerAgent is running and I even restarted it a couple
of times. Also, the "Next Run Time" column displays Date and Time are not
available for all of the scheduled jobs.

Help!

Much thanks, in advance, for any assistance.

Ilya Margolin

2006-01-23, 8:24 pm

J,

Check whether password on SQLServerAgent service account is expired.

Ilya

"j" <j@discussions.microsoft.com> wrote in message
news:8508E6F0-FA58-4B41-B8C1- D71D0D0D0CB6@microso
ft.com...
> Dear knowledgeable ones:
>
> For some reason, out of the blue, I am unable to schedule or run new jobs.
> However, old scheduled tasks continue to run.
>
> When I attempt to run a new job, I receive the following error:
> Microsoft SQL-DMO(ODBC SQLState: 42000)
> Error 22022: SQLServerAgent is not currently running so it cannot be
> notified of this action.
>
> By the way, the SQLServerAgent is running and I even restarted it a couple
> of times. Also, the "Next Run Time" column displays Date and Time are not
> available for all of the scheduled jobs.
>
> Help!
>
> Much thanks, in advance, for any assistance.
>
>
>

2006-01-23, 8:24 pm

Ilya,
Thank you so much for your reply. The SQLServerAgent is running under the
sa account. The twist is that the old jobs continue to run daily. I'm so
confused. Do you have any other suggestions?

By the way, awhile back I denied 3 logins access to the sp_add_dtspackage
stored procedure. Thinking that it was the issue, I have since reversed
this, but it did not remedy the problem. Futhermore, the sa and admin
accounts (mine) would not have been affected.

Thanks again,
J.

"Ilya Margolin" wrote:

> J,
>
> Check whether password on SQLServerAgent service account is expired.
>
> Ilya
>
> "j" <j@discussions.microsoft.com> wrote in message
> news:8508E6F0-FA58-4B41-B8C1- D71D0D0D0CB6@microso
ft.com...
>
>
>

Ilya Margolin

2006-01-24, 9:23 am

J,

SQLServiceAgent is a windows service and cannot run under sa. Go to Control
Panel|Administrative
Tools|Services and try to restart the service.

Ilya

"j" <j@discussions.microsoft.com> wrote in message
news:7499C168-1041-4C6F-8BCE- 06CBFA2A7404@microso
ft.com...[color=darkred]
> Ilya,
> Thank you so much for your reply. The SQLServerAgent is running under the
> sa account. The twist is that the old jobs continue to run daily. I'm so
> confused. Do you have any other suggestions?
>
> By the way, awhile back I denied 3 logins access to the sp_add_dtspackage
> stored procedure. Thinking that it was the issue, I have since reversed
> this, but it did not remedy the problem. Futhermore, the sa and admin
> accounts (mine) would not have been affected.
>
> Thanks again,
> J.
>
>
> "Ilya Margolin" wrote:
>
jobs.[color=darkred]
couple[color=darkred
]
not[color=darkred]

2006-01-24, 11:23 am

Ilya,
You have sent me on the right path. The SQL Server Agent service is running
with the System Account, which I have gather from you means NT Administrator
local account? Anyway, I played around with adding the NT admin account
used to administer to SQL database app. to the administrators group and
changed the owner of the job to that account and it appears to be functioning
now.

I truly appreciate all of your help. It is nice to feel that someone is
there with answers when you need them.

Thanks again! Have a great day!!
J.

"Ilya Margolin" wrote:

> J,
>
> SQLServiceAgent is a windows service and cannot run under sa. Go to Control
> Panel|Administrative
Tools|Services and try to restart the service.
>
> Ilya
>
> "j" <j@discussions.microsoft.com> wrote in message
> news:7499C168-1041-4C6F-8BCE- 06CBFA2A7404@microso
ft.com...
> jobs.
> couple
> not
>
>
>

Sponsored Links