Hi. A couple of days ago, I had trouble installing the Attain Server. The server is a Windows 2000 Server with all the latest SP and hotfixes. Nothing else installed in the server, just waiting to become the Attain Server. After installing from the CD, following the same steps I always do when installing a server, everything went fine. I made a reboot, and in logon window, a window saying an error ocurred and to check out the event viewer. In the event viewer the Server didn’t start. I went to Services, and tried to start it manually - I couldn’t. Although I was logged on as administrator, it said I hadn’t the permissions to start the service [:0]. After uninstalling and installing a couple of times and the error remaing, we installed it without using the setup.exe from the CD. We installed it via command line through the server.exe command. That solved the problem. [;)] What in the world went wrong with the setup? Anyone experienced something similar to this? Regards.
Bruno: I have a similar problem as the one you are reporting. We are using a Windows NT 4.0 server. First I installed NAVISION 3.60 with the setup routine from the NAVISION CD. It works fine and the NAVISION 3.60 has started automatically when the installation has finished. When terminating NAVISION 3.60 server via services I cannot restart the server, always getting system error #1. Restarting the physical machine also starts NAVISION 3.60 server correctly. After terminating NAVISION 3.60 server via services I receive the same error as mentioned above. Reading your report I deinstalled NAVISION 3.60 server with the deinstallation routine and installed it without using the setup.exe from the CD. As you did I installed it via command line through the server.exe command. After the installation I could start the server without any problems. A restart after a previous shutdown failed. After deinstalling the NAVISION 3.60 server and a new installation via command line produces the same result. I did the command line installation with a copy of the directory of the previous setup.exe-installation. The output of the command line based server installation displayed a high value of cache buffer (sorry, didn´t record it). So I deleted the DBMS.ZUP and again started the command line based installation. Voilà! Now I can stop and restart the NAVISION 3.60 server repeatedly without any problems. Here are the command lines I use: InstAsService.bat “D:\Programme\MS Navision 360\Database Server\SERVER.EXE” database="D:\Programme\MS Navision 360\Database\database.fdb, nettype=tcp, servername=msnavision360, installasservice UnInstAsService.bat “D:\Programme\MS Navision 360\Database Server\SERVER.EXE” database="D:\Programme\MS Navision 360\Database\database.fdb, nettype=tcp, servername=msnavision360, uninstallasservice StartServer.bat NET START “Navision Attain Database Server MSNAVISION360” StopServer.bat NET STOP “Navision Attain Database Server MSNAVISION360” Regards Alarich
Hmmm… interesting, Alarich. I don’t recall the values we put in cache, but maybe those values are different from the ones suggested by the setup, which were unabling the start of the service. Thanks for your input. Your command lines are usefull to anyone who must install a server via command line. Regards.
It’s about the cache size. Attain is computing the cache size and it write this in your instalation. So, try to use cache smaller than 900M, I think 850M will work OK. Try different values. Un saludo de mi querida España.
Thanks everyone.[:D] I was having the same problem. After doing the install the service wouldn’t start at all, giving a helpfull ‘Error 1, invalid function’ message. I followed your instructions and sorted it out by changing the cache to 800Mb. When I originally installed it, doing a ‘Custom’ installation it asks for a cache size, suggesting 2.7Gb on my system. This is Ok, as the server has 4Gb of RAM but obviously Navision can’t handle this. It didn’t work with 1Gb either but it works Ok with 800Mb. I wish Navision Server wouldn’t do everything in KB, makes everything a bit long winded.
quote:
Originally posted by bogdanc
It’s about the cache size. Attain is computing the cache size and it write this in your instalation. So, try to use cache smaller than 900M, I think 850M will work OK. Try different values. Un saludo de mi querida España.
[:D][:D][:D][:D][:D]
Just my 2 cents, 1GB cache (out of 2GB) works on a W2K server with SP2 installed. Navision Server installed with the setup procedure from the original CD (DE-Version). May be the latest SP?
Hi I have a similar problem with Navision Server 3.60 (the service fails to start), but when I use the command line to install and start it, then I get the message: ------------------------- The date is not valid – Press any key -------- What could be wrong?