Excel Access Violation Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 07:31:38 GMT by s_wx1094 (squid/3.5.20)
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help
Easyworship Access Violation Error
Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services lacerte access violation error Groups Website Testing Store Headlines Experts Exchange > Questions > EXCEL.exe access violation Want to Advertise Here? Solved EXCEL.exe access violation Posted vindictus access violation error on 2001-07-17 MS Office 1 Verified Solution 13 Comments 6,245 Views Last Modified: 2012-05-04 I am writing a worksheet (with several forms and some macros and some user defined functions within it) and I have been http://answers.microsoft.com/en-us/msoffice/forum/msoffice_excel-mso_winother/excel-keeps-crashing-with-a-acces-violation-error/68c00399-7055-4359-94ea-0b8e4091f8c0 experiencing an intermittent problem when I save and close the worksheet it and attempt to reopen I get the message Dr Watson for Windows NT An Application error has occurred and an application error log is being generated EXCEL.exe Exception: access violation (0xc0000005), Address 0x301177bc I cannot get back in to the worksheet I have the Dr Watson Crash Dump File but I cannot make neither head nor tail from it https://www.experts-exchange.com/questions/20152159/EXCEL-exe-access-violation.html I have to completely shut down excel go back to an older saved version of my spreadsheet and rewrite all my my work. It does not happen all the time Anybody know what I am doing wrong ??? I am running Excel 97 SR2 on NT 0 Question by:hughesp Facebook Twitter LinkedIn Google LVL 13 Best Solution bycri hughesp, besides that you can not exclude the network as being the source of your troubles unless a workbook was corrupted at home, I was not precise enough. An ill aligned floppy drive head or a conflict Go to Solution 13 Comments LVL 8 Overall: Level 8 MS Office 2 Message Expert Comment by:tskelly0825982001-07-17 I searched the internet and found a reference to how the sheet is named in a macro. I don't know if this is relevant or not to your situation. Quote from reference below: "The macro refers to the worksheet directly by its object name as opposed to referring to it as part of a collection (for example, using the syntax Sheet1.Delete rather than Sheets(1).Delete)." http://mspress.microsoft.com/books/ww/sampchap/3846c.htm 0 Message Author Comment by:hughesp2001-07-17 I took a look at the link you posted - I cannot find a reference to the Address 0x301177bc (or any where else on the net for that matter). The colle
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://stackoverflow.com/questions/103516/excel-addin-access-violation and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it access violation only takes a minute: Sign up Excel Addin Access Violation up vote 0 down vote favorite Using c#, VS2005, and .NET 2.0. (XP 32 bit) This is a Winforms app that gets called by a VBA addin (.xla) via Interop libraries. This app has been around for a while and works fine when the assembly is compiled and executed anywhere access violation error other than my dev machine. On dev it crashes hard (in debugger and just running the object) with "Unhandled exception at 0x... in EXCEL.EXE: 0x...violation reading location 0x... But here's the weird part: The first method in my interface works fine. All the other methods crash as above. Here is an approximation of the code: [Guid("123Fooetc...")] [InterfaceType(ComInterfaceType.InterfaceIsIDispatch)] public interface IBar { [DispId(1)] void ThisOneWorksFine(Excel.Workbook ActiveWorkBook); [DispId(2)] string Crash1(Excel.Workbook ActiveWorkBook); [DispId(3)] int Crash2(Excel.Workbook activeWorkBook, Excel.Range target, string someStr); } [Guid("345Fooetc..")] [ClassInterface(ClassInterfaceType.None)] [ProgId("MyNameSpace.MyClass")] public class MyClass : IBar { public void ThisOneWorksFine(Excel.Workbook ActiveWorkBook) {...} string Crash1(Excel.Workbook ActiveWorkBook); {...} int Crash2(Excel.Workbook activeWorkBook, Excel.Range target, string someStr); {...} } It seems like some kind of environmental thing. Registry chundered? Could be code bugs, but it works fine elsewhere. c# interop .net-2.0 add-in share|improve this question edited Sep 22 '08 at 13:38 asked Sep 19 '08 at 16:35 Andrew Cowenhoven 2,5391223 add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted I've had problems in this scenario with Office 2003 in the past. Some things that have