Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Apache Faulting module name: MSVCR110.dll |
|
Author |
|
JohnnyBGood
Joined: 06 Nov 2014 Posts: 1 Location: US, indianapolis
|
Posted: Thu 24 Sep '15 21:27 Post subject: Apache Faulting module name: MSVCR110.dll |
|
|
Apache is crashing on Faulting module path: C:\windows\SYSTEM32\MSVCR110.dll. this happens when users launch a CBT that apache host via Alias to a file share.
we're running version Server version:
Apache/2.4.10 (Win64)
Apache Lounge VC11 Server built: Jul 17 2014 12:58:29
Could this be a 64 bit issue? pasting the event log entry below:
Faulting application name: httpd.exe, version: 2.4.10.0, time stamp: 0x53c7aae5
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098826e
Exception code: 0xc0000006
Fault offset: 0x000000000003c3b9
Faulting process id: 0x242c
Faulting application start time: 0x01d0f6f9d1bff6a2
Faulting application path: D:\Apache24\bin\httpd.exe
Faulting module path: C:\windows\SYSTEM32\MSVCR110.dll
Report Id: 8bf24d57-62ed-11e5-80d2-40a8f0231c3d
Faulting package full name:
Faulting package-relative application ID: "
Execute On Multiple Databases Return |
|
Back to top |
|
maba
Joined: 05 Feb 2012 Posts: 64 Location: Germany, Heilbronn
|
Posted: Fri 02 Oct '15 12:07 Post subject: |
|
|
Might be due to the fact that the "SYSTEM" user which is the default user under which the Apache server runs has no rights to access network shares. This is a Windows security feature since one of the more recent releases (might be Server2008 but could be that it was already in Server2003).
How to test:
Stop the normal Apache service.
Start the httpd.exe as a normal logged in user who has the right to connect to the network shares (either from command line or via Windows Explorer).
Try to access the URL that causes the problem. If the problem is gone, then the root cause is the SYSTEM user. |
|
Back to top |
|
|
|
|
|
|