The virtual server name has to be a network name that does not currently exest on the network.

heres a good white paper. http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en

Here is some info on Domain Controllers

http://support.microsoft.com/kb/281662

For...

Thanks, I looked at both execution plans and they both appear the same. I'll try updating stats and see.

Update:

I updated the stats and still the same thing. On our Test...

One issue that pops up for me are the linked data providers...Make sure that none of your applications use the Micrososoft.jet.oledb.4.0 providers. They do not exsist in a x64bit instance....

Great Thanks. I thought it might have something to do with that.

Marios

I was doing some more thinking on this script....and thought......

Currently the alert is generated from the managed server and the computer name in the event is the managed server. This...

Here is an edit I did to the Custom_SQL2005_Blocking.vbs

added the DBName to the alert description

added the Blocking Login Name to alert description

added SQL Text to alert description

removed waittime to...

I think I am seeing the issue now then. I get the blocking SPID but not the LOGIN from the Blocking SPID. I verified the #blocks table is populated with...

How hard of a change would it be to add the blocking User info.

For example we have the blocking spid and the blocked spid and we have the blocked...

K. Brian Kelley (12/11/2008)

It should be able to renew with a new login, and that includes locking the PC. Here's a blog post that explains the issue:

Ticket expirations as a...

Bradley Deem (12/11/2008)

I have the EXACT same problem with Kerberos. Resulting in the NT AUTHORITY\ANONYMOUS LOGON. It does work though, because I'm able to connect from a Web...

Great article Brian. I've been working with Kerberos Authenication for a while and I had to scour the internet looking for something that explained it like this.

One thing we...

Only solution I found was to make the owner a SQL Account instead of an AD account. This works for this one instance but I know this will not work...

how stupid of me. I kept going though the script and finally hit me to check the permission on the procedure. I grant execute on my db role but something...

I've been testing on the 2000 script and can not get the script to raise the event. I tried running in in the cmd line and it returned the error...

I used the zipped files link from the article. Are the one posted here different?