NAS 4.0 SQL Issue

DenSterDenSter Member Posts: 8,307
edited 2005-06-24 in NAV Tips & Tricks
After hours and hours of trying to figure it out..... ](*,)

When you install NAS for 4.0, it puts 2 services in there, one for CLASSIC and one for SQL. The installer puts the machine name in here and you can change this. Let's call them NAS-CLASSIC and NAS-SQL. There is nothing wrong with the CLASSIC one, you can modify all the settings there.

The problem is with the SQL NAS, because the nettype property does not show the available values. Unfortunately, the installer sets the default value to tcps (secure tcp, or kerberos). Unfortunate, because that simply does not work with Navision.

Here's what you do:
* Open a command prompt and browse to the application server installation folder (The default folder is "C:\Program Files\Microsoft Business Solutions-Navision\Application Server")
* type in "nassql appservername="NAS-SQL",uninstallasservice". This removes the service called NAS-SQL, which is useless anyway because of the wrong nettype setting.
* then, type in "nassql appservername="NAS-SQL",nettype=tcp,installasservice". This now creates a new service with the original name (so your NAS installation will still work), but with the correct nettype. Note that you can also do nettype=netb if that's necessary.

Now... when you open the NAS management console, you will still not see the nettype in the NAS-SQL one, but it should be set with the correct value. All other properties can be modified as needed.

Hope this helps. I'm sure happy that I got it to work now \:D/

Comments

  • kinekine Member Posts: 12,562
    It is corrected in 4.00 SP1 I think... :-)
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • vampireeyesvampireeyes Member Posts: 33
    isn't it possible to edit the service through services.msc ?
    ???????????????????????
    { Intuitively wrong... {
    ¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿¿
  • DenSterDenSter Member Posts: 8,307
    It's possible to edit the service, but this particular parameter is not available there.

    Thanks Kine, why didn't you tell me before I had all these problems? :whistle:
  • kinekine Member Posts: 12,562
    DenSter wrote:
    Thanks Kine, why didn't you tell me before I had all these problems? :whistle:

    It is simple... because I did not know about it... :-) after I saw some webcast last week, I saw that the demonstrator was changing the parameter directly through snap-in...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • ShenpenShenpen Member Posts: 386
    Do you already have SP1 in Czech? We don't ever have a firm promise here! I think I next time I go to Microsoft I will carry a chainsaw :):):)

    Do It Yourself is they key. Standard code might work - your code surely works.
  • kinekine Member Posts: 12,562
    No, there is no SP1 yet, may be 4/4 of the year... :-) we have many problems with the localization done by Russia developers... it is in conflict with our law... but I hope that C/SIDE will be usable with old STX file...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • gedasgedas Member Posts: 87
    Hi,
    Yes. It is corrected in SP1.
    SP1 will comes at september/october/november depends on country group.
    You can change nettype in installation line (as you've shown), but easer is to change it in windows registry. I don't remember right way to NAS registry, but you'll find if you want. There will be key nettype and you can change it.
    GB
  • darrencdarrenc Member Posts: 16
    The registry key is HKEY_LOCAL_MACHINE\SYSTEM\ContorlSet001\Services\NasServiceName

    I just changed all the settings directly in the registry and ignored the MCC snapin. I got tired of bouncing back and forth. I'm looking forward to that sp.
  • DenSterDenSter Member Posts: 8,307
    I found tcps in Controlset001, but it was tcp in ControlSet002, in Controlset003 and in CurrentControlset. This is why I don't like editing the registry, because it always seems that you're missing something. I'd rather just go through the command line uninstall and install, much safer in my opinion.
Sign In or Register to comment.