Ah- good point... would have to created a linked server from the remote back to the source to test that... fortunately though, I recently learned the process is no longer...

DTC settings check out ok... again- it starts the process and cranks along for several minutes but eventually returns error 7393 OLE DB provider 'SQLNCLI' reported an error aborting the...

@Carolyn- YES- there were some patches to the OS recently.... do you remember how your resolved or if a specific patch was the culprit?

All of those check out with the exception of "same password". The account that I am using to access to remote server does not actually exist on the local...

I'm not using windows authentication at all- purely SQL authentication. Also- ran at various time of day over the past week or so.

unfortunately, I'm stuck looking at it from just a SQL perspective on the remote host- I don't currently have access to the OS...yet...

one thing worth mentioning though: The...

I would not see the sense in keeping a copy of the database on the same server for "what ifs"- as long as you are running in full recovery mode...

unless the linked server is configured with a specific login to use--- if you look at the properties of the linked server it will have defined the security context with...

You always see the same IP address in the error log, right?

If so, can you go to that machine and do a netstat -o... this will show you all connections...

also, perhaps there is something running as a local account (ie MACHINENAME\USER) or NT AUTHORITY\SYSTEM that is trying to log in...

If you have the client machine, you should be...

Is it possible that you have a client from a different domain attempting to access the server- I've also seen that error when that happens... the error log should include...

Assuming you mean "long" running jobs? Maybe this is what you are looking for: http://sqlserverpedia.com/blog/sql-server-bloggers/sql-server-agent-%E2%80%93-query-to-find-long-running-jobs/

I've seen this under the following circumstances:

- The server was intially installed using "LocalSystem" (which allowed it to register the SPN with the domain).

- The service was later changed...

From the SQL Server side, there is no "Session timeout" setting. If you need to do it from the server side, the proc described here: http://www.sqlservercentral.com/articles/Administration/sweepuptheslackers/158/...

Not that I know of. I can tell you that I have used dbcc shrinkfile as described in method 3 of the kb, and never had a corruption problem......