The 'windows Authentication' provider may not support this deployment. A bit of Googling and a couple of lucky guesses later, and we worked out what was causing it.
“Extended Protection” is apparently some of new fangled security framework that’s included in recent Windows Updates.
We will refer to this as Pessimistic Database Locking.
Unfortunately, this type of locking requires that you remain connected to the database for the entire process, which is somewhat contrary to the . In addition, this type of locking could hold up other users trying to access the system.
For instance, SQL Server 2000 provides locking at the row level, while others may lock the entire page or table the row resides in.
Logging on to the live server and installing the outstanding Windows security updates seems to have fixed it.
By Wayne Plourde In my recent article, Creating a Data Access Layer in .
Before or during an update, the application logic will check to see if the current record in the database has changed since you retrieved your copy of the record.
If it has, the app will generate an error causing the update transaction to be rolled back.