![]() A bit of server configuration may be necessary though. If you were told by your NAV partner to install NAV 2009R2 make sure they meant the RTC client, as, at least in my personal experience, I haven't come across a partner who prepared their solution for NAV 2009R2 RTC. If you are only installing a demo installation (a Cronus database) to play with, download the latest NAV 2018 version and play with this one. Why are you trying to install the Service Tier? Are you planning to use the RTC client from NAV2009R2? Any particular reason for doing this? You can read a bit of the Service Tier prerequisites here - the link describes a never NAV version but most of the things apply. The service account used to run the NST server service must be configured at the SQL Server - a corresponding login must be created, and the db_owner permissions to the target NAV database must be granted. The NST server must have configured some SQL Server, optionally a SQL Server instance name if the database lives in a named instance, and must have the database name specified. Classic Clients connect directly to the database servers, and the RTC connects to the Service Tier (the NST), which in turn connects to the Microsoft SQL Server. NAV 2009R2 comes with 3 types of clients, 2 Classic Clients (one for the native NAV database server, and one for the SQL Server), and with the Role Tailored Client (the RTC). For using it you also need to have a SQL Server installed somewhere, and configure the NST. The Service tier is only required when you plan to use the RTC client. If you want to run NAV on SQL Server then you need to have a SQL Server installed on your server machine, and use the finsql.exe Client executables. If you use/have used non-default port number while installing NAV database server you may need to add an entry in C:\Windows\System32\drivers\etc\services file on each client machine, listing your selected port number against destination machine name - or alternatively, you can connect by specifying ServerName:PortNumber in the server address box Details can be found in w1w1ism.pdf document which should be somewhere on your installation DVD. You need to install it as a service, configure its parameters, including the database file(s) names and locations, and make sure it is up and running before you can connect clients to it. If your intention to run NAV native database server then you need to install NAV Database Server component on the server machine. The native NAV database client executable is called fin.exe, and I guess from the error message this is the one you are trying to use. You normally have two NAV 2009R2 clients installed - one is for native NAV database server and another is for SQL Server connectivity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |