Network error but not using network

[patrussell]

I am receiving the "general network error" when trying to backup my database. I am not working across a network at all, everything is on my server. I get the error when I run the job manually or set it up on a schedule.

Any ideas on what I should look at here?

Thanks,

Pat Russell

 

[JayKusch]

Are you backing up to disc or tape?

Thanks

J. Kusch

 

[patrussell]

Sorry, should have included that info in the first post. I am backing up to the same disk that the database is on.



Pat Russell

 

[JayKusch]

What does the syntax of the backup job look like? In otherwords, can you post your backup command(s).

Thanks

J. Kusch

 

[patrussell]

I used the Maint. wizard to set it up. Here is the command listed in the job step.

BACKUP DATABASE [2CAPL_Archive] TO  DISK = N'D:\Program Files\Microsoft SQL Server\MSSQL$LVILLE_DATA\BACKUP\2 Cold Line\CAPL_Archive' WITH  INIT ,  NOUNLOAD ,  NAME = N'2CAPL_Archive backup',  SKIP ,  STATS = 10,  NOFORMAT

Pat Russell

 

[ManishH]

Is that a $ sign in the file path for the backup. That could be causing the trouble.

D:\Program Files\Microsoft SQL Server\MSSQL$LVILLE_DATA\BACKUP\2 Cold Line\CAPL_Archive'

HTH

 

[Corran007]

I hope not, thats how sqlserver does named instances in sql2k.

Have you tried creating a backup device and backuping up to that?

 

[patrussell]

Okay, here's the latest.

If I use the maintenance wizard to create the backup jobs, they fail.

If I create my own job using T-SQL commands and backup to disk devices all runs fine. I now have a job that will do this.

There is still one issue that I cannot figure out. I have an eval version of SQL LiteSpeed and would like to use it but each time I try to run a backup with it I get the same "network error". Are any of you familiar with this software?

I'm waiting for tech support to get back with me.

Thanks for all the help here.



Pat Russell

 

[mrdenny]

When ever you are connecting to the SQL Server, the client software (QA, EM, isql, etc) assums that you are connecting to a remote server.

Try connecting to localhost and see if that works any better.

Denny

--Anything is possible. All it takes is a little research. (Me)