locked
Build error: Unable to load DLL 'FileTracker.dll'

    问题

  • After Installation of VS2010 Beta 2, opening a VS208 project and try to build or rebuild it the following error messages (see below) is displayed. I do not use such a dll ! New projects in VS2010 were build correct.
    Is my installation wrong ?
    What is this dll for ?
    What I have to do to build my existing VS2008 projekct ?
    Thanks, Martin 

    Error 1 The "GenerateResource" task failed unexpectedly.
    System.DllNotFoundException: Unable to load DLL 'FileTracker.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
       at Microsoft.Build.Shared.NativeMethodsShared.InprocTracking.StartTrackingContextWithRoot(String intermediateDirectory, String taskName, String rootMarker)
       at Microsoft.Build.Utilities.FileTracker.StartTrackingContextWithRoot(String intermediateDirectory, String taskName, String rootMarkerResponseFile)
       at Microsoft.Build.Tasks.GenerateResource.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask, Boolean& taskResult) TestTheConnectors
    2009年10月21日 13:21

全部回复

  • I also got the same build error when try to create a brand new WPF application and just build it without any changes in VS 2010 Beta2.
    My OS is Windows XP SP3 with VS 2008 installed.
    2009年10月22日 21:02
  • I also have the same error than Tanya, I have the VS 2008 installed.
    I can run the program just the one time. After this I always have the error.
    2009年11月4日 14:49
  • Same error here. Windows 7 + VS2010 Beta 2. I created a new WPF browser application in VS2010.

    2009年11月25日 19:25
  • Same error.  Occurred on my first attempted build VS2010 beta 2.  Don't know if this is useful, but I am trying to build a wpf application.

    The following article

    https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=501894&wa=wsignin1.0

    indicates that the problem may be because of a  v4.0 directory in the C:\WINNT\Microsoft.NET\Framework\ folder.  I do not have that folder, nor have I previously installed an earlier version of the 4.0 framework.
    2009年11月30日 22:52
  • Continued investigating issue above using dependency walker.   Placed in bold the error messages that were generated.

    Best guess is that the problem is that XP is missing kernelbase.dll .  Web search indicates that this is a new dll introduced for windows 7.  This dll does not exist on XP and perhaps it needs to be distributed as part of visual studio beta?

    Loaded "FILETRACKER.DLL" at address 0x43BE0000.  Successfully hooked module.
    DllMain(0x43BE0000, DLL_PROCESS_ATTACH, 0x00000000) in "FILETRACKER.DLL" called.
    GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsAlloc") called from "FILETRACKER.DLL" at address 0x43BEF023 and returned NULL. Error: The specified procedure could not be found (127).
    GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsGetValue") called from "FILETRACKER.DLL" at address 0x43BEF030 and returned NULL. Error: The specified procedure could not be found (127).
    GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsSetValue") called from "FILETRACKER.DLL" at address 0x43BEF03D and returned NULL. Error: The specified procedure could not be found (127).
    GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsFree") called from "FILETRACKER.DLL" at address 0x43BEF04A and returned NULL. Error: The specified procedure could not be found (127).

    LoadLibraryExW("C:\WINNT\Microsoft.NET\Framework\v4.0.21006\1033\FileTrackerUI.dll", 0x00000000, LOAD_LIBRARY_AS_DATAFILE) called from "CSAUSER.DLL" at address 0x10107C66.
    Mapped "FILETRACKERUI.DLL" as a data file into memory at address 0x1D9E0001.
    LoadLibraryExW("C:\WINNT\Microsoft.NET\Framework\v4.0.21006\1033\FileTrackerUI.dll", 0x00000000, LOAD_LIBRARY_AS_DATAFILE) returned 0x1D9E0001.
    GetProcAddress(0x77DD0000 [ADVAPI32.DLL], "CreateProcessAsUserA") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77E10CE8.
    GetProcAddress(0x77DD0000 [ADVAPI32.DLL], "CreateProcessAsUserW") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77DEA8A9.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CoRegisterClassObject") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77517E90.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CoCreateInstanceEx") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77500526.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CoGetClassObject") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x775156C5.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CreateFileMoniker") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77533F99.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CreateItemMoniker") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77555A31.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CreateClassMoniker") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77556AAF.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CoGetInstanceFromIStorage") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77596914.
    GetProcAddress(0x774E0000 [OLE32.DLL], "CoGetInstanceFromFile") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x775401EA.
    GetProcAddress(0x774E0000 [OLE32.DLL], "StgOpenStorage") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77507394.
    GetProcAddress(0x774E0000 [OLE32.DLL], "StgOpenStorageEx") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x7754ED80.
    GetProcAddress(0x77120000 [OLEAUT32.DLL], "GetActiveObject") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x771654BA.
    GetProcAddress(0x7E1E0000 [URLMON.DLL], "CoGetClassObjectFromURL") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x7E21E6BB.
    GetProcAddress(0x7E410000 [USER32.DLL], "SetClipboardData") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x7E430F9E.
    GetProcAddress(0x7E410000 [USER32.DLL], "GetClipboardData") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x7E430DBA.
    GetProcAddress(0x7E410000 [USER32.DLL], "EmptyClipboard") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x7E430D96.
    LoadLibraryW("KernelBase.dll") called from "CSAUSER.DLL" at address 0x10107A2E.
    LoadLibraryW("KernelBase.dll") returned NULL. Error: The specified module could not be found (126).

    LoadLibraryW("Kernel32.dll") called from "CSAUSER.DLL" at address 0x10107A2E.
    LoadLibraryW("Kernel32.dll") returned 0x7C800000.
    DllMain(0x43BE0000, DLL_PROCESS_ATTACH, 0x00000000) in "FILETRACKER.DLL" returned 0 (0x0).
    DllMain(0x43BE0000, DLL_PROCESS_DETACH, 0x00000000) in "FILETRACKER.DLL" called.
    DllMain(0x43BE0000, DLL_PROCESS_DETACH, 0x00000000) in "FILETRACKER.DLL" returned 0 (0x0).
    Unloaded "FILETRACKER.DLL" at address 0x43BE0000.
    LoadLibraryExW("FileTracker.dll", 0x00000000, 0x00000000) returned NULL. Error: A dynamic link library (DLL) initialization routine failed (1114).

    LoadLibraryExW("C:\WINNT\Microsoft.NET\Framework\v4.0.21006\diasymreader.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) called from "CSAUSER.DLL" at address 0x10107C66.
    LoadLibraryExW("C:\WINNT\Microsoft.NET\Framework\v4.0.21006\diasymreader.dll", 0x00000000, LOAD_WITH_ALTERED_SEARCH_PATH) returned 0x5DB20000.
    GetProcAddress(0x77DD0000 [ADVAPI32.DLL], "CreateProcessAsUserA") called from "CSAUSER.DLL" at address 0x10103F2D and returned 0x77E10CE8.
    2009年12月1日 21:37
  • I'm not sure that is where the problem is because I'm experiencing the exact same problem on Win 7.
    Paul Fuller
    2009年12月4日 15:38
  • Having the same issue, no luck so far with getting an answer.
    The machine where I have the issue is XP, there is no 4.0 directory as indicated as a potential problem.

    Jens
    2010年2月13日 8:41
  • Hello all,

     

    Thank you all of you for your posting in this thread.  I also had a test in my lab but with no avail, I did not repro this problem based on your description.   Based on my research, FileTracker.dll included in .NET Framework 4.0 which is under the directly C:\Windows\Microsoft.NET\Framework\v4.0.21006\.  

     

    Great thanks to gbier for your detailed analysis on this problem.   The debugging result via dependency walker is really helpful.  The problem could be occurring on converting VS2008 WPF or SL projects on Windows XP to VS2010 Beta 2 projects.   I have not verify it.   But in the connection ticket here, https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=501894&wa=wsignin1.0, Chooksii seems have found the workaround for this problem.  

     

    Could you please test this workaround to see whether it can solve the problem for you and tell me the results?   Thanks a lot!   If the problem still exist, please provide me with more detailed information to repro the issue, I will do my best to investigate it and report to the product team if necessary. 

     

    Have a nice day, all!

     

     

    Best Regards,
    Lingzhi Sun

    MSDN Subscriber Support in Forum

    If you have any feedback on our support, please contact msdnmg@microsoft.com


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年2月15日 7:33
    版主
  • Hello all,


    How is the problem now?    

     

    Have a nice day!

     

     

    Best Regards,
    Lingzhi Sun

    MSDN Subscriber Support in Forum

    If you have any feedback on our support, please contact msdnmg@microsoft.com


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年2月19日 1:29
    版主
  • I have the exact same problem on VS 2010 RC1 on XP. It happens even on a new console app with no code in it, just hit build and the error occurs.

    I uninstalled VS 2010 Beta 2 (which was working Ok) then installed RC1.

    If I compile a VB.Net program with RC1 on another machine, then try to run it on the XP machine in question, it installs OK but crashes on start up. Older programs compiled with beta 2 still work OK.

    G Shannon
    2010年2月24日 23:51
  • Hi all,

     

    We have reported this issue to the product team.  It seems to be caused by some previous installation of .NET Framework 4.0 on the machine.  Several workarounds have been updated to the bug ticket, https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=501894&wa=wsignin1.0.  Can these workarounds solve the problem?  

     

     

    Have a nice day!

     

     

    Best Regards,
    Lingzhi Sun

    MSDN Subscriber Support in Forum

    If you have any feedback on our support, please contact msdnmg@microsoft.com

     


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年3月2日 2:20
    版主
  • Hi,

    I have removed the temporary asp.net files in the folder: C:\Windows\Microsoft.NET\Framework\v4.0.21006\Temporary ASP.NET Files and it worked.

    Thanks.
    2010年3月3日 18:49
  • Hi, 

    Thanks for sharing the workaround.    

     

    Have a nice weekend, all!

     

     

    Best Regards,
    Lingzhi Sun

    MSDN Subscriber Support in Forum

    If you have any feedback on our support, please contact msdnmg@microsoft.com


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年3月5日 1:25
    版主
  • Hi,

    I spent the entire night to download and install VS2010. And this bug started hitting me at my first project early morning. After reading this posts i found that FileTracker.dll is there where it supposed to be.

    I tried deleting "C:\Windows\Microsoft.NET\Framework\v4.0.21006\Temporary ASP.NET Files" but it didnot work. Then i found that there is another folder "C:\Windows\Microsoft.NET\Framework\v4.0.30128" which i dont know why VS2010 created.

    My Guess was as "v4.0.30128" suppossed to be a higher version VS2010 is looking for FileTracker.dll in this folder. I deleted the folder "v4.0.30128" and VS2010 is happy now. It doesnot complain while building my projects and solutions.
    2010年3月13日 2:21
  • I had the same problem on a Windows 7 Machine.
    I am using VS 2010 Beta 2 but had a previous installation of the VS 2010 RC which I uninstalled.
    However the v4.0.30128 directory in C:\Windows\Microsoft .NET\Framework was not removed.
    Once I deleted it (kept the v4.0.21006 of course) and recompiled, the problem was resolved.

    Doron.
    2010年3月17日 15:51
  • I just installed VS2010 Beta on a virtual machine because I was having trouble with it in XP.  Anyway, I loaded an application that I had written in VS2008 using the 2.0 framework.  When I try to compile the app, I get the same error message that everyone else has received above.  I've attempted every work around that has been posted and none of them have solved the problem.

    Specifically, I don't understand why deleting the v4.0.30128 would help.  Isn't that where the 4.0 framework resides and is VS2010 in any way dependent on it?


    2010年3月17日 15:59
  • Thank to everyone on this thread. You probably saved me days of work.  I had the same problem with a fairly new Win 7 laptop and deleteing (actually just changing the name of) V4.0.30128 works.  I tried, by the way, combinations of removing everything else but this is the one folder that crashes everthing.  In my case the problem started when I accidently deleted net framework 1.1 - adding it back, removing and reinstalling everything was useless.  Eventually I recovered to the point of the uninstallation and got Visual Web 2010 back but Visual Basic 2010 Express still was not functional untill is disabled that folder.
    2010年3月26日 12:09
  • The company I work for uses a standard image for all our computers, since I last posted, I received a new computer, never had Visual Studio beta installed, went straight to the production release of Visual Studio 2010 and encountered the exact same problem. 

    There were no older 4.0.X versions of the .net framework to be found, but the following link worked for me.  Notice that there is a workaround tab on the page displayed.

    The link:

    http://connect.microsoft.com/VisualStudio/feedback/details/527167/upgraded-2008-project-compile-error-filetracker-dll

    I am also reproducing the instructions from that link to save some effort for those who have read this far.

    Find the file: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.Targets

    Locate the <GenerateResource> tag at Line 1835 and delete the attributes TrackFileAccess and TrackerLogDirectory

     

    • 已建议为答案 LSUgirl 2011年4月11日 15:54
    2010年4月29日 20:45
  • Hi all,

    Since VS2010 RTM is released, have you tried it on the RTM version?   Does the problem still exists?    Thanks a lot!


    Best Regards,
    Lingzhi Sun
    MSDN Subscriber Support
    in Forum
    If you have any feedback on our support, please contact
    msdnmg@microsoft.com.  


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年5月5日 8:57
    版主
  • Hi Lingzhi Sun,


    I installed the release version of VS2010Pro just this week. The problem still exists.

    Compiling C++ projects does work, C# projects don't. Same is true for a colleague.

    I don't have any betas on my computer. C:\Windows\Microsoft.NET\Framework contains v1.0.3705, v1.1.4322, v2.0.50727, v3.0, v3.5, v4.0.30319.

    I have admin rights and had the virus scanner disabled during installation. WinXp Pro SP3

     

    thanks

    2010年5月5日 11:06
  • Thank you very much, sgbmw!!!

    Could you please open a bug ticket for this issue at Microsoft Connect and share us the ticket link here?  

    Thank you again!  


    Best Regards,
    Lingzhi Sun
    MSDN Subscriber Support
    in Forum
    If you have any feedback on our support, please contact
    msdnmg@microsoft.com.  


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年5月6日 9:21
    版主
  • I opened case 557633 at MS Connect.

     

    thanks

    2010年5月7日 12:36
  • Thank you so much for sharing the link here, https://connect.microsoft.com/VisualStudio/feedback/details/557633/error-message-the-generateresource-task-failed-unexpectedly-when-trying-to-build-c-projects

    Have a nice day!


    Best Regards,
    Lingzhi Sun
    MSDN Subscriber Support
    in Forum
    If you have any feedback on our support, please contact
    msdnmg@microsoft.com.  


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    2010年5月10日 1:19
    版主
  • Hi Rohim

    I just delete the higher version folder created by the vs2010 setup as you said

     and after that my project which was build in 3.5 is working perfect in vs 4.0 .

    Thanks Rohim

    SR Dusad

     

     

    2010年5月18日 8:24
  • gbier,

    Thanks a lot! this solution (mentioned below again) has perfectly worked for me.

    Find the file: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.Targets

    Locate the <GenerateResource> tag at Line 1835 and delete the attributes TrackFileAccess and TrackerLogDirectory

     

    Thanks,

    Rajas

    2010年5月29日 13:52
  • Note that editing this file (Microsoft.Common.Targets) makes it where the file can no longer be serviced. Also, doing this turns off incremental build, which slows the build.

    You can add an attribute to your project file instead <TrackFileAccess>false</TrackFileAccess> if you are ok with loosing the incremental build performance.

    This issue is indicative of security programs being on the box which you special API's to watch file activity. The build process uses Tracker to watch file access during a build to use in subsequent builds so that the build can occur incrementally. By incremental, we mean that only the files that have changed will cause portions of the build to be re-done. This allows the minimum amount of work to be done when only minor changes are made to say, one file in a project.

    The issue occurs when the security program has already used the API and Tracker attempts to do the same. The API only allows for a single watch, and hence the Tracker call fails giving the error shown above. (See top of this thread)

    The better solution is to find an updated security program that does not use this type of mechanism.

    Chuck England
    Visual Studio Platform
    Program Manager - MSBuild

    • 已建议为答案 Chris Quon 2011年7月26日 20:20
    2010年6月4日 19:15
  • The RTM version of the folder is v4.0.30319. This should be the only v4.0 (i.e. FX 4; you may still have v3 or v2 folders for CLR 2) folder in the %WinDir%\Microsoft.NET\Framework folder.

    There was a known issue where the .NET framework installer was not deleting Beta and RC folder versions during an uninstall. After uninstalling one of these older products, and rebooting, you should check that all v4.0 folders have been removed. Then you can install the RTM version of Visual Studio 2010, which will install .NET v4.0 and recreate the appropriate folder.

    Chuck England
    Visual Studio Platform
    Program Manager - MSBuild

    2010年6月4日 19:21
  • I think i found a sln that is, i have two folders v4.0.30128 and v4.0.30319 so i renamed v4.0.30319 to xv4.0.30319 then rebuild the application it's working fine..
    2010年10月2日 2:19
  • I also had the same compile error. What I did was run VSNET administrator privileges,then complile and it worked.

    I hope they work
    2011年2月18日 0:57
  • this is the answer

     

    In the <PropertyGroup> section (without conditions) add:

    <TrackFileAccess>false</TrackFileAccess>


    2011年7月26日 20:21
  • Just Run Visual Studio 2010 as an administrator and the issue is resolved. It seems that it needs admin rights to access resources in c:\ drive

    2012年8月29日 12:26