Job Queue Setup error in NAV 2013 R2 with multi-tenancy

Original URL…

I finally got this all working. There were a couple of separate issues. Starting the queue manually was failing due to some of our own code in the job queue dispatcher. Once that was resolved I still couldn’t get a queue to start automatically though. I discovered through trial and error that in a multi-tenant environment the Services Default Company is not actually where you want to put the default company. Instead, you must specify a Default Company when you mount the tenant in addition to enabling NAS services for that tenant. You must do this even if there is only 1 company within that tenant. Also, the Windows account running the service must be a user within the tenant – even if you aren’t using Windows Authentication for that service.

Now that it’s all set up though it works well – I can have 1 NAS service instance with all of the tenants mounted to it each with their own job queue, entries, and recurrences.


NAV 2013 R2 – Multi-Tenancy Environment Web Client

Web client in  Multi-Tenancy Environment. More…

NAV 2013 R2 – Multiple Web Clients. More…

Sample: http://IP_HOST:8080/DynamicsNAV71/WebClient/List.aspx?company=EMPRESA&node=XXX...XXX&mode=View&page=9006&i=A3&ni=2&tenant=tenant1

Importing objects in a multi tenancy environment

The following posting is based on a support request where a partner wanted specific instructions what the process should be when trying to import a FOB file in a true multi tenant environment. If you simply import the FOB file. More…

Note: NAV Multitenant sync.

Waldo Blog: NAV 2013 R2 Multi Tenancy: Force Full Sync on All Tenants.

Export and Import Dynamics NAV objects in NAV 2013 and 2013 R2 with the new NAV 2015 PowerShell Commandlets