Conmari
asked on
An unhandled win32 exception occurred in Excel.exe
My question is similar to a related one by TRAININGBSC of 2/19/09 that was closed after there was no further response to a reply by boag2000 on 3/7/09. In my case, the error message is the same except for the number in square brackets, which was [1104] in the original question and changes in my case, e.g., [1272], [3796], [980]....
To answer boag2000's questions re: the original post:
1. This message appears as part of a Visual Studio Just-In-Time Debugger dialog. A list of Possible Debuggers (only one called "New Instance of Visual Studio" is listed) is presented and I am prompted to choose to debug with the selected debugger (Yes/No). Clicking on Yes invokes the debugger. Clicking on No closes Excel immediately, without any opportunity to save the file.
The Excel file is fairly straightforward (it does include multiple worksheets) and does not include any macros or custom code.
In addition to the Yes/No buttons within the dialog, there are two option checkboxes as follows: "Select the currently selected debugger as the default" and "Manually chose the debugging engines." If I select the latter, I am presented with an "Attach to Process" dialog within Visual Studio with checkboxes for the types of code (Managed and Native) to debug for the Excel process (...\Excel.exe). Native is already checked and if I attempt to uncheck it, an error messages says it must be selected.
2. I have SQL Server 2008 Developer Edition, including Visual Studio, installed on the same Windows XP SP3 machine (Gateway laptop). I have used Reporting and Analysis Services but have not done any development directly through VS. Therefore, I have no experience using the debugger. (I am, however, experienced with using many Excel features other than macros and other customizing.)
3. I am running Office 2000, including Excel, Word, etc.
Additional details:
* This problem has occurred several times in the past (only since SQL Server was installed) but I didn't keep track of the details. In this instance, I had modified the file Page Setup to landscape. The worksheet can be printed successfully, but the error occurs when I attempt to save the file. I am able to make other other worksheet content changes and save the file without problem. It is only changes to anything related to page setup that cause the problem on saving this file. Furthermore, I can make changes, including page setup, to other similar files without problem. I don't recall having problems with Excel files prior to installing SQL Server
* If I simply disable the Just-In-Time debugger options for all the code types, including Native, from within Visual Studio and repeat the changes to the Excel file and attempt to save it, an error appears that tells me that the Just-In-Time debugger has been disabled. Clicking OK causes both the message and Excel file to both close immediately.
Is there any other way to disassociate Excel from Visual Studio to avoid interference from the debugger? As mentioned, I don't recall having any similar problem prior to installing SQL Server.
Thanks for any assitance.
To answer boag2000's questions re: the original post:
1. This message appears as part of a Visual Studio Just-In-Time Debugger dialog. A list of Possible Debuggers (only one called "New Instance of Visual Studio" is listed) is presented and I am prompted to choose to debug with the selected debugger (Yes/No). Clicking on Yes invokes the debugger. Clicking on No closes Excel immediately, without any opportunity to save the file.
The Excel file is fairly straightforward (it does include multiple worksheets) and does not include any macros or custom code.
In addition to the Yes/No buttons within the dialog, there are two option checkboxes as follows: "Select the currently selected debugger as the default" and "Manually chose the debugging engines." If I select the latter, I am presented with an "Attach to Process" dialog within Visual Studio with checkboxes for the types of code (Managed and Native) to debug for the Excel process (...\Excel.exe). Native is already checked and if I attempt to uncheck it, an error messages says it must be selected.
2. I have SQL Server 2008 Developer Edition, including Visual Studio, installed on the same Windows XP SP3 machine (Gateway laptop). I have used Reporting and Analysis Services but have not done any development directly through VS. Therefore, I have no experience using the debugger. (I am, however, experienced with using many Excel features other than macros and other customizing.)
3. I am running Office 2000, including Excel, Word, etc.
Additional details:
* This problem has occurred several times in the past (only since SQL Server was installed) but I didn't keep track of the details. In this instance, I had modified the file Page Setup to landscape. The worksheet can be printed successfully, but the error occurs when I attempt to save the file. I am able to make other other worksheet content changes and save the file without problem. It is only changes to anything related to page setup that cause the problem on saving this file. Furthermore, I can make changes, including page setup, to other similar files without problem. I don't recall having problems with Excel files prior to installing SQL Server
* If I simply disable the Just-In-Time debugger options for all the code types, including Native, from within Visual Studio and repeat the changes to the Excel file and attempt to save it, an error appears that tells me that the Just-In-Time debugger has been disabled. Clicking OK causes both the message and Excel file to both close immediately.
Is there any other way to disassociate Excel from Visual Studio to avoid interference from the debugger? As mentioned, I don't recall having any similar problem prior to installing SQL Server.
Thanks for any assitance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
To clarify, I meant to ask whether the VS debugger only tracks MS Office Processes in addition to VB code or other processes, MS or otherwise.
I don't really know, I am no VS programmer, so I have little to no experience with the debugger. I do have a similar setup as you have however (SQL Server installed), which is why I have experienced something like you in the past.
ASKER
OK, I suppose the VS debugger's scope is a separate question. Thanks, jkpieterse, for your insight re: the Excel file. I ended up finding a means to create a new file based on the data in the corrupt file, so I also haven't lost anything in this case -- always a plus.
ASKER
What I've been able to do since my original post is select all of the worksheet tabs and copy them to a new book. When I open that book, I can make the page setup changes and successfully resave the file. So whatever was corrupted in the original file doesn't seem to have been replicated by copying the pages. When I tried to simply save the original file under a new name, I still was not able to save the file after making the page setup changes.
I'm curious whether the Visual Studio debugger only tracks MS Office processes or other processes running on the machine.