This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 46%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We have a simple WCF service installed on Windows Server 2012 with IIS 8.5. This has been running flawless for many years. We have now started installing our services on our new Windows Server 2022 with IIS 10.0
Unfortunately one of the few services we are activating on the new server is running into problems, and I have no idea why. We have directly copied all files from the old server to the new server and set up the site with the same settings. Most of the settings are default. The only differences I have found is that under application pools, I need to set it to Enable 32-Bit Applications and Load User Profile should be false
When I try to call the service on the new server, all I'm getting is an 500 internal error. Nothing useful as far as I can tell
The service itself is very simple. It just takes a string (html) and sends it to TuesPechkin.Wkhtmltox and returns the output. Neither the service, nor the part of the client calling the service, has been changed in the 4 years I have been working here. We have never had any issues with it
I tried set up some try catch inside the first method called on the service and have it write information in a txt file, but nothing is ever written. I have a feeling the method is not called
Any idea on what could be wrong? What am I missing?
Edit:
Seems like the problem is TuesPechkin.Wkhtmltox that doesn't work on the new server for some unknown reason
Check the IIS log files and also the HTTP error logs in C:\Windows\System32\LogFiles\HTTPERR. And obviously the Application and System event logs.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 70%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYD%3C/text%3E%3C/svg%3E)
Hi @Adagio_B,
For us, it is impossible to reproduce the problem based on your description. The best way is to use the failed request trace, which will provide key errors and warnings to help you identify the problem.
This link provide the method to enable failed request tracing to capture the detailed error:
"The service itself is very simple. It just takes a string (html) and sends it to TuesPechkin.Wkhtmltox and returns the output." But that's not what people usually call "simple". A third party dependency like that might require extra configuration, which you need to refer to the original installation guide your team followed for the old server. If that's a piece of lost knowledge, you will have to search about that from scratch. Microsoft's forum like this does not cover third party library like that.
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
Seems like the problem is TuesPechkin.Wkhtmltox that doesn't work on the new server for some unknown reason
Did you review the error logs like I suggested?
In the IIS web site, do you have error pages set to return detailed errors?
What error do you get?