Manufacturing, Distribution, and Internet Applications

[marklinder]

I'm setting up WA on our test server (finally) and I'm getting an error on the Data Collection Console that we can't figure out. 

Error has occurred.  Source 10.10.1.46:6710 listener communication.  Internal Error has occurred while connecting to a service.  Server ID: 10.10.1.46.  No connection could be made because the target machine actively refused it 10.10.1.46:6710

I know that support has been turned over to Scanco, but it seems that "support" does not cover any issues related to the initial setup of the product.  Can't say that I'm happy about that.  Our VAR (who is WA authorized with Scanco) called Scanco and again was told this was outside of normal support and Scanco wanted to bill them.

Anyone here have any experience with this?

Thanks!

Mark

[jnoll]

It appears as though the port 6710 might not be open on the server or some rights issue. You can have your Partner give us a call.

[marklinder]

Thanks.  The firewall service is turned off so there shouldn't be anything blocking any ports.  We thought maybe it was something in our anti-virus (ESET) so we disabled that as well.  We have tried other ports too.

It is totally frustrating because I'm certified on WA (from when I was a VAR), and our current VAR is certified...and Scanco has hinted that they know what the problem is but won't share any information unless we pay for their implementation assistance.

Hmmm, interesting.  As I was writing this I went back and configured it for port 80 and...no error.  So now we just need to figure out what is blocking that port on that server.  One step closer...  Gotta go hunt down my IT director and go through our network configs now.

[oyama]

Is the test server and the local machine on the same network?

[marklinder]

Actually same machine - trying to run the Console directly on the server.  But yes my local machine, the scanners and the test server are all on the same network (10.10.1.x).

[jnoll]

If you stop a firewall service from services.msc it does not stop it completely. You should go into the Control Panel - Firewall Settings and turn it off there.

[marklinder]

Joe - with the service turned off, you can't access it through Control Panel because the service is completely shut down.  But just to be sure, I restarted the service, made sure it was turned off in Control Panel (it was off) and turned the service back off.

Can get it to connect using port 80 or 443, but no other ports.  Totally disabled the anti-virus because it does have some port-blocking functions but that didn't change anything.

Anyone from Sage care to join in this conversation?

[marklinder]

Have the console up and running on port 80.  Have IIS shut off so there is no interference from any web services.  Configured the DCD to use port 80.  Can actively ping from server to DCD and from DCD to server.  Still have the DCD generating a "Message Code (3).  Cannot start in Batch Mode".  Everything in MAS is set to Live (all Batch flags turned off).  Went through every troubleshooting step in the manual with no success.  I guess it is time to bite the bullet and pay Scanco their $200/hour implementation assistance.

[jnoll]

Mark,

Give us a call or email before you pay any fees. Reach out to Bob Miller at rmiller@rklcpa.com or (717) 735-9109 x 1609.

[SHulme]

Mark,

The Sage MAS 500 Warehouse Automation (WA) and LabelXpert (LX) solutions have always been developed and maintained by Scanco, and prior to April 1 were marketed and sold by Sage under an OEM agreement (similar to common private label business practices). Given this, support for these modules has not changed materially since Scanco has always been ultimately responsible for development and technical support. The only difference is that Scanco now responds directly to these requests instead of Sage taking the initial call.

I can tell you that it is particularly critical that WA be installed and configured by a qualified partner or by Scanco themselves. Improper installation and setup are without question the number one cause of problems with this module given that it incorporates external hardware (e.g. handheld devices, listeners, access points, etc.) and requires specialized expertise that is not common to any other MAS 500 module. This was always a Sage requirement even before Scanco assumed direct responsibility for sales and support of this module.

If you want to be sure that WA is properly installed I would strongly recommend that you either have Scanco or a certified partner do this for you. From our experience, this will pay for itself in short order if only in time saved and aspirin avoided.