Pam, thanks for your suggestion.  It did allow me to capture the SQL from the execution of the prepared SQL statements.  To my dispair, however, the index tuning wizard had...

Thanks, Pam.  I'll take a look.

I didn't set it up, so I couldn't tell you for sure.  Sorry.

Chris

Here's what I use to query our LDAP server.

SELECT distinct top 100 percent department

FROM OpenQuery(ADSI, 'SELECT department FROM ''LDAP://DC=...,DC=...,DC=...'' where samAccountType = ''805306368''')

This is just a view that I created...

So, I figured out what was wrong...and as usual...it was user error.  I changed the database which I was updating to have a linked table.  The error message generated was...

Yeah...been burned by that in the past, Jim, so I'm on top of that.  Like I said, when it runs, it looks like it is pointing at a database that...

No...that wasn't it.  Anyone else have any other ideas?  Thanks.

Thanks, Lowell.

It runs as an administrator account (I know...bad), but there are no problems with permissions.  What the job history shows is that it is trying to make a connection to...

You won't have to run the log-shipping jobs at that exact moment, although, you may want to do so.  If you have an OLTP database where users could be updating the database...

Disable all log-shipping jobs for the database.  Take a full backup of the primary database and restore it on the target/secondary server.  Then re-enable the log-shipping jobs and run them...

Thanks, guys.  I'll alert our network manager.  Again, thanks.

Hey, SQLBill.  Thanks for the reply.  I did check the logs...event logs and SQL logs.  Nothing there.  Any other ideas?  Thanks.