Home Dashboard Directory Help
Search

COMException was unhandled: Catastrophic Failure by Tony Henrique


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 636697
Opened: 1/18/2011 12:10:48 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I am having a problem with a WPF Application in Visual Studio 2010 and .Net Framework 4:

Inside Visual Studio 2010, When debugging, if I try to run a function that sets a property of a Interop COM object at the second time it throws this error:

COMException was unhandled: Catastrophic Failure
Error code: -2147418113

If I run the same application using the Windows Explorer, on the Debug output folder, the function runs normally.

If i change the Framework version to 3.5 the Visual Studio also runs the function normally
Details
Sign in to post a comment.
Posted by Tony Henrique on 4/13/2011 at 11:00 AM
A long time ago, I had already added a solution on the workspace that you provided.
Did you check that?

https://sftus.one.microsoft.com/choosetransfer.aspx?key=1d9ea00a-8c28-4453-819d-30256b0b9625

Password is 9f]XUpR2Vq

Posted by Microsoft on 4/5/2011 at 9:49 AM
We haven't received a repro for this problem. Please follow the instructions listed below so we can take a look at this.

Thank you,
The CLR Team
Posted by Tony Henrique on 2/3/2011 at 2:50 PM
Have you looked this issue? I am working now on a project that uses that, and I am with that error.
Posted by Tony Henrique on 1/21/2011 at 4:44 AM
Ok, I posted an example project where this bug can be reproduced.
Posted by Microsoft on 1/18/2011 at 8:32 PM
Hi Tony,

Could you please attach a zipped project to help us reproduce it?

************************************************************
Please zip the file and use "FeedbackID-636697" as prefix of the file name.

************************************************************
You can use the following workspace to upload the file:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=1d9ea00a-8c28-4453-819d-30256b0b9625
Password is 9f]XUpR2Vq
Posted by Microsoft on 1/18/2011 at 12:15 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.