Monday, January 11, 2016

Dynamics NAV 2015 - LS Retail - "Either the caller does not have the required permission or the specified path is read only. No page, report or navigation has been specified in the URL"

Right click on POS button that launches the pos and edit properties, check the connection info


------------------------------------
We have a machine that connects to both the head office, and to a local instance of LS retail.
Whenever the user launches the remote instance, and then attempts to launch the local instance, they get this error.


I have tried this solution

http://saurav-nav.blogspot.com/2012/09/either-caller-does-not-have-required.html

But it only worked the first time.

The issue re-occurred, and the second time, we had to switch the account that the NAV service was running as from local, back to network service, then it worked fine...until the next restart.
Then the error came back.

This error occurs rarely on specific machines.

It can be temporarily resolved by changing the account on the NAV service, then changing it back to Network Service.

Ensure that the windows user and network service user has full access to the SQL database

Ensure the user and network service user has full access to the Program Files\Dynamics NAV folder and subfolders

  • Ensure Ls Retail folders and launcher are closed
  • Right click on folder>Security
  • Assign current user, and network service user (or whichever account is used for the nav service)
  • Edit>Full control>OK (not cancel or x)
  • Advanced>Tick replace all child object permissions>OK (not cancel or x)

If you navigate to
\\mypc\c$\ProgramData\Microsoft\Microsoft Dynamics NAV\80\Server\MicrosoftDynamicsNavServer$DynamicsNAV80\users\default\[Instance]
You should see a folder for each user that attempts to login to that instance, along with a temp folder within that user folder.

In this case, it seems as if our user was unable to create new folders in this location (even though he had the correct security priveleges)

I created the folder structure manually in this location, and this seems to have resolved the error.

No comments:

Post a Comment