IIS7 is a major change in IIS. Don Henderson contacted me and asked if I could help get it working. It really isn't hard but involves a few steps.
How do you get SAS/IntrNet operational.
1. Enable CGI Role on Server through the Server Manager.
2. Add in your website in IIS. Right-click the scripts or cgi-bin directory where
the broker.exe is located and select Convert to Application.
3. While still having the scripts/cgi-bin folder selected, double-click on the handler mappings icon on the right-hand side. There should already be a listing for *.cgi at the top. Double-click on it --> Request restrictions --> Mapping --> Invoke --> File or Folder, Access --> Execute.
4. Click on the machine name in IIS. Click on ISAPI and CGI restrictions. Click on Add..., specify the full path to the broker.exe.
5. Optional: set up a host header.
Click on the Default website or on the website name. On the far right-hand side of the screen, click on bndings. Specify a host header (demos.savian.net, for example).
See here for more details:
http://www.wrensoft.com/zoom/support/faq_cgi_iis.html
Good luck and contact me if you have issues.
Alan
This blog is designed to show various ways to use Data Virtualization, technologies, and SAS with Microsoft technologies with an eye toward outside of the box thinking.
Subscribe to:
Post Comments (Atom)
SAS throwing RPC error
If you are doing code in C# and get this error when creating a LanguageService: The RPC server is unavailable. (Exception from HRESULT:...
-
I am finally ready with my SAS dataset reader/writer for .NET. It is written in 100% managed code using .NET 3.5. The dlls can be found here...
-
I was just tasked to read in LDAP records so we could cross-reference userids with login identifiers and general ledger information. Using...
-
Well, around 14 months ago, I started on a journey to understand the SAS dataset so I could read and write one independently. Originally, I ...
4 comments:
Thanks Alan. Making it an application was the trick. I guess MS changed that since the last release. Leave it the MS to do $%^$%^%$#@% like that. Of course, that is why I asked for your help ;-)
They (MS) need to make it simpler.
Not sure if you did them then backed them out but each step, including the host header, was required.
I never had to touch security which I was shocked by.
Hello there (I couldn't find your e-mail so I am writing this here)
I'd like to invite you to add your blog to the new:
http://sas-x.com/
Website.
It's a news website, all dedicated to SAS, based on bloggers content.
I am it's founder, and I created it after creating a similar (and somewhat successful) such website around the topic of R programming. That website can be seen at:
http://www.r-bloggers.com/
If you are interested in joining, you can simply add your site at:
http://sas-x.com/add-your-blog/
Best wishes,
Tal
Post a Comment