Hi all
I am on Nav 2009 cc. Recently we have added new client system running on Windows 10 Home edition. After Nav client installation, while login to navision initially i was getting SQL startup parameter error which i had resoled. Now while login to navision i find following error:
"The XXXX database on the server XXXXX cannot be opned by this version of Dynamics navision. The Database is alreay been converted by newer program vesion. You must upgrade navision client to the latest version to view database.
This the only client running on windows 10 where all other clients are on windows 8.1 below, please advice.
thanks
satish
0
Answers
It looks like the server is running on a higher cumulative update than the NAV client you've installed.
Check with Programs and Features the version number of the NAV installation on the client and on the server. Check if there is any difference. The version number should be the same.
Thanks for your reply,
When all other clients on my network are working perfectly without any issues why only on this client, even though any other versions of nav is running on the server.
Somewhere along the way of NAV releases the parameter 'Build Restriction' showed up in the NST configuration with the options 'DoNotAllow', 'WarnClient' and 'AlwaysConnect'.
I can imagine this property excised before in another configuration file, client configuration or something like that. I don't know but maybe it gives you a clue.
The nnnnn is the build number of your classic client. You need to install the same version on your new PC. If you don't have the installer you can copy the content of Classic folder (or whatever the folder name where you found the finsql.exe) to the new PC, overwritting all the files at the destinations.
If your copy all of the client binaries, and all folders underneath the folder where finsql.exe lives, the copied client will probably work - most of the time. Some of the features, like e-mailing (through Outlook or SMTP server) may not be working properly in copied client, as some of dlls acting as interfaces between NAV and external components differs from version to version, and won't work without being properly registered
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
Satish installed an older version already. I think the integration with Windows/ other program's won't be a problem if you've installed NAV from an original dvd, even though it's an older client. If you replace the client folders with the folders from the other machine it's probably going to work. Like you've described.