microsoft visual basic for applications automation error

And COMProcess.dll uses DotNetProcessDAL.dll via CCW. => DotNetProcess.dll => COMProcess.dll =>DotNetprocessDAL.dllĭotNetProcess.dll uses the COMProcess.dll, via RCW. We are able to get the windows application working, but not the website nor the web service.ĭiagram below shows the relationship of the components and applications. We have written asp.net website, webservice and. NET assembly), that works fine with Windows Apps and Web Apps. This works fine in Windows Apps.īut, if we only have Assembly call the COM Component (this COM Components does not call another other. NET assembly working in the call chain (Assembly->COM component -> Assembly), when used in Web Application. NET assembly, and we would not be able to get the COM components call. NET Assembly calls a COM components and that COM components calls another. net Assembly and COM component together, and is having problem with loading the private assembly. If any of these three are disabled in any combination the VBA will start running bug-free.Issue with Interop of COM component and. BUT, if given a fresh copy of the same exact file, sometimes the problem will disappear.Īfter some online review, I have tracked the error down to three references being used: OLE Automation, Microsoft Office 12.0 Object Library, Microsoft CDO for Windows 200 Library.

Once, a 2007 machine encounters the error, that file will never work on that machine or any other 2007 machine again. The have been several instances where a machine will run the VBA code fine and suddenly the error will start occurring. There is no noticeable difference between the versions that work and those that don't from a code perspective. These same machines have been running and testing the tool all day every day up until the point it occurs.

Only happens every couple weeks (every 3-5 versions of the tool). It only happens on the machines running 2007, 20 machines never have this issue. From time to time when running VBA on an excel tool that my team is building, Excel will crash and the 'Microsoft has stopped working' pop-up will appear and when the user selects the 'close the program' option another pop-up stating 'Automation Error Exception Occurred' appears. My team has had this strange error bugging us during development.

Microsoft visual basic for applications automation error