Sage 100

Upgrade from v450 Std. to v2016 Std. Customer has laptops that when not connected to the network when booted pop up an installer screen that says on window tittle ""Sage 100 Standard 2016 Workstation"" and the message reads ""Please wait while Windows configures Sage 100 Standard 2016 Workstation"" as if its trying to install a workstation. No issue if connected to the network. Issue did not happen with same laptops that had v450 workstations (still) installed. Client says can smack down the screen about 11x and it will finally stay closed and let them do whatever offline task they were firing up for but its annoying them. Does anyone know how to stop this behavior (besides keeping the laptops connected to the network). Thanks in advance for any insight.

The Workstation Setup client installation was not installed correctly: A specific set of DLL (Dynamic Link Library) files .dll's are not properly installed or registered Resolution Possible Resolution 1: Locate the following DLL files and manually register them with the operating system: ?bsConfig.dll ?bsRegistration.dll ?bsStartPageHelper.dll Note: The DLL files listed should be located in ""C:\Program Files\Common Files\Sage\Sage Common Desktop\1.0"" (or ""2.0"" on later versions). For more information on how to register DLL files, see the Related Resources section below. Possible Resolution 2: Reinstall the workstation client installation as the Administrator with the following disabled: ?User Account Control ?Firewall ?Anti-virus software Note: The DLL files listed should be located in ""C:\Program Files\Common Files\Sage\Sage Common Desktop\1.0"" (or ""2.0"" on later versions). For more information on how to register DLL files, see the Related Resources section below. ID:50277Last Modified Date:8-5-2016

I was thinking too Wkstn Setup did not install correctly and maybe you do it again but look at the log it creates for errors. Also I like installing by rt-clicking the MSI and choosing Install.

I always install ""As Administrator"", using the autorun so prerequisites are included. I've also seen some folder redirection settings do some strange things. Was any part of the workstation software installed to a network path?

This turned out to be Outlook Messenger set to fire up on startup was actually triggering the Sage 100 workstation installer when booted up offline. We disable the Outlook messenger from auto startup and this resolved the issue. I still don't know for sure what caused it, maybe a PID conflict or some oddball thing. We are able to launch the messenger manually so this is the workaround. Thanks for your input, this was a red herring case.