sp_msforeachdb will handle database names with a length of up to 128 characters, you can't create databases with longer names, so not sure what the issue is with the long...

Not this?

declare @report smalldatetime

select @report = getdate()

update dbo.[PS - daily Temp]

set [report Date] = @report

Where [Report Date] is null

Just remember to add the ability for the account to lock pages in memory if you are using a beefy box.

There's plenty of script on the site to check for blocking and to return the information on the blocking spid, for example http://www.sqlservercentral.com/scripts/Lock+and+Connection+Management/30800/%5B/url%5D (you might want to remove the kill...

Are you able to open SSMS on the actual servers themselves and attempt to execute the xp_cmdshell or are you strictly limited to attempting it from your admin box?

Clustered servers?

Right, but the admin box connects to the remote servers for you to attempt running the xp_cmdshell, correct?

I agree with the C. There is no mention of a log backup ever being performed, therefore a restore using log backups does not fall within the scope of yes...

Given that you are connected to the server via SSMS there should be no firewall issues involved.

Does it show any further errors in the SQL log or the Windows Event...

Does the SQL service account have "Act as a part of the operating system" permissions from within start--> administrative tools-->local security policy -->local security settings --> user rights assignment

try sp_revokelogin or sp_denylogin to prevent members of a group or account from logging in.

Are you trying to pull information across the network via a mapped drive on a local server?

Do you have a limit as regards the downtime you can have associated with the database? ie could you shut down any and all things using the database and have...

Sorry, a little confused by what you are asking, but I'll try to answer this as best I can.

You are performing a full database backup, then restore this on another...

I would also recommend getting up to SQL 2000 SP4 at minimum. There is a memory leak bug in SP3 (fixed in SP3a).

Check out this Microsoft KB article as regards...