Sage 100

Trying to do a test upgrade of a 4.3 customer. Customer had CRM setup as a test by mistake from prior support (not EES). 2013 required CRM (in Sage) be uninstalled, which I did. Now 4.3 won't go past login screen - main screen flashes briefly and dies. Made a copy of 4.3 folder on new server and tried upgrade from there and it fails saying someone is running something. Apparently there is a file I need to kill somewhere, but no idea what file. Any ideas? Oh, one more thing - can run Administrator mode just fine.

There are services for both CRM Integration and MAS90/200 Integration services. Are both off?

All I see is Integration Engine - there are 2 for some reason, and they are both off. What is the CRM called?

CRM Integration Service"". There are 3 others that begin with ""CRM"" but I believe they are for more current versions. Running out the door. Good luck

OK, that didn't help. Any more ideas?

Ah, I just restored from the backup and will try it again tonight. Grrrr.

For Win Server 2008 - Start, Right click on ""Computer"", Manage, Roles, File Services, Share and Storage management, Manage Open Files. Close any open files.

@DougHiggs - I had done that, too. My restore ended up putting the MAS back where it was, and I was able to uninstall CRM again and it still worked. And I copied back the data files from this morning (vs last night's backup) and it STILL worked. But then I copied the folder back over to my new server and did the test upgrade there successfully and when I try to open Sage 100 2013 after the upgrade - now IT CLOSES. I want to hurt something.

How are you copying the files over? Using the network? Also, are you running wksetup after the installation?

Copied over the network, had run wksetup on original 2013 setup, but not since 4.3 files copied over.

Try running wksetup on the new installation.

Oh, joy! Have this happening on another 4.3 install, but nothing done to this one. Just up and fades away this morning, at both workstation and server. No upgrade going on, etc. Have renamed SY_Workstation, put out a new SY_ModuleDate, reran WKSETUP on the server... Nuttin', honey. So, any more suggestions? No upgrade or 2013 involved in this one.

@Beth Check and see if the Launch32.exe file is in the Launcher directory. I had a client who's AV software quarantined this file.

OMG, @JohnLeonard - YOU ARE DA MAN!!!!!!!!!! YAYAYAYAYAYAYAYAYAYAYAYAYAYAYAY!

Wow........