Options
Ants 4 broken on my machine - how to fix?
js_vistadb
Posts: 6
OK, I have tried this on two machines that I use. Neither one works. ANTS 3 is installed and has run for a long time. Installed ANTS 4 but can't even get the mandlebrot to show times even though it is running.
I can launch apps, but it never records anything. I am linking a screencase I did to show the issue.
Both these machines are 64 bit Vista with Visual Studio 2008 SP1.
The only thing I ever see is "No results to display". I don't see any CPU bar, nothing. And almost all of the help files point to ANTS 3.
Screencast demonstrating no results
How do I get ANTS 4 to actually record something? These same machines ANTS 3 works fine.
I can launch apps, but it never records anything. I am linking a screencase I did to show the issue.
Both these machines are 64 bit Vista with Visual Studio 2008 SP1.
The only thing I ever see is "No results to display". I don't see any CPU bar, nothing. And almost all of the help files point to ANTS 3.
Screencast demonstrating no results
How do I get ANTS 4 to actually record something? These same machines ANTS 3 works fine.
Comments
If the problem persists then my next guess is that it almost looks to me like the profilerCore hasn't registered although i don't know for sure. If it's 64bit then the first thing to try might be to open a command prompt and manually register (regsvr32) the profilerCore dll
It will be in: Program Files/Red Gate/ANTS Profiler 4/x64/ProfilerCore.dll
Let me know how you get on,
Stephen
I went and attempted to register the profiler core, but I get an error message.
"The application failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail."
That then reveals the following from the event log:
Activation context generation failed for "c:\Program Files\Red Gate\ANTS Profiler 4\X64\ProfilerCore.dll".Error in manifest or policy file "C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_465807b554eb9197.manifest" on line 1. The manifest file root element must be assembly.
.NET Runtime version 2.0.50727.3053 - Failed to CoCreate profiler.
So this would appear to be a side by side install error caused by the active template library (VC80.ATL). I did see that 4.1 include a new VC runtime redistributable for x64. Maybe that had something to do with it?
http://msdn.microsoft.com/en-us/library/ms235624(VS.80).aspx
WARNING: VS2005 SP1 installs some MSM files with version 8.0.50727.42, but builds your code against 8.0.50727.762. WHen you deploy your app on a raw WinXP machine, it gets the 8.0.50727.42 redistributables from the MSMs, which won't work with your installed app.
My workaround is to put the 8.0.50727.762 MSM versions into "C:\Program Files\Common Files\Merge Modules"
Here are some example affected files:
Microsoft_VC80_CRT_x86.msm
Microsoft_VC80_ATL_x86.msm
I still have no idea how you fix a broken side by side for ATL....
Here is my sxstrace:
=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = AMD64
CultureFallBacks = en-US;en
ManifestPath = c:\Program Files\Red Gate\ANTS Profiler 4\X64\ProfilerCore.dll
AssemblyDirectory = c:\Program Files\Red Gate\ANTS Profiler 4\X64 Application Config File =
INFO: Parsing Manifest File c:\Program Files\Red Gate\ANTS Profiler 4\X64\ProfilerCore.dll.
INFO: Manifest Definition Identity is (null).
INFO: Reference: Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
INFO: Reference: Microsoft.VC80.ATL,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762"
INFO: Resolving reference Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_09c0f5a3facc9779.manifest
INFO: Publisher Policy redirected assembly version.
INFO: Post policy assembly identity is Microsoft.VC80.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.3053".
INFO: Begin assembly probing.
INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_88e044e32fae7230.manifest.
INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.3053_none_88e044e32fae7230.manifest.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.CRT.mui,language="*",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.3053".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture en-US.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.3053_en-US_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en-US.
INFO: End assembly probing.
INFO: Resolving reference for culture en.
INFO: Applying Binding Policy.
INFO: No publisher policy found.
INFO: No binding policy redirect found.
INFO: Begin assembly probing.
INFO: Did not find the assembly in WinSxS.
INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC80.CRT.mui\8.0.50727.3053_en_1fc8b3b9a1e18e3b\Microsoft.VC80.CRT.mui.DLL.
INFO: Did not find manifest for culture en.
INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC80.ATL,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762".
INFO: Resolving reference for ProcessorArchitecture amd64.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.8.0.microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_465807b554eb9197.manifest
INFO: Begin assembly probing.
INFO: End assembly probing.
ERROR: Activation Context generation failed.
End Activation Context Generation.
It would appear the VC80 ATL is not installed correctly or is corrupt. I have re-run the x64 redist from MS site but it does not appear to help. Have no further ideas. Any help is appreciated.
I do _not_ normally recommend a user modify these files by hand. After careful consideration and reading through the MSDN I modified mine to the following:
This fixed my issue. It appears the one on the machine was referencing an ATL version that was not actually installed. I have read where using the default redist in VS 2005 SP1 can cause this issue. I am not sure if Red Gate did this or maybe some other app I use had already done it.
The above build (8.0.50727.762) is the actual build on my machine using the latest VC redirect for VS 2005 today. It appears to work because now my ANTS is working correctly.
I just wanted to follow up in case some other user has the same error.
glad you got it working. We will look into this further and maybe put a knowledge base article on our site about it.
Regards,
Stephen