Error at client connect

[tman1]

If the option for retrieving devices at client connection is enabled the client will not connect. The "Connected Retrieving Info" wait section is shown but just stays there.

This appears in the log when the connection is attempted and all devices and events are ask to be returned.

5/22/2005 9:48:14 AM~!~Message Server log~!~Client PC Name: 'duesduesplus' user name: wants all devices: 'True' wants all events: 'True' By: 192.168.0.101
5/22/2005 9:48:14 AM~!~Message Server log~!~Connection Request from pc: duesduesplus By: 192.168.0.101
5/22/2005 9:48:19 AM~!~Message Server log~!~Transfer took : (00:00:01) for 185624 characters By: 192.168.0.101
5/22/2005 9:49:00 AM~!~Message Server log~!~Connection Close By: 192.168.0.101

This appears in the log when only events are asked to be returned. i.e. the device box is cleared on connect options.

5/22/2005 9:49:02 AM~!~Message Server log~!~Client PC Name: 'duesduesplus' user name: wants all devices: 'False' wants all events: 'False' By: 192.168.0.101
5/22/2005 9:49:02 AM~!~Message Server log~!~Connection Request from pc: duesduesplus By: 192.168.0.101
5/22/2005 9:49:02 AM~!~Message Server log~!~Transfer took : (00:00:00) for 3740 characters By: 192.168.0.101

Any ideas? Oh yeah this happend to clients on two differant machines so it seems server side related?

Thanks in advance, Terry

[cyvinec]

Terry,

This is probably caused by a device just added recently that have an illegal xml character (&<>) in the name.
You should have files in your client folder called msc_xml_error_##.xml if you can send me some I will look at it.
Or you can get one location at the time until you not getting any devices in that location and then track the device that cause problem.

Regards,
Christian

[tman1]

Great!!

I'll sort this out, thanks as always for the immediate response Christian.

Later, Terry