Showing posts with label serveragent. Show all posts
Showing posts with label serveragent. Show all posts

Monday, March 26, 2012

Error 165 - Sql state Hy000

Hi
I have Sql 2000 Server Sp4 with two instances from some day the Sql server
agent of second instance don't start and i can't do automatically backup. In
Sql log i try Error 165, error odbc [sql state HY000]
Can help me to risolve this problem.
Tia pupo
Pupo
take a look at following article:
http://support.microsoft.com/default...b;en-us;811889
Also ,check your SQLAgent service and make sure the account is right.
"Pupo" <123star@.libero.it> wrote in message
news:%2310q9c34FHA.2548@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have Sql 2000 Server Sp4 with two instances from some day the Sql server
> agent of second instance don't start and i can't do automatically backup.
> In Sql log i try Error 165, error odbc [sql state HY000]
> Can help me to risolve this problem.
> Tia pupo
>

Error 165 - Sql state Hy000

Hi
I have Sql 2000 Server Sp4 with two instances from some day the Sql server
agent of second instance don't start and i can't do automatically backup. In
Sql log i try Error 165, error odbc [sql state HY000]
Can help me to risolve this problem.
Tia pupoPupo
take a look at following article:
http://support.microsoft.com/defaul...kb;en-us;811889
Also ,check your SQLAgent service and make sure the account is right.
"Pupo" <123star@.libero.it> wrote in message
news:%2310q9c34FHA.2548@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have Sql 2000 Server Sp4 with two instances from some day the Sql server
> agent of second instance don't start and i can't do automatically backup.
> In Sql log i try Error 165, error odbc [sql state HY000]
> Can help me to risolve this problem.
> Tia pupo
>

Error 165 - Sql state Hy000

Hi
I have Sql 2000 Server Sp4 with two instances from some day the Sql server
agent of second instance don't start and i can't do automatically backup. In
Sql log i try Error 165, error odbc [sql state HY000]
Can help me to risolve this problem.
Tia pupo
Pupo
take a look at following article:
http://support.microsoft.com/default...b;en-us;811889
Also ,check your SQLAgent service and make sure the account is right.
"Pupo" <123star@.libero.it> wrote in message
news:%2310q9c34FHA.2548@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have Sql 2000 Server Sp4 with two instances from some day the Sql server
> agent of second instance don't start and i can't do automatically backup.
> In Sql log i try Error 165, error odbc [sql state HY000]
> Can help me to risolve this problem.
> Tia pupo
>

Error 165 - Sql state Hy000

Hi
I have Sql 2000 Server Sp4 with two instances from some day the Sql server
agent of second instance don't start and i can't do automatically backup. In
Sql log i try Error 165, error odbc [sql state HY000]
Can help me to risolve this problem.
Tia pupo
Pupo
take a look at following article:
http://support.microsoft.com/default...b;en-us;811889
Also ,check your SQLAgent service and make sure the account is right.
"Pupo" <123star@.libero.it> wrote in message
news:%2310q9c34FHA.2548@.TK2MSFTNGP10.phx.gbl...
> Hi
> I have Sql 2000 Server Sp4 with two instances from some day the Sql server
> agent of second instance don't start and i can't do automatically backup.
> In Sql log i try Error 165, error odbc [sql state HY000]
> Can help me to risolve this problem.
> Tia pupo
>
sql

error 16389

Hello,
We have a active x script that has been running for weeks from sql server
agent and all of sudden last night we are receiving "ActiveScripting specific
error 16389 occurred" on the jobs. I have search both BOL and newsgroups but
not finding anything that is giving me any help on this. Has anyone seen
this before, is so what step are need to be performed to troubleshoot the
issue.
The sql server that we are running this from is central DBA sql server
connecting to both production and non-production servers via SQL-DMO trusted
connections and extracting scripts for object generation.
Stopping and starting SQL Agent has fixed the issue. What could have caused
this issue?
"Tom" wrote:

> Hello,
> We have a active x script that has been running for weeks from sql server
> agent and all of sudden last night we are receiving "ActiveScripting specific
> error 16389 occurred" on the jobs. I have search both BOL and newsgroups but
> not finding anything that is giving me any help on this. Has anyone seen
> this before, is so what step are need to be performed to troubleshoot the
> issue.
> The sql server that we are running this from is central DBA sql server
> connecting to both production and non-production servers via SQL-DMO trusted
> connections and extracting scripts for object generation.

error 16389

Hello,
We have a active x script that has been running for weeks from sql server
agent and all of sudden last night we are receiving "ActiveScripting specifi
c
error 16389 occurred" on the jobs. I have search both BOL and newsgroups bu
t
not finding anything that is giving me any help on this. Has anyone seen
this before, is so what step are need to be performed to troubleshoot the
issue.
The sql server that we are running this from is central DBA sql server
connecting to both production and non-production servers via SQL-DMO trusted
connections and extracting scripts for object generation.Stopping and starting SQL Agent has fixed the issue. What could have caused
this issue?
"Tom" wrote:

> Hello,
> We have a active x script that has been running for weeks from sql server
> agent and all of sudden last night we are receiving "ActiveScripting speci
fic
> error 16389 occurred" on the jobs. I have search both BOL and newsgroups
but
> not finding anything that is giving me any help on this. Has anyone seen
> this before, is so what step are need to be performed to troubleshoot the
> issue.
> The sql server that we are running this from is central DBA sql server
> connecting to both production and non-production servers via SQL-DMO trust
ed
> connections and extracting scripts for object generation.

Wednesday, March 21, 2012

Error 14258: ... SQL ServerAgent is starting

Whenever I attempt to edit/run/... a scheduled job, I get the error message:
"Error 14258: Cannot perform this operation while SQL ServerAgent is
starting. Try again later."
I also notice that all scheduled jobs have "Date/time not available" in
"Next Run Date".
Of course Agent is not starting now, it has already started (Alerts and
Operators can be edited without a problem). The server is SQL2000, SP4.
Check the status of the service from Administrative Tools -
is the service Running or Starting?
Alerts and operators can be edited without Agent running.
Also check your Agent.out file.
-Sue
On Thu, 16 Feb 2006 03:55:29 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:

>Whenever I attempt to edit/run/... a scheduled job, I get the error message:
>"Error 14258: Cannot perform this operation while SQL ServerAgent is
>starting. Try again later."
>I also notice that all scheduled jobs have "Date/time not available" in
>"Next Run Date".
>Of course Agent is not starting now, it has already started (Alerts and
>Operators can be edited without a problem). The server is SQL2000, SP4.
|||The service IS running. I restarted it to make sure though, as I also did
with the server and the machine; nothing worked. The service is reported to
be running in both enterprise manager and windows services but no scheduled
jobs can be edited/run/...etc.
Also, when I stop the service I can edit jobs or create new ones, but there
is no way to run them.
There is no Agent.out file.
"Sue Hoegemeier" wrote:

> Check the status of the service from Administrative Tools -
> is the service Running or Starting?
> Alerts and operators can be edited without Agent running.
> Also check your Agent.out file.
> -Sue
|||ok, I checked SQLAgent.out file. It has one entry:
"... ? [393] Waiting for SQL Server to recover databases..."
but I don't understand which databases it is recovering as there is no such
indication in SQL server logs or Current activity.
"Sue Hoegemeier" wrote:

> Check the status of the service from Administrative Tools -
> is the service Running or Starting?
> Alerts and operators can be edited without Agent running.
> Also check your Agent.out file.
> -Sue
|||If you tried stopping and then restarting just the Agent
service and it won't start, reporting the same error then my
guess would be that you are running SQL Server in
lightweight pooling mode. Set it back to the default of
thread mode.
sp_configure 'allow updates', 1
go
reconfigure with override
go
sp_configure 'lightweight pooling', 0
go
reconfigure with override
go
-Sue
On Fri, 17 Feb 2006 00:41:28 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>ok, I checked SQLAgent.out file. It has one entry:
>"... ? [393] Waiting for SQL Server to recover databases..."
>but I don't understand which databases it is recovering as there is no such
>indication in SQL server logs or Current activity.
>
>"Sue Hoegemeier" wrote: