Trying to install NAS...

ZiqXx

Hi,

I have installed the Navision Client, and now I am trying to install the NAS and I got two services in my service list:
NAS-CLASSIC and NAS-SQL

But neiter service will start, I get an error msg: Error 1 - Incorrect Function

Does someone here know what I did wrong ?

kine

you must set parameters for the service... see documentation...

ZiqXx

I tried it using these parameters:

nas appservername=nas1, servername=MACHINENAME, company="Cronus International Ltd.", startupparameter=p

But I get this error when I try to:
Date: 11.02.05
- 11:19:49:
11:19:49: Navision Application Server version 4.0 (Build 19365)
11:19:49: Copyright (c) 1987-2004 Microsoft Corporation
11:19:49:
- 11:19:49: The TCP/IP connection's 'host' is not answering (TCP/IP error ECONNR
EFUSED).
11:19:49:
11:19:49: You can see how to make changes to your 'hosts' and 'services' files
in the documentation for the network. Contact your system manager if you need a
ssistance.
- 11:19:49: The Navision Application Server nas1 could not initialize properly.
11:19:49: The server will attempt to initialize every 30 seconds until this is
successful.
11:19:49:
- 11:19:52: The Navision Application Server will shut down when the processing o
f the current request has finished.
11:19:52:
- 11:19:52: The Navision Application Server nas1 was shut down.
11:19:52:

The Machinename is the name of the computer that holds both the Navision Database server and the NAS service.

Do you know what I am doing wrong ? :-k

kine

Navision DB server is running on default port? Any manual changes into services file?

ZiqXx

yes default port and I dont think I have done any changes at all, this is a fresh install of the whole package...

kine

TCP/IP error ECONNREFUSED

Have you some firewall (Win XP + SP2)? You must open the standard port.

ZiqXx

I am running this on a Windows Server 2003, and the Firewall was turned off.

#-o

kine

Try to use IP 127.0.0.1 instead of machine name...

ZiqXx

Tried both using 127.0.0.1 and localhost, neither worked...

What services file were you talking about earlier? Where can I find that ?

kine

if you have win xp than c:\windows\system32\drivers\etc\services

Still same error? Or another when loopback (localhost) used...

ZiqXx

No I havn't touched that file at all.

Yes I get the same error for all three versions, 127.0.0.1, localhost, MachineName....

ZiqXx

Could I be missing some pre-req or something ??

henrikohm

Hi

Maybe redundant to say, but

nas1 = NAS-CLASSIC....

Try using the Navision Attain Application Server Manager

Best regards
Henrik Ohm

ZiqXx wrote:

I tried it using these parameters:

nas appservername=nas1, servername=MACHINENAME, company="Cronus International Ltd.", startupparameter=p

But I get this error when I try to:
Date: 11.02.05
- 11:19:49:
11:19:49: Navision Application Server version 4.0 (Build 19365)
11:19:49: Copyright (c) 1987-2004 Microsoft Corporation
11:19:49:
- 11:19:49: The TCP/IP connection's 'host' is not answering (TCP/IP error ECONNR
EFUSED).
11:19:49:
11:19:49: You can see how to make changes to your 'hosts' and 'services' files
in the documentation for the network. Contact your system manager if you need a
ssistance.
- 11:19:49: The Navision Application Server nas1 could not initialize properly.
11:19:49: The server will attempt to initialize every 30 seconds until this is
successful.
11:19:49:
- 11:19:52: The Navision Application Server will shut down when the processing o
f the current request has finished.
11:19:52:
- 11:19:52: The Navision Application Server nas1 was shut down.
11:19:52:

The Machinename is the name of the computer that holds both the Navision Database server and the NAS service.

Do you know what I am doing wrong ? :-k

naushie

hi there
can you try this on e

>nas appservername="nas1", servername="MACHINENAME", company="Cronus International Ltd.", startupparameter=p

Please make sure that for running NAS you are having Windows Administrator rights.
you can set it from properties of nas in services on Log-On tab.

Try this pal may be it will work.

ZiqXx

I think I was able to start the NAS from the Snap-in Console thingy... At least the status is Started, but ...

My Event Viewer had this message for me:

The description for Event ID ( 109 ) in Source ( NBX-NAVISION-CLASSIC ) 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 network is not functioning correctly. A 'packet' has been corrupted (a checksum error).

This error indicates that the network is not completely reliable. Please note how often this type of error occurs in the network. Contact your system manager if yo.

---------------------------------------------------------------------------------

The description for Event ID ( 109 ) in Source ( NBX-NAVISION-CLASSIC ) 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 Navision Application Server NBX-NAVISION-CLASSIC could not initialize properly.
The server will attempt to initialize every 30 seconds until this is successful.

Correct me if I am wrong, but the "startupparameter" does that not specify what codeunit inside codeunit 1 you want to trigger to run ?

I put the "Machine name" in the line where it said: Database Server name
I put nothing in the line where it said: Database
I put "CRONUS International Ltd." where it said Company
I put "testcode"(the name of my codeunit) in the line where it said start-up parameter

lphan

Hi

The startup parameter testcode must be in the codeunit 1 - function ID 99, and you can add a call to your codeunit under that parameter.
And make sure that you check in your setup:
- Go to that NAS service in the services and you must set it up to use window log in, i.e. tich the log os as This Account, select user id from window log in
- In the Local Security Settings, make sure you add that user into:
1) act as part of the operating system
2) log on as a batch job
3) log on as a service
- And in Navision, set SUPER permission for that window log in

And then you go

pedroccda

Control in windows resistry if the navision server service is started with TCP or TCPS! 8)

naso

Has anyone solved this issue?](*,)


Regards

jorgecph

If this a Native database (non-SQL), most likely the problem is that the network type does not match the server's. If server is set up using TCPS try changing it to TCP (as well as the NAS), and see if this helps.

If using TCPS does not work, but using TCP works (again, both on the Server and the NAS) then there is some problem in getting the credentials.

Saalek

Hi
The windows user that have start permission in the NAS service, is it added in Navision ??

The startup parameter must be the same that you put in the codeunit 1 in function NASHANDLER

bye :-k

pedroccda

jorgecph wrote:

If this a Native database (non-SQL), most likely the problem is that the network type does not match the server's. If server is set up using TCPS try changing it to TCP (as well as the NAS), and see if this helps.

If using TCPS does not work, but using TCP works (again, both on the Server and the NAS) then there is some problem in getting the credentials.

You are right! This is what I have said... to start Navision server service with TCP and not TCPS you must change startup parameter from windows registry. In some case during installation Navision service is started with TCPS... and also using TCPS from client it doesn't work.

SOLUTION:
- change startup parameter of Navision server service from windows registry
- connect to server using TCP

Trevor_Norcross

I am not clear on what goes in the Startup Parameter field in the NAS Management Snap-in... Is it always NAS1? I am trying to determine if a problem I am having is related to this field at all... I am using Attain 3.6 and NAS off the Attain 3.6 CD.

Peter_Wijntjes

with Startupparameter you specify the intended action you want this particular NAS to perform.

this parameter i.e. will on startup be sent to the function

NASHandler(NASID : Text[260])
in CodeUnit 1

so in case you supply startupparameter=p the function NASHandler will run with a value of NASID=p

You will have to customize this function in order to let Navision perform whatever action you want to associate with this p (i.e. run a codeunit).

Be aware that the function NASHandler is only called during startup of NAS. So you will have to write code that uses a loop or timer that will keep running until the nas is stopped. Otherwise it will stop immediately.

DenSter

The start up parameter does not specify the name of the codeunit you want to run. There is a function called NASHandler. In it, you'll find a CASE statement that you will have to add your parameter to. Something like this:

// preceding code snipped
  IF CGNASStartedinLoop = FALSE THEN
    CASE Parameter OF
      'MAILLOG':
        CODEUNIT.RUN(CODEUNIT::"E-Mail Dispatcher");
      'SMARTTAG':
        STPublisher.StartTimer;
      //*** New parameter
      'testcode':
        BEGIN
          CODEUNIT.RUN(CODEUNIT::"the name of your codeunit");
        END;
      //*** end of new parameter
      ELSE

What you enter as the startup parameter in the snap-in will be sent into the NASHandler function when the service starts. You will have to program which codeunit runs.

Stephan

Hi,

you can also try to install the NAS as a nt-service again. After that you can create a link in the NAS management console and enter the parameters.
Make sure in the nt-service properties a login with enough permissions is used.

nas.exe appservername=myNASServiceName, (un)installasservice

Stephan

Dave_Cintron

I have gone through the Smart Tag installation instructions and checked everything 15 times. The Smart Tags do not show up in the Word Auto-Correct setup. The NAS is running with startup parameter SMARTTAG. The only message I get in Event Viewer is that the Application Server was started with a message 109.

I continue to check the NAS, tell Navision to publish the Profile and Datasets, then look in Word. No Navision SmartTags show up. I looked at the protocol in the registry. I don't get it ???

DenSter

<post removed, I was replying to a message on the first page that was already answered :oops: >

Zors

The bug is the MMC doesn't fill the NETTYPE combobox, in the registry this results in tcps shock: . So all you have to do is go to:
1. Create a new application server
2. Fill in the field correctly
3. See to it that you change the nettype in the registry
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\COMPUTERNAME-SQL


4. add some dummy code to the correct nashandler. To see if its really working.


Have fun! :

DenSter

TCPS is the default nettype of all Navision programs, don't ask me why. For NAS-CLASSIC you can change the nettype in the mgt snapin, but for NAS-SQL you will have to do an uninstallasservice and then an installasservice while specifying the nettype. See the installation manual for more details. I am not a fan of manually changing the registry, although it's not rocket science.

Dave_Cintron

Thanks guys, but I have already confirmed the CLASSIC NAS is using TCP and not TCPS. As far as I know I don't need the SQL NAS for SMARTTAGS on a Navision database.

Dave