nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS7.2 Setup IIS7 iwproxy_isapi.dll

FredGravel

Hi All I am struggling in setting up IIS7 with iwproxy_isapi.dll and the IWUSR_MACHINENAME and all we were doing with IIS 5 and IIS 6 but it seems more complicated anybody have step or doc I have look all over the 7.2 docs and did not find any info

Thanks

Find more posts tagged with

Comments

Rick Poulin

What problem are you running into? The dll won't load? Access denied trying to get a resource through IIS? Proxy rules aren't working? ...

FredGravel

First it did not create the Web Instance.

So I had to create it manually.

1 - Create the IWUSR_MACHINENAME

2 - add IWUSR_MACHINENAME to Teamsite Web Preview Group

3 - I create default bind it to port 81

4 -add in ISAPI the IWHOME\lib\iwproxy_isapi.dll

5 - Create the iw-mount Virtual Directory pointing to Y:

6 - Put the IWUSR_MACHINENAME in the ASP.NET Impersonation

7 - result to
401 - Unauthorized: Access is denied due to invalid credentials.

You do not have permission to view this directory or page using the credentials that you supplied.

Rick Poulin

Sounds like you're forgetting to set the Directory Security on the Default Web Site. You'll need to enable anonymous access using IWUSR there too.

FredGravel

Done but I still receive The same error

403 - Forbidden: Access is denied.

You do not have permission to view this directory or page using the credentials that you supplied.

The other thing and might be an issues is the Shared IWSERVER is not setup on the Y: drive maybe it is related

Rick Poulin

The IWServer share is not related to this. As long as your Y: drive is up, your iw-mount virtual mount in IIS should work fine.

I notice you had a 401 before and now have a 403. At least now your credentials work... I would suggest running a command prompt as IWUSR (runas /user:IWUSR_MACHINENAME cmd.exe) and making sure you can browse the Y drive to the resource you were trying to access. If you can do so, then perhaps your directory security is not set up quite right?

I also remember something about TeamSite expecting TSIMP_MACHINENAME rather than IWUSR_MACHINENAME -- don't know if that's still the case but it has thrown me for a loop before.

FredGravel

Ok

runas as work I am able to browse and see the content

I did the switch to TSIMP_machinename add to Teamsite Web Preview and set the Anonymous user with it in IIS

Did not do any difference

I have notice that Directory Browsing was disable put it enable and restart the instace, Same error.

I delete the iw-mount setting
I recreate it from scratch and it works

thanks

slopes

This seems to be a fix for other IIS related authentication issues as well.
We had to re-init our TS_IMP-user and IIS was only showing 401.2 errors after that. Simply deleting and recreating the iw-application solved the issue.

cute_guy

This seems to be a fix for other IIS related authentication issues as well.
We had to re-init our TS_IMP-user and IIS was only showing 401.2 errors after that. Simply deleting and recreating the iw-application solved the issue.

from where did u delete the iw-application

AgeFromDate.rptdesign

Rick Poulin

He may have meant the iw-mount virtual mount in IIS.