We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
encountered a problem which failed to start jobs in sql agent after restart
mssql server and aql agent services. It failed with exception error in the
job status dialogue.
There is no error message in event viewer and we found an error aqlagent.out
it shows
2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
process due to delay in opening server connection [SQLSTATE 08001]
Kindly advise and thanks in advanceCheck your service account (SQLAgent) and permissions related to this job.
Plus, check your cluster resources pertaining to SQL Agent service
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> encountered a problem which failed to start jobs in sql agent after
> restart
> mssql server and aql agent services. It failed with exception error in
> the
> job status dialogue.
>
> There is no error message in event viewer and we found an error
> aqlagent.out
> it shows
>
> 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> process due to delay in opening server connection [SQLSTATE 08001]
>
> Kindly advise and thanks in advance
>|||This problem only exist in node A. If failover to Node B , the agent works
normally.
the sql agent service a/c is an administrator. I compared the permission and
sql agent setting in cluster admin. Thery are the same
Kindly advise. Thanks a lot.
"bass_player [SBS-MVP]" wrote:
> Check your service account (SQLAgent) and permissions related to this job.
> Plus, check your cluster resources pertaining to SQL Agent service
>
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
>
>
Showing posts with label restart. Show all posts
Showing posts with label restart. Show all posts
Thursday, March 29, 2012
Failed to start jobs in sql agent after restart service
We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
encountered a problem which failed to start jobs in sql agent after restart
mssql server and aql agent services. It failed with exception error in the
job status dialogue.
There is no error message in event viewer and we found an error aqlagent.out
it shows
2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
process due to delay in opening server connection [SQLSTATE 08001]
Kindly advise and thanks in advanceCheck your service account (SQLAgent) and permissions related to this job.
Plus, check your cluster resources pertaining to SQL Agent service
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> encountered a problem which failed to start jobs in sql agent after
> restart
> mssql server and aql agent services. It failed with exception error in
> the
> job status dialogue.
>
> There is no error message in event viewer and we found an error
> aqlagent.out
> it shows
>
> 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> process due to delay in opening server connection [SQLSTATE 08001]
>
> Kindly advise and thanks in advance
>|||This problem only exist in node A. If failover to Node B , the agent works
normally.
the sql agent service a/c is an administrator. I compared the permission and
sql agent setting in cluster admin. Thery are the same
Kindly advise. Thanks a lot.
"bass_player [SBS-MVP]" wrote:
> Check your service account (SQLAgent) and permissions related to this job.
> Plus, check your cluster resources pertaining to SQL Agent service
>
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> > We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> > encountered a problem which failed to start jobs in sql agent after
> > restart
> > mssql server and aql agent services. It failed with exception error in
> > the
> > job status dialogue.
> >
> >
> >
> > There is no error message in event viewer and we found an error
> > aqlagent.out
> >
> > it shows
> >
> >
> >
> > 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> > process due to delay in opening server connection [SQLSTATE 08001]
> >
> >
> >
> > Kindly advise and thanks in advance
> >
>
>
encountered a problem which failed to start jobs in sql agent after restart
mssql server and aql agent services. It failed with exception error in the
job status dialogue.
There is no error message in event viewer and we found an error aqlagent.out
it shows
2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
process due to delay in opening server connection [SQLSTATE 08001]
Kindly advise and thanks in advanceCheck your service account (SQLAgent) and permissions related to this job.
Plus, check your cluster resources pertaining to SQL Agent service
"stephanie" <stephanie@.discussions.microsoft.com> wrote in message
news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> encountered a problem which failed to start jobs in sql agent after
> restart
> mssql server and aql agent services. It failed with exception error in
> the
> job status dialogue.
>
> There is no error message in event viewer and we found an error
> aqlagent.out
> it shows
>
> 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> process due to delay in opening server connection [SQLSTATE 08001]
>
> Kindly advise and thanks in advance
>|||This problem only exist in node A. If failover to Node B , the agent works
normally.
the sql agent service a/c is an administrator. I compared the permission and
sql agent setting in cluster admin. Thery are the same
Kindly advise. Thanks a lot.
"bass_player [SBS-MVP]" wrote:
> Check your service account (SQLAgent) and permissions related to this job.
> Plus, check your cluster resources pertaining to SQL Agent service
>
> "stephanie" <stephanie@.discussions.microsoft.com> wrote in message
> news:754761F4-D5A9-460F-904A-BA0FC63CFBC6@.microsoft.com...
> > We have clustered sql2005 (sp2) installed in win2003 (sp2). Recently, we
> > encountered a problem which failed to start jobs in sql agent after
> > restart
> > mssql server and aql agent services. It failed with exception error in
> > the
> > job status dialogue.
> >
> >
> >
> > There is no error message in event viewer and we found an error
> > aqlagent.out
> >
> > it shows
> >
> >
> >
> > 2007-07-28 02:08:11 - ! [165] ODBC Error: 0, Unable to complete login
> > process due to delay in opening server connection [SQLSTATE 08001]
> >
> >
> >
> > Kindly advise and thanks in advance
> >
>
>
Monday, March 19, 2012
failed jobs ..to restart automatically.
hi
my job was scheduled at 11.45 pm..but server went down at 11.40..and restart
ed at 12.10 am..
i want to know
1) how can we reschedule our jobs..so that if server went down and job was s
chedule somewhere in between it should automatically start..
jobs can be anything like backup/reindex//etc
regards
sunnyHi,
Set SQL server agent to start automatically, when the server starts. And the
n schedule your job to run automatically at the startup, i.e when the agent
starts up.
You can use the following stored proc
sp_add_jobschedule
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent
starts.
Thanks
GYK
my job was scheduled at 11.45 pm..but server went down at 11.40..and restart
ed at 12.10 am..
i want to know
1) how can we reschedule our jobs..so that if server went down and job was s
chedule somewhere in between it should automatically start..
jobs can be anything like backup/reindex//etc
regards
sunnyHi,
Set SQL server agent to start automatically, when the server starts. And the
n schedule your job to run automatically at the startup, i.e when the agent
starts up.
You can use the following stored proc
sp_add_jobschedule
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent
starts.
Thanks
GYK
failed jobs ..to restart automatically.
h
my job was scheduled at 11.45 pm..but server went down at 11.40..and restarted at 12.10 am.
i want to kno
1) how can we reschedule our jobs..so that if server went down and job was schedule somewhere in between it should automatically start.
jobs can be anything like backup/reindex//et
regard
sunnHi,
Set SQL server agent to start automatically, when the server starts. And then schedule your job to run automatically at the startup, i.e when the agent starts up
You can use the following stored pro
sp_add_jobschedul
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent starts
Thank
GYK
my job was scheduled at 11.45 pm..but server went down at 11.40..and restarted at 12.10 am.
i want to kno
1) how can we reschedule our jobs..so that if server went down and job was schedule somewhere in between it should automatically start.
jobs can be anything like backup/reindex//et
regard
sunnHi,
Set SQL server agent to start automatically, when the server starts. And then schedule your job to run automatically at the startup, i.e when the agent starts up
You can use the following stored pro
sp_add_jobschedul
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent starts
Thank
GYK
Friday, March 9, 2012
Fail to hide the restart dialog after installed MSDE
Hi,
I want to hide the restart dialog after installed MSDE. I
use the follow command:
setup /settings "setup.ini" /qb
But, the result fails. The restart dialog is also
prompted. Is my command wrong? How to do it?
Thanks.
Using /qn instead of /qb did the trick for me. Do you only get the restart
dialog, or do you get other dialogs as well? I ran mine without a settings
file, just with all the parameters on the command prompt.
Jacco Schalkwijk
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1311101c41243$45fd3f30$a501280a@.phx.gbl...
> Hi,
> I want to hide the restart dialog after installed MSDE. I
> use the follow command:
> setup /settings "setup.ini" /qb
> But, the result fails. The restart dialog is also
> prompted. Is my command wrong? How to do it?
> Thanks.
|||A solution I saw on another newsgroup was to include the following switch:
REBOOTPROMPT=Suppress
(I haven't had chance to try it yet)
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
I want to hide the restart dialog after installed MSDE. I
use the follow command:
setup /settings "setup.ini" /qb
But, the result fails. The restart dialog is also
prompted. Is my command wrong? How to do it?
Thanks.
Using /qn instead of /qb did the trick for me. Do you only get the restart
dialog, or do you get other dialogs as well? I ran mine without a settings
file, just with all the parameters on the command prompt.
Jacco Schalkwijk
SQL Server MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:1311101c41243$45fd3f30$a501280a@.phx.gbl...
> Hi,
> I want to hide the restart dialog after installed MSDE. I
> use the follow command:
> setup /settings "setup.ini" /qb
> But, the result fails. The restart dialog is also
> prompted. Is my command wrong? How to do it?
> Thanks.
|||A solution I saw on another newsgroup was to include the following switch:
REBOOTPROMPT=Suppress
(I haven't had chance to try it yet)
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Subscribe to:
Posts (Atom)