Kine: Microsoft Dynamics NAV 2013 beta–installation and configuration tips

[Blog bot]

If you are installing Microsoft Dynamics NAV 2013 beta, you can struggle from some problems. There are some tips for you:


Ports
If you are installing the NAV server on computer, where are already some NAV services, you need to use different ports for the NAV 2013 services. NAV 2013 beta is not supporting Port Sharing. You need to think on it when configuring the installation.


Function not supported
When you successfully installed the NAV 2013 client with development environment on PC, where the NAV 2009 is already installed, you can have problems when you try to run something from the devenv. Instead starting the RTC client, you will see error that “Function not supported”. Weird on first sight could be, that you see the error e.g. in your local language, even you have installed the W1 version of NAV 2013. Problem is, that the devenv is using the protocol DYNAMICSNAV to run the RTC. On my PC the NAV 2013 installation have not changed the path for this protocol. You need to check the registry path “HKEY_CLASSES_ROOTDYNAMICSNAVShellOpenCommand” and look if there is NAV 2013 path or not.

You can deduct from this, that coexistence of NAV 2009 and NAV 2013 will be problem. Running page from NAV 2009 classic client will run NAV 2013 RTC after this, or NAV 2013 devenv will start NAV 2009 RTC if not changed. You can decide what will suit you most. But one info: to run the table from NAV 2013 devenv, NAV need to run the RTC, In general, NAV 2013 devenv is more linked to the RTC. I expect that most of you will want to run NAV 2013 RTC through the DYNAMICSNAV protocol. It is question of time till someone will develop some tool which will correctly decide what to run…


NavUserPassword authentication
Because the Domain groups are not working in the NAV 2013 beta, it could be a problem to add all the users into NAV. You can decide to use the new authentication model “NavUserPassword”, where you create login and password directly in NAV without connection to Active Directory, which you can then share with the users to provide the “demo” access. BUT! It is not so simple. You need to go through few steps:

1. Change the NST settings – you need to change the ClientServicesCredentialType to NavUserPassword instead the default Windows value.
2. Create certificate – to be able to login by user name and password, NAV need to crypt the transport. For this, he need certificate. You can create self-signed certificate by using commands mentioned in the .config file: makecert -n "CN=YourServiceNameOrURL" -r -sky exchange -sv YourFileName.pvk YourFileName.cer
   pvk2pfx -pvk YourFileName.pvk -spc YourFileName.cer -pfx YourFileName.pfx
   certutil -importpfx YourFileName.pfx
   
   
   Where to take the makecert and pvk2pfx tools? You can take them e.g. from Windows SDK.
3. Enter the certificate thumbprint into the config – first, you need to look at the Thumbprint on the generated certificat. Open it, find the field thumbprint, remove the spaces and the value enter into ClientServicesCertificateThumbprint key in the config of NST.
4. Change the RTC authentication type – in the file c:Users<loginname>AppDataRoamingMicrosoftMicrosoft Dynamics NAV70ClientUserSettings.config change the settings named ClientServicesCredentialType to same value as in step 1.
5. Make the client to trust the certificate – import the certificate to the client PC, to trust it. Or you can disable the check by changing value ClientServicesCertificateValidationEnabled in the config.
6. After all this, you can still have problem to run the NST service. In event log you can see error with error like “no access to the keys” or something similar. It means that the NST service have not enough permissions to read the certificate keys. Try to run it as admin. It should work. Quick fix is to add permissions for the service account on folder c:ProgramDataMicrosoftCryptoRSAMachineKeys.

Installation of NAV 2009 when compiling objects
After you install NAV 2013, you can have problems with compiling objects with older version of NAV like NAV 2009. When you start compile some object which use automation variable, it will start NAV 2009 installer and will try to repair the installation. It is because registry info about NAV help libraries like NTimer.dll, NSAppHandler.dll etc. were changed. You can repair it by unregistering and reregistering the dlls. I have created batch for this. You can use it (it is designed for 64bit systems). Just create file with this text, save it as .cmd file and run it as admin:

——————

regsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVOLHandlerOLHandler.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVApplication HandlerNSAppHandler.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommerce Gateway ClientCGReqClient.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommerce Gateway ClientCGTimer.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentNPipeBusAdapter.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentNSComCom2.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentSocketBusAdapter.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentMSMQBusAdapter.dll" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVTimerNTimer.dll" /u /s regsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVNatHashNATHash.dll" /u /sregsvr32 "c:WindowsSysWOW64comdlg32.ocx" /u /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVOLHandlerOLHandler.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVApplication HandlerNSAppHandler.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommerce Gateway ClientCGReqClient.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommerce Gateway ClientCGTimer.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentNPipeBusAdapter.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentNSComCom2.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentSocketBusAdapter.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVCommunication ComponentMSMQBusAdapter.dll" /sregsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVTimerNTimer.dll" /s regsvr32 "c:Program Files (x86)Common FilesMicrosoft Dynamics NAVNatHashNATHash.dll" /sregsvr32 "c:WindowsSysWOW64comdlg32.ocx" /S

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



.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

This will do it for you. I am not sure if it is just my local problem or it is because NAV 2013 was installed side-by-side with NAV 2009. If you hit this problem, it should help you…



Источник: http://blogs.msmvps.com/kine/2012/05...guration-tips/