I completely agree with you. Honestly I am lost as to what the resolution may be. The last thing I could figure was trying to back it up from another...

Check out this thread.

http://www.sqlservercentral.com/Forums/Topic561810-5-1.aspx

It looks like reinstalling the .NET framework provided resolution.

Random question, have you attempted to use a different SSMS console to perform the backup?

Phil Auer (12/9/2008)

---

Removed the NOFORMAT, NOREWIND and SKIP directives (wanted INIT) and got the same result:

BACKUP DATABASE [JDE_EGEN] TO DISK = N'H:\SQL2005\EGEN.BAK' WITH INIT, NAME = N'JDE_EGEN-Full Database...

Give a try to the following

BACKUP DATABASE [JDE_EGEN] TO DISK = N'H:\SQL2005\EGEN.BAK' WITH INIT, NAME = N'JDE_EGEN-Full Database Backup', STATS = 10

GO

The NOFORMAT, NOREWIND, NOUNLOAD, SKIP aren't relevant...

Can you post the script that is created?

Does the job run all the procedures within a single transaction?

You could run a profile when the job is running, include the errors and warnings as well as growth information...

How does the single public IP route traffic to the 3 servers behind the firewall?

Couple of questions:

Does each SQL Instance sit on a different machine and you have different IP addresses?

Is there a single public IP and that redirects traffic to the machines behind...

Personally, and this is just a personal opinion, I would ditch the lot and go with domain logins (with carefully assigned rights) or defined local logins.

That makes me wonder if the pagefile was accidentally put on there and then ripped from the system on a failover.

Were you able to check the hidden and system files...

Is the E drive a clustered resource? Sorry, forgot to ask.

To show hidden and system files:

Open Windows Explorer

Tools

Folder Options

View (tab)

Change Radio Button on "Hidden files and folders" to Show

...

I would certainly check on the pagefile being located on that drive.

Right click on My computer then drill down to

System Properites

Advanced (tab)

Performance - Settings

Advanced...

Realistically the only way to do that is to either backup the SQL2000 databases, uninstall SQL2000 then install SQL2005 and restore the databases.

Or install another instance of SQL2005, backup and...