Andrew, thanks for the feedback. From what I can tell, this it telling me to run SSMS...

GSquared (1/29/2009)

---

Yeah, I think I mixed two answers into one statement. Wasn't very clear.

It's a lock-timeout error. If it's happening in msdb, then it's probably something to do...

GSquared (1/28/2009)

---

That error means that a lock was requested in msdb and timed out. Usually, that's going to mean it's a big transaction on a big temp table or...

I am getting a lot of these from the msdb database as well. Does anyone know what this means?

schep021 (1/16/2009)

---

Luke L (1/16/2009)

---

It looks like you are going in through an admin share. c$/d$ etc... depending on how your security is setup I've seen security apps where...

Have you...

Luke L (1/16/2009)

---

It looks like you are going in through an admin share. c$/d$ etc... depending on how your security is setup I've seen security apps where it...

Another note:

I was trying different permission settings. I was able to obtain access by adding the account to the backup operators group on serverB. Adding account to Users,...

Thank you for the suggestions Luke and Mike. I did check effective permissions - the account that sql server service is using does have full control of both that...

Mike (1/14/2009)

---

I believe that in order to do the dir command on a folder you only need to have Read permissions. I could be wrong but that is my...

schep021 (1/14/2009)

---

We recently upgraded from Windows 2003 32-bit to Windows 64-bit (SQL Server 2005 SP2). I am able to map the drive, but when I run master..xp_cmdshell 'dir \\...

I was able to successfully get the gateway working!

The gateway we were using 10g oracle transparent gateway would not even install on the new server. But, the gateway for...

Just the user database.

UPDATE:

I also get the same error when I run the following:

exec xp_readerrorlog

To explain more on my first posting...

I did a trace to see why I was not able to open...

I thought I would post an update. Sql Server Agent is still unable to start. I did not try the .NET Framework update as we are unsure of...