ADCS - "Fault in Communication"

(0) Share

Report

Posted on by Community Member

Hello,

In our environment we are using Dynamics NAV 2015 and ADCS for our portable scanning equipment. We are having a problem where errors in NAV are displaying on the scanner, but are starting with the message "Fault in Communication". Since our scanners only have a small fixed screen size, this means the message is "cut off" and our users can't tell what the error really says.

I've exported all the relevant objects (and ADCS objects) as a text file so I could search for that string but my search didn't turn up anything. Stepping through the session with a debugger also indicated NAV is not generating "Fault in Communication" as part of the error. I even tried inspecting the ADCS executable with a hex editor and found what looks like the fault message embedded in the exe file.

Is there any way to disable or shorten this message so our users' errors do not get "cut off" at the edge of their screens? We did not have this issue until we upgraded from 2009 to 2015. I have already looked through all the ADCS documentation I could find but didn't see anything relevant to this problem.

Thank You!

*This post is locked for comments

I have the same question (0)

All responses (14)

Answers (0)

keoma 32,729 on at

Like (0)

Report

Cjheck ADCS Plugin Type in Whse Mgt. Setup, if it's set for the wrong communication method.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I am able to connect to the scanners and work with them on a regular basis. This problem only happens under certain cirumstances (for example if the inventory in a bin is unexpectedly negative). I did try your suggestion though and restarted the service tier and VT100 plugin but that did not fix the issue unfortunately.

Was this reply helpful? Yes No
Alexander Ermakov 28,096 on at

Like (0)

Report

What exactly ADCS model do you use?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

We are using the standard microsoft vt100 plugin / automatic data capture system that is included on the install media for dynamics NAV 2015.

The configuration file for the plugin contains the following line as well,

<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>

Does that answer your question?

Was this reply helpful? Yes No
Alexander Ermakov 28,096 on at

Like (0)

Report

I'm actually more interested in hardware (the one that has small screen :-) )

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

We are using Barcom CK-71 scanners. Link below.

www.barcominc.com/.../ck71aa4mc00w1400

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

So, this device uses Windows Embedded Handheld operating system? If you are connecting using a remote desktop, try playing with the desktop resolution to have possibility to scroll the screen on the handheld device. E.g., activate "Fullscreen" in the settings, but do not activate "Fit remote desktop setting", you should get the possibility to scroll the screen and perchance you will have an option to see what is the error fully...

Was this reply helpful? Yes No
keoma 32,729 on at

Like (0)

Report

best you run the handheld app in a windows ce emulator. then you will get easier the full error message. also you can debug.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks, but we're not using remote desktop. A telnet client on the scanner connects to our VT100 plugin. The same error is shown through a telnet client on a normal computer though as the error is generated by the ADCS plugin itself.

If we try to add more screen space by enabling scroll bars then we lose efficiency because right now all input is done through scanning. If we increase the resolution to show a bigger window then the text becomes too small to be legible. This is why we've been trying to remove the "fault in communication" messages.

Was this reply helpful? Yes No
Alexander Ermakov 28,096 on at

Like (0)

Report

But, as I understood, you need to learn what is actually the message as it has been cut on the screen - that is why I offered (temporarily!) to enable more space on the screen to be able at least to catch full error text. Then, when you get it, you can further troubleshoot the exact error...

Was this reply helpful? Yes No