I will say this...We called quest and ended up changing our call to their extended procedure. We added verbose logging on failure to 1 of our servers that was...

You might try changing them to a SQL Login with appropriate permissions and see if that changes anything

Who owns the snapshot job?

I don't suppose your service account might be locked out?

I am sorry to not be of more help. Have you seen anything useful in the event logs on the...

Are you referring to the drive as C:\SQLShapShot or \\. I am assuming your SQL Server Service and SQL Agent are running as an account with permissions on the...

So just so I understand.

Are you dumping the snapshot on the same server with publication and distributor or is it a remote server?

Can you browse to the snapshot location from the server?

What kind or replication are you doing?

Is this a clustered SQL Server?

Is the publisher and distributor on the same server?

There are a few ways you can do this.

1. In Excel you can connect to a database and have the query come back to a worksheet.

2. If it...

I would try tuning his query instead of automating a process to kill it. If he is a bigshot as you say, he is likely to get upset when...

I would be careful automatically killing a process for a user.

For 2005 I would look into using sys.dm_exec_sessions,sys.dm_exec_requests, and sys.dm_exec_sql_text

I can tell you I have used the Quest Spotlight for SQL Server and find it a bit of a pain to deal with at times. We have the...

I am not 100% sure about SQL 2008, but 2005 I thought each publisher could only have 1 distributor(It can either be on the same server, or you can use...

Good Luck, hope everything works out well

I would agree with the previous post. Try a backup and restore in test environment to make sure you understand how to get the application up and running again....