Sage 100

Running into an error when trying to install 2013 on a customer's server. I've been working with Ronnie Aspe on the error but he's stumped. The server is 2003 Standard SP2 with 4GB of RAM. I'm installing it logged in as the administrator and have unloaded the AV (TrendMicro) and all other background programs. I've also downloaded another 2013 image from Atlas, just to be sure the original one was not corrupted. All of the installation prerequisites have been uninstalled and reinstalled.

@JohnShaver sorry but I got that error in 4.5 and it was the service pk not sure what it can be for 2013.

The closest I got was with a SY_Migration on 4.5 as @DianeRuth mentions - here's my note in the group KB - https://www.evernote.com/shard/s1/sh/3492f9d9-2d43-46cb-9e2e-4b26f69d47f5/b6d9d88e7262d1718220c314d7374418

I saw those articles about 4.5. The problem is that I can't get 2013 to even install, much less put on a product update.

I'm sure you have done this but just making sure ""running as administrator"" ? I know you said you were logged in as admin but that running as administrator gets me every once in awhile.

+1 Diane - I've run into this recently as well. Some installs even though you are admin still require ""run as admin"". No idea why.

Yes, I have. We've tried pretty much everything. UAC is turned off as well. This is one of the stranger ones that I have seen in quite a while.

Any mention of the error in Event Viewer?

No mentions that I can find.

Are you installing to a mapped drive by chance? I'd also try deleting sy_installation.pvc from mas90/soa folder, and reinstall. Have you looked for error details in the sy_installationxxx.log file in mas90\mas_system folder?

No, I'm installing it directly on the server. After each uninstall, I've been deleting the entire MAS90 folder. The log didn't shed any light either.

Install again. When you get the error, reboot the server and copy a stock 2013 installation over the recently installed mas90 folder.

I'll give that one a try, Mark. Thanks for the suggestion! Well, I'll try it as soon as their IT folks unlock the file transfer option in logmein.

Circling back to this. I was finally able to schedule a day with the customer to try @MarkKotyla 's suggestion. It worked perfectly.