Okay, so here’s the situation. We originally installed Server 3.10, and then a few months later Server 3.60. Now the Server 3.60 was running a little sluggish and I have determined that it partly hardware (a whole nother story) and software (the commit cache was not enabled). So I tried to enabled the commit cache, and unfortunatly I could not load the MMC snap-in. So I thought I’d uninstall the Server software and re-install it (thinking it’s an install error). Now that I’ve removed it and reinstalled it won’t load the service! PLUS I had to create a new Server name b/c it said my old was already been used. ??? I’ve tried to reboot the server hoping that it would pick up the service but I get nothing but a big fat error in my Application Log. (The operating system returned the error (87). I’m running Small Business Server 2000 and haven’t had any troubles except the the commit cache and MMC snap-in thing, and now it seems I’ve got a REALLY big trouble. Help, anyone, I need to have this back up and running ASAP! oh, and Happy New year!
Open a command prompt in the server directory. Type SERVER.EXE SERVERNAME=MyServerName, UNINSTALLASSSERVICE for each server that appears in the services list. Now You server(s) should be uninstalled as services. After that You can uninstall the server files from “Add/Remove programs” ands start all over again.
Is there any reason why I can’t install my 3.7 Server and still my 3.6 clients?
The Management Console problem could be down to the 3.60 RTM install bug, whereby the wrong msxml.dll file is registered at installation time. If so you need to register this dll again which resides in the /windows/system32 folder by executing regsrv32 msxml.dll. Management Console (using any content) is then up and running again. Server-client compatibility depends on the changes made in each version. E.g. in 3.60 the layout of the roots in the database to support the AutoIncrement feature, were changed and the server/clients changed accordingly. It meant that 3.10 clients couldn’t connect to that server. As far as I remember there was no such type of change for 3.70, so 3.60 clients should work ok.
OKay, so uninstall went great, smooth as glass. BUT, I reinstall the server…ok…but when I go to start the Service I get an error … Could not start the Navision Attain Database Server HEAD-OFFICE-SVR Service on local computer. Error 1: Incorrect Function…and Application Log shows …The operating system returned the error (87)… suggestions?
Problem Solved! As it turns out after I re-installed everything I could run the MMC snap in, and Navision had defaulted all of my available RAM to the Commit Cache, and since this is over 1GB the service didn’t want to load. So I lowered the commit cache to 500MB and BAM! everything loaded up just like it was meant to be. Thank you all for you help! BTW. I tried to run 3.7 Server and 3.6 Clients on another setup and it didn’t seem to like it too much. I received an error on the client side. Thanks again. Happy New Year!
Hi Sandy, I hope you know what you are doing ! 500 MB data which can be corrupted cause they are not written to disk is a very high risk ! I wouldn’t do this
quote:
Originally posted by iammicky
Hi Sandy, I hope you know what you are doing ! 500 MB data which can be corrupted cause they are not written to disk is a very high risk ! I wouldn’t do this
… without an UPS!
The data can not be corrupted! The only way this might happen is if you were to set write cache on the hard drives, or some other such sillyness. Navision uses the version principle even when using its commitcache. You will NOT corrupt data if you have a power failure.
Ofcourse my server is power protected (I wouldn’t be very good at my job if I didn’t insist on it). Opinions: I keep reading all over the Navision manuals etc. that you allocate as much as you can to the commit cache. Is this the right thing to do?
You can use up to 1Gb for cache as long as You leave enough RAM for OS and other applications that are running on the server. The only downside with a large cache is that the first logon will take longer time since the server fills the cache for the first login.
Lars, I thought the Delay is Windows allocating the ram to the server service? Sandy, please be aware that Navision’s version principle will NOT allow the database to become corupt, you may loose some information, but you can feel safe that if you have followed Navision’s recommendations, then even without a UPS and a power failure, your data will not corrupt.
Sorry for unexact : i mean “losing data” not “corrupt data”