Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Vista General Discussion > Re: cannot start adaware

Reply
Thread Tools Display Modes

Re: cannot start adaware

 
 
Richard G. Harper
Guest
Posts: n/a

 
      08-29-2009
Have you contacted Lavasoft for support on this question?


"James Gilman" <> wrote in message
news:...
When I try to start adaware application I get the following error:

The application has failed because its side-by-side configuration
is incorrect. Please see the application event log for more detail.

The application event log shows the following error:

Activation context generation failed for "C:\Program
Files\Lavasoft\Ad-Aware\Ad-Aware.exe". Dependent Assembly
Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1"
could not be found. Please use sxstrace.exe for detailed diagnosis.


with sxstrace running I tried to start adaware and got the following trace:

=================
Begin Activation Context Generation.
Input Parameter:
Flags = 0
ProcessorArchitecture = x86
CultureFallBacks = en-US;en
ManifestPath = C:\Program Files\Lavasoft\Ad-Aware\Ad-Aware.exe
AssemblyDirectory = C:\Program Files\Lavasoft\Ad-Aware\
Application Config File =
-----------------
INFO: Parsing Manifest File C:\Program Files\Lavasoft\Ad-Aware\Ad-Aware.exe.
INFO: Manifest Definition Identity is (null).
INFO: Reference:
Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1"
INFO: Reference:
Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.21022.8"
INFO: Resolving reference
Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1".
INFO: Resolving reference for ProcessorArchitecture x86.
INFO: Resolving reference for culture Neutral.
INFO: Applying Binding Policy.
INFO: Find publisher policy at
C:\Windows\WinSxS\manifests\x86_policy.9.0.microso ft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_60a5 df56e60dc5df.manifest
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_32\Microsoft.VC90.CRT\9.0. 30729.1__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\Program
Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\Program
Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT.MANIFEST.
INFO: Attempt to probe manifest at C:\Program
Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT\Microsoft.VC90.CRT.DLL.
INFO: Attempt to probe manifest at C:\Program
Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT\Microsoft.VC90.CRT.MANIFE ST.
INFO: Did not find manifest for culture Neutral.
INFO: End assembly probing.
ERROR: Cannot resolve reference
Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1".
ERROR: Activation Context generation failed.
End Activation Context Generation.

----------------
Can you help? How extensive is this problem? Will it only effect adaware?
How can it be fixed? I don't know how it happened except this morning on
startup some unidentified appl wanted to run, on hitting control-alt-del to
identify it, it disappeared. Thanx for any light you can shed on this.



 
Reply With Quote
 
 
 
 
James Gilman
Guest
Posts: n/a

 
      09-01-2009

"Richard G. Harper" <> wrote in message
news:7E453254-83E5-40B0-ACA3-...
> Have you contacted Lavasoft for support on this question?
>
>
> "James Gilman" <> wrote in message
> news:...
> When I try to start adaware application I get the following error:
>
> The application has failed because its side-by-side configuration
> is incorrect. Please see the application event log for more detail.
>
> The application event log shows the following error:
>
> Activation context generation failed for "C:\Program
> Files\Lavasoft\Ad-Aware\Ad-Aware.exe". Dependent Assembly
> Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1"
> could not be found. Please use sxstrace.exe for detailed diagnosis.
>
>
> with sxstrace running I tried to start adaware and got the following
> trace:
>
> =================
> Begin Activation Context Generation.
> Input Parameter:
> Flags = 0
> ProcessorArchitecture = x86
> CultureFallBacks = en-US;en
> ManifestPath = C:\Program Files\Lavasoft\Ad-Aware\Ad-Aware.exe
> AssemblyDirectory = C:\Program Files\Lavasoft\Ad-Aware\
> Application Config File =
> -----------------
> INFO: Parsing Manifest File C:\Program
> Files\Lavasoft\Ad-Aware\Ad-Aware.exe.
> INFO: Manifest Definition Identity is (null).
> INFO: Reference:
> Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1"
> INFO: Reference:
> Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.21022.8"
> INFO: Resolving reference
> Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1".
> INFO: Resolving reference for ProcessorArchitecture x86.
> INFO: Resolving reference for culture Neutral.
> INFO: Applying Binding Policy.
> INFO: Find publisher policy at
> C:\Windows\WinSxS\manifests\x86_policy.9.0.microso ft.vc90.crt_1fc8b3b9a1e18e3b_9.0.21022.8_none_60a5 df56e60dc5df.manifest
> 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_32\Microsoft.VC90.CRT\9.0. 30729.1__1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.DLL.
> INFO: Attempt to probe manifest at C:\Program
> Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT.DLL.
> INFO: Attempt to probe manifest at C:\Program
> Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT.MANIFEST.
> INFO: Attempt to probe manifest at C:\Program
> Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT\Microsoft.VC90.CRT.DLL.
> INFO: Attempt to probe manifest at C:\Program
> Files\Lavasoft\Ad-Aware\Microsoft.VC90.CRT\Microsoft.VC90.CRT.MANIFE ST.
> INFO: Did not find manifest for culture Neutral.
> INFO: End assembly probing.
> ERROR: Cannot resolve reference
> Microsoft.VC90.CRT,processorArchitecture="x86",pub licKeyToken="1fc8b3b9a1e18e3b",type="win32",versio n="9.0.30729.1".
> ERROR: Activation Context generation failed.
> End Activation Context Generation.
>
> ----------------
> Can you help? How extensive is this problem? Will it only effect adaware?
> How can it be fixed? I don't know how it happened except this morning on
> startup some unidentified appl wanted to run, on hitting control-alt-del
> to identify it, it disappeared. Thanx for any light you can shed on this.
>
>
>


I un-installed ad-aware. Installed Microsoft Visual C++ 2008 SP1.
Re-installed ad-aware. This corrected the problem.

 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
scheduler fails to start task five hours after session close OBones Windows Server 4 04-29-2008 02:20 AM
Telephony Will Not Start Nick Windows 64 Bit 3 12-22-2007 12:21 AM
Re: Telephony service failed to start Theo Windows 64 Bit 1 05-15-2007 06:53 PM
Start Menu is for the Birds!!! Rick Blake Windows Server 3 03-11-2006 03:19 AM
Disabling folder access on Start Menu Brian Windows Server 1 04-18-2005 09:37 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59