Plesk dead after power failure - Apache.exe - ntdll.dll problem!

[eugenevdm]

This is the second time I'm having this problem. Last time it happened when I upgraded from Plesk 7.5.3 to 7.5.4, and this time it's happened after a power failure.

Plesk won't load anymore. It gives a "page cannot be found" error. The problem definitely appears related to Apache because every time I try to load Plesk I get an error in the Windows Event Log. I have listed this error. Last time I had this error and after two weeks of hellish research on Google (IMO the problem appears mostly undocumented) I had no choice but to completely reinstall the operating system and restore from backup. My customers and myself went without Plesk for two weeks and you can imagine the damage this does to a hosting company.

If anyone from SW-Soft is reading this I would like to make the following comment. It's almost impossible to log a call using your online server support form if Plesk is down because the form insist having the license key and build number which is not accessbile when Plesk is down.

So here is the error, and my question is why is Apache.exe suddenly having a problem with ntdll.dll? The server was running very stable for about a month and we haven't loaded anything new. I have restarted the server but this had no effect. I was wondering if it could be corruption in the MySQL database or something that's stopping the admin interface thus Plesk from starting. Is there a way of checking this?

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 2005/08/18
Time: 11:11:31 AM
User: N/A
Computer: CP2
Description:
Faulting application Apache.exe, version 2.0.52.0, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x000396d0.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 41 70 61 ure Apa
0018: 63 68 65 2e 65 78 65 20 che.exe
0020: 32 2e 30 2e 35 32 2e 30 2.0.52.0
0028: 20 69 6e 20 6e 74 64 6c in ntdl
0030: 6c 2e 64 6c 6c 20 35 2e l.dll 5.
0038: 32 2e 33 37 39 30 2e 31 2.3790.1
0040: 38 33 30 20 61 74 20 6f 830 at o
0048: 66 66 73 65 74 20 30 30 ffset 00
0050: 30 33 39 36 64 30 0396d0

 

[robtbs]

i had this issue yesterday, but my problem was due to Zend,

For some reason Apache didnt like the new Zend Optimizer i installed.

And i also had to change paths in php.ini

I had paths... C:\Progra~1

for some reason having space free paths caused issues.
I had to change them to C:\Program Files

To get plesk to run again.
All i can suggest about the support for is, try typing junk in it, and explaining your plesk installation is down so you cant get the Key...
The key may be stored in the registry maybe?

Rob

 

[eugenevdm]

New information regarding this problem

I found a php.ini file in "C:\Program Files\SWsoft\Plesk\admin" and then noticed when I comment out the line,

extension_dir = "C:\Program Files\SWsoft\Plesk\admin\modules"

Apache runs fine (instead complaining in the browser about some function it can't find).

Therefor my conclusion is that one of the Plesk / Apache modules that Plesk uses is corrupt, or perhaps the interaction a specific module is having with the Plesk database and /or operating system is corrupt.

Does anyone know how to view the Apache log on Windows or how to troubleshoot Apache modules?

AT THIS POINT I AM VERY DESPERATE SO IF ANYONE IS ABLE TO HELP ME FOR A FEE PLEASE CONTACT ME. I have already logged a "once off" incident at SW-Soft but I have had no response as of yet
(eugene at snowball dot co dot za)

 

[swarm]

I've sent you message with same subject as subject of this thread.

 

[eugenevdm]

PROBLEM RESOLVED

It turns out the problem is related to Zend. I must have installed Zend a month ago and never rebooted (as I recall it didn't ask for a reboot). After the power failure and the OS restarted something that Zend did kicked in.

When I uninstalled Zend the problem went away. I compared my paths to those mentioned by "robtbs" but I didn't have similar issues.

I've since learned the problem is related to a registry setting "HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFileLocation"

Apparently this must be empty. I have not been able to test it yet.