[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Please help!  Upgraded from 2.0.53 to 2.2 and Apache service crashes and burns.

Posted on 2006-05-10
3
Medium Priority
?
235 Views
Last Modified: 2012-05-05
Hello everyone!  I hope you can help me today, because we're in a bit of a bind.

The two computers we're dealing with are a Windows XP SP2 workstation and a Windows 2000 Server.

The WinXP machine had Apache 2.0.53 installed originally and the initial configuration worked perfectly.  Then we upgraded to Apache 2.2.  Suddenly, the Apache service will not start and crashes when it tries to start.  The crash only happens when the documentroot is set to a remote location on the Win2000 Server (for example: //ServerName/htdocs).

When documentroot is set to a local directory on the XP machine using 2.2, everything works fine.  But, when the documentroot is changed to a shared location on our Win2000 Server, then the service fails and crashes.  Crazy thing is, when 2.0.53 was installed, having the documentroot set to the Win2000 Server location caused no problems at all.  The problem only started when we upgraded.

Any help would be GREATLY appreciated!
Thank you so much.
-Mike
0
Comment
Question by:mlamartina
  • 2
3 Comments
 

Author Comment

by:mlamartina
ID: 16651828
I have a mini update...  I didn't even think to checked the service login and entered the proper domain, login, and password.  I had accidently left it as local login, which obviously doesn't work when accessing a network location.  I entered in the correct login and password.

However, I'm still getting a crash screen that asks me to debug, send error info to MS, or don't send info.  This time, I got a few new things.  I received an error in the System Event Log this time.  Error ID 7024.  Microsoft says that's an error due to the firewall being on and says to exclude File and Print Sharing.  But, it is already checked and so is Apache Server.  Interesting note, I also had two entries for Apache Server in the exclusions tab.  I removed one and rebooted and received this error at startup:

The instruction at "memory address" referenced memory at "0x0000".
The memory could not be "read"

Thank you for your help.  Hopefully this info helps in the resolution.
0
 

Author Comment

by:mlamartina
ID: 16652050
I found the solution.  Don't all rush to help!  ;-)  Just kidding.  I'm just happy it's fixed.  Here's what happened.  We uninstalled 2.0.53 and installed 2.2 overtop.  In the Services manager, there was a disabled service for 2.0.53 and an automatic service for 2.2.  Went into regedit, HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services, and deleted both Apache 2.0.53 and 2.2 services.  I reinstalled the Apache server.  Went into the service manager, manually stopped the service, and changed the login for the Apache 2.2 service for a valid domain login.  Then, changed the config file for the documentroot to "//servername/htdocs".  Rebooted and life was happy once again!

I guess the uninstall for 2.0.53 wasn't a very good uninstaller and the service that it left behind messed things up.  I'm not sure why, but I know it works beautifully now!

Thanks,
Mike
0
 

Accepted Solution

by:
EE_AutoDeleter earned 0 total points
ID: 16839574
mlamartina,
Because you have presented a solution to your own problem which may be helpful to future searches, this question is now PAQed and your points have been refunded.

EE_AutoDeleter
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you are running a LAMP infrastructure, this little code snippet is very helpful if you are serving lots of HTML, JavaScript and CSS-related information. The mod_deflate module, which is part of the Apache 2.2 application, provides the DEFLATE…
If you are a web developer, you would be aware of the <iframe> tag in HTML. The <iframe> stands for inline frame and is used to embed another document within the current HTML document. The embedded document could be even another website.
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…
Suggested Courses
Course of the Month20 days, left to enroll

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question