Let’s clean up NAV – Telex

Back in the old days Telex was the most advanced form of electronic communication. But since the 80’ties and 90’ties this has been taken over by Fax and Email.

NAV still have fields for Telex No.  on Customer, Vendors and Contacts, perhaps its time to send this technology to rest.

The fields are not on the UI, but still in the database.

telex

telex2

And the same time, either modernize the current communication setup, so it could be possible to have a cell phone fields or perhaps other fields for newer forms of communication.

 

 

This months CU’s are out..

Grab ’em while they’re hot 🙂

2016 CU5 – https://blogs.msdn.microsoft.com/nav/2016/03/07/cumulative-update-5-for-microsoft-dynamics-nav-2016-has-been-released/

2015 CU17 – https://blogs.msdn.microsoft.com/nav/2016/03/07/cumulative-update-17-for-microsoft-dynamics-nav-2015-has-been-released/

2013R2 CU29 – https://blogs.msdn.microsoft.com/nav/2016/03/07/cumulative-update-29-for-microsoft-dynamics-nav-2013-r2-has-been-released/

2013 CU36 – https://blogs.msdn.microsoft.com/nav/2016/03/07/cumulative-update-36-for-microsoft-dynamics-nav-2013-has-been-released/

And a very nice surprise, hotfixes are no longer distributed as a ZIP inside a EXE, just a regular self extracting EXE – Nice !
Not true, sometimes I get fooled by my own cleverness 🙂 (But it would be nice)

Dynamics NAV Server cannot start after enabling soap or odata

Sometimes when you turn on SOAP or OData services, the service tier starts and stops again, and give you this error:

The service MicrosoftDynamicsNavServer$DynamicsNAV90 failed to start. This could be caused by a configuration error. Detailed error information: System.ServiceModel.AddressAccessDeniedException: HTTP could not register URL http://+:9047/DynamicsNAV90/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details). ---> System.Net.HttpListenerException: Access is denied

This is WCF failing to reserve the URL inside http.sys .

The solution is quite easy, just perform the registration yourself, open a command line and execute the following command:

netsh http add urlacl url=http://+:9047/DynamicsNAV90/ user="NT AUTHORITY\NETWORK SERVICE"

Make sure to specify the correct port number, instance name and the user name of the user running the service tier (In my case here, “NETWORK SERVICE”).