issues in IIS. Hence, I document it below.
People may ask why use SAS/IntrNet anymore? Well, it is fast and is probably the fastest way to interact with SAS via the web. It has limitations but it implements a standard REST api that is used by loads of web companies (i.e. Twitter, Facebook, etc.). I absolutely love IntrNet due to its simplicity.
Let's make it happen:
I posted a short while back on how to get SAS/IntrNet operational on IIS 7. Well, I had to do everything again under IIS 7.5 and eiteher things have changed slightly or I didn't get it all captured last time. So here we go again, but this time with pictures:
1. Open up IIS in Windows Server 2008 R2 and right-click on sites, Add a new site:
3. Pay attention to the application pool and any host header information. Host headers are nice for handling lots of different sites under a single domain name.
4. You should now have a basic site. Add in a virtual directory for the scripts directory:
5. Point it to the SAS/IntrNet scripts location (normally c:\inetpub\scripts).
7. Go to Windows Explorer, go to the scripts directory, right-click and select properties. Go to the security tab and add in the app pool identity. This is different than previous versions of IIS. If you used DefaultAppPool as shown above, use the following id:
[Note: Even a single space at the end of the above name will cause it to not work.]
8. Go back to IIS, click on the site, select Handler Mappings, Add Managed Handler:
9. CRITICAL STEP. While inside of Handler Mappings, click on request restrictions, go to the Access tab, and select Execute:
10. Finally, go to the Authentication tab for your site and open it. Under Anonymous Authentication, select edit and change it to the pool identity:
If all of the above does not work, call or email.