If you speak about "server" as phisical PC - YES (I can install new Navision
server on this phisical server), if speak as service - NO.
To clarify, I would like to have two instances of a Navision database
running on a single server. Can there not be two services? Different
ports?
You can run MANY Navision services on the same server, I do it all the
time for testing.
Great. How? That is exactly what I would like to do.
Thank you!
Isn't this the same question asked previously? By adopting my
instructions you can install more that one Navision service on the
server on a different port. I would however strongly advise you NOT
to use your production server, can't you just use a spare Windows PC
instead?
Assuming you are the same AF here is your previous post and my reply:
> I've adopted a Navision 4 system, looking to move it from the current
> server to a new server. I've taken a copy of the current database via
> hotcopy and am having trouble getting it loaded onto the new server.
> How should I do this? I'm trying to open the database file but it
> continuously tells me there was a network error - but - it's opening a
> local file.
If I understood you correctly, you are saying that you wish to move a
Native Navision database to another server?
You do not need to use Hotcopy as part of the move. Just stop the
Navision service and copy the database files across to the new
server. Below is a previous post I made on MANUALLY setting up a new
server, this shows the command line method, rather than the wizard, so
you know what is going on and how to install and uninstall the
services and their options.
If you have lots of clients you may wish to keep the same IP address
and Service name/Port number. I've assumed that the old server is
*not* used for any other purpose, so it's IP address can be changed.
Miss this bit out if you can't change it and are installing onto a new
server with new address.
You can do the installation using the wizard if you wish, but I much
prefer to do it manually under my control. This method allows you to
do a DOS copy of the database parts to a different server with a
different path without the need to do a Navision backup and restore.
Note: Below, Navision uses the phrase "servername". This is NOT the
same as the Windows server name. Navision "servername" is the name of
the SERVICE that you are installing and can be different to the
Windows
server name. Indeed you can run several Navision services on one
Windows server, I do so for testing.
Make a Navision backup somewhere safe.
Make a note of the Navision service name.
Make a note of the Navision servers IP address, services and hosts
file
entries.
Stop the Navision service.
Copy of the database parts onto the new server (not a Navision backup
and restore).
Change the IP address of the old server so it doesn't clash with the
new one.
Edit the new servers SERVICE and HOSTS file as required.
Install Navision, call the service FRED and accept the defaults for
cache etc, you are going to uninstall this service anyway. Do not
point this service at the database parts, select the option to do it
later.
Don't forget to install the licence file (or just copy it across from
the old server).
Got to the command prompt and go to the Navision folder. Type the
following to uninstall the service that was created at installation.
server servername=fred, unistallasservice
As a precaution, delete the dbms.zup file if there is one.
Then install the new service using the same service name used on the
old server (change the values as required).
server servername=INSERTSEVICENAME,
database=e:\part1.fdb+f:\part2.fdb+g:\part3.fdb, cache=850000,
commitcache=yes, installasservice
The cache can be anything up to 1Gb (my example shows 850Mb).
Start the service and you are done. Because you have kept the service
name and IP address the same as the old one, you do not need to make
any changes to your client PCs.
I always use this manual method to install Navision because I am
usually copying the database parts to another server with different
drive letters for the database path, usually for testing stuff.
Thanks Eddie, I did try that - will do so again. Maybe something was
overlooked.
AF
Sorry I hit "send" before completing the instructions. What you need
to do is take a copy of the Navision program folder and call it
something else, like \Navision Test\.
Delete the dbms.zup from the test folder and then in *that* folder do
something like this:
server servername=INSERTSEVICENAME, database=e:\part1.fdb+f:\part2.fdb
+g:\part3.fdb, cache=850000,
commitcache=yes, installasservice
Do not run this command in the original Navision folder!! That
command will install a new service (call it whatever you want). You
just need to point it at your copy of the database. Set the cache= to
something very low so your server doesn't run out of memory (ones of
the reasons not to do it on a production server). You don't need a
lot of cache on a test database.
Ah, maybe that's the problem. I'll try another folder.
I can get both services installed, but I can only have 1 running at a
time.
I created a second copy of c:\navision\* and creatively called it c:
\navision2\
Then used:
server servername=nav1, database=c:\navision
\database.fdb,cache=850000,commitcache=yes, nettype=tcp,
installasservice
server servername=nav2, database=c:
\navision2\database2.fdb,cache=850000,commitcache=yes, nettype=tcps,
installasservice
Did I miss something?
Does your server have enough RAM to run two copies at 850Mb each? Try
experimenting by changing the cache= to something very low, say 50000
instead.
Sorry, that was a bad copy / paste on my part. The first instance is
using 256MB, the second is using 32MB. The server has 1GB of physical
RAM.
Are they running on different ports?
TCP & TCPS - figured that would be enough? Perhaps not :)
Have you edited c:\windows\system32\drivers\etc\services ?
I assume that one of the services is running on the default Navision
port, add the following to the END of the services file for the test
service (NAV2?).
nav2 60000/tcp # Navision Test Server
Start the Nav2 service and it will be running on TCP port 60000,
change the details of what port you want as you wish.
Forgot you are on Nav 4. You may wish to use tcps rather than tcp.
If you use tcp then you will have to change your clients so that they
also use tcp, no big deal, but worth a mention.
I added:
nav2 47555/tcp #TEST
and changed it back to use TCP rather than TCPS.
Are you saying both services are now running?
No, I can still only start one or the other.
The only thing I can think of is add an entry to the c:\windows
\system32\drivers\etc hosts file.
192.168.1.1 nav1, nav2
Change the address as required. I am assuming that nobody is using
the Navision database as you play with it.
I have a couple of servers here that are running multiple services for
Nav3 and Nav4, so am a bit puzzled. Try this and if it doesn't work
I'll type some step-by-step instructions.
server servername=COPY_server_Name, nettype=tcp, cache=64000,
commitcache=yes, database=D:\Test-Folder\Database\database.fdb,
installasservice
After you may use MMC-console for correction anothe parameters.
And you will use 2 servers simultaneously!
Fantastic, I will try that. Thank you very much for all the help!
OK, now I am getting:
"The operating system can not gain access to the file: c:\navision
\database.fdb"
On both, bot the services are running...
You don't have both services pointing to the same data by mistake do
you?
I'm leaving for the day now, if I remember I'll check back tomorrow.
No problem, thanks! I'll try again from scratch.
Savatage wrote:
> Here are step by step instructions
> http://www.mibuso.com/howtoinfo.asp?FileID=10
Don't use registered ports like 3100. Go a lot higher than that, an
easy starting place to remember is 50000.
It doesn't explain how to have more than one database part on
different drives when using DATABASE. It is as follows...
database=e:\part1.fdb+f:\part2.fdb+g:\part3.fdb,
You also don't need to do DATABASE="C:\db\CRONUS\N370 W
\DBServer370\N370 W.fdb" because you are creating the service in the
folder where the server.exe is. All you need is the DATABASE
parameter shown above.
If you made a mistake or want to make a change, rather than change the
start-up parameter as the document suggests, you would be better doing
an uninstallasservice, it only takes a minute to do it properly. It
also makes no mention of the dbms.zup file, which can cause problems
if not deleted before doing the installasservice.
A tip, when doing the hosts file, you can actually do this:
127.0.0.1 CRONUS370IT, CRONUS370W1, CRONUS370AIT, CRONUS370AW1
Other than that, it's about right.