Sage 100

I have a customer I am trying to upgrade to Sage 100 2016. I sent IT the SPM and was told we were good. Now, when trying to install the software, we are getting an Error 1330- ""Error 1330"" when installing Sage 100 2016 or 2017 on Windows 2008 SP2 and Windows Vista ""Error 1330. A file that is required cannot be installed because the cabinet file C:\...\data1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. Error 24592 was returned by WinVerifyTrust"") Turns out IT didn't look past Windows 2008 to see if the server was SP2 or R2. Of course it is SP2. IT says they have downloaded the update package from Microsoft's web site and it didn't work. Does anyone have a way around this error? TIA.

Deal breaker. We've halted upgrades for this (2008, not R2) until the customer had a supported server operating system.

I've had to halt an upgrade due to this.

Ditto to what Kevin and Ron said. The compatibility matrix dated 11/5/15 shows it's supported but the one dated 11/25/15 shows it's not.

Are you sure it is 2008 R2 and NOT STD??? 2008 Std has been a non starter since day one. I had to delay install v2016 on my 2008 std server for five months until I could get it upgraded to 2012 R2. A royal PTA since my server support is 900 miles away. I had to back it up, box it up and ship it out. Went on a week long vacation. Three days after I returned, it was on my front door (yes, there is a long story behind this). I have several people on 2008 R2 running it without issue.

They are running 2008 SP2, not 2008 R2. SP2=bad, R2=good. I was hoping there was a way around bad.

Where are they coming from? Can you put 2015 on? Not sure SP2 is supported with 2015 either. It buys them a year if currently unsupported.

It sounds like it was standard with Service pack two installed. A no go until they swap out the server OS.. Here is probably the earliest thread on this. Numerous quotes from Sage tech support. https://90minds-com.socialcast.com/messages/27703459?ref=stream

We have been burned by the same mistake by client IT personnel twice too! SP2 instead of R2

Please take 30 minutes a couple days before an upgrade to verify what IT told you is accurate and ensure your login credentials have the admin rights they promised. It'll be the best investment you'll make.

I too was hit with this. I believe it was Server 2008 and it was a hard stop. I don't recall getting this error but no pre-requisites would install and even some tools like Dropbox wouldn't load. I tried going onsite with a USB drive but that did not get me any farther. As @MarkKotyla suggests, it's a good idea to verify what IT has established. I do quite a few upgrades remotely and I start them all off with installing Dropbox for my needed files so usually if I'm getting warnings that DB won't install I know there's a big problem with the server OS off the bat.

I pretty much always do the server software install remotely (often including a test / system migration) days before any planned live upgrade.

Thanks everyone. We are going to upgrade to 2015 instead of 2016. The knowledgebase says the issue is with 2016 and 2017. BTW, does anyone else have a problem constantly converting Sage versions? IE, 5.20 = Sage 20What and 5.30 = Sage 20What?

One more little thing for us to remember @JaneCavanaugh.

I always have to start at the beginning - 5.00 = 2013, 5.10 - 2014....... At some point my brain spots the pattern.

I have a post it note on my wall with the conversion! :)

I just click Help - About... since both numbers are shown on that screen.

I have the conversions on my whiteboard.