now this one is nice to read

imo switch your sql-agent service account to a windows account (grant the account the needed rights to the fileshares)

and...

definitely

And if you pull open the umbrella you can find a YOU !

If you activate the job via EM, the job may run using your windows-auth (it is logged your useraccount started the job).

That would explain why it can reach the share.

- what was the timegap between the backup and the restore ?

- have these procs, .. been created/altered during your backup ? (open transaction will be rolledback during recover)

hey, hey ... apparently I started a workaround section .....

As you all have seen, there's a remark in huge letters stating "... could cost you your job..."

- They must have no confidence at all regarding their DBA's.

- If this is a political issue, have it placed back on the agenda ! In case of disaster, problems,...

is the share granted public read/write ?

read this : http://support.microsoft.com/kb/224071/EN-US/

just to add to Eddie Wuerch 's reply :

- also check if you still use the same recovery mode. Maybe even switch...

I guess you're connected using implicit transactions.

(or use an oledb.begintran statement which switches your connection to "implicit transactions)

just to comfort you a bit :

- 1204 and 3605 are set as startup parameters at all our sqlserver instances

     (24/7/ +-365)!

- We switch...

I tried it, knowing our network is very outdated, and indeed, it chokes quit often.

It's a pitty, you cannot just download it and watch.

It's also a pitty, there isn't...

Did you check http://support.microsoft.com/kb/280101/

 GRANT EXECUTE ON sp_sdidebug  TO public

 EXECUTE  master..sp_sdidebug 'LEGACY_ON'

If I'm correct that cannot be done.

You'll be stuck with creating another instance and moving all the stuff.

or drop the instance (off course keep your datafiles (mdf,ndf,ldf !! and script...

tempdb should return to its starting size when you restart sqlserver.