database backup job quits for no apparent reason

I created a maintenance plan to back up a database as a file to another server. Full backup was specified. The job has been running for about 3 months, then quit last night (after the server was rebooted). Error is:

Message
Executed as user: xxxxx\Administrator. The command line parameters are invalid. The step failed.

not sure what to do to fix this - -

Do a profiler trace to see if it's a TSQL issue somewhere, maybe the plan was accidentally changed somehow.|||I turned on Profiler to trace database backups - now all the backups are running fine -|||This is typically caused by the account changing the password. If you change the password of the account you used to run the job, you won't see any problems until you reboot your server/restart SQL Server service as this is the only time that the new security credentials will take effect.|||the jobs were created by and are run under the domain master system administrator account|||

Please go the SQL server jobs and change user domain\Administrator to sa (SQL Administrators).

it should be resolve......

Database backup job failure

Hi,
I'm new to sql server. Had been having issues with backups for last 3 weeks.
On 1 server, my main database "DB1" recovery model option is set to Simple.
The backups run every night. I have set the maintenance plan to delete the
file older than 12 hours. All the steps complete successfully except 1 step.
The error shows "can not delete DB1 backup file".
Another question I have is, if a db is set to 'Simple' recovery mode, the
transaction log fails right?
Please help!!!!!!
Thank you> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
Yes, it will fail. You can not backup the transaction log aof a db that has
simple recovery model.
Check if the account being used by sql agent service has rights to delete
from that folder.
AMB
"helpplease" wrote:
> Hi,
> I'm new to sql server. Had been having issues with backups for last 3 weeks.
> On 1 server, my main database "DB1" recovery model option is set to Simple.
> The backups run every night. I have set the maintenance plan to delete the
> file older than 12 hours. All the steps complete successfully except 1 step.
> The error shows "can not delete DB1 backup file".
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
> Please help!!!!!!
> Thank you|||Need more info here. What do you mean by "set the maintenance plan to
delete the file older than 12 hours" - which file? The backup file?
Why are you deleting the backup file? Don't you want the backup file
to hang around? If you include the INIT parameter in your backup
statement, it just reinitializes the backup file and you can overwrite
the previous days. You can just leave the file there and the job will
backup over the file that's already there....include your script and
more error info....right-click job and "view job history" then "show
step details".
Example -
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
helpplease wrote:
> Hi,
> I'm new to sql server. Had been having issues with backups for last 3 weeks.
> On 1 server, my main database "DB1" recovery model option is set to Simple.
> The backups run every night. I have set the maintenance plan to delete the
> file older than 12 hours. All the steps complete successfully except 1 step.
> The error shows "can not delete DB1 backup file".
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
> Please help!!!!!!
> Thank you|||How do I check this.
"Alejandro Mesa" wrote:
> > Another question I have is, if a db is set to 'Simple' recovery mode, the
> > transaction log fails right?
> Yes, it will fail. You can not backup the transaction log aof a db that has
> simple recovery model.
> Check if the account being used by sql agent service has rights to delete
> from that folder.
>
> AMB
> "helpplease" wrote:
> > Hi,
> >
> > I'm new to sql server. Had been having issues with backups for last 3 weeks.
> > On 1 server, my main database "DB1" recovery model option is set to Simple.
> > The backups run every night. I have set the maintenance plan to delete the
> > file older than 12 hours. All the steps complete successfully except 1 step.
> > The error shows "can not delete DB1 backup file".
> >
> > Another question I have is, if a db is set to 'Simple' recovery mode, the
> > transaction log fails right?
> >
> > Please help!!!!!!
> >
> > Thank you|||Browse to the folder in windows - right click and view the
security...see if the sql service acct. has permissions on the
folder. If you don't know who the sql service acct is - go to control
panel, administrative tools, services, and double click on mssqlserver.|||In the Database Maintenance Plan, under 'Complete Backup' tab there is an
option that says 'Remove files older than'. I have this option checked, with
the value 12 hours. Backup file extension is BAK.
Under view job history all I see is this
"Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed."
Under Maintenance Plan History all I see under status failed is this
Activity is "Delete old DB backup files" Status is failed.
"unc27932@.yahoo.com" wrote:
> Need more info here. What do you mean by "set the maintenance plan to
> delete the file older than 12 hours" - which file? The backup file?
> Why are you deleting the backup file? Don't you want the backup file
> to hang around? If you include the INIT parameter in your backup
> statement, it just reinitializes the backup file and you can overwrite
> the previous days. You can just leave the file there and the job will
> backup over the file that's already there....include your script and
> more error info....right-click job and "view job history" then "show
> step details".
> Example -
> BACKUP DATABASE master
> TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
> WITH INIT ,
> NAME = 'master',
> DESCRIPTION = 'master INIT BackupFull'
> helpplease wrote:
> > Hi,
> >
> > I'm new to sql server. Had been having issues with backups for last 3 weeks.
> > On 1 server, my main database "DB1" recovery model option is set to Simple.
> > The backups run every night. I have set the maintenance plan to delete the
> > file older than 12 hours. All the steps complete successfully except 1 step.
> > The error shows "can not delete DB1 backup file".
> >
> > Another question I have is, if a db is set to 'Simple' recovery mode, the
> > transaction log fails right?
> >
> > Please help!!!!!!
> >
> > Thank you
>|||My newsreader screwed up so sorry if this ends up being a repost ...
If I'm understanding you, you have a backup running every 24 hours, but
you want to delete the file after 12 hours' This leaves you a 12 hour
window without a backup. Not advisable.
I'm not a big fan of the wizards - just an opinion. If you are simply
shooting for a daily backup of your databases...don't do the database
maintenance wizard. Create a new job - Enterprise manager, browse to
your server, management, sql server agent, jobs. Create a new job, &
job sql step. Issue the backup command. Then schedule your job
(schedule tab).
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'|||If I'm understanding you correctly, you're taking full backups every
day with simple recovery (every 24 hours), but deleting them after 12
hours - this leaves a 12 hour window where you have no backups. So I'm
still unclear as to why you'd want to do this'
It sounds like you just want to create a backup schedule, but not
retain backups forever. My vote would be to skip the database
maintenance wizard altogether and create a new job (in enterprise
manager, browse to server, then management, then sql server agent, then
jobs) . Create a new job, add a sql job step and execute the backup
command, replacing the parameters below with parms specific to your
situation. Use the INIT parm to reinitialize the media header on the
file....You can then schedule your job (schedule tab) to run every 24
hours or whatever you want. See Books online BACKUP command for all
the other parameters.
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
helpplease wrote:
> In the Database Maintenance Plan, under 'Complete Backup' tab there is an
> option that says 'Remove files older than'. I have this option checked, with
> the value 12 hours. Backup file extension is BAK.
> Under view job history all I see is this
> "Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
> 42000] (Error 22029). The step failed."
> Under Maintenance Plan History all I see under status failed is this
> Activity is "Delete old DB backup files" Status is failed.
>
> "unc27932@.yahoo.com" wrote:
> > Need more info here. What do you mean by "set the maintenance plan to
> > delete the file older than 12 hours" - which file? The backup file?
> > Why are you deleting the backup file? Don't you want the backup file
> > to hang around? If you include the INIT parameter in your backup
> > statement, it just reinitializes the backup file and you can overwrite
> > the previous days. You can just leave the file there and the job will
> > backup over the file that's already there....include your script and
> > more error info....right-click job and "view job history" then "show
> > step details".
> >
> > Example -
> >
> > BACKUP DATABASE master
> > TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
> > WITH INIT ,
> > NAME = 'master',
> > DESCRIPTION = 'master INIT BackupFull'
> >
> > helpplease wrote:
> > > Hi,
> > >
> > > I'm new to sql server. Had been having issues with backups for last 3 weeks.
> > > On 1 server, my main database "DB1" recovery model option is set to Simple.
> > > The backups run every night. I have set the maintenance plan to delete the
> > > file older than 12 hours. All the steps complete successfully except 1 step.
> > > The error shows "can not delete DB1 backup file".
> > >
> > > Another question I have is, if a db is set to 'Simple' recovery mode, the
> > > transaction log fails right?
> > >
> > > Please help!!!!!!
> > >
> > > Thank you
> >
> >

Database backup job failure

Hi,
I'm new to sql server. Had been having issues with backups for last 3 weeks
.
On 1 server, my main database "DB1" recovery model option is set to Simple.
The backups run every night. I have set the maintenance plan to delete the
file older than 12 hours. All the steps complete successfully except 1 step
.
The error shows "can not delete DB1 backup file".
Another question I have is, if a db is set to 'Simple' recovery mode, the
transaction log fails right?
Please help!!!!!!
Thank you> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
Yes, it will fail. You can not backup the transaction log aof a db that has
simple recovery model.
Check if the account being used by sql agent service has rights to delete
from that folder.
AMB
"helpplease" wrote:

> Hi,
> I'm new to sql server. Had been having issues with backups for last 3 wee
ks.
> On 1 server, my main database "DB1" recovery model option is set to Simple
.
> The backups run every night. I have set the maintenance plan to delete th
e
> file older than 12 hours. All the steps complete successfully except 1 st
ep.
> The error shows "can not delete DB1 backup file".
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
> Please help!!!!!!
> Thank you|||Need more info here. What do you mean by "set the maintenance plan to
delete the file older than 12 hours" - which file? The backup file?
Why are you deleting the backup file? Don't you want the backup file
to hang around? If you include the INIT parameter in your backup
statement, it just reinitializes the backup file and you can overwrite
the previous days. You can just leave the file there and the job will
backup over the file that's already there....include your script and
more error info....right-click job and "view job history" then "show
step details".
Example -
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
helpplease wrote:
> Hi,
> I'm new to sql server. Had been having issues with backups for last 3 wee
ks.
> On 1 server, my main database "DB1" recovery model option is set to Simple
.
> The backups run every night. I have set the maintenance plan to delete th
e
> file older than 12 hours. All the steps complete successfully except 1 st
ep.
> The error shows "can not delete DB1 backup file".
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
> Please help!!!!!!
> Thank you|||How do I check this.
"Alejandro Mesa" wrote:
[vbcol=seagreen]
> Yes, it will fail. You can not backup the transaction log aof a db that ha
s
> simple recovery model.
> Check if the account being used by sql agent service has rights to delete
> from that folder.
>
> AMB
> "helpplease" wrote:
>|||Browse to the folder in windows - right click and view the
security...see if the sql service acct. has permissions on the
folder. If you don't know who the sql service acct is - go to control
panel, administrative tools, services, and double click on mssqlserver.|||In the Database Maintenance Plan, under 'Complete Backup' tab there is an
option that says 'Remove files older than'. I have this option checked, wit
h
the value 12 hours. Backup file extension is BAK.
Under view job history all I see is this
"Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed."
Under Maintenance Plan History all I see under status failed is this
Activity is "Delete old DB backup files" Status is failed.
"unc27932@.yahoo.com" wrote:

> Need more info here. What do you mean by "set the maintenance plan to
> delete the file older than 12 hours" - which file? The backup file?
> Why are you deleting the backup file? Don't you want the backup file
> to hang around? If you include the INIT parameter in your backup
> statement, it just reinitializes the backup file and you can overwrite
> the previous days. You can just leave the file there and the job will
> backup over the file that's already there....include your script and
> more error info....right-click job and "view job history" then "show
> step details".
> Example -
> BACKUP DATABASE master
> TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
> WITH INIT ,
> NAME = 'master',
> DESCRIPTION = 'master INIT BackupFull'
> helpplease wrote:
>|||My newsreader screwed up so sorry if this ends up being a repost ...
If I'm understanding you, you have a backup running every 24 hours, but
you want to delete the file after 12 hours' This leaves you a 12 hour
window without a backup. Not advisable.
I'm not a big fan of the wizards - just an opinion. If you are simply
shooting for a daily backup of your databases...don't do the database
maintenance wizard. Create a new job - Enterprise manager, browse to
your server, management, sql server agent, jobs. Create a new job, &
job sql step. Issue the backup command. Then schedule your job
(schedule tab).
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'|||If I'm understanding you correctly, you're taking full backups every
day with simple recovery (every 24 hours), but deleting them after 12
hours - this leaves a 12 hour window where you have no backups. So I'm
still unclear as to why you'd want to do this'
It sounds like you just want to create a backup schedule, but not
retain backups forever. My vote would be to skip the database
maintenance wizard altogether and create a new job (in enterprise
manager, browse to server, then management, then sql server agent, then
jobs) . Create a new job, add a sql job step and execute the backup
command, replacing the parameters below with parms specific to your
situation. Use the INIT parm to reinitialize the media header on the
file....You can then schedule your job (schedule tab) to run every 24
hours or whatever you want. See Books online BACKUP command for all
the other parameters.
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
helpplease wrote:[vbcol=seagreen]
> In the Database Maintenance Plan, under 'Complete Backup' tab there is an
> option that says 'Remove files older than'. I have this option checked, w
ith
> the value 12 hours. Backup file extension is BAK.
> Under view job history all I see is this
> "Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
> 42000] (Error 22029). The step failed."
> Under Maintenance Plan History all I see under status failed is this
> Activity is "Delete old DB backup files" Status is failed.
>
> "unc27932@.yahoo.com" wrote:
>

Database backup job failure

Hi,
I'm new to sql server. Had been having issues with backups for last 3 weeks.
On 1 server, my main database "DB1" recovery model option is set to Simple.
The backups run every night. I have set the maintenance plan to delete the
file older than 12 hours. All the steps complete successfully except 1 step.
The error shows "can not delete DB1 backup file".
Another question I have is, if a db is set to 'Simple' recovery mode, the
transaction log fails right?
Please help!!!!!!
Thank you
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
Yes, it will fail. You can not backup the transaction log aof a db that has
simple recovery model.
Check if the account being used by sql agent service has rights to delete
from that folder.
AMB
"helpplease" wrote:

> Hi,
> I'm new to sql server. Had been having issues with backups for last 3 weeks.
> On 1 server, my main database "DB1" recovery model option is set to Simple.
> The backups run every night. I have set the maintenance plan to delete the
> file older than 12 hours. All the steps complete successfully except 1 step.
> The error shows "can not delete DB1 backup file".
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
> Please help!!!!!!
> Thank you
|||Need more info here. What do you mean by "set the maintenance plan to
delete the file older than 12 hours" - which file? The backup file?
Why are you deleting the backup file? Don't you want the backup file
to hang around? If you include the INIT parameter in your backup
statement, it just reinitializes the backup file and you can overwrite
the previous days. You can just leave the file there and the job will
backup over the file that's already there....include your script and
more error info....right-click job and "view job history" then "show
step details".
Example -
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
helpplease wrote:
> Hi,
> I'm new to sql server. Had been having issues with backups for last 3 weeks.
> On 1 server, my main database "DB1" recovery model option is set to Simple.
> The backups run every night. I have set the maintenance plan to delete the
> file older than 12 hours. All the steps complete successfully except 1 step.
> The error shows "can not delete DB1 backup file".
> Another question I have is, if a db is set to 'Simple' recovery mode, the
> transaction log fails right?
> Please help!!!!!!
> Thank you
|||How do I check this.
"Alejandro Mesa" wrote:
[vbcol=seagreen]
> Yes, it will fail. You can not backup the transaction log aof a db that has
> simple recovery model.
> Check if the account being used by sql agent service has rights to delete
> from that folder.
>
> AMB
> "helpplease" wrote:
|||Browse to the folder in windows - right click and view the
security...see if the sql service acct. has permissions on the
folder. If you don't know who the sql service acct is - go to control
panel, administrative tools, services, and double click on mssqlserver.
|||In the Database Maintenance Plan, under 'Complete Backup' tab there is an
option that says 'Remove files older than'. I have this option checked, with
the value 12 hours. Backup file extension is BAK.
Under view job history all I see is this
"Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
42000] (Error 22029). The step failed."
Under Maintenance Plan History all I see under status failed is this
Activity is "Delete old DB backup files" Status is failed.
"unc27932@.yahoo.com" wrote:

> Need more info here. What do you mean by "set the maintenance plan to
> delete the file older than 12 hours" - which file? The backup file?
> Why are you deleting the backup file? Don't you want the backup file
> to hang around? If you include the INIT parameter in your backup
> statement, it just reinitializes the backup file and you can overwrite
> the previous days. You can just leave the file there and the job will
> backup over the file that's already there....include your script and
> more error info....right-click job and "view job history" then "show
> step details".
> Example -
> BACKUP DATABASE master
> TO DISK = 'c:\sqlbackups\Full\master_dump.BAK'
> WITH INIT ,
> NAME = 'master',
> DESCRIPTION = 'master INIT BackupFull'
> helpplease wrote:
>
|||My newsreader screwed up so sorry if this ends up being a repost ...
If I'm understanding you, you have a backup running every 24 hours, but
you want to delete the file after 12 hours? This leaves you a 12 hour
window without a backup. Not advisable.
I'm not a big fan of the wizards - just an opinion. If you are simply
shooting for a daily backup of your databases...don't do the database
maintenance wizard. Create a new job - Enterprise manager, browse to
your server, management, sql server agent, jobs. Create a new job, &
job sql step. Issue the backup command. Then schedule your job
(schedule tab).
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
|||If I'm understanding you correctly, you're taking full backups every
day with simple recovery (every 24 hours), but deleting them after 12
hours - this leaves a 12 hour window where you have no backups. So I'm
still unclear as to why you'd want to do this?
It sounds like you just want to create a backup schedule, but not
retain backups forever. My vote would be to skip the database
maintenance wizard altogether and create a new job (in enterprise
manager, browse to server, then management, then sql server agent, then
jobs) . Create a new job, add a sql job step and execute the backup
command, replacing the parameters below with parms specific to your
situation. Use the INIT parm to reinitialize the media header on the
file....You can then schedule your job (schedule tab) to run every 24
hours or whatever you want. See Books online BACKUP command for all
the other parameters.
BACKUP DATABASE master
TO DISK = 'c:\sqlbackups\master_dump.BAK'
WITH INIT ,
NAME = 'master',
DESCRIPTION = 'master INIT BackupFull'
helpplease wrote:[vbcol=seagreen]
> In the Database Maintenance Plan, under 'Complete Backup' tab there is an
> option that says 'Remove files older than'. I have this option checked, with
> the value 12 hours. Backup file extension is BAK.
> Under view job history all I see is this
> "Executed as user: NT AUTHORITY\SYSTEM. sqlmaint.exe failed. [SQLSTATE
> 42000] (Error 22029). The step failed."
> Under Maintenance Plan History all I see under status failed is this
> Activity is "Delete old DB backup files" Status is failed.
>
> "unc27932@.yahoo.com" wrote:
sql

DataBase Backup

SQL Server 2000
We have a db maintenance job which backup all the db's in a Production
Server to a remote server.
Production Server - Windows 2000 server
Remote Box - Windows 2003 Standard Edition
We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
maintenance job with error message 'Operating system error 64 (The specified
network is no longer available..)
Certain days it will backup all databases but with this error message.
Any thoughts/suggestions/ideas
Thanks
MikeMS User wrote:
> SQL Server 2000
> We have a db maintenance job which backup all the db's in a Production
> Server to a remote server.
> Production Server - Windows 2000 server
> Remote Box - Windows 2003 Standard Edition
> We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
> maintenance job with error message 'Operating system error 64 (The specifi
ed
> network is no longer available..)
> Certain days it will backup all databases but with this error message.
> Any thoughts/suggestions/ideas
> Thanks
> Mike
>
I'm not sure this is a SQL problem, sounds more like a network or OS
problem on the remote side. You're losing the connection to the remote
box during the file copy (the backup) that SQL is doing. Search Google
for "The specified network is no longer available", lots of hits.

DataBase Backup

MS User wrote:
> SQL Server 2000
> We have a db maintenance job which backup all the db's in a Production
> Server to a remote server.
> Production Server - Windows 2000 server
> Remote Box - Windows 2003 Standard Edition
> We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
> maintenance job with error message 'Operating system error 64 (The specifi
ed
> network is no longer available..)
> Certain days it will backup all databases but with this error message.
> Any thoughts/suggestions/ideas
> Thanks
> Mike
>
I'm not sure this is a SQL problem, sounds more like a network or OS
problem on the remote side. You're losing the connection to the remote
box during the file copy (the backup) that SQL is doing. Search Google
for "The specified network is no longer available", lots of hits.SQL Server 2000
We have a db maintenance job which backup all the db's in a Production
Server to a remote server.
Production Server - Windows 2000 server
Remote Box - Windows 2003 Standard Edition
We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
maintenance job with error message 'Operating system error 64 (The specified
network is no longer available..)
Certain days it will backup all databases but with this error message.
Any thoughts/suggestions/ideas
Thanks
Mike|||MS User wrote:
> SQL Server 2000
> We have a db maintenance job which backup all the db's in a Production
> Server to a remote server.
> Production Server - Windows 2000 server
> Remote Box - Windows 2003 Standard Edition
> We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
> maintenance job with error message 'Operating system error 64 (The specifi
ed
> network is no longer available..)
> Certain days it will backup all databases but with this error message.
> Any thoughts/suggestions/ideas
> Thanks
> Mike
>
I'm not sure this is a SQL problem, sounds more like a network or OS
problem on the remote side. You're losing the connection to the remote
box during the file copy (the backup) that SQL is doing. Search Google
for "The specified network is no longer available", lots of hits.

DataBase Backup

SQL Server 2000
We have a db maintenance job which backup all the db's in a Production
Server to a remote server.
Production Server - Windows 2000 server
Remote Box - Windows 2003 Standard Edition
We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
maintenance job with error message 'Operating system error 64 (The specified
network is no longer available..)
Certain days it will backup all databases but with this error message.
Any thoughts/suggestions/ideas
Thanks
MikeMS User wrote:
> SQL Server 2000
> We have a db maintenance job which backup all the db's in a Production
> Server to a remote server.
> Production Server - Windows 2000 server
> Remote Box - Windows 2003 Standard Edition
> We recently applied SP1 to Windows 2003 box (Remote Box), after that Db
> maintenance job with error message 'Operating system error 64 (The specified
> network is no longer available..)
> Certain days it will backup all databases but with this error message.
> Any thoughts/suggestions/ideas
> Thanks
> Mike
>
I'm not sure this is a SQL problem, sounds more like a network or OS
problem on the remote side. You're losing the connection to the remote
box during the file copy (the backup) that SQL is doing. Search Google
for "The specified network is no longer available", lots of hits.

Database (loading)

I have a database that is in (loading) status. Don't know why, we don't have a job running on it.
How to resolve this issue.What does DBCC CHECKDB tell you?

my guess is that you had a failed load|||What does DBCC CHECKDB tell you?

my guess is that you had a failed load|||What does DBCC CHECKDB tell you?

my guess is that you had a failed load...

Data Viewers not viewable

I came back from the weekend and noticed that none of my data viewers pop-up any longer, neither existing nor new ones. The job pauses at the point where the data would be following through the viewer but I cannot make it continue (since I don't have a "play" or Detach button.) The only way to terminate the job is with the "Stop" button on the Toolbar. Anyone know how I can get these back?

Thanks.Never mind, it was pulled down to the very bottom of my second screen, almost out of sight. I swear...