Last month I got some error messages after creating a customized onet.xml and content types in SharePoint. One of the error messages was: A duplicate name "Item" was found. After taking a look into the SharePoint log files I found more details:

I tried to create a website based on my custom ont.xml and my custom content types. The reason for this error message was a spelling error in my custom content type:

<ContentType ID="0x010100............08}"

After removing the bracket at the end the site creation process was successful.

Problem

If you are getting errors in your Event Viewer like

"The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID 02b5e3f2-21e3-4552-bf1d-6e152749458a) threw an exception. More information is included below." and

"Attempted to read or write protected memory. This is often an indication that other memory is corrupt." on your SharePoint Server you need to apply a hotfix from Microsoft.

Solution

This happens if a process with more than one thread tries to access the Internet Information Services 6.0 (IIS 6.0) using the Active Directory Service Interfaces (ADSI) provider at the same time.

You can find the solution in the article KB946517.

From now on I want to write about errors I had to deal with. All of them will be filed under the "Event viewer" category.

TF220066

When you try to install the Visual Studio 2008 Team Foundation Server (TFS) and get this error you should check the following:

• Are the SQL Server 2005 Reporting Services installed?
• Are they installed on the same machine as the TFS?
• Are the SQL Server 2005 Services enabled?
• Did you use SQL Server 2005 Express? TFS 2008 doesn't support that...

By the way you need to install SP2 for the SQL Server and you have to use the following Collation at the installation: CI and AS. You can't change that for system databases after installation using "ALTER DATABASE".

TF30170

If you are using TFS 2008 with Windows SharePoint Services 3 (WSS 3) and you try to create a Team Project with Visual Studio 2005 you have to ensure that you

1. have Visual Studio 2005 SP1 installed at your client and that
2. you have installed the fix: VS80sp1-KB932544-X86-ENU.exe

If not you are getting the error: "The plugin Microsoft.ProjectCreationWizard.Portal failed during task SharePointPortal from group Portal."

Credits go here: Connecting Visual Studio 2005 to Team Foundation Server 2008

Problem

"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {61738644-F196-11D0-9953-00C04FD919C1} to the user DOMAIN\ACCOUNT SID (S-1-5-21-2412572953-1870457451-2878546156-1119).  This security permission can be modified using the Component Services administrative tool."

Solution

You have to go to Start->Administrative Tools->Component Services. From there locate the IIS WARMREG admin Service and switch to the tab "Security". Click edit in the group "Launch and Activation Permissions". There you have to add the mentioned service account and give it "Local Activation" permission.

You can repeat the steps for every account reported in "Event Viewer". Usually there are the application pool accounts of your SharePoint farm reported.

Problem

“Unable to get the private bytes memory limit for the W3WP process. The ASP.NET cache will be unable to limit its memory use, which may lead to a process restart. Error: 0x80070005”

Solution

In order to develop with SharePoint I use Virtual PC or Virtual Server 2005 images. Installing Windows Server 2003 takes about an hour and because of that I copy the images and change the SID using NewSID.exe. After that I get the error and using Google I found the solution at Joe unfiltered:

“I had created this VPC by copying the virtual hard disk from another VPC and running NewSID on it. I was under the impression that this fixed any issues regarding SIDs from the old machine conflicting with SIDs on the new one. Not quite, it turns out. The IIS_WPG group from the old box is on the ACL of the app pools in the metabase, not IIS_WPG of the new box. Use metaacl.vbs (download from MS) to check.”

Use the command:

MetaAcl.vbs "IIS://localhost/W3SVC/AppPools"

One of the entries will be an SID, not a user/group name. This is the IIS_WPG from the old box. To fix this, add the IIS_WPG group of the new box to the ACL in question using the command:

MetaAcl.vbs "IIS://localhost/W3SVC/AppPools" IIS_WPG U

So if your working with WSS 3 or MOSS 2007 and you use virtualization you should apply the fix.

Thanks to Joe!