running wpf console application on windows LTSB problem

[WJBons]

Hi,

we have an wpf application which runs fine on windows 7 and higher.
Part of it starts a separate console application which uses a servicehost with namepipebinding to setup a connection between two applications on the same pc. this has been working fine for years from windows 7 and higher

We are testing this under Windows 10 LTSB and found out that is does not work. The client which creates the channel gets the "there was no endpoint listening" message back.

is there anyone having info about limitations using the Windows LTSB version???
Can't find a lot of info about this.
Thanks

 

[ChatGPT]

The issue you are encountering with your WPF application and console application, utilizing servicehost with named pipe binding, on Windows 10 LTSB could be due to various factors. Windows 10 LTSB (Long-Term Servicing Branch) is a specialized version of Windows 10 meant for systems that require minimal update frequency and stability. Here are some steps you can take to troubleshoot and potentially resolve the problem: 1. Check Firewall Settings: - Ensure that the Windows Firewall is not blocking the communication between your applications. Add exceptions for both applications or disable the firewall temporarily to see if it resolves the issue. 2. Named Pipe Access: - Check the named pipe settings and permissions on Windows 10 LTSB. Ensure that the named pipe is accessible and has the appropriate permissions set. 3. Ensure Correct Path and Endpoint Naming: - Double-check the path and endpoint naming used in your applications to establish the connection via named pipes. Small differences in how paths are specified can lead to connection failures. 4. ServiceHost Configuration: - Review the configurations in your console application using ServiceHost to ensure that it is correctly configured to establish the named pipe connection. Verify that the address and binding configurations match between the client and the service. 5. Windows Event Viewer: - Check the Windows Event Viewer for any relevant errors or logs that could shed light on why the named pipe connection is failing on Windows 10 LTSB. 6. Compatibility Mode: - Try running the applications in compatibility mode on Windows 10 LTSB to see if there are any compatibility issues causing the problem. 7. Update Windows 10: - Ensure that Windows 10 LTSB is up to date with the latest updates and patches. Sometimes, new updates include fixes for compatibility issues. By following these steps and investigating the potential causes as outlined above, you may be able to identify the specific reason why the named pipe connection is failing on Windows 10 LTSB and take appropriate corrective actions to address the issue.