IIS Config on W2K8

[doctor_r]

Just wondering if there are more detailed instructions on configuring the server web components on Windows Server 2008? I can't seem to get it working.

The install created a "bpcsxsrvr" web app running under the "RMSSL" app pool pointing to %programfiles%\BishopPhillips\BPCRiskManagerV625\scripts... That contains the "HTTPSrvr.dll. I have configured DCOM the best I can tell. Just have everything running under the local admin account for testing. Still cannot connect via HTTP. Socket server is working fine.

Is there anymore detailed info for IIS7 on 2008?

Thanks,
Ryan

[bishopj]

(12-15-2009 02:27 AM)doctor_r Wrote:  Just wondering if there are more detailed instructions on configuring the server web components on Windows Server 2008? I can't seem to get it working.

The install created a "bpcsxsrvr" web app running under the "RMSSL" app pool pointing to %programfiles%\BishopPhillips\BPCRiskManagerV625\scripts... That contains the "HTTPSrvr.dll. I have configured DCOM the best I can tell. Just have everything running under the local admin account for testing. Still cannot connect via HTTP. Socket server is working fine.

Is there anymore detailed info for IIS7 on 2008?

Thanks,
Ryan

The IIS7 instructions should be pretty close to the IIS 6 instructions as I recall. When I did it on IIS 7 it seemed to be basically the same as IIS 6 with slightly prettier screens.

We haven't done the Win 2008 screen shots yet, but normally we would only do that if there was a significant difference. My recollection was that when we ran the tests on Win7 + II7 it all just went through as normal.

My guess is that the problem you are seeing is something we have had reported by email. The new installer tries to put things into the new HTTPSrvr directory bpcsxsrvr, but at least some part of the app set is looking for the older scripts directory. Most likely it is just the client defaulting to scripts, which you can reset on the client the first time you cannect. The work around is to rename the virtual directory to be "scripts".

We moved from scripts because IT Audit doesn't like it, and there could be other apps in that directory. We have machines using both configs (although most use scripts), so I know it works with bpcsxsrvr.

Obviously we messed something up, because it should work automatically for you.

Other issues include the need to allow unknown ISAPI extensions on the server - but that is in the instructions. My recollection is that that was the only thing that was in a different place under IIS7 from IIS6.

Seriously all the actual settings are the same. Generally the instructions that illustrate Vista are the ones that apply to WIn7 and W2008 - but we only show the differences where there are noticeable changes (eg SQL Server is illustrated for multiple versions on multiple environments).

The pool name doesn't matter. Try changing the virtual directory name to scripts and see if that works OR check the directory the client is using in HTTP/hTTPS connection mode and change it to bpcsxsrvr instead of scripts, and see if it connects.

Let me know how you go.