Answered by:
Installing Windows Service on Windows Server

Question
-
Hello,
we have an old C++ project for Windows Service. It goes back to VC 6.0.
But it is also compiled under Visual Studio 2010.
Independent of the compiled version (VC 6.0 or VS 2010) we have the same problem.
The service can be installed on Windows 7 Professional and Windows 10 Professional and it works on both OS normally.
However, we cannot install it and we cannot run it under Windows Server 2008 and Windows Server 2012.
The error is the same on both OS and
error message is "The application was unable to start correctly (0xc000007b). Click OK to close the application."
Event viewer records:
Windows Server 2008:
************************
Application popup: OurService.exe - Application Error : The application was unable to start correctly (0xc000007b). Click OK to close the application.
************************
Windows Server 2012:
************************
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: OurService.exe
P2: 1.1.0.5
P3: 56b4751d
P4: ntdll.dll
P5: 6.3.9600.18146
P6: 5650afd4
P7: c000007b
P8: 0009d572
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OurService_1be3baf378161ad0aaa791eb2585a8543fdd5a16_73491f84_0b75056c
Analysis symbol:
Rechecking for solution: 0
Report Id: 8137763e-cc22-11e5-80ff-000c2975a90b
Report Status: 2048
Faulting application name: OurService.exe, version: 1.1.0.5, time stamp: 0x56b4751d
Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650afd4
Exception code: 0xc000007b
Fault offset: 0x0009d572
Faulting process id: 0x910
Faulting application start time: 0x01d1602f683ced82
Faulting application path: C:\OurService\bin\OurService.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a6fd9fd4-cc22-11e5-80ff-000c2975a90b
Faulting package full name:
Faulting package-relative application ID:
Windows cannot access the file for one of the following reasons: there is a problem with the network connection,
the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing.
Windows closed the program OURSERVICE MFC Application because of this error.
Program: OURSERVICE MFC Application
File:
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.
Additional Data
Error value: 00000000
Disk type: 0
***********************
However we can install the service on Windows Server 2003 and it works normally.
Any advice would be highly appreciated.
Thanks,
Vladimir
Vladimir Belitski
- Edited by Vladimir Belitski Saturday, February 6, 2016 11:49 AM
Saturday, February 6, 2016 11:46 AM
Answers
-
Hi,
Thank you for posting in MSDN forum.
Firstly , please go to the path "C:\Windows\SYSTEM32\ntdll.dll" to check if the dll files are missing or corrupted.
If there is something wrong with it, I recommend you use sfc /scannow command to see if there are any system errors and to repair missing or corrupted system files before turn on the features.
Reference link about sfc/scannow command:
https://support.microsoft.com/en-us/kb/929833
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.Monday, February 8, 2016 2:19 PM -
Hi,
we have finally found the problem. It was a conflict between SQL library we use and Oracle installation on the server. The error message was complitely misleading, but this is not new.
Thanks for reading and answering.
Regards,
Vladimir
Vladimir Belitski
Wednesday, February 10, 2016 10:25 AM
All replies
-
Hi,
Thank you for posting in MSDN forum.
Firstly , please go to the path "C:\Windows\SYSTEM32\ntdll.dll" to check if the dll files are missing or corrupted.
If there is something wrong with it, I recommend you use sfc /scannow command to see if there are any system errors and to repair missing or corrupted system files before turn on the features.
Reference link about sfc/scannow command:
https://support.microsoft.com/en-us/kb/929833
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.Monday, February 8, 2016 2:19 PM -
Hi,
thank you very much for answering.
Yes, the dll is on the right place and i ran the sfc check (found nothing).
I also tried to control (using sysinternals Process Explorer) what dlls are loaded and to compare it with the list from machine where it works. No success. When the error comes, the number of loaded dlls is still very small compared to the real number loaded when it works correctely.
In the meantime we have got another test machine with Windows 2012 Server where it works. We cannot see where is the difference. The bad thing is that it does not work by our customer exactely the same way (see error described in the first post).
Any further ideads?
Best regards,
Vladimir
Vladimir Belitski
Tuesday, February 9, 2016 7:26 AM -
Hi,
we have finally found the problem. It was a conflict between SQL library we use and Oracle installation on the server. The error message was complitely misleading, but this is not new.
Thanks for reading and answering.
Regards,
Vladimir
Vladimir Belitski
Wednesday, February 10, 2016 10:25 AM