Error when i try to open NAV 2013 ( Three Server Installatio

hafedh

Hi everyone,

I have installed NAV 2013 R2 in three Server:

1- SQL Server, NAV SQL

2- NAV Server, Application Server of NAV

3- Client: Client application fo NAV 2013 R2.



==> I would like to use NAV 2013 R2 with and without multi tenant, but in both case i have errors;

A- Without multi-tenant, i have this error:

The microsoft dynamic NAV server is currently not ready to serve request. try again later or contact your system administrator

B- With multi tenant, but i have this error

A microsoft dynamic NAV application has not been mounted. contact your system administrator.

Thanks for your response.

Best regards.

Guiga Hafedh

hafedh

Hi everyone,
Can i have any response please ?
Best regards.
GH

defiant701

Hi,

so in R2 all instances are multi-tenancy, even when business logic & data is still in one database.

Anyway your error looks like a mismatch somewhere in your settings. So is it possible to post the settings from the instance configuration (General Tab) as well as your ClientUserSettings.config?

Especially the <add key="TenantId" value="YOURTENANTID" />
and the access URL looks like that for MT: IPorFQDN:PORT/INSTANCE/TENANT

Kr defiant701

hafedh

Hi Defiant
Thanks for your response,
This is a general tab config for server and the file config for client in attached file.
Best reagrds.
GH

********
*******
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<appSettings>
<!--
Name of the machine hosting the Microsoft Dynamics Nav Server to
be connected to.
-->
<add key="Server" value="navserver"/>

<!--
The listening TCP port for the Microsoft Dynamics NAV Server.
This is part of the server's URL.
Valid range: 1-65535
-->
<add key="ClientServicesPort" value="7041"/>

<!--
Name of the Microsoft Dynamics NAV Server instance to connect
to (for client).
-->
<add key="ServerInstance" value="DynamicsNAV71"/>

<!--
Id of the tenant to connect to (for client).
-->
<add key="TenantId" value=""/>

<!--
The security services used to protect the client/server data stream.
Valid options: EncryptAndSign, Sign, None
-->
<add key="ClientServicesProtectionLevel" value="EncryptAndSign"/>

<!--
Collection of past servers that have been connected to. This setting
should not be edited by the user.
-->
<add key="UrlHistory" value=""/>

<!--
Threshold for when to start compressing data sets to avoid that they
consume prohibitive amounts of memory.
-->
<add key="ClientServicesCompressionThreshold" value="64"/>

<!--
Sets the default size of a chunk, in KB. Should be a value between 4 and 80.
-->
<add key="ClientServicesChunkSize" value="28"/>

<!--
Sets the interval between reliable session keep alive messages in seconds.
If the NAV Server sits behind a load balancer, set this value to approx. half of the load balancer's idle timeout.
-->
<add key="ClientServicesKeepAliveInterval" value="120"/>

<!--
The amount rows that will be handled when sending a number of records through xml to Word or Excel.
-->
<add key="MaxNoOfXMLRecordsToSend" value="5000"/>

<!--
Maximum image size (in bytes) allowed by validation.
-->
<add key="MaxImageSize" value="26214400"/>

<!--
The type of client credential used for authentication.
Possible values:
Windows - Windows authentication is used, and client will connect with "current user"
this user is expected to be the same and known to both server and client
This is the default mode and is typically used on a LAN with Active Directory
In this mode X.509 certificates are not used and options set below are ignored
Username - Windows authentication on the server. Client is expected to present username/password
indentifying a windows user known (created) on the server.
Typically the client will ask for these credentials and pass them to the server
Certificates are used to protect the passing of credentials.
This is typically used when only the server is part of an Active Directory, or
when the client is not trusted, e.g. connection over a WAN/Internet
NavUserPassword - Authentication is managed by the server but not based on windows users.
Client is expected to present username/password matching a user known to the server.
Typically the client will ask for these credentials and pass them to the server
Certificates are used to protect the passing of credentials.
This mode is used in hosted environments e.g. Azure where the list of allowed users
are maintained by NAV and not based on windows users.

-->
<add key="ClientServicesCredentialType" value="Windows"/>


<!-- Setting for the ACS and AAD authentication (WS Federation authentication) -->

<!--
When using it to setup ACS authentication:
ACSUri is a top level partition of Windows Azure Access Control Service that is used to create the ACS tokens
Ex. https://CRONUSInternationalLtd.accessco ... calhost%2f
When using it to setup AAD authentication:
ACSUri points to the AAD authentication page specific to the AAD tenant that the users are going to authenticate against
Ex. https://login.windows.net/<Tenant_Id>/wsfed?wa=wsignin1.0%26wtrealm=https%3a%2f%2flocalhost%2f
"<Tenant_Id>" CAN be replaced with "common" when the application has External access to the AAD world (and multiple AAD tenant support is needed)
Remarks:
- Notice the difference between ACS "wsfederation" and AAD "wsfed" resource
- The query string parameter needs to be URI-encoded (use "%26" instead of "&").
-->
<add key="ACSUri" value=""/>

<!-- Settings for making sure we're connecting to an authenticated server, and that it's the server we want to connect to. -->

<!--
Specifies whether NTLM fallback is permitted when authentication of the server is not needed.
Authentication of the server is only possible with kerberos.
To require Kerberos authentication, set this value to false.
This setting is only relevant if ClientServicesCredentialType is Windows.
-->
<add key="AllowNtlm" value="true"/>

<!--
Specifies whether the service requires an SPN from Active Directory.
If true, the connection will only be made to a service with an SPN <ServerInstance>/<Server>:<ClientServicesPort>
If false, the connection will be attempted to a service with or without an SPN.
This setting is only used together with Kerberos authentication and ClientServicesCredentialType is Windows.
-->
<add key="ServicePrincipalNameRequired" value="False"/>

<!--
Indicate if you want to enforce validation of the certificate.
In a production environment this is strongly recommended. (Default is true)

When validation is enabled, the certificate needs to be trusted, not revoked and the CN name should
match the URL of your service.

When validation is disabled you can use a self-signed certificate with no revocation list and there
are no constraint on the CN name
-->
<add key="ServicesCertificateValidationEnabled" value="true"/>

<!--
One of the initial checks when a client authenticates a server is to compare the value of the Subject field
of the certificate to the Uniform Resource Identifier (URI) used to contact the service: the DNS of both must match.
For example, if the URI of the service is "net.[url=tcp://NavServer.com:7046/DynamicsNav/Service]tcp://NavServer.com:7046/DynamicsNav/Service[/url]. then the Subject field
of the certificate must also contain the value "NavServer.com".
Most commonly, the Subject is prefixed with "CN" (for common name), e.g., "CN = NavServer.com", but it can also just be "NavServer.com".
It is also possible for the Subject field to be blank, in which case the validation rules will be applied to the Subject Alternative Name field of the certificate.
The DnsIdentity configuration settings can be used to associate an endpoint with the specified Dns name.
-->
<add key="DnsIdentity" value=""/>

<!--
Name of the Microsoft Dynamics NAV Help Server to connect
to. The value of the "Server" setting is used as the default.
-->
<add key="HelpServer" value="NAVCLIENT"/>

<!--
The listening TCP port for the Microsoft Dynamics NAV Help Server.
Valid range: 1-65535
-->
<add key="HelpServerPort" value="49000"/>

<!--
Alternative product name for the Microsoft Dynamics NAV client.
Refer to the license terms before changing the product name.
-->
<add key="ProductName" value=""/>

</appSettings>
</configuration>

defiant701

Thanks,

as far as I see the NAV instance is configured to run in the non-multi-tenancy mode(your picture attached). According to your settings it's like this:

Servername FQDN in your case: navsql
SQL instance: default
NAV instance: DynamicsNAV71
Client Port: 7046
App DB: navsql

that means your access URL should look like this: navsql:7046/DynamicsNAV71 nothing more nothing less.

To switch to MT mode you need to:
- set the Multitenant check mark (right side)
- split the navsql database into at least navsql_app & navsql_bd1 .. n
- point to new app db
- mount tenant(s) (see under nav instance name on the left panel)
- change access URL to navsql:7046/DynamicsNAV71/navsql_bd1 or navsql:7046/DynamicsNAV71/navsql_bdn

This should solve your problem (in case there are no other errors). Please check also your settings in terms of the values for servername, sql etc. and change them if e.g. servername is not correct.

KR

P.S. just saw your ClientUserSettings.config has also a mismatch in terms of servername & port

hafedh

Thanks for response,
I will try these procedure,
Juste one more question please.
Right now, i dont need to configure multi-tenancy, but i have also this error and i would like to correct this error before to activate Mul-tenancy.
The error is:'' the microsoft dynamics nav server is currently not ready to serve requests. try again later or contact your system administartor ''

Best regards.
GH

defiant701

Guess when your settings are correct, you won't get this message again. But I'm not sure if you understood the multi-tenant principles correctly. It's not just turn on or off.

hafedh

Hi,
I have read some articls about how to configure multi-tenancy but i've not yet appliyed.
Thanks a lot for your help.
GH