We have a customer that is running navision attain 3.60 server on a windows 2000 box. They recently ran windows update and rebooted the machine. Now the Attain service will not start. The service is set to automatic but apparently doesn’t start on restart. When I try to start it manually I get this error. Could not start the Navision Attain Database Server SERVERW2K service on Local Computer Error 1: Incorrect Function Anyone have any ideas on how to fix it. No updates or changes have been made since the reboot.
Have a look at Event Viewer what it says. Reinstall service … go to server directory and run command [i]server unsinstallasservice[i], reboot PC, and run again [i]server installasservice[i]. Maybe will help.
Arthur, I followed your suggestion and there is no change. I still get Error 1: Incorrect function. However in the event viewer under application I have this warning message before the error The operating system returned the eror (87): The parameter is incorrect.
Ok, I’ve found the solution. I deleted the zup file in the server directory and then created the service. The service created fine but didn’t start. However it did let me start the service as long as I started the service before trying to connect locally to the database file. Personally I think way to many things are fixed by deleteing the zup file.
This is a security issue (yes I know you don’t want to believe that). Deleting the zup file, was not the solution, just a coincidence. Basically there is a problem in change of ownership of the navision folder. There are basically 5 ways (that I know) to fix it. 1/ Start the server from a dos prompt, in this case you own the session, so it works fine, but is a useless solution, because you can’t use the service. 2/ Create a new folder use dos naming conventions, 8 char and no spaces, and put db there (f:\navi\db.fdb). 3/ Start navision without a database, then connect to the database after the server starts from the client. Not recommended, since a user could accidently change databases. 4/ use regedit, and put the database name in full quotes (database=“f:\program files\navision server\my database.fdb”). Only if you know and understand regedit. 5/ Format and reinstall windows. good luck.
David, On your fourth solution what key would you put the database name under?
I was running into the same error, different situation but same error. I found that the system was trying to load too many kb into the commit cache. I used the MMC snap-in, reduced the amount of commit cache it wanted to use, and BAM! started the service. Good luck, I hope it’s fixed by now!
Sandy - Yes, the cache error can occur on some machines when you try to load more than 400meg cache, and activate commitcache. Regedit will not help here, though an OS re-install sometimes does. someguy - install the server as a service, with the correct db. The service will be installefd, but stopped, now just fond the db ref in reg edit, and fix the quotes. then rrestart. Note this does not always work.