ADCS TelNet failing

nbrewer

In an attempt to test my ADCS installation, I'm attempting to telnet to port 6666 without success.

Nas is running correctly as seen in the event viewer:

The Navision Application Server TSWKS070-CLASSIC#1 started with the following configuration:
Database Server Name = 127.0.0.1
Database =
Company = CRONUS USA, Inc.
Startup Parameter = ADCS,NAS1

Note the 'CLASSIC#1'. I found out v3.6 had already been installed on this computer, and I'm installing v4.0. I'm guessing the #1 is added if more than 1 NAS exists. I've went into 'Add/Remove Files' and removed all 3.6 installations. However, I still see the 3.6 NAS and database server listed in services, but I have set those services to manual.

I've also verified the following services are running:

Navision Database Server
Navision Communication System Service
Navision VT100 Plugin

When I attempt to TelNet to port 6666, nothing happens. The cursor just sits there and blinks. If I look at the event viewer, I see the error:

Could not send Message to NAS
CAN NOT FIND PIPE: Assure the pipe server is started, check share name

Any help will be much appreciated.
Thanks in advance,
Neil Brewer

nbrewer

To ensure that ADCS was firing codeunit 1, trigger 99, I inserted some code that writes a line to a temp table (record) I created. After starting NAS, I checked my temp table and that record did in fact exist. So, I know NAS is at least interacting with Navision.
Might this have something to do with message cues?
How can I tell the proper message cues have been created? Does ADCS use message queues?
What/Where is the pipe server?

Related registry entires:
[HKEY_LOCAL_MACHINE\SOFTWARE\Navision\ADCS\Application Servers\ADCSNAS1]
"RequestPipeName"="RequestPipe_CRONUS USA, Inc._NAS1"
"ReceivePipeName"="ReplyPipe_CRONUS USA, Inc._NAS1"
"RequestTimeOut"="5"

I have also tried:
[HKEY_LOCAL_MACHINE\SOFTWARE\Navision\ADCS\Application Servers\ADCSNAS1]
"RequestPipeName"="RequestPipe_NAS1"
"ReceivePipeName"="ReceivePipe_NAS1"
"RequestTimeOut"="5"

and

"ReceivePipeName"="ReplyPipe_NAS1"

One of my events shows:
Named Pipe: RequestPipe_NAS1

That's why I decided to try some alternatives.

Again, any help would be greatly appreciated.
Thanks,
Neil Brewer

nbrewer

For anyone in the future with this same problem, I solved it by setting every service to use the domain administrator for login.
To do so, right click on the 4 associated services and go to the 'Log On'.

I will start constricting permissions now.
NB

bbrown

What account were the services set to before you changed them to Domain Admin? I see from your last entry, that you are planning on restricting permissions. Can I assume that the use of Domain Admin is temporary?

Running services as Domain Admin can be a dangerous habit to get into. The accounts used for services should only have access to the resources required to run the service.

If all services are on the same machine, yuor first step might be to create a new domain user and make that user a member of the machine's lcoal admin group. You could restrict further from there.

mandyk

Related registry entires:
[HKEY_LOCAL_MACHINE\SOFTWARE\Navision\ADCS\Application Servers\ADCSNAS1]
"RequestPipeName"="RequestPipe_CRONUS USA, Inc._NAS1"
"ReceivePipeName"="ReplyPipe_CRONUS USA, Inc._NAS1"
"RequestTimeOut"="5"

Guys I believe your PipeName above are incorrect. You should change all period with underscore. So the correct one should be like this one:
"RequestPipe_CRONUS USA, Inc__NAS1".

change all of your PipeName, and please restart all of services afterward.

btw, Any idea if comma character also need to be replaced by underscore aswell?
:-k

Stardust77

Related registry entires:
Guys I believe your PipeName above are incorrect. You should change all period with underscore. So the correct one should be like this one:
"RequestPipe_CRONUS USA, Inc__NAS1".

change all of your PipeName, and please restart all of services afterward.

btw, Any idea if comma character also need to be replaced by underscore aswell?
:-k

Thank you mandyk, you are right. I have had the same problem as nbrewer had, and when replaced the period with underscores, the Hyperteminal finally connected.

I assume that the commas should be also replaced by underscores; at least in the manual they say: "Replace all special characters and blanks with underscores". But as any regular user, I did not pay attention to that

If any of you is more advanced with the ADCS, could he reccomend the most suitable device? Or, at least which one do you intend to use?

Thank you, and have a great weekend!

mandyk

I had done some information research on Symbol RFID device and Intermec RFID devices. If we use Navision standard ADCS product solution technology, which is using VT100, telnet, Navision plugin and Navision miniform. It is not really require a heavy hardware requirements.

Both product symbol & intermec will require a client telnet emulator and the OS device don't come out with it. Mostlikely they will offer you the wavelink emulator which own by third party company.

Symbol will offer you either Ms CE.net or Ms Pocket PC for the latest models they have. Meanwhile Intemec side, they have default OS Linux version and I heard can be installed with Ms. CE. or Pocket PC aswell.

If you want to go with windows base OS, it is seem Navision ADCS solution is under utilize the device, because the emulator is nothing but black and white screen color and no taste when you see it. 8-[

Stardust77

mandyk wrote:

If you want to go with windows base OS, it is seem Navision ADCS solution is under utilize the device, because the emulator is nothing but black and white screen color and no taste when you see it. 8-[

Thank you once again. O:) I agree with you that we underutilize the device, but we would like to avoid the additional costs implied by using a 3rd party solution. We have seen one, and it is costing about 60% of the customer's Navision license! Finally, the warehouse employee does need only the basic functions, which are - at least teoretically - fulfilled by the ADCS, and does not need any fancy (and rather expensive) solution.