<![CDATA[Monitor Windows Service with Special characters -> DCI not working after restart]]>

<![CDATA[Monitor Windows Service with Special characters -> DCI not working after restart]]>Unfortunately some Windows Services from German vendors has special characters in their service name

I know this is pretty ugly, but I can't force the vendors to change their naming conventions...
In the example above it uses the special character "Ü" in the service name.

The DCI is working until NetXMS has restarted, after restart NetXMS Core it changes the DCI to unsupported.
The output in the parameter of the DCI shows like that:
System.ServiceState("Service Vendor ÃƒÆ’Ã†â€Ãƒâ€ Ã¢â‚¬â„¢ÃƒÆ’Ã¢â‚¬Â ÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢ÃƒÆ’Ã†â€ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â ÃƒÆ’Ã‚Â¢ÃƒÂ¢Ã¢â‚¬Å¡Ã‚Â¬ÃƒÂ¢Ã¢â‚¬Å¾Ã‚Â¢ÃƒÆ’Ã†â€Ãƒâ€ Ã¢â‚¬â„¢ÃƒÆ’Ã‚Â¢ÃƒÂ¢Ã¢â‚¬Å¡Ã‚Â¬Ãƒâ€šÃ‚Â ÃƒÆ’Ã†â€Ãƒâ€šÃ‚Â¢ÃƒÆ’Ã‚Â¢ÃƒÂ¢Ã¢â€šÂ¬Ã…Â¡Ãƒâ€šÃ‚Â¬ÃƒÆ

Any suggestions?

Thank you

Joël

]]>https://forum.netxms.org/topic/1128/monitor-windows-service-with-special-characters-dci-not-working-after-restartRSS for NodeFri, 13 Nov 2026 12:19:09 GMTTue, 01 Feb 2011 09:50:51 GMT60<![CDATA[Reply to Monitor Windows Service with Special characters -> DCI not working after restart on Tue, 01 Feb 2011 10:18:46 GMT]]>Hi!

That's very strange, because German characters should be supported even by latin1 (ISO 8859-1) encoding. On what platform you are running NetXMS server and what database you are using?

Best regards,
Victor

]]>https://forum.netxms.org/post/5094https://forum.netxms.org/post/5094Tue, 01 Feb 2011 10:18:46 GMT