OECGI.exe on IIS 6.0 (OpenInsight 32-bit Specific)
At 07 MAR 2006 05:59:16PM Carl Brandenburg wrote:
I have a customer that just moved from a W2K Server to a Win 2003 server, and I'm trying to get the OECGI working on it.
I moved the registry settings over. Created the virtual directory containing the oecgi.exe and the various dll's required. I verified that I can see plain html content in that directory, but when I try to go to something like http://localhost/oiweb/oecgi.exe/INET_TRACE, I get a 404 not found error.
I'm guessing that there are permissions set that are preventing me from accessing the executable, but I have no idea where or how to find them (I've never worked with 2003 server). When I created the virtual directory, I did make sure to set it to "Scripts and Executables".
Can anyone give me a guide for the proper permission on IIS 6? Thanks!
At 08 MAR 2006 12:30PM Pascal Landry wrote:
With IIS6 you will need to create a Web Service Extensions in which you will have to set to "Allowed" the files that oecgi.exe need such as oengine.exe, oengine.dll, oinsight.exe utf8.dll, rcl4.dll, xrev.dll, lh.dll.
This is found just below the "Application Pools" and "Web Site" in IIS6.
This should help you.
Pascal
At 08 MAR 2006 01:13PM Carl Brandenburg wrote:
Thanks for your help Pascal, that moved me along a little further.
Now I'm getting a 403 Forbidden error. I double checked and the website is using the IUSR_SERVERNAME user for anonymous access, and I gave that user full control of the oiweb directory. Still nothing.
Anymore ideas? Thanks!
At 08 MAR 2006 02:36PM Pascal Landry wrote:
You need not give that user rights to the OI directory but the SYSTEM, LOCAL SERVICE and SERVICE account modify to write if so desired.
I beleive the first two already have rights, the third may help your cause. Restart the IIS after you do the changes.
At 08 MAR 2006 02:49PM Carl Brandenburg wrote:
Well, I modified the user rights per your last post, but the problem was something to do with the DefaultAppPool in the Application Pools folder. Under the Itendity tab of the DefaultAppPool, the security account was set to Network Service. Changing this to Local System fixed our issues.
It's working now, but if you know of any security issues this may cause, please let me know.
And thanks again for all of your help!
At 08 MAR 2006 02:57PM Pascal Landry wrote:
I've been running on IIS6 for 2 to 3 years now and haven't had a problem other that the same you had way at the begining.
My web app uses Active Directory which have all authorised uses included there. It also uses the username within OI for restricting read write access.
Good luck,
Pascal Landry