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(128, 78%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAH%3C/text%3E%3C/svg%3E)
A user of mine on Windows 11 is having trouble with a line of business application. We worked with the support for this software and they wanted HTTP error logs to troubleshoot the specific problem the user was having. I followed the instructions at https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/aspnet/site-behavior-performance/error-logging-http-apis but no logs are generated when we run the software. Does anyone know if HTTP error logging is not supported on Windows 11 or has any other ideas on why logs wouldn't be getting generated? We also ran into an issue when trying to stop and restart the HTTP service. net stop http would stop all dependent services but fail to stop HTTP and would leave the service stuck in an in-between state. Only rebooting got us going again so perhaps there's an issue with Windows itself? Thanks in advance!
Typically when someone references HTTP that involves IIS where the default log files are in C:\inetpub\logs\LogFiles. HTTP error logs are in C:\Windows\System32\LogFiles\HTTPERR.
Beyond that you will need to provide more details about what software you are using, how it was installed, what configuration settings were used, etc.
Thank you so much for your response, my apologies for not including further details. I did check the HTTPERR folder and also created a registry entry for log files to be placed there but nothing is created. The software is called MorningStar Direct and it's running into issues with a function where it's supposed to download data from over the internet to generate a report. It uses TCP port 49992, we also tried changing it to 49998 in case there was a port issue but that didn't help with the issue.
That looks like client side software. That is, you run a program on the pc and it connects over the internet to Morningstar servers to download financial data. The IIS and HTTP logs are going to be on the Morningstar servers, not the local pc.
I use Quicken to manage my finances. When I run its update process, it connects to my banks for transactions and Quicken.com to download stock prices. If it can't connect, I use the Help menu to view the OFX and connection log files to view the errors. I would expect the Morningstar program to have the same functionality.
If your user can't connect, then it could be the firewall settings on local pc. Or the user might have a VPN session established and internet access is blocked at that time.
See if you can find any application specific log file with the name of the site (web address) that it can't connect to.
You can use Powershell's Test-NetConnection (or Invoke-WebRequest) to see if you can connect. Also test that on other pc's to see the problem is isolated to just that one user's pc.
Thank you so much for the help. That's what I assumed reading the article on the HTTP logging but it was actually a developer at MorningStar who was insisting we needed this from the device, that doesn't bode well haha. Other users on the same network are working fine, tried disabling the SGN service on the device and testing but still ran into the error. We did generate logs through the software and I sent it to them but the developer didn't sound interested in them. Thank you for mentioning the Test-NetConnection command, it will absolutely be helpful. Thank you for all of your assistance!
If you can post the log that you found, I can take a look just for fun. Sanitize the data to remove any user id's and stuff like that.
I would suggest temporarily stopping the usual suspects, the window firewall and any antivirus software that you have installed.