Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 03 NOV 2010 05:14:04AM Jon Brewster wrote:

I'm having an issue configuring Oecgi on IIS7, previously it was returning a HTTP 404 error, however since adding Handler Mappings for the oecgi.exe and the dll's in the scripts directory I am getting an OECGI SetCurrentDirectory failure.

I'm guessing it's something to do with permissions but I'm uncertain what the issue is.

Any help/advice would be gratefully received.


At 03 NOV 2010 08:40AM Jared Bratu wrote:

Have you tried OECGI2.exe or OECGI3.exe? These versions overcome several limitations of the original OECGI module. As a result OECGI.exe is deprecated in favor of the later releases.

There is an extensive configuration guide for configuring OECGI3.EXE on IIS7. Please see:

http://www.revelation.com/revelation.nsf/26967e116b65dee585256b6d004a6bb8/0765cab4817fe5f7852576a80064c313/$FILE/103-960%20OECGI3.EXE%20Quick%20Start%20Guide.pdf


At 03 NOV 2010 11:32AM Jon Brewster wrote:

Thanks for that Jared.

I've had a look at that Quick Start Guide and I've got IIS configured as it says, however it's still not working.

I was looking at oecgi2 but doesn't it require an oengine service running on the server, and I didn't know if that was compatible with openinsight 7.2


At 03 NOV 2010 12:04PM Jon Brewster wrote:

Please ignore that last post, I've got oengine running as a service, I just need to sort out my configuration.

I'll let you know how I get on


At 04 NOV 2010 04:56AM Jon Brewster wrote:

I've got oecgi2 configured now, and I'm running an oesocketserver on localhost.

However when I run the INET_TRACE using

http://localhost/cgi-bin/oecgi2.exe/INET_TRACE

I get the following error.

Cannot process query: /cgi-bin/oecgi2.exe/cgi-bin/oecgi2.exe/INET_TRACE

where the /cgi-bin/oecgi2.exe is repeated. Is this an issue with my IIS 7 configuration? Or is it to do with the fact that I'm running this on openinsight 7.2?

Or is it something else?

Thanks


At 04 NOV 2010 07:50AM Dave Harmacek wrote:

Did you define "cgi-bin" as a virtual directory? or oecgi2.exe?

Try again removing first cgi-bin/ and oecgi2.exe/

Dave


At 04 NOV 2010 10:24AM Jon Brewster wrote:

I've defined cgi-bin as my virtual directory, containing oecgi2.exe.

I've registered oecgi2.exe as a valid extension in the ISAPI and CGI extensions window, and set the security rights in the Handle mappings.

Basically all it says in the oecgi quick start guide.

I've tried removing everything to do with oecgi from IIS and adding it all in again, but that has made no difference.

Jon


At 04 NOV 2010 04:08PM Dave Harmacek wrote:

At 08 NOV 2010 08:22AM Jon Brewster wrote:

I tried that, no joy.

I'm going to try and run it on another box just to exclude the possibility that it's something misconfigured on this one.

I'll let you know how I get on with that.


At 08 NOV 2010 11:07AM Jared Bratu wrote:

This is likely an IIS configuration issue. I've seen it occur when IIS is mis-configured. I can't put my finger on the problem but you probably have a bad setting.

Would you run the command:

%systemroot%\system32\inetsrv\appcmd list site /config ] iisconfigtemp.txt

Please post the contents of iisconfigtemp or email the file to jared@revelation.com?

I think the problem lies in a handler mapping. You may want to check the server, default web site, and virtual directory handler mapping settings.

Are you using IIS 7 or 7.5?


At 10 NOV 2010 12:03PM Jon Brewster wrote:

I've posted the contents of iisconfigtemp.txt below.

I'm running IIS 7.5.

Thanks.


At 11 NOV 2010 10:12AM Jared Bratu wrote:

Thanks, it looks correct, I also need the config section. Please run the command:

%systemroot%\system32\inetsrv\appcmd list config ] iistemp.txt

Please email iistemp.txt to me jared@revelation.com and I'll post the relevant sections back.


At 11 NOV 2010 11:57AM Jared Bratu wrote:

At first I thought this was a IIS configuration issue because this issue has been tied to incorrect IIS settings. After examining your configuration files and doing some testing of my own the problem has been narrowed to OI 7.2.

The duplicate / repeating text in the query is a red herring. To prove it change the OECGI2 registry entry "ProcedureName" from "RUN_OECGI_REQUEST" to "INET_TEST" and add this routine to your OI system:

Function inet_test(params, params2)

Declare Function Inet_QueryParam

r=Content-type: text/plain":\0A0A\

r=12345"

r=Hello World"

Return r

Restart your engine server and send a request to OECGI2. You should get a valid response.

I'm not sure if the problem lies in the RUN_OECGI_REQUEST, INET_TRACE, or combination of IIS / OI 7.2. Use of OI 7.2 on IIS 7 isn't supported - for this environment I would recommend upgrading to OI 9.2.

Thank you for working through this issue and posting your IIS configuration files. Please let me know if you have any further questions.


At 24 NOV 2010 04:41AM Jon Brewster wrote:

Jared,

I've tried as you suggested and I get the expected response from INET_TEST.

I've tried with different function calls that used to work on OECGI and they give me the same duplicated response, so it appears that the problem lies with RUN_OECGI_REQUEST.

Further up in the thread, you recommended using OECGI2 with IIS7, does this mean that OECGI is unsupported with IIS7, I only ask because I have a customer who's moving servers from one running IIS6 and OECGI to one (hopefull) running IIS7 and OECGI.

If I'm not going to be able to get this setup running then I should probably tell him sooner rather than later.

Is there any documentation about getting OECGI running on IIS7, or is it simply not recommended.

Thanks


At 24 NOV 2010 10:45AM Jared Bratu wrote:

Running OECGI is not recommended and at some point it will be removed from the main distribution. The migration to OECGI2 should be fairly painless unless there is some application specific dependency I'm not aware of.

Upgrading to 8.0.8 may replace RUN_OECGI_REQUEST but the problem may be specific to OECGI.exe. All of the documentation focuses on OECGI2 and OECGI3 so even if the upgrade resolves the problem documentation for OECGI isn't going to be updated for IIS7.

Thanks for the follow-up and providing the configurations. If you need assistance moving to OECGI2 please open a new thread.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/330d2143496d7905852577d00032ba32.txt
  • Last modified: 2023/12/28 07:39
  • by 127.0.0.1