Skip to main content
A
Anonymous
October 14, 2010
Question

Apache no longer working after latest Microsoft patches

  • October 14, 2010
  • 4 replies
  • 861 views

I'm still in the testing phase of Intralink 9.1 M060.
I did a fresh install (OS & Windchill) which appeared to work fine.
However, when opening up the Windchill home page for the first time, I'm getting:
Service Temporarily Unavailable.
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

As in the past, I created a Windows service to start all components.
The Apache service fails to start. The event viewer only states that the failure occurred with exit code 1.

The only difference from prior install tests is that several new Microsoft patches (Windows Update) were included.

Anyone else seen this?

Gerry

4 replies

A
Anonymous
October 15, 2010

I forgot to mention. My test server is Windows 2003 x64 SP2 running on a VMWare virtual machine.

If necessary, I can revert to a prior install of the OS without the latest Windows security patches, but would like to avoid such.

Gerry

A
Anonymous
October 15, 2010

Many thanks to Raimondas who led me to the problem and solution.

I had created services to start all the Windchill components, which had been working fine until the latest Microsoft security patches.
Specifically, I used the ant command to create the service for Apache (per the advanced install guide).
Apache would fail even when launched from a command line.
Deleting the service (with ant) solved the problem. Apache works from the command line once again.
And fortunately, Raimondas knew that Apache has its own command to create a service (without ant).

This does not explain why the Microsoft patches caused this to happen.
And maybe the problem lies elsewhere.
However, this solution is plenty good for me.

Gerry

J
jessh12-Amethyst
12-Amethyst
October 15, 2010
This also does not explain why the Ant created service didn't work
properly (as it simply uses the Apache command) -- or whether something
about the patch simply required re-creating the service (and thus the
Ant command would have worked fine as well).

--
Jess Holle

A
Anonymous
October 15, 2010
To answer your question: After the problem arose, I did use ant to delete and recreate the service.
The problem was still present. Rebooting didn't help either.
Terms & ConditionsAccessibility statement