ADCS - Blank Screen on HyperTerminal

zero

Hi everybody!

I'm trying to use the ADCS (I already tried to do all the steps from the topics: http://www.mibuso.com/forum/viewtopic.php?t=5710 and http://www.mibuso.com/forum/viewtopic.php?t=8214) but it doesn't work yet.

:arrow: Errors:
- The HyperTerminal connects but no menu is shown, just a blank screen.
- When the NAS service starts, it displays the following warning message on Event Viewer: The description for Event ID ( 109 ) in Source ( ZERO ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The program failed to publish Navision Database Server Service Connection Point in Active Directory. In order for Navision Database Server to publish a Service Connection Point, the Active Directory Schema on the network domain controller must be extended.
- When I connect the HyperTerminal, the following error message is shown on Event Viewer: Could not send Message to NAS. CAN NOT FIND PIPE: Assure the pipe server is started, check share name.

:arrow: System:
- Navision NA 4.00
- Windows XP Professional SP2

:arrow: My Steps:
1. Client Instalation
2. Database Server Instalation
3. NAS Instalation
4. ADCS Instalation
5. Connection with HyperTerminal

:arrow: Setup:

1. Client Instalation
- PATH: C:\Program Files\Microsoft Business Solutions-Navision\Client
- DATABASE: Demo USA/CANADA
- LICENSE: Demo
- COMPANY NAME: CRONUS (yes, just 'CRONUS').
- WMS EMPLOYEE LOGIN: ADCS
- LOGIN ROLES: SUPER; ALL

2. Database Server Instalation
- SERVERNAME: ZERO
- PROTOCOL: TCP (not Kerberos)
- LICENSE: Demo
- DATABASE: C:\Program Files\Microsoft Business Solutions-Navision\Client\database.fdb

3. NAS Instalation
- APPLICATION SERVER: ZERO-CLASSIC
- DATABASE SERVER NAME: localhost
- DATABASE: blank
- COMPANY NAME: CRONUS
- START-UP PARAMETER: ADCS ADCSID=NAS1
- NET TYPE: TCP/IP
- RECEIVE PIPE NAME: ReplyPipe_CRONUS_NAS1
- REQUEST PIPE NAME: RequestPipe_CRONUS_NAS1
- REQUEST TIME OUT: 5

4. ADCS Instalation
- CSS SERVER IP: 127.0.0.1
- CSS TCP PORT: 6000
- PLUGIN SERVER IP: 127.0.0.1
- PLUGIN TCP PORT: 5900
- SCREEN LINES: 6
- SCREEN WIDTH: 30
- STYLE PATH: C:\Program Files\Microsoft Business Solutions-Navision\Automated Data Capture System\VT100_W2k_and_OtherClients.xsl
- TCP PORT: 6666

5. Connection with HyperTerminal
- HOST ADDRESS: localhost
- PORT NUMBER: 6666
- CONNECT USING: TCP/IP (Winsock)

:arrow: Workarounds:
1. I've changed the company's name just to CRONUS believing that this was my problem, but it didn't work.
2. I've tried to run all the 4 services with the Local System account, but it didn't work. :x
3. I've tried it all on a computer out of a domain, running the services with the Administrator's account, but it didn't work. :evil:
4. I've tried again in my domain, with the Domain's Administrator account, but it didn't work. ](*,)

Please, help me!

nunomaia

if you are using NAV 4.0 SP2, see http://www.mibuso.com/forum/viewtopic.php?t=11402

zero

nunomaia wrote:

if you are using NAV 4.0 SP2, see http://www.mibuso.com/forum/viewtopic.php?t=11402

Thanks Nuno, but is a version without SPs.

nunomaia

NAvision publishes the database info in the AD. You have permissions to change AD Schema ?

Poltergeist

Some pointers:

The NAS needs to be installed with a local or domain account (preferably domain, so the database can be moved to another server). This user has to be added to the Navision Database's Windows logon. So you need to change the account the NAS service uses from localacount to domain\user (and this user has to have sufficient rights to run a service). Check if the NAS is connected to the server by looking in file->database->info. The NAS user should always be in the sessionlist.

Don't know if you're trying to connect from the same server (so the hyperterminal client is on the same machine as the ADCS/NAS/Navision server) but if it's not, you need to change the registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Navision\ADCS\VT100Plugin\Symbol1, CSS ServerIP. As a matter of fact, you do need to change it in a productionenvironment anyway). It now says 127.0.0.1, which results in only local clients to be able to connect. If the server has for example the address 192.168.1.10, use this address in the registryentry.

You might also try to use the IPaddress in the connection settings in HyperTerminal (instead of 'localhost')

If you're looking into the registry, just check if the key HKEY_LOCAL_MACHINE\SOFTWARE\Navision\ADCS\Application Servers\ADCSNAS1, ReceivePipeName and RequestPipeName hold the values ReplyPipe_<Companyname>_NAS1 and RequestPipe_<Companyname>_NAS1, The Company should be exactly the same as in the database, with spaces and other "special" characters replaced by an Underscore. Also capitals et cetera should be exactly the same. With the name you choose, it should read ReplyPipe_CRONUS_NAS1, which it probably does, but it does not hurt to check again. Beware of spaces after the companyname: you do not see them, but they sure could be there (speaking from own experience, it once took me 30 minutes to figure out there where two spaces after a companyname instead of one...)

BTW: A lot of settings can be done in the registry. Just restart the services everytime you change something.

pedrocalvin

- RECEIVE PIPE NAME: ReplyPipe_CRONUS_NAS1
- REQUEST PIPE NAME: RequestPipe_CRONUS_NAS1

the error message seems to mean that this Pipe is not well configured... i suggest you to try ReplyPipe_NAS1 and RequestPipe_NAS1 instead.

zero

Poltergeist wrote:

This user has to be added to the Navision Database's Windows logon. So you need to change the account the NAS service uses from localacount to domain\user (and this user has to have sufficient rights to run a service). Check if the NAS is connected to the server by looking in file->database->info. The NAS user should always be in the sessionlist.

IT WORKED!!!
I forgot to add the user that I was running the service in the Navision Windows Logon list.
Thaaaaank you!