Wednesday, December 15, 2010

Unable to load DLL 'FileTracker.dll' error in Visual Studio 2010

I got this error, when I tried to build a project in Visual Studio 2010 (professional).
System.DllNotFoundException: Unable to load DLL 'FileTracker.dll': The specified module could not be found.
This build error occurred only in projects in which resource files were used.

Resolution:
1) Open "Microsoft.Common.targets" file located at "C:\Windows\Microsoft.NET\Framework\v4.0.30128".
2) Locate the following line "<TrackFileAccess Condition="'$(TrackFileAccess)' == ''">true</TrackFileAccess>"
3) Change the value to "false"
4) Do the same for the file found in "Framework64" folder also.

Note:
If we have to get rid of this problem in all the machines where it would be deployed, we can edit the ".csproj" file of our project, to include the following lines:


<PropertyGroup>
      <TrackFileAccess>false</TrackFileAccess>
</PropertyGroup>



Make sure that this is at the the bottom of the file just before the closing project tag (</Project>).
Doing so, will however slow down the build time, during deployment.


SharePoint 2010 installation on Windows 7 - Product Config Wizard fails in step 2 with System.FormatException

Today I was trying to install SharePoint 2010 enterprise on my Windows 7 laptop. The product configuration wizard was failing with the following error in Step 2 [creating configuration database].


The exception was:

System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).   at System.Guid..ctor(String g)   at Microsoft.SharePoint.Administration.SPFarm.GetInstalledProductIds()
Reason:
The following registry key had an "invalid" value "0" for the registry name {90140000-110D-0000-1000-0000000FF1CE} :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server extensions\14.0\WSS\InstalledProducts
Solution:


This is the key that is used to determine the current edition (Foundation, Standard,Enterprise..) of SharePoint installed. The correct value of this should be:



88BED06D-8C6B-4E62-AB01-546D6005FE97 - For Enterprise trial
D5595F62-449B-4061-B0B2-0CBAD410BB51 - For Enterprise licensed
B2C0B444-3914-4ACB-A0B8-7CF50A8F7AA0 - For Standard trial
3FDFBCC8-B3E4-4482-91FA-122C6432805C - For Standard licensed

Changing this solved the problem.