Sage 100

Upgrade from v4.05 standard on 2003 server to 2017 premium on 2012 server. The 2003 server crashes every 5 minutes and we are desperately trying to get 2017 up and running by tomorrow. SQL 2012 is installed. Trying to install Sage 100 2017 premium. After entering the unlocking information, the files start copying and a file copy error 1310 pops up then a 1304. I ignore the 1310 error then get the error 1304. The only option then is abort or retry. Retry only re-displays the error. I have tried installing as both local administrator and domain administrator. Everyone has full control over all folders in E:\Sage and below. Some of the files copy then the installation stops on one file. Any ideas? I talked to Sage today and they escalated it to a return call tomorrow afternoon. I would like to get this resolved before then.

WINDOW SERVER 2003 isn't support anymore. Can you upgrade to to 2008R2 or better.

This is Windows server 2012 R2.

Soory I misread that. ... Can you try install into a different folder I also recommend downloading a new copy and try from a different folder

Thanks Jim. I am going to copy a new folder of 2017 programs that I know work (instead of using the programs I downloaded from Sage today). I have already tried changing the folder name. I originally used Sage\Sage100v54\MAS90. This is my standard naming convention and have never had an issue. I changed it to Sage\Sage100v2017\MAS90. Just to eliminate this being the issue, I am going to rename it again not using numerics.

As a side note, when the error displays and I look in the folder the file is writing to, there are several files there that were previously written during the installation. If this were related to permissions or to the folder names I would expect no files to be written in the folder.

Look at permissions on the local c drive on the sql server as well. Look at the file locations where sql log files are writtten. Sent from my cell phone. Please forgive any misspellings.

Got this solved a few minutes ago. Posting this in hopes it will save others some grief. The issue was caused by malware protection. After the malware protection was turned off the installation completed successfully. The malware is a feature built into Windows File Server Resource Manager. It is used to block evil software with file screens that look for certain types of files that ransomware tends to use.

We should have a separate discussion topic on how FSRM (File Server Resource Manager) works, how to configure it. I've run into it several times this year but rarely from years past. Doug it sounds like it was preventing copying M4P files because FSRM had a file group filter for music file extensions. I have run into just that applying a PU. The latest file group filters for FSRM on Server 2012 include Cryptolocker ransomware groups. Few months ago we had a customer using iSales and it partly uses BOI. It was working fine for years then suddenly on a Monday it stopped. Traced it down to FSRM preventing creation of ZZZ files on the D: (data) drive where Sage was installed (not just ZZZ but the relevant one here). Learned that BOI itself creates a temp file in \mas90\Home\Lib with a ZZZ extension (when it does the oScript.Init). The simple experiment of creating a TXT file in \Lib and renaming it to ZZZ failed as well as just copying a ZZZ file to \Lib folder. Removed ZZZ from one of the Crypto file groups and everything started working again (not a permissions issue). Explained it to IT who said ZZZ was one of the dozens of cryto variants and why they turned on FSRM. They found an an alternate for ZZZ but the dozens of other Crypto variants are still monitored by FSRM. @MoiraGoggin I can create a KB style article for Evernote on this if you like.

@AlnoorCassim absolutely! Thank you so much.

Thanks for the input Alnoor. This was a tough nut to crack. I will be on the lookout from now on.