Hi

I built an ISAPI extension which works perfectly on Windows 2019 Server. I setup another Windows 2019 Server and the extension does not load. I always get a 404 error. I cannot find any differences between the two servers. I have ISAPI feature installed on both servers. I am using a script map (.fusion) on both servers to trigger the ISAPI extension. In IIS Management console it shows that the ISAPI extension is allowed and flagged as "execute". Does anyone have any ideas about what else I should check?

Thanks, Simon

Looks like you need the handler mapping. Without the .dll mapping the file won't be loaded as an ISAPI extension.

I would recommend assigning a scriptmap to the DLL to make it easier to handle. Never good to have .dll links...

Is there any reason you're building an ISAPI DLL rather than a .NET component? That's gotta be a heck of a lot easier than dealing with the C++ handling.

+++ Rick ---

Hi

I am using PureBasic for the ISAPI extension so it is very easy. I am not sure I understand your comment about a script map because that is exactly what did (.fusion) is the script map extension that I setup.

Simon

Sorry I didn't read your images correctly... yeah that looks right.

Make sure that the bitness is right. Make sure it's explicitly marked for 32 bit or (64 bit if that's what it's compiled to). Either switch the app pool to match (it's 64 bit by default) and explicitly provide the bitness on the handler mapping.

+++ Rick ---

Hi

It would help if I entered the extension properly. I entered the script map as .fusion when I should have entered *.fusion. I did not notice the missing *.

Simon

Been there - done that...

+++ Rick ---