SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems ( - Contact me direct: or call 704-873-8846 x704.

Search This Blog

Friday, January 13, 2012

Problems with SharePoint Feature Deployments with SQL Deadlock, Dispose errors

Ran across this problem with a client. A seemingly good feature deployment that had been working for several months ran into a snag. On a full retract/delete then re-deploy, the process suddenly started getting SQL Deadlock errors, SPUsage errors and even SPDispose errors. Odd thing: deployment failed in different spots with these different errors so no common thread.

Code checked out with the SP Dispose checker (and visually), all looked OK. Checked the environment and verified that a) sites could be created fine, b) empty feature deployed fine and c) a third party (Bamboo's Hello) web part also deployed OK.

In reviewing the logs, I noticed that after an IIS Reset, the Application Event log showed Event ID 1511 for the application pool accounts.This error indicates that the accounts (in this case there were three applications with three accounts) that a Windows Profile could not be found so a temporary one being created.

So after much review, it turns out that the deployment problem was due this error - when the installation part of the deployment completed and IIS is reset, the attempt to activate the features (there were several) fails because the Application Pool account has a different profile. After creating a profile for each of these accounts, viola! Ran through no problem.

A quick fix to create a Windows Profile is to simply add the Application Pool account to the local administrators group, login to the server with that account (this creates the profile) then logout and remove it from the Local Administrators group.

For the another method, see this link:

No comments: