I am currently running Sage 50 CDN 2016.1 on a MS Windows 2012-R2 server with absolutely no issues!

Thanks, I am trying to get a company to upgrade from Sage 50 2013 since I am having problems getting it running on windows 2012

What problem are you having with Sage 2013 running on your MS Windows 2012 Server, I had problems with that version due to the 6 TB hard drive on the server was too big and Sage 50 did not see the disk space as usable ( think it was due to the sector size)!

Hi Bruce, I installed the server component and added the exe for connection manager to the firewall allow list. I am getting network errors. I turned off the firewall as well and still get it. Is your Sage 2013 running fine? Did you have to change the sector size?

In my case it was due to the version of MySQL that was being used in the 2013 and possibly 2014 and earlier versions of Sage not supporting the very large size of the hard drive that I had on my server. I worked around it by creating a virtual server using Hyper-V and making a smaller virtual disk that was recognized by MySQL. I believe that stating with the 2015 version of Sage it now recognizes the large Hard Drives and I have stopped using the virtual server and I am now running directly from my 14TB Raid 5 server drive ( I had earlier said that it was 6TB - which was incorrect).

Can you tell me what the exact network error message is that you are receiving?
How large is your server Hard Drive? If it is very large you might be able to work around the large Hard Drive issue by installing a second smaller drive to run the Sage data files on! This assumes that you have HD space and SATA connections available in your server (I did not so it was not an option for me at the time I was trying to run Sage 2013 on my 2012 R2 server)

Have you looked in the "errorlog.txt" or "ExceptionError.log" files to see what errors are shown there also (The files are located in your acountname.SAJ folder?

I am no longer running 2013 I am running 2016.1 as stated in my first reply (I am on a support/maintenance contract and keep my system current)!

Hi,

We have been using Sage 50 on Windows Server 2012 since early 2013 with no problems. We are using 1.3 GB of a virtual server's 126 GB volume, and have the cache set at 1536 MB for better performance. All the workstation client can 'see' is an IP address and a port number.

Sometimes, 'Support speak' for "Not supported" is better translated as "We cannot help you fix that", as with Terminal Server.

http://www.sage.com/ca/sage-50-accounting/lp/sysreqs

• 256-colour or higher SVGA monitor, minimum resolution of 1024 x 768
• CD-ROM drive

Not specifically stating that Sage 50 Canadian can use Windows Server 2012 as the data storage point, is probably just out-of-date documentation.

Unless you found somewhere that stated that Sage 50 Canadian wasn't supported on Server 2012?   Because I don't see that.

Hi,

We have been using Sage 50 on Windows Server 2012 since early 2013 with no problems. We are using 1.3 GB of a virtual server's 126 GB volume, and have the cache set at 1536 MB for better performance. All the workstation client can 'see' is an IP address and a port number.

Sometimes, 'Support speak' for "Not supported" is better translated as "We cannot help you fix that", as with Terminal Server.

http://www.sage.com/ca/sage-50-accounting/lp/sysreqs

• 256-colour or higher SVGA monitor, minimum resolution of 1024 x 768
• CD-ROM drive

Not specifically stating that Sage 50 Canadian can use Windows Server 2012 as the data storage point, is probably just out-of-date documentation.

Unless you found somewhere that stated that Sage 50 Canadian wasn't supported on Server 2012?   Because I don't see that.

Thanks, my client just purchased the 2016 with support, so I suspect all my issues will go away now. Thanks for the feedback everyone!
Matt