Can someone provide some guidence to move a Dynamics Navision 4.0 database from a SQL Server 2005 SP2 x32 bit server to a x64 SQL Server 2005 cluster running SP3?
I am testing the process by trying to bring a test database over. I performed a SQL backup/restore, migrated the user accounts, but when I try to open or create a new database from within the NAV client, i don’t see the new SQL Server listed in the drop-down list. When I plug in the servername and credentials, I get:
"there are errors in the text conversion (text no. 2338-31 does not exist in the .stx file). Internal error: 47-1
firstly you have two errors you need to fix. The first Erik mentions above. The second is that you have a corrupt version of Navision Client installed. This could have happened for a number of reasons, most likely being either you applied hotfix incorrectly, or maybe you have incorrectly installed a different language. Becasue basically the version of the STX file you have is not the same as the Fin.exe file. Also make sure you have a good version of 4.00sp3, I recommend build 26565.
Also the move to 64bit is a good one, but do you have a good reason for using clusters? It may just plug and play, but also you may have a lot of problems getting Navision to work with a cluster. Log shipping and othe such disaster recovery methods generally are better options for Navision. Unless of course you can not even afford a few minutes of downtime.
I am working on a project to consolidate all instances of SQL over to two clustered SQL environments. One for Dev/Staging and the other is Production. I appreciate the heads up on the potential problems running Navision in a cluster. I will have to engage a Navision consultant to see if there are any problems and if it’s going to cause too much disruption. As far as the Nav client goes, the one I was using is an accountants client that she uses everyday, so I know it works.
Database Mirroring (High Availability Mode) is a good option that provides quick failover and zero data loss. Users just need to reconnect to the mirror and resume working.
Hi Same, I believe that this problem can be fixed by Recovery Toolbox for SQL Server application. Users often ask, can Microsoft repair mssql 2005 database? It is not always possible with in-built database recovery solutions, therefore we can try 3rd party applications