When I faced this problem, running the developer environment as an administrator, and selecting the correct nav service when compiling helped. If you select wrong nav service, then you will not be able to compile, you have to close the client and log back in. If you are using Development environment with SQL logins and with NavUserPassword authentication , you have to have same username and password in SQL and in NAV in order to make it work. - I will blog one day about this, it is worth a longer post. Development client and NAV service both have to have same authentication method. You cannot have Windows login in Development environment and NAVUserPassword in RTC at the same time. If you are using externally only NavUserPassword authentication, on developer's laptop, check file: C:\ProgramData\Microsoft\Microsoft Dynamics NAV\90\ClientUserSettings.config It has to have entries that reflect the NAV service in the Azure server in following elements: Server, ClientServicesPort, ServerInstance and ClientServicesCredentialType br, urpo
↧