Location of HTTPD.CONF incorrect
3 posts
• Page 1 of 1
- RichardHauer
- Posts: 2
- Joined: 28 Oct 2014, 05:23
Location of HTTPD.CONF incorrect
I have just installed APE on IIS 8.5 and while it has worked a million times for me before, this time when I go to the APE component in IIS on the SERVER node instead of showing the path to httpd.conf as
C:\Program Files (x86)\Helicon\Ape\httpd.conf as one normally expects, the path is set to
C:\Windows\assembly\GAC_MSIL\Helicon.Ape.Editor\3.1.0.138__95bfbfd1a38437eb\httpd.conf
Clearly this is picking up the path to the module and not the path as specified in applicationHost.config.
I can confirm the presence of the following in applicationHost:
<HeliconApe InstallDir="C:\Program Files (x86)\Helicon\Ape\" />
I'm not really sure where to go from here. I tried uninstalling and reinstalling and it didn't help.
Thoughts?
C:\Program Files (x86)\Helicon\Ape\httpd.conf as one normally expects, the path is set to
C:\Windows\assembly\GAC_MSIL\Helicon.Ape.Editor\3.1.0.138__95bfbfd1a38437eb\httpd.conf
Clearly this is picking up the path to the module and not the path as specified in applicationHost.config.
I can confirm the presence of the following in applicationHost:
<HeliconApe InstallDir="C:\Program Files (x86)\Helicon\Ape\" />
I'm not really sure where to go from here. I tried uninstalling and reinstalling and it didn't help.
Thoughts?
- RichardHauer
- Posts: 2
- Joined: 28 Oct 2014, 05:23
Re: Location of HTTPD.CONF incorrect
In case this is haunting anybody else, I have fixed it.
I decompiled the Helicon.Ape.Editor to see where the management snapin was looking and found a method called SnapinService.GetRootPathFromRegistry(). I surmised that the method was failing since the path is in the registry and is correct, therefore I first assumed a permissions issue, but it was not that.
I noticed that Helicon is installed into "Program Files (x86)" and assume therefore it is compiled for 32bit. Checking for reg keys in HKLM\SOFTWARE\Wow6432Node\Helicon\Ape sure enough reveals there are extra values in there, of particular interest was the InstallDir entry.
Duplicating the values from the HKLM\SOFTWARE\Wow6432Node\Helicon\Ape into the HKLM\SOFTWARE\Helicon\Ape solved the issue. I copied all the values as I presumed the other values would need to be read sooner or later.
Below I include the contents of a file called "ape.reg" that, when double-clicked, will add the necessary values. Be sure to check that you have the correct version number and path before applying this to your system.
I decompiled the Helicon.Ape.Editor to see where the management snapin was looking and found a method called SnapinService.GetRootPathFromRegistry(). I surmised that the method was failing since the path is in the registry and is correct, therefore I first assumed a permissions issue, but it was not that.
I noticed that Helicon is installed into "Program Files (x86)" and assume therefore it is compiled for 32bit. Checking for reg keys in HKLM\SOFTWARE\Wow6432Node\Helicon\Ape sure enough reveals there are extra values in there, of particular interest was the InstallDir entry.
Duplicating the values from the HKLM\SOFTWARE\Wow6432Node\Helicon\Ape into the HKLM\SOFTWARE\Helicon\Ape solved the issue. I copied all the values as I presumed the other values would need to be read sooner or later.
Below I include the contents of a file called "ape.reg" that, when double-clicked, will add the necessary values. Be sure to check that you have the correct version number and path before applying this to your system.
- Code: Select all
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Helicon\Ape]
"InstallDir"="C:\\Program Files (x86)\\Helicon\\Ape\\"
"AcceptEULA"="Yes"
"FreeVersion"="Yes"
"Version"="3.1.0.138"
"LicensingMode"="Free"
Re: Location of HTTPD.CONF incorrect
Hi,
Thank you for doing the homework on this. I spotted the odd path, and found your post.
I copied current values from my installation, e.g., version number 145 and no free version. There were only a few, so it was easy enough to do it manually.
Bob
Thank you for doing the homework on this. I spotted the odd path, and found your post.
I copied current values from my installation, e.g., version number 145 and no free version. There were only a few, so it was easy enough to do it manually.
Bob
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 35 guests