Internet Information Services - .exe does not recognize actions in url

Question

I am having a problem when invoking an .exe that is a webservice developed in Delphi.

The exe has an action by default but if I pass it actions, for example myexe.exe/actionExample, it should grab it, the problem is that it doesn't grab it.

It is a server that was installed from scratch but I have another server that is old and I was not involved in its configuration. The problem I'm telling you about works fine on this server (the old one).

I was testing all afternoon and couldn't get anything.

I tested filters, permissions, made rewriting rules and nothing worked.

In fact, I compared it with the old server and in general everything is the same, I don't know if it is some dll or some separate installer.

If anyone had this problem and can help me, I would appreciate it.

Answer 1

Check the Windows Event Viewer, IIS logs, or Apache error logs for any relevant error messages when you attempt to run the executable with an action.

If the old server has certain DLLs or other components installed that the new one does not, this could cause issues. Use a tool like Dependency Walker to analyze the executable and check for any missing dependencies on the new server.

Use Process Monitor to track.

Answer 2

@Pablo Cristiani,

it's likely due to a configuration or environment difference, here are some steps and considerations to troubleshoot the problem:

1. Application Pool: Check the application pool settings in IIS. Make sure that the application pool for your web service is configured identically on both servers. Differences in the managed pipeline mode (Integrated vs. Classic) or .NET CLR version might cause issues.
2. Handler Mappings: Look at the handler mappings in IIS. Ensure that .exe files are mapped correctly and that the necessary request handling modules (like ISAPI or CGI) are enabled and properly configured.
3. Request Filtering: Ensure that the request filtering settings on the new server allow the URLs you're trying to access. Sometimes, request filtering can block URLs with certain patterns or extensions.
4. Review both the web server logs (e.g., IIS logs) and the logs of your Delphi application (if available). This can give you clues about what happens when a request is made and why the action isn’t being processed.

If after checking all these points the problem persists, it might be helpful to create a small test application that mimics the behavior of your web service to isolate whether the issue is within your Delphi code or the server configuration.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.