ClickOnce error : fsvc.exe has encountered an error...

[Hugues]

Hi

We have a .NET Framework 2.0 Windows Forms application deployed with
ClickOnce (available online only). When we update the application, some of
our users cannot install the new version.

Here is the error message that the user receives : "dfsvc.exe has
encountered an error and needs to close. We are sorry for the inconvenience."

The error happens when the dialog box "Verifying application requirements.
This may take a few moments." is displayed. The users were able to run
previous version of the application and the error only occured after we
installed a new version of the application on the web server

In the Event Viewer, we have 2 errors :
First error : .NET Runtime version 2.0.50727.832 - Fatal Execution Engine
Error (7A0592A2) (80131506)
Second error : Faulting application dfsvc.exe, version 2.0.50727.832, stamp
461ef22a, faulting module mscorwks.dll, version 2.0.50727.832, stamp
461f2e2a, debug? 0, fault address 0x003a585f.

Our users mostly use Windows XP and .NET Framework 2.0, but we have also
seen a similiar error on 2 Windows Vista workstations.

When the error happens, we have been able able to fix it by deleting files
under C:\Documents and Settings\[user name]\Local Settings\Apps\2.0 on
Windows XP and a similiar folder on Vista. This fix is documented on
newsgroups, but we cannot ask many users to delete those files manually. It
looks like a bug in the framework. There must be a way to correct the error
before it happens.

Has anybody seen this error and found a way to fix it?

Thank you in advance.

Hugues

[Hugues]

Sorry, I made a typo in the title of my last post. Should read : dfsvc.exe
has encountered an error...

Post by Hugues
Hi
We have a .NET Framework 2.0 Windows Forms application deployed with
ClickOnce (available online only). When we update the application, some of
our users cannot install the new version.
Here is the error message that the user receives : "dfsvc.exe has
encountered an error and needs to close. We are sorry for the inconvenience."
The error happens when the dialog box "Verifying application requirements.
This may take a few moments." is displayed. The users were able to run
previous version of the application and the error only occured after we
installed a new version of the application on the web server
First error : .NET Runtime version 2.0.50727.832 - Fatal Execution Engine
Error (7A0592A2) (80131506)
Second error : Faulting application dfsvc.exe, version 2.0.50727.832, stamp
461ef22a, faulting module mscorwks.dll, version 2.0.50727.832, stamp
461f2e2a, debug? 0, fault address 0x003a585f.
Our users mostly use Windows XP and .NET Framework 2.0, but we have also
seen a similiar error on 2 Windows Vista workstations.
When the error happens, we have been able able to fix it by deleting files
under C:\Documents and Settings\[user name]\Local Settings\Apps\2.0 on
Windows XP and a similiar folder on Vista. This fix is documented on
newsgroups, but we cannot ask many users to delete those files manually. It
looks like a bug in the framework. There must be a way to correct the error
before it happens.
Has anybody seen this error and found a way to fix it?
Thank you in advance.
Hugues

[Hugues]

Hi all,

Is anyone at Microsoft aware of that problem?
Is it a bug in the framework?
Is there a way to correct the problem?

Thank you.

Hugues

Post by Hugues
Sorry, I made a typo in the title of my last post. Should read : dfsvc.exe
has encountered an error...

Post by Hugues
Hi
We have a .NET Framework 2.0 Windows Forms application deployed with
ClickOnce (available online only). When we update the application, some of
our users cannot install the new version.
Here is the error message that the user receives : "dfsvc.exe has
encountered an error and needs to close. We are sorry for the inconvenience."
The error happens when the dialog box "Verifying application requirements.
This may take a few moments." is displayed. The users were able to run
previous version of the application and the error only occured after we
installed a new version of the application on the web server
First error : .NET Runtime version 2.0.50727.832 - Fatal Execution Engine
Error (7A0592A2) (80131506)
Second error : Faulting application dfsvc.exe, version 2.0.50727.832, stamp
461ef22a, faulting module mscorwks.dll, version 2.0.50727.832, stamp
461f2e2a, debug? 0, fault address 0x003a585f.
Our users mostly use Windows XP and .NET Framework 2.0, but we have also
seen a similiar error on 2 Windows Vista workstations.
When the error happens, we have been able able to fix it by deleting files
under C:\Documents and Settings\[user name]\Local Settings\Apps\2.0 on
Windows XP and a similiar folder on Vista. This fix is documented on
newsgroups, but we cannot ask many users to delete those files manually. It
looks like a bug in the framework. There must be a way to correct the error
before it happens.
Has anybody seen this error and found a way to fix it?
Thank you in advance.
Hugues

[p***@gmail.com]

Post by Hugues
Sorry, I made a typo in the title of my last post. Should read : dfsvc.exe
has encountered an error...

Hi
nhvdvggfgfhdbdgbvgdggdbghyvwgudwsevghbgvchg
We have a .NET Framework 2.0 Windows Forms application deployed with
ClickOnce (available online only). When we update the application, some of
our users cannot install the new version.
Here is the error message that the user receives : "dfsvc.exe has
encountered an error and needs to close. We are sorry for the inconvenience."
The error happens when the dialog box "Verifying application requirements.
This may take a few moments." is displayed. The users were able to run
previous version of the application and the error only occured after we
installed a new version of the application on the web server
First error : .NET Runtime version 2.0.50727.832 - Fatal Execution Engine
Error (7A0592A2) (80131506)
Second error : Faulting application dfsvc.exe, version 2.0.50727.832, stamp
461ef22a, faulting module mscorwks.dll, version 2.0.50727.832, stamp
461f2e2a, debug? 0, fault address 0x003a585f.
Our users mostly use Windows XP and .NET Framework 2.0, but we have also
seen a similiar error on 2 Windows Vista workstations.
When the error happens, we have been able able to fix it by deleting files
under C:\Documents and Settings\[user name]\Local Settings\Apps\2.0 on
Windows XP and a similiar folder on Vista. This fix is documented on
newsgroups, but we cannot ask many users to delete those files manually. It
looks like a bug in the framework. There must be a way to correct the error
before it happens.
Has anybody seen this error and found a way to fix it?
Thank you in advance.
Hugues

[p***@gmail.com]

Post by Hugues
Sorry, I made a typo in the title of my last post. Should read : dfsvc.exe
has encountered an error...

Post by Hugues
Hi
We have a .NET Framework 2.0 Windows Forms application deployed with
ClickOnce (available online only). When we update the application, some of
our users cannot install the new version.
Here is the error message that the user receives : "dfsvc.exe has
encountered an error and needs to close. We are sorry for the inconvenience."
The error happens when the dialog box "Verifying application requirements.
This may take a few moments." is displayed. The users were able to run
previous version of the application and the error only occured after we
installed a new version of the application on the web server
First error : .NET Runtime version 2.0.50727.832 - Fatal Execution Engine
Error (7A0592A2) (80131506)
Second error : Faulting application dfsvc.exe, version 2.0.50727.832, stamp
461ef22a, faulting module mscorwks.dll, version 2.0.50727.832, stamp
461f2e2a, debug? 0, fault address 0x003a585f.
Our users mostly use Windows XP and .NET Framework 2.0, but we have also
seen a similiar error on 2 Windows Vista workstations.
When the error happens, we have been able able to fix it by deleting files
under C:\Documents and Settings\[user name]\Local Settings\Apps\2.0 on
Windows XP and a similiar folder on Vista. This fix is documented on
newsgroups, but we cannot ask many users to delete those files manually. It
looks like a bug in the framework. There must be a way to correct the error
before it happens.
Has anybody seen this error and found a way to fix it?
Thank you in advance.
Hugues

gtgerrhw