Microsoft Dynamics NAV

Team Blog

January, 2013

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2013 Compatiblity with Microsoft Windows 8 and Microsoft Windows Server 2012

    • 11 Comments

    We are proud to announce that Microsoft Dynamics NAV 2013 is compatible with Microsoft Windows 8 and Microsoft Windows Server 2012.

    We support the following versions of Microsoft Dynamics NAV with Microsoft Windows Server 2012 and Microsoft Windows 8:

    • Microsoft Dynamics NAV 2009 R2
    • Microsoft Dynamics NAV 2013

    For more information about requirements, see System Requirements for Microsoft Dynamics NAV 2013.

  • Microsoft Dynamics NAV Team Blog

    New finsql.exe Command Prompt Options

    • 7 Comments

    Based on partner feedback and the increasingly important goal of automating processes around a Microsoft Dynamics NAV installation, we’re pleased announce that we have added company-related and database-related command-line options to finsql.exe, in addition to the existing options. Introduced in hotfix 2791548, you can use the following commands to perform development tasks without using the Microsoft Dynamics NAV Development Environment.

    • Create company - new
    • Delete company - new
    • Rename company - new
    • Create database - new
    • Compile objects
    • Export objects
    • Import objects

    Note

    To use the new and changed command-line options, you must install hotfix 2791548 (requires access to PartnerSource/CustomerSource).

    You can start the Microsoft Dynamics NAV Development Environment by running finsql.exe at the command prompt. By default, finsql.exe is located at C:\Program Files (x86)\Microsoft Dynamics NAV\70\RoleTailored Client\. The extended full syntax is:

    Finsql.exe [command=<command> | designobject=<object type> <object ID>,] [servername=<server>,] [database=<database>,] [collationname=<collation>,] [company=<company>,] [newcompany = <new company>,] [filter=<filter>], [logfile=<logfile>,] [username=<user name>,] [password=<password>,] [ntauthentication=<yes|no|0|1>]

    The full documentation is available on the MSDN Library. Additional documentation is available at Development Environment Commands.

    Parameters

    The following list describes the parameters that you can use with finsql.exe.

    collation

    The collation to use when you create a new database. The value must be one of the following:

      • A full language culture name. For example, da-DK for Danish or hu-HU for Hungarian.
      • A SQL Server collation name without case or accent. For example, Latin1_General_100.
      • A SQL Server collation name with case and accent. For example, Danish_Greenlandic_100_CS_AI.

    Use this optional parameter when you create a database with the command=createdatabase parameter.

    command

    The development command that you want to run. The possible values include:

      • CompileObjects
      • CreateCompany
      • CreateDatabase
      • DeleteCompany
      • ExportObjects
      • ImportObjects
      • RenameCompany

    If you specify this parameter and run a command, then the development environment does not open.

    For more information, see Development Environment Commands.

    company

    The name of the company that you want to create, delete, or rename.

    A company name cannot be more than 30 characters.

    If you create, delete, or rename a company with the command parameter, then the company parameter is required.

    database

    If you use the command=CreateDatabase parameter, then the database parameter specifies the name of the new database that you want to create. In this case, the database parameter is required.

    For all other commands, the database parameter specifies the database that you want to open.

    If you do not specify both the servername and the database parameter, then the database server and database that are stored in the .zup file are used. If you do not specify the database parameter but you do specify the servername parameter, then the Open Databasewindow opens so that you can specify the database name.

    For more information, see Saving Setup Parameters in the Zup File.

    designobject

    The type and ID of the object that you want to design. The possible values of the object type include:

      • Table
      • Page
      • Report
      • Codeunit
      • Query
      • XMLport

    The possible values of the object ID are 0 and any ID of an existing object. If you specify 0 for the object ID, then you open a new object to design.

    For more information, see DesignObject.

    file

    The path and file name. Use the file parameter for the following:

      • To specify the path and file name to which you export objects if you use the command=ExportObjects parameter. The file must have a .fob or .txt file name extension.
      • To specify the path and file name from which you import objects if you use the command=ImportObjects parameter. The file must have a .fob or .txt file name extension.
      • To specify the directory for the new database file if you use the command=createdatabase parameter.

    For more information, see ExportObjects and ImportObjects.

    filter

    A filter on the Object table.

    Use this parameter if you use the command parameter to compile, export, or import objects.

    For more information, see Development Environment Commands.

    id

    Specifies the ID of the .zup file. By default, the setup parameters are stored in and retrieved from the fin.zup file. If you specify the id parameter, then the setup parameters are stored in and retrieved from a file that is named <id>.zup.

    By default, the fin.zup file is located at C:\users\<user name>\AppData\Roaming\. To change the location of the .zup file, specify the path and ID in the id parameter.

    For more information, see Saving Setup Parameters in the Zup File.

    logfile

    Specifies the path and file name for the file that contains error messages that result from running finsql.exe with the command parameter. If there are no errors, then a log file is not created.

    For more information, see Development Environment Commands.

    newcompany

    The new name of the company that you rename.

    A company name cannot be more than 30 characters.

    If you rename a company with the command parameter, then the newcompany parameter is required.

    ntauthentication

    Specifies if you want to use NT authentication. The possible values are yes, no, 1, or 0. If you specify the username and password parameters, then you must specify ntauthentication=no or ntauthentication=0.

    objectcache

    Specifies the size of the object cache, in kilobytes. Objects such as code, descriptions, and windows that are used on the computer that is running the development environment are stored in the object cache.

    The default value is 32000.

    password

    Specifies the password to use with the username parameter to authenticate to the database. If you do not specify a user name and password, then the command uses the Windows user name and password of the current user to authenticate to the database.

    servername

    Specifies the name of the database server.

    If you do not specify both the servername parameter and the database parameter, then the database server and database that are stored in the .zup file are used. If you do not specify the servername parameter but you do specify the database parameter, then the Open Database window opens so that you can specify the database server name.

    For more information, see Saving Setup Parameters in the Zup File.

    temppath

    Specifies the path of the location to store temporary files that are created while Microsoft Dynamics NAV runs. These files are automatically deleted when Microsoft Dynamics NAV is closed.

    By default, these files are put in the Temp folder for the user, such as C:\Users\user name\AppData\Local\Temp\

    username

    The user name to use to authenticate to the database. The user name must exist in the database. If you do not specify a user name and password, then the command uses the Windows user name and password of the current user to authenticate to the database.

    Warning

    If User Access Control (UAC) is turned on and you do not specify to run the Command Prompt window as Administrator, then the Command Prompt window runs as a standard user. In this case, if you do not specify the username parameter and the current Windows user is an Administrator, then the command is run as the standard user.

    If you specify the username parameter, then you must also specify the password parameter and the ntauthentication parameter must be no or 0.

    For more information about database users and permissions, see Setting Database Owner and Security Administration Permissions in the MSDN Library.

     

     

    Best regards from the NAV Management Tools team

     

     

     

  • Microsoft Dynamics NAV Team Blog

    New Management Admin Cmdlets

    • 0 Comments

    Windows PowerShell is becoming ever more used in the professional IT organization, and in Microsoft Dynamics NAV we are continuously extending and improving the set of administration management PowerShell cmdlets.

    With hotfix 2791548, we introduce these additions and updates, all fully backward compatible with cmdlets shipped with Microsoft Dynamics NAV 2013:

    • New-NAVServerInstance
      • Creates a new Microsoft Dynamics NAV Server instance - new parameters
    • New-NAVWebServerInstance
      • Creates a new Microsoft Dynamics NAV Web Server instance and binds this instance to a Microsoft Dynamics NAV Server instance - new
    • New-NAVDatabase
      • Creates a new Microsoft Dynamics NAV database from a backup file - new
    • Rename-NAVCompany
      • Renames a company in a Microsoft Dynamics NAV database - new

    Note

    To use the new and changed cmdlets, you must obtain the relevant hotfix through your Microsoft Dynamics NAV support contact. For more information, see the KnowledgeBase article for the hotfix (requires access to PartnerSource/CustomerSource).

    The rest of this blog post describes the cmdlets at a summary level. The full documentation is available on the MSDN Library. Additional documentation is available at Microsoft Dynamics NAV Windows PowerShell Cmdlets.

    New-NAVServerInstance

    Creates a new Microsoft Dynamics NAV Server instance.

    Syntax

    Parameter Set: __AllParameterSets

    New-NAVServerInstance [-ServerInstance] <String> -ManagementServicesPort <ServicePort> [-ClientServicesCertificateThumbprint <String> ] [-ClientServicesCredentialType <String> ] [-ClientServicesPort <ServicePort> ] [-DatabaseInstance <String> ] [-DatabaseName <String> ] [-DatabaseServer <String> ] [-ODataServicesPort <ServicePort> ] [-ServiceAccount {<LocalService> | <NetworkService> | <LocalSystem> | <User>} ] [-ServiceAccountCredential <PSCredential> ] [-SOAPServicesPort <ServicePort> ] [ <CommonParameters>]

    Detailed Description

    Use the New-NAVServerInstance cmdlet to create a new Microsoft Dynamics NAV Server instance. You must specify a name for the instance, in addition to values for the four port parameters. All other configuration values for the new instance are based on default values. Make sure that you verify the DatabaseServer and DatabaseName values after the instance is created, to ensure that the instance can accept client requests.
    All permissions that are required for the instance to start are configured automatically.

    See Also

     For more information, see New-NAVServerInstance on the MSDN Library.

    Examples

    Example 1

    This example creates a new Microsoft Dynamics NAV Server instance. It configures the necessary firewall exceptions and performs the necessary Access Control List registrations.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

     

    C:\PS>New-NAVServerInstance NewInstance -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 –verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Creating Instance directory C:\Program Files (x86)\Microsoft Dynamics NAV\70\Service\Instances\NewInstance

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: NavCommand.EndProcessing

    Example 2

    This example prompts for ServiceAccount credentials and then creates a new Microsoft Dynamics NAV Server instance.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

     

    C:\PS>Get-Credential | New-NAVServerInstance NewInstance -ServiceAccount User -ManagementServicesPort 8099 -ClientServicesPort 8100 -SOAPServicesPort 8101 -ODataServicesPort 8102 –verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Creating Instance directory C:\Program Files (x86)\Microsoft Dynamics NAV\70\Service\Instances\NewInstance

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: Adding Windows Firewall (and UrlAcl) rules for Server Instance MicrosoftDynamicsNavServer$NewNAVServer

    VERBOSE: NavCommand.EndProcessing

     

    New-NAVWebServerInstance

    Creates a new Microsoft Dynamics NAV Web Server instance and binds this instance to a Microsoft Dynamics NAV Server instance.

    Syntax

    Parameter Set: Default

    New-NAVWebServerInstance -Server <String> -ServerInstance <String> -WebServerInstance <String> [-ClientServicesCredentialType <String> ] [-ClientServicesPort <String> ] [-DnsIdentity <String> ] [ <CommonParameters>]

    Detailed Description

    Use the New-NAVWebServerInstance cmdlet to create a new Microsoft Dynamics NAV Web Server instance and bind this instance to a Microsoft Dynamics NAV Server instance on the same computer or on a remote
    computer. If you call this cmdlet multiple times then multiple instances of the Microsoft Dynamics NAV Web Server are created. Each instance of the Microsoft Dynamics NAV Web Server is created as an IIS Web application under a generic Microsoft Dynamics NAV Web Server web site.

    See Also

    For more information, see New-NAVWebServerInstance on the MSDN Library.

     

    New-NAVDatabase

    Creates a new Microsoft Dynamics NAV database from a backup file.

    Syntax

    Parameter Set: __AllParameterSets

    New-NAVDatabase [-FilePath] <String> -DatabaseName <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]

     

    Parameter Set: MultipleDestinations

    New-NAVDatabase [-FilePath] <String> -DatabaseName <String> -DataFilesDestinationPath <String> -LogFilesDestinationPath <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]

     

    Parameter Set: SingleDestination

    New-NAVDatabase [-FilePath] <String> -DatabaseName <String> -DestinationPath <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-Force] [-ServiceAccount <String> ] [ <CommonParameters>]

    Detailed Description

    Use the New-NAVDatabase cmdlet to restore a database from a backup file. You can specify the location of transaction log files and data files.

    You can use this cmdlet to restore a database to a remote SQL Server instance or to a SQL Server instance that is running on the same computer on which you run the cmdlet.

    See Also

    For more information, see New-NAVDatabase on the MSDN Library.

    Examples

    Example 1

    This example restores a database and preserves the original file names and locations.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

     

    New-NAVDatabase C:\Backups\backup1.bak –DatabaseName NewDatabase –Verbose | fl

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Restoring database 'NewDatabase' from backup file: 'C:\Backups\backup1.bak'...

    VERBOSE: Restore of database 'NewDatabase' from file 'C:\Backups\backup1.bak' has been completed successfully.


    DatabaseName : NewDatabase

    DatabaseInstance : MSSQLSERVER

    DatabaseServer : server1.cronus.com



    VERBOSE: NavCommand.EndProcessing

    Example 2

    This example restores a database, moves transaction log files and data files to the new location 'C:\newdestination', and preserves the original file names.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

     

    New-NAVDatabase C:\Backups\backup.bak -DestinationPath c:\newdestination -DatabaseName NewDatabase –Verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Restoring database 'NewDatabase' from backup file: 'C:\Backups\backup.bak'...

    VERBOSE: Restore of database 'NewDatabase' from file 'C:\Backups\backup.bak' has been completed successfully.


    DatabaseName DatabaseInstance DatabaseServer

    ------------ ---------------- --------------

    NewDatabase MSSQLSERVER server1.cronus.com

    VERBOSE: NavCommand.EndProcessing 

     

    Rename-NAVCompany

    Renames a company in a Microsoft Dynamics NAV database.

    Syntax

    Parameter Set: Default

    Rename-NAVCompany -CompanyName <String> -DatabaseName <String> -NewCompanyName <String> [-DatabaseInstance <String> ] [-DatabaseServer <String> ] [-ErrorLogFileName <String> ] [ <CommonParameters>]

    Detailed Description

    Use the Rename-NAVCompany cmdlet to rename a company in a Microsoft Dynamics NAV database.

    See Also

    For more information, see Rename-NAVCompany on the MSDN Library.

    Examples

    Example 1

    This example renames the company Cronus Ltd. in the Cronus database to MyCompany.

    // Copyright © Microsoft Corporation. All Rights Reserved.

    // This code released under the terms of the

    // Microsoft Public License (MS-PL, http://opensource.org/licenses/ms-pl.html.)

     

    Rename-NAVCompany -DatabaseName Cronus -CompanyName "Cronus Ltd." -NewCompanyName MyCompany –Verbose

     

    VERBOSE: NavCommand.BeginProcessing

    VERBOSE: NavCommand.ProcessRecord

    VERBOSE: Renaming company 'Cronus Ltd.' to 'MyCompany' ...


    VERBOSE: Renaming of company 'Cronus Ltd.' to 'MyCompany' has completed successfully.

    VERBOSE: NavCommand.EndProcessing

    Example 2

    This example renames the company Cronus Ltd. in the Cronus database to MyCompany. Errors are logged to the file C:\NavDatabases\ErrorLog.txt.

    Rename-NAVCompany -DatabaseName Cronus -CompanyName "Cronus Ltd." -NewCompanyName MyCompany -ErrorLogFileName C:\NavDatabases\ErrorLog.txt

     

    - Morten Jensen and the rest of the Microsoft Dynamics NAV Management Tools team

     

  • Microsoft Dynamics NAV Team Blog

    Microsoft Dynamics NAV 2013 Management Pack for System Center

    • 0 Comments

    In the past few months we talked to many hosting companies across several countries which deal with Microsoft Dynamics NAV hosting. They all are confirming that the new platform capabilities of Microsoft Dynamics NAV 2013 are making the product much easier to deploy and
    maintain.

    The tools that are essential for the companies dealing with volume deployment of Microsoft Dynamics NAV 2013 include:

    • Flexible authentication capabilities
    • Streamlined 2- and 3-tier deployment
    • Windows PowerShell cmdlets to allow advanced scripting of repeated tasks
    • Management Console user interface built on top of PowerShell cmdlets
    • The ability to deploy the Microsoft Dynamics NAV Windows client using ClickOnce technology

    We also gained insight into the typical hosted Microsoft Dynamics NAV incidents. One of the biggest cost factors for companies dealing with a variety of products, not only from Microsoft, but also from multiple third-party software providers, was support and troubleshooting – finding the root cause faster and being able to see which product is causing problems to relay the support incident to the right support professional.

    Many of these companies chose to use the Microsoft System Center platform to manage their virtual, physical, and cloud IT environments. This is a single end-to-end service management solution to handle infrastructure, service delivery, automation, and applications that is easy to customize and extend.

    The way to extend this management platform to recognize and maintain all kinds of software and hardware is to use Management Packs (MPs) developed for them. Management Packs are the building blocks which extend Operations Manager capabilities to operating systems, applications, and other technology components. An MP contains best practice knowledge to discover, monitor, troubleshoot, report on, and resolve problems for a specific technology component.

    Microsoft provides MPs for more than 60 Microsoft products and Windows components. There are more than 500 Microsoft Partner Management Packs covering most technologies used by organizations today.

    We are pleased to announce that a Microsoft Dynamics NAV 2013 Management Pack for System Center is now available for download for all IT professionals working with System Center 2007 R2 Operations Manager or System Center 2012 Operations Manager components of the Microsoft System Center.

    This extension package provides Microsoft System Center Operations Manager users with the ability to detect and monitor computer systems running Microsoft Dynamics NAV 2013, including the following components:

    • Computers on which Microsoft Dynamics NAV Server is installed and Microsoft Dynamics NAV Server instances are installed.
    • Computers on which Microsoft Dynamics NAV Web Server components are installed. These include the websites for the Microsoft Dynamics NAV Web client.

    Companies providing hosting services to Microsoft Dynamics NAV Partners now have a toolset for extending their offering with Microsoft Dynamics NAV-specific monitoring and basic troubleshooting.

    Microsoft Dynamics NAV 2013 Management Pack for System Center enables Operations and IT Management teams to easily identify and resolve issues affecting the health of numerous distributed Microsoft Dynamics NAV 2013 installations. It lowers client support costs by surfacing critical statistics and alerts in context of running Microsoft Dynamics NAV 2013 components. It also reduces IT management complexity by automating routine administration and providing basic actions for working with Microsoft Dynamics NAV 2013 components.

     

    On a final note, we would like to thank all the companies who shared their experience and provided their feedback to our R&D team. This feedback is extremely valuable and greatly appreciated.

     

    - The Microsoft Dynamics NAV Product Marketing team 

     

Page 1 of 1 (4 items)