Do a full uninstall/reinstall

Hello Jay. I just did as you had suggested but am still coming up against the same problem.

This is the full details from the Event Log:

Faulting application name: accpac.exe, version: 6.5.0.0, time stamp: 0x59778a7b
Faulting module name: MSVCR120.dll, version: 12.0.40649.5, time stamp: 0x56bc018f
Exception code: 0xc0000005
Fault offset: 0x0000f26d
Faulting process id: 0x638
Faulting application start time: 0x01d8e955562acc37
Faulting application path: C:\Program Files (x86)\Sage\Sage 300 ERP\Runtime\accpac.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCR120.dll
Report Id: cc0e06ec-5549-11ed-81da-6c4b907a198f
Faulting package full name:
Faulting package-relative application ID:

Hello Jay. I just did as you had suggested but am still coming up against the same problem.

This is the full details from the Event Log:

Faulting application name: accpac.exe, version: 6.5.0.0, time stamp: 0x59778a7b
Faulting module name: MSVCR120.dll, version: 12.0.40649.5, time stamp: 0x56bc018f
Exception code: 0xc0000005
Fault offset: 0x0000f26d
Faulting process id: 0x638
Faulting application start time: 0x01d8e955562acc37
Faulting application path: C:\Program Files (x86)\Sage\Sage 300 ERP\Runtime\accpac.exe
Faulting module path: C:\Windows\SYSTEM32\MSVCR120.dll
Report Id: cc0e06ec-5549-11ed-81da-6c4b907a198f
Faulting package full name:
Faulting package-relative application ID:

Don't know if this is your issue exactly, but the file MSVCR120.dll is part of the Microsoft Visual C++ 2013 Redistributable Package.  

Download and reinstall that and see if that resolves your issue.

Which version, Andrew? 64 Bit or 32 Bit?

As Sage is a 32bit application, I would go for the 32bit

Thank you very much, Vega. The WSSETUP on the Server itself resolved the issue by installing the Microsoft Visual C++ 2013 Redistributable Package. I must admit I have never had to run the WSSETUP on the Server since I am always able to open and test the installation successfully. I am surprised though why the FULL uninstall/reinstall didn't address the missing component.