Last post Sep 18, 2013 09:52 AM by Shawk
Apr 29, 2013 01:04 PM|lee.steven|LINK
I have a windows command line application that retrieves information from a SQL database. This information is then used to populate a new Excel workbook and saves it as an xls file. The application works as specified from the command line. However, when
I try executing the same application through an ASP.NET webpage on the web server, it executes part way and the Excel process becomes orphaned.
The only information I have to go on from the event viewer are the following errors.
1st Error: (#1000 Application Error)
Faulting application name: xl.exe, version: 126.96.36.199, time stamp: 0x5159c582
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0xe0434352
Fault offset: 0x0000b9bc
Faulting process id: 0x5bc
Faulting application start time: 0x01ce315fe8ce455b
Faulting application path: D:\Inetpub\www\build\report\xl.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 279d396c-9d53-11e2-863b-6ad9cec2af31
2nd Error: (#1026 .NET Runtime)
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.RuntimeType.ForwardCallToInvokeMember(System.String, System.Reflection.BindingFlags, System.Object, Int32, System.Runtime.Remoting.Proxies.MessageData ByRef)
at ExcelCheckList.ScoreSheet..ctor(Boolean, Boolean, System.String, Int32)
Please note that these errors do not appear when executing the same app from the command line.
Any suggestions on how to suppress these errors so that my application can execute is much appreciated.
Apr 29, 2013 01:15 PM|thirumaran007|LINK
This could be problem of version updation.. please check this MSDN link
Apr 29, 2013 01:22 PM|lee.steven|LINK
If this was the case, then why does it run from the command line on the web server without any problems?
Please note that this problem occurs when an ASP.NET web form tries to execute this command line program.
Sep 18, 2013 09:52 AM|Shawk|LINK
I have a very similar problem - were you able to get this resolved?
In my case, the calling program is a service. When I run it from the command line it works without issue.
*** UPDATE ***
The problem appears to be security related. Our GPO had been reconfigured - unfortunately I do not know specifics - however, that caused issues that made me switch the service to run under the local service account.
When I was running the console application from the command prompt, I was logged in as a domain account with local admin rights.
Once our domain account with local admin (and service) rights was removed from the GPO, and the service was reconfigured to log in using said account, the service was able to run our console applications again.