Failed services after backup

Last night we did a backup through backup exec using the
no recovery option. This was not part of a plan but it was
done anyway.
This morning when all the databases that had been backed
up with no recovery set were inaccessible (because they
were marked (Loading)) one of the things we did was to
stop to of our SQL server servers.
We now know all we had to do was do a restore database
with recovery but at the time we thought we would stop and
restart the service.
After stopping the service we can not restart it.
it gives a message indicating there was a failure with no
return code.
Does anyone have any ideas on how we can get these servers
started again?
ThanksThe first step is to check the errolog file and see specific messages there.
Then take it from there.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Bob Ryan" <anonymous@.discussions.microsoft.com> wrote in message
news:f32001c3f18c$d1138a20$a001280a@.phx.gbl...
> Last night we did a backup through backup exec using the
> no recovery option. This was not part of a plan but it was
> done anyway.
> This morning when all the databases that had been backed
> up with no recovery set were inaccessible (because they
> were marked (Loading)) one of the things we did was to
> stop to of our SQL server servers.
> We now know all we had to do was do a restore database
> with recovery but at the time we thought we would stop and
> restart the service.
> After stopping the service we can not restart it.
> it gives a message indicating there was a failure with no
> return code.
> Does anyone have any ideas on how we can get these servers
> started again?
>
> Thanks

Failed services after backup

Last night we did a backup through backup exec using the
no recovery option. This was not part of a plan but it was
done anyway.
This morning when all the databases that had been backed
up with no recovery set were inaccessible (because they
were marked (Loading)) one of the things we did was to
stop to of our SQL server servers.
We now know all we had to do was do a restore database
with recovery but at the time we thought we would stop and
restart the service.
After stopping the service we can not restart it.
it gives a message indicating there was a failure with no
return code.
Does anyone have any ideas on how we can get these servers
started again?
ThanksThe first step is to check the errolog file and see specific messages there.
Then take it from there.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Bob Ryan" <anonymous@.discussions.microsoft.com> wrote in message
news:f32001c3f18c$d1138a20$a001280a@.phx.gbl...
> Last night we did a backup through backup exec using the
> no recovery option. This was not part of a plan but it was
> done anyway.
> This morning when all the databases that had been backed
> up with no recovery set were inaccessible (because they
> were marked (Loading)) one of the things we did was to
> stop to of our SQL server servers.
> We now know all we had to do was do a restore database
> with recovery but at the time we thought we would stop and
> restart the service.
> After stopping the service we can not restart it.
> it gives a message indicating there was a failure with no
> return code.
> Does anyone have any ideas on how we can get these servers
> started again?
>
> Thankssql

Failed on runnning maintenance backup plan but....

Hi,
Thank you for your help in advance...
We are running SQL 2K Sp3. For some reason, the maintenance plan (both
backup and optimize) stopped running. I made sure the SQL agent running but
the job never ran successfully. It ran fine before for long time but just
stopped running recently.
I did some tests by setting a maintenanace plan just running a simple db
backup (no transaction log included). it still failed. The error in the
report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
database. Login failed.
However, I setup some backup jobs to backup both db and transaction log by
NOT using maintenance plan. Those work fine.
Do you know what I should look into to fix the problem?
Hope you can help.
Thank you very much for your help.
Bobson
Hi Bobson,
That should be very easy to fix. Probably the job is running under a user
that has an incorrect default database. Perhaps the default database was
deleted or the user does not have access to it. Change the default database
for this user.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:

> Hi,
> Thank you for your help in advance...
> We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> backup and optimize) stopped running. I made sure the SQL agent running but
> the job never ran successfully. It ran fine before for long time but just
> stopped running recently.
> I did some tests by setting a maintenanace plan just running a simple db
> backup (no transaction log included). it still failed. The error in the
> report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
> database. Login failed.
> However, I setup some backup jobs to backup both db and transaction log by
> NOT using maintenance plan. Those work fine.
> Do you know what I should look into to fix the problem?
> Hope you can help.
> Thank you very much for your help.
> Bobson
|||Hi Ben,
Thank you very much for your response. After reading your response, I
checked into that but still has no clue.
sa - is default to "master" db. It has full access to it and other dbs.
lsadmin - is the Domain admin account I logged onto the Windows server. It
has full admin right on the local servers and access right to two dbs, ch and
pd.
I tried to run the maintenance jobs on master, ch and pd...but no luck. I
also treid to set up a test maintenance job to backup just the Master db...
but failed as well.
What else should I check ?
Thank you agian for your help.
Bobson
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Bobson,
> That should be very easy to fix. Probably the job is running under a user
> that has an incorrect default database. Perhaps the default database was
> deleted or the user does not have access to it. Change the default database
> for this user.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
|||Try this:
Right-click the job that is not working. Select View Job History, Show step
details. See the steps and look for 'Executed as user: x' or 'The Job was
invoked by User x'. Check the account under which the SQL Server Agent is
running. Also, on SQL Server Agent Properties go to the Connection tab and
see the account used under 'SQL Server connection'.
Then verify that these logins have a valid default database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
[vbcol=seagreen]
> Hi Ben,
> Thank you very much for your response. After reading your response, I
> checked into that but still has no clue.
> sa - is default to "master" db. It has full access to it and other dbs.
> lsadmin - is the Domain admin account I logged onto the Windows server. It
> has full admin right on the local servers and access right to two dbs, ch and
> pd.
> I tried to run the maintenance jobs on master, ch and pd...but no luck. I
> also treid to set up a test maintenance job to backup just the Master db...
> but failed as well.
> What else should I check ?
> Thank you agian for your help.
> Bobson
>
>
> "Ben Nevarez" wrote:
|||Hi Ben,
Good morning. Thank you for your response again!
I just checked it...in the Connection tab. It was pointing to Windows
Authenticaitons...so I change it to use SA account instead. And tried to run
the job again. It works!!
Again, thank you very much for your help. Happy holidays to you and your
family!!
Bobson
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Try this:
> Right-click the job that is not working. Select View Job History, Show step
> details. See the steps and look for 'Executed as user: x' or 'The Job was
> invoked by User x'. Check the account under which the SQL Server Agent is
> running. Also, on SQL Server Agent Properties go to the Connection tab and
> see the account used under 'SQL Server connection'.
> Then verify that these logins have a valid default database.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
|||Hi Bobson,
I am glad you fixed the problem.
Happy holidays!
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
[vbcol=seagreen]
> Hi Ben,
> Good morning. Thank you for your response again!
> I just checked it...in the Connection tab. It was pointing to Windows
> Authenticaitons...so I change it to use SA account instead. And tried to run
> the job again. It works!!
> Again, thank you very much for your help. Happy holidays to you and your
> family!!
> Bobson
> "Ben Nevarez" wrote:

Failed on runnning maintenance backup plan but....

Hi,
Thank you for your help in advance...
We are running SQL 2K Sp3. For some reason, the maintenance plan (both
backup and optimize) stopped running. I made sure the SQL agent running but
the job never ran successfully. It ran fine before for long time but just
stopped running recently.
I did some tests by setting a maintenanace plan just running a simple db
backup (no transaction log included). it still failed. The error in the
report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
database. Login failed.
However, I setup some backup jobs to backup both db and transaction log by
NOT using maintenance plan. Those work fine.
Do you know what I should look into to fix the problem?
Hope you can help.
Thank you very much for your help.
BobsonHi Bobson,
That should be very easy to fix. Probably the job is running under a user
that has an incorrect default database. Perhaps the default database was
deleted or the user does not have access to it. Change the default database
for this user.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
> Hi,
> Thank you for your help in advance...
> We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> backup and optimize) stopped running. I made sure the SQL agent running but
> the job never ran successfully. It ran fine before for long time but just
> stopped running recently.
> I did some tests by setting a maintenanace plan just running a simple db
> backup (no transaction log included). it still failed. The error in the
> report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
> database. Login failed.
> However, I setup some backup jobs to backup both db and transaction log by
> NOT using maintenance plan. Those work fine.
> Do you know what I should look into to fix the problem?
> Hope you can help.
> Thank you very much for your help.
> Bobson|||Hi Ben,
Thank you very much for your response. After reading your response, I
checked into that but still has no clue.
sa - is default to "master" db. It has full access to it and other dbs.
lsadmin - is the Domain admin account I logged onto the Windows server. It
has full admin right on the local servers and access right to two dbs, ch and
pd.
I tried to run the maintenance jobs on master, ch and pd...but no luck. I
also treid to set up a test maintenance job to backup just the Master db...
but failed as well.
What else should I check ?
Thank you agian for your help.
Bobson
"Ben Nevarez" wrote:
> Hi Bobson,
> That should be very easy to fix. Probably the job is running under a user
> that has an incorrect default database. Perhaps the default database was
> deleted or the user does not have access to it. Change the default database
> for this user.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
> > Hi,
> >
> > Thank you for your help in advance...
> >
> > We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> > backup and optimize) stopped running. I made sure the SQL agent running but
> > the job never ran successfully. It ran fine before for long time but just
> > stopped running recently.
> >
> > I did some tests by setting a maintenanace plan just running a simple db
> > backup (no transaction log included). it still failed. The error in the
> > report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
> > database. Login failed.
> >
> > However, I setup some backup jobs to backup both db and transaction log by
> > NOT using maintenance plan. Those work fine.
> >
> > Do you know what I should look into to fix the problem?
> >
> > Hope you can help.
> >
> > Thank you very much for your help.
> >
> > Bobson|||Try this:
Right-click the job that is not working. Select View Job History, Show step
details. See the steps and look for 'Executed as user: x' or 'The Job was
invoked by User x'. Check the account under which the SQL Server Agent is
running. Also, on SQL Server Agent Properties go to the Connection tab and
see the account used under 'SQL Server connection'.
Then verify that these logins have a valid default database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
> Hi Ben,
> Thank you very much for your response. After reading your response, I
> checked into that but still has no clue.
> sa - is default to "master" db. It has full access to it and other dbs.
> lsadmin - is the Domain admin account I logged onto the Windows server. It
> has full admin right on the local servers and access right to two dbs, ch and
> pd.
> I tried to run the maintenance jobs on master, ch and pd...but no luck. I
> also treid to set up a test maintenance job to backup just the Master db...
> but failed as well.
> What else should I check ?
> Thank you agian for your help.
> Bobson
>
>
> "Ben Nevarez" wrote:
> >
> > Hi Bobson,
> >
> > That should be very easy to fix. Probably the job is running under a user
> > that has an incorrect default database. Perhaps the default database was
> > deleted or the user does not have access to it. Change the default database
> > for this user.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "Bobson" wrote:
> >
> > > Hi,
> > >
> > > Thank you for your help in advance...
> > >
> > > We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> > > backup and optimize) stopped running. I made sure the SQL agent running but
> > > the job never ran successfully. It ran fine before for long time but just
> > > stopped running recently.
> > >
> > > I did some tests by setting a maintenanace plan just running a simple db
> > > backup (no transaction log included). it still failed. The error in the
> > > report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
> > > database. Login failed.
> > >
> > > However, I setup some backup jobs to backup both db and transaction log by
> > > NOT using maintenance plan. Those work fine.
> > >
> > > Do you know what I should look into to fix the problem?
> > >
> > > Hope you can help.
> > >
> > > Thank you very much for your help.
> > >
> > > Bobson|||Hi Ben,
Good morning. Thank you for your response again!
I just checked it...in the Connection tab. It was pointing to Windows
Authenticaitons...so I change it to use SA account instead. And tried to run
the job again. It works!!
Again, thank you very much for your help. Happy holidays to you and your
family!!
Bobson
"Ben Nevarez" wrote:
> Try this:
> Right-click the job that is not working. Select View Job History, Show step
> details. See the steps and look for 'Executed as user: x' or 'The Job was
> invoked by User x'. Check the account under which the SQL Server Agent is
> running. Also, on SQL Server Agent Properties go to the Connection tab and
> see the account used under 'SQL Server connection'.
> Then verify that these logins have a valid default database.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
> > Hi Ben,
> >
> > Thank you very much for your response. After reading your response, I
> > checked into that but still has no clue.
> >
> > sa - is default to "master" db. It has full access to it and other dbs.
> > lsadmin - is the Domain admin account I logged onto the Windows server. It
> > has full admin right on the local servers and access right to two dbs, ch and
> > pd.
> >
> > I tried to run the maintenance jobs on master, ch and pd...but no luck. I
> > also treid to set up a test maintenance job to backup just the Master db...
> > but failed as well.
> >
> > What else should I check ?
> >
> > Thank you agian for your help.
> >
> > Bobson
> >
> >
> >
> >
> > "Ben Nevarez" wrote:
> >
> > >
> > > Hi Bobson,
> > >
> > > That should be very easy to fix. Probably the job is running under a user
> > > that has an incorrect default database. Perhaps the default database was
> > > deleted or the user does not have access to it. Change the default database
> > > for this user.
> > >
> > > Hope this helps,
> > >
> > > Ben Nevarez
> > > Senior Database Administrator
> > > AIG SunAmerica
> > >
> > >
> > >
> > > "Bobson" wrote:
> > >
> > > > Hi,
> > > >
> > > > Thank you for your help in advance...
> > > >
> > > > We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> > > > backup and optimize) stopped running. I made sure the SQL agent running but
> > > > the job never ran successfully. It ran fine before for long time but just
> > > > stopped running recently.
> > > >
> > > > I did some tests by setting a maintenanace plan just running a simple db
> > > > backup (no transaction log included). it still failed. The error in the
> > > > report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
> > > > database. Login failed.
> > > >
> > > > However, I setup some backup jobs to backup both db and transaction log by
> > > > NOT using maintenance plan. Those work fine.
> > > >
> > > > Do you know what I should look into to fix the problem?
> > > >
> > > > Hope you can help.
> > > >
> > > > Thank you very much for your help.
> > > >
> > > > Bobson|||Hi Bobson,
I am glad you fixed the problem.
Happy holidays!
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
> Hi Ben,
> Good morning. Thank you for your response again!
> I just checked it...in the Connection tab. It was pointing to Windows
> Authenticaitons...so I change it to use SA account instead. And tried to run
> the job again. It works!!
> Again, thank you very much for your help. Happy holidays to you and your
> family!!
> Bobson
> "Ben Nevarez" wrote:
> >
> > Try this:
> >
> > Right-click the job that is not working. Select View Job History, Show step
> > details. See the steps and look for 'Executed as user: x' or 'The Job was
> > invoked by User x'. Check the account under which the SQL Server Agent is
> > running. Also, on SQL Server Agent Properties go to the Connection tab and
> > see the account used under 'SQL Server connection'.
> >
> > Then verify that these logins have a valid default database.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "Bobson" wrote:
> >
> > > Hi Ben,
> > >
> > > Thank you very much for your response. After reading your response, I
> > > checked into that but still has no clue.
> > >
> > > sa - is default to "master" db. It has full access to it and other dbs.
> > > lsadmin - is the Domain admin account I logged onto the Windows server. It
> > > has full admin right on the local servers and access right to two dbs, ch and
> > > pd.
> > >
> > > I tried to run the maintenance jobs on master, ch and pd...but no luck. I
> > > also treid to set up a test maintenance job to backup just the Master db...
> > > but failed as well.
> > >
> > > What else should I check ?
> > >
> > > Thank you agian for your help.
> > >
> > > Bobson
> > >
> > >
> > >
> > >
> > > "Ben Nevarez" wrote:
> > >
> > > >
> > > > Hi Bobson,
> > > >
> > > > That should be very easy to fix. Probably the job is running under a user
> > > > that has an incorrect default database. Perhaps the default database was
> > > > deleted or the user does not have access to it. Change the default database
> > > > for this user.
> > > >
> > > > Hope this helps,
> > > >
> > > > Ben Nevarez
> > > > Senior Database Administrator
> > > > AIG SunAmerica
> > > >
> > > >
> > > >
> > > > "Bobson" wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > Thank you for your help in advance...
> > > > >
> > > > > We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> > > > > backup and optimize) stopped running. I made sure the SQL agent running but
> > > > > the job never ran successfully. It ran fine before for long time but just
> > > > > stopped running recently.
> > > > >
> > > > > I did some tests by setting a maintenanace plan just running a simple db
> > > > > backup (no transaction log included). it still failed. The error in the
> > > > > report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
> > > > > database. Login failed.
> > > > >
> > > > > However, I setup some backup jobs to backup both db and transaction log by
> > > > > NOT using maintenance plan. Those work fine.
> > > > >
> > > > > Do you know what I should look into to fix the problem?
> > > > >
> > > > > Hope you can help.
> > > > >
> > > > > Thank you very much for your help.
> > > > >
> > > > > Bobson

Failed on runnning maintenance backup plan but....

Hi,
Thank you for your help in advance...
We are running SQL 2K Sp3. For some reason, the maintenance plan (both
backup and optimize) stopped running. I made sure the SQL agent running but
the job never ran successfully. It ran fine before for long time but just
stopped running recently.
I did some tests by setting a maintenanace plan just running a simple db
backup (no transaction log included). it still failed. The error in the
report is " ODBC SQLState:42000" Error 4064...... Cannot open user default
database. Login failed.
However, I setup some backup jobs to backup both db and transaction log by
NOT using maintenance plan. Those work fine.
Do you know what I should look into to fix the problem?
Hope you can help.
Thank you very much for your help.
BobsonHi Bobson,
That should be very easy to fix. Probably the job is running under a user
that has an incorrect default database. Perhaps the default database was
deleted or the user does not have access to it. Change the default database
for this user.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:

> Hi,
> Thank you for your help in advance...
> We are running SQL 2K Sp3. For some reason, the maintenance plan (both
> backup and optimize) stopped running. I made sure the SQL agent running bu
t
> the job never ran successfully. It ran fine before for long time but just
> stopped running recently.
> I did some tests by setting a maintenanace plan just running a simple db
> backup (no transaction log included). it still failed. The error in the
> report is " ODBC SQLState:42000" Error 4064...... Cannot open user defaul
t
> database. Login failed.
> However, I setup some backup jobs to backup both db and transaction log by
> NOT using maintenance plan. Those work fine.
> Do you know what I should look into to fix the problem?
> Hope you can help.
> Thank you very much for your help.
> Bobson|||Hi Ben,
Thank you very much for your response. After reading your response, I
checked into that but still has no clue.
sa - is default to "master" db. It has full access to it and other dbs.
lsadmin - is the Domain admin account I logged onto the Windows server. It
has full admin right on the local servers and access right to two dbs, ch an
d
pd.
I tried to run the maintenance jobs on master, ch and pd...but no luck. I
also treid to set up a test maintenance job to backup just the Master db...
but failed as well.
What else should I check ?
Thank you agian for your help.
Bobson
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Bobson,
> That should be very easy to fix. Probably the job is running under a user
> that has an incorrect default database. Perhaps the default database was
> deleted or the user does not have access to it. Change the default databas
e
> for this user.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
>|||Try this:
Right-click the job that is not working. Select View Job History, Show step
details. See the steps and look for 'Executed as user: x' or 'The Job was
invoked by User x'. Check the account under which the SQL Server Agent is
running. Also, on SQL Server Agent Properties go to the Connection tab and
see the account used under 'SQL Server connection'.
Then verify that these logins have a valid default database.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
[vbcol=seagreen]
> Hi Ben,
> Thank you very much for your response. After reading your response, I
> checked into that but still has no clue.
> sa - is default to "master" db. It has full access to it and other dbs.
> lsadmin - is the Domain admin account I logged onto the Windows server. It
> has full admin right on the local servers and access right to two dbs, ch
and
> pd.
> I tried to run the maintenance jobs on master, ch and pd...but no luck. I
> also treid to set up a test maintenance job to backup just the Master db..
.
> but failed as well.
> What else should I check ?
> Thank you agian for your help.
> Bobson
>
>
> "Ben Nevarez" wrote:
>|||Hi Ben,
Good morning. Thank you for your response again!
I just checked it...in the Connection tab. It was pointing to Windows
Authenticaitons...so I change it to use SA account instead. And tried to run
the job again. It works!!
Again, thank you very much for your help. Happy holidays to you and your
family!!
Bobson
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Try this:
> Right-click the job that is not working. Select View Job History, Show ste
p
> details. See the steps and look for 'Executed as user: x' or 'The Job was
> invoked by User x'. Check the account under which the SQL Server Agent is
> running. Also, on SQL Server Agent Properties go to the Connection tab and
> see the account used under 'SQL Server connection'.
> Then verify that these logins have a valid default database.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Bobson" wrote:
>|||Hi Bobson,
I am glad you fixed the problem.
Happy holidays!
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Bobson" wrote:
[vbcol=seagreen]
> Hi Ben,
> Good morning. Thank you for your response again!
> I just checked it...in the Connection tab. It was pointing to Windows
> Authenticaitons...so I change it to use SA account instead. And tried to r
un
> the job again. It works!!
> Again, thank you very much for your help. Happy holidays to you and your
> family!!
> Bobson
> "Ben Nevarez" wrote:
>sql

Failed Maintenance Plan Job

Could anybody tell me why this job would be failing based on this log?
Running SQL 2000 SP4.
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'servername' as 'domain\username' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
PM
Backup can not be performed on database 'axdata_live'. This sub task is
ignored.
Backup can not be performed on database 'axdata_test'. This sub task is
ignored.
Backup can not be performed on database 'Northwind'. This sub task is
ignored.
Backup can not be performed on database 'pubs'. This sub task is
ignored.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)My guess would be that those databases are in Simple recovery mode and you
are attempting to issue a Log backup. Take out the log backup and it should
work.
--
Andrew J. Kelly SQL MVP
<bjorgenson@.charter.net> wrote in message
news:1146001380.696610.165740@.g10g2000cwb.googlegroups.com...
> Could anybody tell me why this job would be failing based on this log?
> Running SQL 2000 SP4.
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'servername' as 'domain\username' (trusted)
> Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
> PM
> Backup can not be performed on database 'axdata_live'. This sub task is
> ignored.
> Backup can not be performed on database 'axdata_test'. This sub task is
> ignored.
> Backup can not be performed on database 'Northwind'. This sub task is
> ignored.
> Backup can not be performed on database 'pubs'. This sub task is
> ignored.
> Deleting old text reports... 1 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>

Failed Maintenance Plan Job

Could anybody tell me why this job would be failing based on this log?
Running SQL 2000 SP4.
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
Server 'servername' as 'domain\username' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
PM
Backup can not be performed on database 'axdata_live'. This sub task is
ignored.
Backup can not be performed on database 'axdata_test'. This sub task is
ignored.
Backup can not be performed on database 'Northwind'. This sub task is
ignored.
Backup can not be performed on database 'pubs'. This sub task is
ignored.
Deleting old text reports... 1 file(s) deleted.
End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)My guess would be that those databases are in Simple recovery mode and you
are attempting to issue a Log backup. Take out the log backup and it should
work.
Andrew J. Kelly SQL MVP
<bjorgenson@.charter.net> wrote in message
news:1146001380.696610.165740@.g10g2000cwb.googlegroups.com...
> Could anybody tell me why this job would be failing based on this log?
> Running SQL 2000 SP4.
>
> Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL
> Server 'servername' as 'domain\username' (trusted)
> Starting maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16
> PM
> Backup can not be performed on database 'axdata_live'. This sub task is
> ignored.
> Backup can not be performed on database 'axdata_test'. This sub task is
> ignored.
> Backup can not be performed on database 'Northwind'. This sub task is
> ignored.
> Backup can not be performed on database 'pubs'. This sub task is
> ignored.
> Deleting old text reports... 1 file(s) deleted.
> End of maintenance plan 'DB Maintenance Plan2' on 4/25/2006 4:35:16 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>

Failed Maintenance Plan

Please advice.
I run a SQL2k SP4 on WIN2K SP4.
I have a maintenance plan to backup the databases at 01:30AM. This has alway
s been succesfull.
Strangely it did the backup at 02:25PM with no entry in SQL Error Log and ca
using subsequent backups to fail as the files created had the 02:25 badge he
nce could not be deleted.
Please help as to what caused the maintenance plan to backup at 02:25 and wh
at to do to avoid it.
Thanks for your kind response.I posted a reply to this yesterday. Here's that text:
My guess is that it wasn't Main Plan that did the backup, someone else did i
t (or explicitly started the main
plan job, or scheduled the main plan job at that hour). If it was executed a
s a job, you can view the job
history under EM, Management, Jobs. In any event, each backup is written to
the eventlog and the errorlog
file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Timi" <anonymous@.discussions.microsoft.com> wrote in message
news:EA0A7329-EAA1-49B3-9DDB-1736B6F35A4C@.microsoft.com...
> Please advice.
> I run a SQL2k SP4 on WIN2K SP4.
> I have a maintenance plan to backup the databases at 01:30AM. This has alw
ays been succesfull.
> Strangely it did the backup at 02:25PM with no entry in SQL Error Log and causing
subsequent backups to fail
as the files created had the 02:25 badge hence could not be deleted.
> Please help as to what caused the maintenance plan to backup at 02:25 and
what to do to avoid it.
> Thanks for your kind response.
>|||Thanks for your response.
The maint plan was ran at 02:25AM as opposed to 01:30AM the scheduled time.|||can you check with your server guys if there was a problem
with the server which resulted in it being restarted on or
arounf 2:25 ?, but the best way of finding out is to check
the error log.
J

>--Original Message--
>Thanks for your response.
>The maint plan was ran at 02:25AM as opposed to 01:30AM
the scheduled time.
>.
>|||Agent does no run a job if it was down at the time it should have executed.
I doubt that this is the reason,
based on that. I bet a beer that someone started the job at that time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Julie" <anonymous@.discussions.microsoft.com> wrote in message news:13fdd01c41357$84085e80$
a301280a@.phx.gbl...
> can you check with your server guys if there was a problem
> with the server which resulted in it being restarted on or
> arounf 2:25 ?, but the best way of finding out is to check
> the error log.
> J
>
> the scheduled time.|||Bet a beer against you and your SQL Server knowledge, never ;)
Anyway your right but my sneaky plan was to get Timm to check the server, as
we both agree thats where the problem is, and who actually started it.|||:-)
<<as we both agree thats where the problem is, and who actually started it.>
>
Yep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:D6CB3367-9F9F-4633-B7FE-3FBEBFFA8B74@.microsoft.com...
> Bet a beer against you and your SQL Server knowledge, never ;)
> Anyway your right but my sneaky plan was to get Timm to check the server, as we bo
th agree thats where the
problem is, and who actually started it.

Failed Maintenance Plan

Please advice.
I run a SQL2k SP4 on WIN2K SP4.
I have a maintenance plan to backup the databases at 01:30AM. This has alway
s been successfull.
Strangely it did the backup at 02:25PM with no entry in SQL Error Log and ca
using subsequent backups to fail as the files created had the 02:25 badge he
nce could not be deleted.
Please help as to what caused the maintenece plan to backup at 02:25 and wha
t to do to avoid it.
Thanks for your kind response.My guess is that it wasn't Main Plan that did the backup, someone else did i
t (or explicitly started the main
plan job, or scheduled the main plan job at that hour). If it was executed a
s a job, you can view the job
history under EM, Management, Jobs. In any event, each backup is written to
the eventlog and the errorlog
file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Timi" <anonymous@.discussions.microsoft.com> wrote in message
news:CDA33615-5054-47D3-8D06-0A52B8FB7544@.microsoft.com...
> Please advice.
> I run a SQL2k SP4 on WIN2K SP4.
> I have a maintenance plan to backup the databases at 01:30AM. This has alw
ays been successfull.
> Strangely it did the backup at 02:25PM with no entry in SQL Error Log and causing
subsequent backups to fail
as the files created had the 02:25 badge hence could not be deleted.
> Please help as to what caused the maintenece plan to backup at 02:25 and w
hat to do to avoid it.
> Thanks for your kind response.
>

failed backup

what can I look at to determine why a backup failed. I have a maintence pla
n that does a full backup once a week and another plan that will do a transa
ction log backup every day at 1am. The full backups are running fine. The
daily backup of the trans l
og fails everyday. The SQL Server log does not mention the failed backup.
The History of the job does say failed but gives no reason. The Server (box
) has an entry in the Application Log but it is not much better; it just say
s failed. What can I do to
troubleshoot this?Is your database in Simple recovery mode? You can't back up the
transactionlog in simple recovery mode, only in Bulk Logged or Full recovery
mode.
Jacco Schalkwijk
SQL Server MVP
"rich" <anonymous@.discussions.microsoft.com> wrote in message
news:8354B199-B0F2-4FFD-919B-17841BB1EF66@.microsoft.com...
> what can I look at to determine why a backup failed. I have a maintence
plan that does a full backup once a week and another plan that will do a
transaction log backup every day at 1am. The full backups are running fine.
The daily backup of the trans log fails everyday. The SQL Server log does
not mention the failed backup. The History of the job does say failed but
gives no reason. The Server (box) has an entry in the Application Log but
it is not much better; it just says failed. What can I do to troubleshoot
this?|||Outstanding Jacco! Two out of the fourteen databases I was trying to backup
the transaction log on were set to "simple". Those happen to be the two I
did not make! Thanks for the tip!|||Another thing you can do for the future is go to the Scheduled Task itself,
Go to Steps and edit the Step, Go to Advanced and set an output file. This
way you can always look at the file to see why something failed.
Jeff Duncan
MCDBA, MCSE+I

failed backup

what can I look at to determine why a backup failed. I have a maintence plan that does a full backup once a week and another plan that will do a transaction log backup every day at 1am. The full backups are running fine. The daily backup of the trans l
og fails everyday. The SQL Server log does not mention the failed backup. The History of the job does say failed but gives no reason. The Server (box) has an entry in the Application Log but it is not much better; it just says failed. What can I do to
troubleshoot this?
Is your database in Simple recovery mode? You can't back up the
transactionlog in simple recovery mode, only in Bulk Logged or Full recovery
mode.
Jacco Schalkwijk
SQL Server MVP
"rich" <anonymous@.discussions.microsoft.com> wrote in message
news:8354B199-B0F2-4FFD-919B-17841BB1EF66@.microsoft.com...
> what can I look at to determine why a backup failed. I have a maintence
plan that does a full backup once a week and another plan that will do a
transaction log backup every day at 1am. The full backups are running fine.
The daily backup of the trans log fails everyday. The SQL Server log does
not mention the failed backup. The History of the job does say failed but
gives no reason. The Server (box) has an entry in the Application Log but
it is not much better; it just says failed. What can I do to troubleshoot
this?
|||Outstanding Jacco! Two out of the fourteen databases I was trying to backup the transaction log on were set to "simple". Those happen to be the two I did not make! Thanks for the tip!
|||Another thing you can do for the future is go to the Scheduled Task itself, Go to Steps and edit the Step, Go to Advanced and set an output file. This way you can always look at the file to see why something failed.
Jeff Duncan
MCDBA, MCSE+I

Fail to save Maintenace Plan using 'sa' with blank password

sa with no password is not exactly supported (for reasons which should be
obvious). What is your business need to leave this password blank?
"Michael Bergman" <simutek@.community.nospam> wrote in message
news:B90366AD-B401-43EA-AA3E-3A86939AABF2@.microsoft.com...
> Is it not supported to create a Maintenance Plan when logged in as 'sa'
> with
> blank password in SQL Server Management Studio?
> When logged in as 'sa' I get the following error when trying to save a
> Maintenance Plan:
> One or more arguments are invalid
> But if I login using Windows Authentication, or add a password to 'sa', I
> can successfully save a Maintenance Plan. I am using SQL Server 2005 SP1
> with
> Integration Services installed.
> --
> Regards,
> Michael Bergman
> SIMUTEK AB
>
This was an issue for one of our customers. We recommend strong passwords.
However, some customers still use blank password from old habit.
Now that I have confirmed that creating Maintenance Plans using blank
password is not supported, this might encourage our customers to change to a
strong password.
Regards,
Michael Bergman
SIMUTEK AB
"Aaron Bertrand [MVP]" wrote:

> sa with no password is not exactly supported (for reasons which should be
> obvious). What is your business need to leave this password blank?
>
>
> "Michael Bergman" <simutek@.community.nospam> wrote in message
> news:B90366AD-B401-43EA-AA3E-3A86939AABF2@.microsoft.com...
>
>