Sage 100

Working with a client on upgrading to Sage 100 2016 on Server 2008. We have an issue where the installation fails and stops due to the certificate not being validated. Sage support has duplicated the same issue and right now the recommendation is to update to Server 2008 R2 but they are still waiting to see what engineering says about the issue.

Without knowing the exact error, this is just an FYI / WAG - https://www.evernote.com/l/AQ6ZHxLolHtDuZ9dX3FRb7eSVVeKWaheIX4

oh how I love a product with no beta cycle!!

https://www.evernote.com/l/AQ6EOx1898tBebrS4oHNNmdsTHOOWpGvGgA

Love their solution - Upgrade the server OS....

I had a customer call me yesterday to say they had called Sage because their FAS update wouldn't run. Long boring story short - Sage looked at the install and deemed it incompatible with the OS. What really happened is the customer downloaded the crappy installer that queues the download and that's what was hung. I always try for the direct download - which worked like a charm.

I just called Sage today about the certificate error I was getting installing 2016 and Server 2008 SP2 (NOT R2) and support said it was considered a bug and would be fixed. So don't upgrade your OS yet! Maybe wait a week or 2.

@MaryMays - thanks for the update. I was expecting a call from the Sage tech today but it never took place.

Anyone know if this has been patched? I can't find a fix on the KB. Have just wasted 2.5 hours on it!!!!!! What a bunch of **&^%^$##%*()()*&^%%$$$$%^^&**((()(**

This just in...... There is NO JOY in Mudville tonight. The mighty Sage strikes again!!!!! Sorry for that frustration Jeff. After fully researching the issue, a decision was made to **not support Server 2008 with Sage 100 2016**. Note that 2008 R2 will still be supported. An update to the SPMs will be posted shortly, and under the Not Supported section, some explanation behind the decision Windows Server 2008 As a result of Microsoft's decision to no longer trust any code that is signed with a SHA-1 code signing certificate (see Microsoft Technet Article 32282), beginning in November 2015, Sage 100 began upgrading its product installers to use the more secure SHA-256 certificate. Issues have been reported with SHA-256 certificates on Windows Server 2008 (see Microsoft KBID 2763674) Note that Windows Sever 2008 R2 is supported. The KB will be updated as well.

Wow and double wow! Now I get to go and sit in front of a client and tell them the wonderful news. @JeffSchwenk do you have the SPM before this one updated on 11/25 which shows that Server 2008 is supported? I sure would like to have something in my hands to give to the client showing the before and after.

Here is what I downloaded a couple weeks ago from the v2016 download site.

Thank you for keeping it and now sharing it.

OK, I dug a little deeper into what Sage is trying to get me to drink. In the new SPM where they are stepping away from WIN 2008 SP2 support, there reference a MSFT KB as their source for refusal (below). In fact, it appears that the KB is a patch needed so that SHA-256 certificate CAN be read by the recalcitrant OS. Am I reading it correctly? If so, why on earth is Sage stepping away from its support???? https://support.microsoft.com/en-us/kb/2763674#%2Fen-us%2Fkb%2F2763674

You go @JeffSchwenk

so @JeffSchwenk were you able to install the patch referenced and then get Sage 2016 to install without error?

What? **ME** be the guinea pig??? I thought that is why we pay SAGE the big bucks. Waiting for clarification from Mitchell Jagosz

We have a customer to upgrade from 4.5 and we recommended 2015 at this point. They want to know when they should go to 2016. My current answer is not before Q2

From Mitch Jeff, in our testing on a number of Windows 2008 Servers up through Server 2008 SP2, applying the fix listed in the article, and/or applying the latest SP and/or MS update which includes the fix, did not resolve the issue. Investigating a number of ""workarounds"" suggested on various articles for the ""Error 1330 During Installation"", also did not resolve the issue. Knowing Microsoft's decision regarding SHA-1 and the fact that Server 2008 is now in Extended Support, all lead to the decision to not support it. In testing we were successful in using the same installer and build on Sever 2008 R2 (as well as the newer Client and Servers), so we maintained support for it.

So I guess we are still back to having the client upgrade the OS or install 2015. However the client feels that they pay maintenance on the software and since it was supported at the time Sage released it on the OS they were using, they want Sage to correct this. It's going to get interesting since this client has 5 attorneys on the board. I'm just going to watch.

Gotta know when to hold them, know when to fold them, know when to walk away......... I asked my IT guy about upgrading to my server to 2008 R2 and he is suggesting 2012 R2..... Really big sigh...

I've done 4 successful installations and conversions on 2012 R2 on new servers so far (2 are live - I know... dicey but the clients INSISTED. Thanks so much to Sage for sending emails to the clients about 2016 release!). Server 2008 SP2 was released in 2008, so unless they downgraded, the server hardware will be old as well and ready for replacement by our recommendations.