Backup on Local Disk Failing! urgent help plz!

Folks, this is the error i get when backing up user db to local disk:

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.

Connection Broken

If i copy a file (2gb) to local disk from network it works. The disk have much space. Any ideas;;; :confused:

I get the same error when backuping up even MSDB to a network path using UNC [\\].How large is the db you're trying to back up. How much disk space do you have? Can you backup a very small database?|||As i mentioned; i get the error even backing up MSDB(system) db either on network or local disk. Strangely; when i try backing up any db to local disk using EM; i get the message; backup successfully completed. and the file disappears(0 kb during backup) disappears on the disk!
Killing me!|||How is your SQL Server registered? Are you using the server name or are you using (local) or . ?
Whenever you use the 2 last options to register your server in EM it uses the shared memory driver, If you use the name of your server/instance, It should make it use the network librbary instead. I say that only to get to the point that if it is not a diskspace issue, it may be a memory issue, perhaps RAM going out.

I know that's not really a solution, but perhaps it can help you troubleshoot.|||How is the SQLServerAgent service and the MSSQLServer Service configured on the Log On tab in services? Are they configured to log on as "Local System"? Also, are there any messages in the SQL Server errorlog, or the NT Application event log?|||I don't quite understand "disappears from the disk" part. But in your first post you mentioned something about copying the file (2GB) from a share to a local drive and the backup would work. This leads me to believe that you're appending to the same backup file. I've seen cases when an interupted backup/restore would corrupt the device and no further appends are possible. The only solution would be to re-create the backup file by deleting the old one and creating a new one by backing up your database. Appending is a bad idea because it leads to what I've just described, in which case you DR is down the drain.|||Hi folks, thanx so much for ur input.
RESTARTING the instance just squared it away; so i suspect as mentioned by the fellow, memory problem (but what's the permanent fix?)
I didn't change any SQL-AGENT of SQL changes so far nor did this production machine had been restarted for last 2 months. I just saw my scheduled backup job failed last night and since then i tried restarting the job; backing the databases manually using QA or EM. So i didn't change any settings so far. I couldn't restart the instance during working times so i posted for the suggestion. After the restart it's working.
And, guru? believe me the file on the disk was of zero kb while backing up the db, then after the success message on EM i coldn't find the file; while in QA i get the GENERAL NETWORK error. Wasn't using the append db option!

Howdy!|||See this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;827452|||Hmmm, and I had this in my Favorites for while it was still in the Premier section...Good catch, pshisbey!|||Many thanx to ya all!