Problem installing demo database
Saurav did get before me in writing this blog post. Have you ever seen below error when installing the demo database.
Could not connect to the SQL database. (-2147467259 master ). This can be caused by insufficient permissions. Indirect permissions through Windows group memberships may not work as expected when User Account Control (UAC) is turned on.
Few resolutions to the problem
1) UAC is turned on.
2) SQL server is not running
3) Your user doesn’t have sufficient privileges on the SQL server.
4) Old database file are left on the system.
Take a look at Saurav’s blog for the solutions. Saurav’s blog post is found here
Change listener connetion error
“The Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server because of the following error: user ‘NT AUTHORITY\NETWORK SERVICE’ failed when log in”.
This error may happen when you are attaching the database manually, or if database and NAV service is on two different machines. A variation of this may also happen if you setup NAV server to user domain user account. Luckily the solution is the same for all problems
Enabling the Object Change Listener Read more
CREATE DATABASE failed when installing Cronus Sample Database
Today I did run into a problem installing the “Cronus Sample Database”. In the error report view I found this error message
SQL Server option
Cronus Sample Database for Microsoft Dynamics NAV 2009
Fatal error during installation.
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
Read more
“User ID and password are invalid.try again?”
If you get “User ID and password are invalid.try again?” when starting RTC you need to first check that you can login to database in the classic client. Note that the database should be the same as the service tier (the service you are trying to connect with RTC) is connected to.
1. Start “classic client with SQL”
2. Click File->Database->Open
3. Pick the server the database exist one
4. Select authentication “Windows Authentication”
5. Pick the database
6. Press OK
If it works in the classic client make database login synchronization.
1. Start “classic client with SQL” and connect to the database as above
2. Click Tools->Security->Synchronize all logins
3. Answer yes to the question if you would like to synchronize
If it doesn’t to connect to the database start SQL server manager and verify that the windows user have permission to login and use the NAV database
Troubleshooting multi-machine installations of NAV 2009
Today I found a really good and interesting blog about general troubleshooting of multi-machine scenarios in NAV 2009. Most of the blog is checking SPN settings, delegations settings and different problems with those.
Intro
The NAV 2009 documentation walkthroughs provide step-by-step instructions for installing NAV 2009 on 2 or 3 machines. However, we have found that some of the same configuration issues come up time after time after installation.
When on calls with partners and customers, it seemed to me that this information was spread out all over the place, so I wanted to organize it in a different way for troubleshooting purposes so that I would have most everything in one place. Hopefully this will be helpful to others as well.
The intention of this post is to provide a checklist of sorts for troubleshooting some of the areas where we frequently find errors or omissions in configuration after NAV 2009 has been installed.
Find the whale blog here: http://blogs.msdn.com/nav_developer/archive/2009/08/17/troubleshooting-multi-machine-installations-of-nav-2009.aspx
Changing stored procedure to 64 bit in NAV 2009
Did install Dynamics NAV 2009 on windows 2008 64 bit. When trying to connect to the database in classic client I got this error.
The following SQL server error or errors occurred:
17750,“42000”,[Microsoft][ODBC SQL Server Driver][SQL Server]Could not load the DLL C:Program Files (x86)Microsoft Dynamics NAV60Databasexp_ndo.dll, or one of the DLLs it references. Reason: 193(failed to retrieve text for this error. Reason: 15100).
SQL:
INSERT INTO [#$ndo$groups] {CALL [master]..[xp_ndo_enumusergroups](?,?)}
The reason for this error is that the installed xp_ndo.dll is 32 bit and not 64 bit. My solution was simple to replace xp_ndo.dll with the 64 bit version.
1. Stop SQL server
2. Copy \vedfssrv01DynamicsNAV2009W1DVDSql_espx64 xp_ndo_x64.dll to C:Program Files (x86)Microsoft Dynamics NAV60Database
3. Rename existing xp_ndo.dll to xp_ndo_x32.dll
4. Rename xp_ndo_x64.dll to xp_ndo.dll
5. Start SQL server
How to install more than one Dynamics NAV 2009 Demo Database alternative 2
Earlier I did describe how to duplicate an installed and existing database in post “How to install more than one Dynamics NAV 2009 Demo Database”. This time I will attached the DB directly from DVD.
The steps is as follow
1. Create the directory where you would like to have the new database.
2. Copy the database from DVDSQLDemoDatabasePFilesMicrosoft Dynamics NAV60Database Demo Database NAV (6-0)_Data.mdf to the new directory.
3. Run the following command in SQL manager studio and replace the @physname path with the new created on and set @dbname to the database name you would like to use.
sp_attach_single_file_db @dbname= ‘new_Demo Database NAV (6-0)’, @physname= ‘C:Program Files (x86)Microsoft Dynamics NAV60Database – CopyDemo Database NAV (6-0)_Data.mdf’
You need to ensure that the SQL server user have correct permissions to ‘C:Program Files (x86)Microsoft Dynamics NAV60Database – Copy’ or where you put the db files. I’m using ‘NETWORK SERVICE” as the SQL server user account, the NAV will use this account by default when doing demo installation.
To set permission
1. Open properties for the directory.
2. Click security tab
3. Click advance
4. Click edit
5. If the SQL server user is not present press add and pick the user else select the SQL server user and click edit
6. Change the permission so that the following permission is checked
a. Read attributes
b. Read extended attributes
c. Create files / write data
d. Create folders / append data
e. Write attributes
f. Write extended attributes
g. Delete subfolders and files
h. Delete
7. Click OK
8. Click Ok
9. Click OK
10. Click OK
Multiple Service Tiers – NAV 2009 SP1
Freddy have update his blog about how to run multiple service tiers in NAV 2009 SP1. One of the new things in SP1 is that you can use named instance of SQL server. On the blog post he has some nice bat script that can set everything up.
The post can be found here http://blogs.msdn.com/freddyk/archive/2009/08/05/multiple-service-tiers-sp1.aspx
Multiple Service Tiers in Dynamics NAV 2009
Freddy have posted an interesting blog about having multiple service tiers.
From the post “A very typical scenario with both partners and customers is to have more than one database. This can be because you have a development database and a production database – or it could be the partner having a copy of all customer databases locally for troubleshooting.
You could of course install the Service Tier locally on all computers – and then change the CustomSettings.config to point to a new database every time you need to logon, but that doesn’t really sound like something we want people to do.
The setup we would like to have is:
• One or more SQL Server boxes with a bunch of databases on
• One or more Service Tier boxes with at least one Service Tier pr. database
• The Client installed locally on all machines being able to connect to these Service Tiers.
This post will go into detail about how to accomplish this.”
Trace flag in SQL Server for Dynamics NAV 2009
When starting the RTC client or open the database in classic client you will get a warning if you have not set the trace flag correct. Because of changed security in SQL Server 2005 Dynamics NAV 2009 will only connect to the SQL Server if the trace flat ‘4616’ is set.
How to:
1. Open SQL Server Configuration Manager
2. Right click on MSSQLSERVER and select properties
3. In properties click advanced tab
4. Click to the right of Setup Parameters and go to the end of the line
5. Add this string “;-T4616”
6. Click ok and restart your SQL Server.