Desktop Communicator Startup Issues

[sbramblett]

I have a problem with getting the Desktop Communicator to run on one specific PC. The system is Wave 4.5 and I have communicators running on the same subnet on other PCs. I can surf to the management server on the offending PC and can run the dispatch communicator on it. The error occurs after entering the login data and pushing the "OK" button. After a few seconds I get a dialog titled "WAVEDesktop" that says -

Failed to parse XML
Switch from current encoding to specified encoding not supported.

After I hit the "OK" button on the dialog I get a second dialog titled "WAVE Desktop Communicator" that says -

No profiles were found. You will not be allowed to proceed at this time.

Please contact your WAVE system administrator.

For the record, the Dispatch Communicator does run on the offending PC. I tested the login on a known good PC with no problems. Since I am the administrator and I don't have an idea what is going on I would like to see if anyone on the forum knows what is up.

[kcarpenter]

I have seen this happen when another program overwrites MX XML v3 that we install with Desktop Communicator. I've found that manually re-installing these DLLs usually solves the issue.

[steps to replace DLLs]

Go grab a copy of System32 that's found in your WAVE setup package.
Copy & paste the DLLs in this package into Windows\System32 (all of them, including MSXML*.DLL).
When prompted you cannot overwrite a file because it's in use, locate that file and rename it with a _ at the beginning of the filename. For example, 'dbghelp.dll' becomes '_dbghelp.dll'.
Re-paste, repeat steps 3 & 4 until all files copy successfully.
Start Desktop Communicator.


If this doesn't solve your issue we will need more information about your current setup.


What version of WAVE?
What OS? This includes service packs etc.
Are there any domain security policies?
Has the machine been STIG'd?


I can also send you instructions on putting Desktop Communicator into debug mode and capturing that data.

Thank you,
Kenneth

[sbramblett]

I tried the replacement of the DLLs to no avail. We are running Wave 4.5.0.204 (GA). The offending PC is running Windows XP Pro Service Pack 3. It is not on a domain...it is on the workgroup "WORKGROUP" and that alone should tell you that no one has attempted to STIG it. It is running Symantec antivirus and does have MS SQL Express on it (currently stopped). Since we are going to install on STIGed machines I would like to figure out what is going on before I head to Iraq....I might see it again there and communications are a little more tedious there.

[kcarpenter]

Grab a copy of Dependency Walker from http://www.dependencywalker.com/. Open the various Windows\System32\MSXML*.DLL files in this program.

Basically we're looking for any DLLs that may be unavailable to MSXML*.DLL when it tries to load. Feel free to email screenshots etc to support@twistpair.com

Thank you,
Kenneth

[Trathe]

Can you not hook the printer directly to the desktop computer and avoid the memory card altogether?