The deployed machine is:Windows Server 2008 32 Bit (VM Ware)
The symptom is that ClickOnce deployed application suddenly doesn't work and triggered this exception. It was working previously for many months.
Description:
* Stopped working
Problem signature:
* Problem Event Name: CLR20r3 * Problem Signature 01: svacs_v2_2.exe * Problem Signature 02: 1.0.0.0 * Problem Signature 03: 4e040aee * Problem Signature 04: SVACS_v2_2 * Problem Signature 05: 1.0.0.0 * Problem Signature 06: 4e040aee * Problem Signature 07: ac * Problem Signature 08: e9 * Problem Signature 09: InvalidOperationException? ? * OS Version: 6.0.6001.2.1.0.274.10 * Locale ID: 1033
Read our privacy statement:
* http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
Reinstalling using ClickOnce method didn't help, same issue remains. It seems that the application couldn't even get started before this exception is triggered.
The problem (for my case), is actually due to ClickOnce deployment.
It seems that certain security policy has been configured in such manner which prevents ClickOnce deployment to execute.
Check out 'windows security log' under 'Event viewer' to determine what has been changed in the context of security.
The solution is not to make use of ClickOnce deployment to deploy the application, make use of the conventional setup file deployment instead.
The symptom is that ClickOnce deployed application suddenly doesn't work and triggered this exception. It was working previously for many months.
Description:
* Stopped working
Problem signature:
* Problem Event Name: CLR20r3 * Problem Signature 01: svacs_v2_2.exe * Problem Signature 02: 1.0.0.0 * Problem Signature 03: 4e040aee * Problem Signature 04: SVACS_v2_2 * Problem Signature 05: 1.0.0.0 * Problem Signature 06: 4e040aee * Problem Signature 07: ac * Problem Signature 08: e9 * Problem Signature 09: InvalidOperationException? ? * OS Version: 6.0.6001.2.1.0.274.10 * Locale ID: 1033
Read our privacy statement:
* http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
Reinstalling using ClickOnce method didn't help, same issue remains. It seems that the application couldn't even get started before this exception is triggered.
The problem (for my case), is actually due to ClickOnce deployment.
It seems that certain security policy has been configured in such manner which prevents ClickOnce deployment to execute.
Check out 'windows security log' under 'Event viewer' to determine what has been changed in the context of security.
The solution is not to make use of ClickOnce deployment to deploy the application, make use of the conventional setup file deployment instead.
Comments
was ωondering if you knеω of
аny forums that cover the same toрics talked about here?
I'd rеally love tο be a part of community wheгe I can get feed-bacκ from other κnoωledgeable individuаls that share the same
intеrеst. If you haѵe any suggеstiоns, please lеt me knοω.
Thank уou!
Reviеω my ωeblog: Facts About Tornadoes