Hi,
I want to install Database Component of NAV 2013 in a SQL Cluster environment.
The problem is that setup configuration interface does not allow to specify the name of SQL Server. I can specify only the name of SQL Server Instance name.
I've tried to modify setup configuration file (.xml) passing SQL Server parameter as below:
<Configuration>
<Component ShowOptionNode="no" State="Absent" Id="ClickOnceInstallerTools"/>
<Component ShowOptionNode="yes" State="Absent" Id="WebClient"/>
<Component ShowOptionNode="yes" State="Absent" Id="AutomatedDataCaptureSystem"/>
<Component ShowOptionNode="no" State="Absent" Id="OutlookAddIn"/>
<Component ShowOptionNode="yes" State="Absent" Id="SPCServer"/>
<Component ShowOptionNode="yes" State="Local" Id="SQLServerDatabase"/>
<Component ShowOptionNode="yes" State="Absent" Id="SQLDemoDatabase"/>
<Component ShowOptionNode="yes" State="Absent" Id="ServiceTier"/>
<Component ShowOptionNode="yes" State="Absent" Id="Pagetest"/>
<Component ShowOptionNode="yes" State="Absent" Id="STOutlookIntegration"/>
<Component ShowOptionNode="no" State="Absent" Id="Documentation"/>
<Component ShowOptionNode="yes" State="Absent" Id="ServerManager"/>
<Component ShowOptionNode="no" State="Absent" Id="RoleTailoredClient"/>
<Component ShowOptionNode="no" State="Absent" Id="ExcelAddin"/>
<Component ShowOptionNode="no" State="Absent" Id="ClassicClient"/>
<Parameter Id="TargetPath" Value="[WIX_ProgramFilesFolder]\Microsoft Dynamics NAV\70"/>
<Parameter Id="TargetPathX64" Value="C:\Program Files\Microsoft Dynamics NAV\70"/>
<Parameter Id="NavServiceSQMOption" Value="false"/><Parameter Id="NavServiceServerName" Value="localhost"/>
<Parameter Id="NavServiceInstanceName" Value="DynamicsNAV70"/>
<Parameter Id="NavServiceAccount" Value="navserviceaccount"/>
<Parameter Id="NavServiceAccountPassword" Value="" IsHidden="yes"/>
<Parameter Id="NavServiceClientServicesPort" Value="7046"/>
<Parameter Id="WebServiceServerPort" Value="7047"/>
<Parameter Id="DataServiceServerPort" Value="7048"/>
<Parameter Id="NavFirewallOption" Value="true"/>
<Parameter Id="CredentialTypeOption" Value="Windows"/>
<Parameter Id="DnsIdentity" Value=""/>
<Parameter Id="ACSUri" Value=""/>
<Parameter Id="SQLServer" Value="CLUSTER_SQL"/>
<Parameter Id="SQLInstanceName" Value=""/>
<Parameter Id="SQLDatabaseName" Value="Demo Database NAV (7-0)"/>
<Parameter Id="SQLReplaceDb" Value="FAILINSTALLATION"/>
<Parameter Id="WebServerPort" Value="8080"/>
<Parameter Id="WebClientRunDemo" Value="true"/>
<Parameter Id="WebClientDependencyBehavior" Value="install"/>
<Parameter Id="SPCServerDeployment" Value="1"/>
<Parameter Id="SPCServerHost" Value="localhost"/>
<Parameter Id="SPCServerPort" Value="80"/>
</Configuration>
but "SQLServer" parameter is ignored during installation.
I suppose that NAV 2013 setup search and connect only to local SQL Server instance, so when I connect to a cluster node in order to install Database components it fail because don't find any SQL Server installated locally.
There is any solution?
What is installed during "Database Server Components"? Can I install manually these Components?
Thank you
0
Comments
What we have done is install the Database Component to a local, default SQL instance and move it manually to the SQL Cluster. Initial testing indicates this has worked, however, we dont know if we've captured all the activity that may have happened on the SQL instance during the install.
I can't believe that Microsoft, after adding cluster/load balancing support at the app level, did not even bother testing an install on a high availability SQL Cluster ....
Any insight would be appreciated ...
Regards,
Greg.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
The blog post:
http://blogs.msdn.com/b/nav/archive/201 ... abase.aspx
The net issue is that Microsoft has a bug in their install process that needs to be resolved ...
I will post an update from all as we escalate this to Microsoft.
Greg.
You can achieve this by manually installaing These database components.
In NAV 2013 Database components Installation involves
- Restoring the NAV Database to the SQL Server.
- Create a Login for the user which is configured to run NST Service (By Default it's NETWORK SERVICE),
- Creating "$ndo$listener" Default schema for this User in this database.
- Assigning the required following permissions for the NST user in this database.
-db_datareader
-db_datawriter
-db_ddladmin
Arvind
Arvind