Re: Enabling dlls in IIS 7.5

In the Application Pool I enabled 32-bit applications and that solved the problem.

Thanks.

BR

Rick:

Thanks for the response.

I did remember that and I had read, script, and execute all checked. Tried it with execute unchecked, too. I think I've tried it every which way and I'm basically stuck.

I'm thinking I might be hunting in the wrong places. The only other thing I might add is that when I go to the page it doesn't error out, it just keeps the previous page up (ie. if I'm on google and try to go the url with wc it will ask if I want to save or open the file, I click cancel and google page is still there.)

If anybody has any ideas I'm listening.

TIA.

BR

It's still there...

In the virtual, go to Handler Mappings | Edit Feature Permissions (on the right sidebar).

The default is Read / Script. You only need Execute if you access wc.dll directly.

+++ Rick ---

Rick:

Thanks for the response.

As you describe things I think I've set every thing up properly. There is a difference in 7.0 and 7.5. The big thing is you can no longer set virtual directories with script and execute rights. Or, at least, if there is a way to do it it sure isn't easy to find. I think if I knew how to do that in 7.5 I might be all set.

TIA.

BR

This question is how to enable the wc.dll to run in an IIS 7.5 environment. The documentation is very good, but in only goes up to 7.0.

Configuration for 7.5 is the same as 7.0 so those instructions should work.

Several things:

Make sure you explicitly enable wc.dll execution in the ISAPI restrictions as well enabling generic ISAPI suport.

Make sure the folder has read and execute rights and the virtual folder in IIS has Script AND Execute rights if you're running the DLL.

Make sure the ISAPI module is installed in the handler mappings for the virtual (you should see a .dll listing)

If you're running locally to test the site in IIS (ie. using Localhost) you should also see more detailed error information. Unfortunately IIS returns 404 errors for a whole host of operations that have nothing to do with "file not found" to not give away any info about what the actual failure is, but on the local machine there should be a lot more error info showing in the detailed error page.

FWIW, we recommend not using wc.dll directly but scriptmaps, but you might not have contorl over that with FoxInCloud. In general we recommend using wc.wc instead of wc.dll - less security issues and you can r

Hope this helps,

+++ Rick ---

I have installed the ISAPI and CGI Restriction feature. In there I have set the path to c:\app\site\bin\wc.dll. I have checked the "Allow extension path to execute." In the Handler Mappings I have ISAP-dll enabled, path set to *.dll, Path Type as File, and Handler set to ISAPIModule.

I'm not sure this is right. Well, I'm sure it's not right because it fails. When I type in the url - http://192.168.1.7/mud/bin/wc.dll?FoxInCloud~Default: It wants to save or open the wc.dll.

Any help is appreciated.

TIA.

BR