IIS stopped in server 2019

mc 4,111 Reputation points
2024-07-07T06:32:06.4266667+00:00

in windows 10 it is ok.

in server 2019 it is stopped. I Use IISModule (c++) in IIS

a2a78aa817e49e93492313df9239a56

34e69921e0adc68c5ccb3e917b31320

11602de4ffd4197105d2cc9541fb9c3

Report.log

Internet Information Services
{count} votes

Accepted answer
  1. MotoX80 32,986 Reputation points
    2024-07-08T12:52:27.04+00:00

    I Use IISModule (c++) in IIS

    Here is what I would suggest.

    First, remove any reference to your dll in the IIS config. Test the site as best you can. The goal is to verify that the crash is directly related to your dll and it's not related to something else that is configured on this server.

    Second, modify your dll to display a "My dll got called." message to OutputDebugString and then returns. On the server, run the Debugview tool to capture debug output. The goal is to verify that IIS can load your dll and call it successfully. The important part is that this initial version of your dll should not do anything other than just exit after it writes to OutputDebugString. All you want to do is to see your debug message in the Debugview output.

    https://www.bing.com/search?q=+c%2B%2B+OutputDebugString

    https://learn.microsoft.com/en-us/sysinternals/downloads/debugview

    Third, enable the application functionality in your dll. Add additional OutputDebugString calls to display what functions are being call, what data you are processing, what return values it sets, etc. The goal is to determine if whatever your code does causes the IIS crash and that your dll is seeing the data that you expect to see.

    Start with that.


1 additional answer

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more