Hi, Still no official line on using MICROSOFT Business Solutions Navision with MICROSOFT Small Business Server 2003 (YOU GET THE POINT![;)]). I believe that Navision would not “support” SBS 2000 implementations. Does anyone one know if this has changed since Microsoft acquired Navision? Is anyone running Navsion native or SQL option in SBS 2003 (or 2000)environment? What are the limitations/problems if any! Thanks for any comments!
Hi, It will work on SBS 2000. Still there is no support for navision SBS 2003.
I have a successful install of Navision on 2003, however, not with the SQL option. No problems so far and they have been live for about 6 months and have even been upgraded from 3.6 to 3.7.
i have successfully installed navision 4.0 on sbs 2003, but i continue to get an error, the error is a tcp/ip when trying to connect using windows authentication. when i use database authentication it works fine but when i try windows it gives the tcp/ip econn error and it stops the server service. i have not been able to find a fix for this. i am trying to work with microsoft but they havent come up with a solution yet. has anyone come across this situation before.
thrustuha: Have you looked at ‘Update 1 for 4.0’…? http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=13228
quote:
i have successfully installed navision 4.0 on sbs 2003, but i continue to get an error, the error is a tcp/ip when trying to connect using windows authentication. when i use database authentication it works fine but when i try windows it gives the tcp/ip econn error and it stops the server service. i have not been able to find a fix for this. i am trying to work with microsoft but they havent come up with a solution yet. has anyone come across this situation before.
Originally posted by thrustuha - 2005 Mar 15 : 16:48:49
I had this same problem, to get around it without appling sp1, I did this. Try to connect using windows authentication. Server service stops, ect. . First Restart the service, then back on the client you will have the open database box window, Click on advanced tab, and it will have TCPS rather then TCP, Even though your startup icon had TCP, change it back to TCP. and close the box. Now use your icon to start the client again and it should connect. Not sure why this works but it does. It is a pain, but it works and you should only have to do it once for that client. In our case it is better then, upgrading to SP1, or paying our provider to apply a fix.
What about running the server on TCPS? wont that be easier? Also keep in mind that SBS is not an ideal platform for Navision, unless it is a very small implementation. You just have too many things running on that server to make it a proper Navision server. Hardware costs are so low these days, that its hard to make a case for not outting Navision on a dedicated server.
David is right regarding the hardware costs. Windows 2003 Server is more expensive [;)]
quote:
What about running the server on TCPS? wont that be easier? Also keep in mind that SBS is not an ideal platform for Navision, unless it is a very small implementation. You just have too many things running on that server to make it a proper Navision server. Hardware costs are so low these days, that its hard to make a case for not outting Navision on a dedicated server.
Originally posted by David Singleton - 2006 Mar 09 : 15:01:51
It is my understanding the Navision doesn’t run reliably on TCPS, on versions prior to 4.0 SP1, so unless you are ready to upgrade TCPS is not really a good option. I agree on not running Navision on SBS, hardware is cheap and small business server slows to a crawl on many occasions, such as doing a virus definition update (at least our Sabari Antivirus solution uses a lot of resources) My ideal platform for Navision for a small office with remote branches, ( which is us) is a SBS running email, file sharing, firewall, a second machine running Navision database server and a third machine running terminal server. Although you can easily load the Navision database on the terminal server, we ran the two together for many years supporting 30 remote users very well. But hardware got so cheap, we added the separate terminal server. I just bought a second terminal server machine off of ebay, a quad xeon machine with 4 gig ram, and 6 – 36 gig scsi raid configuration for $300. It is not the latest machine, but it is more then powerful enough to support terminal services for 30 users.