We’ve just updated our live system from 10.2.200 to 10.2.500 and all seems well except for Service Connect. (And it was all fine on our dev system in our test upgrade).
The problem seems to be that the core Sca services aren’t running, and won’t run due to missing files when I try to start them manually. So none of the admin tools will even open either because they can’t find the logon service.
Any ideas, anyone? I have a ticket open with Support, but I’m nervous about how long it may be before I get some usable info back.
It looks like the SC server installer didn’t work properly somehow when it detected that upgrade rather than installation was appropriate. If I uninstall and reinstall to test that theory, does that affect the workflows and connectivity?
I’m pretty sure that I uninstalled an old version of SC and reinstalled the latest version when we went to 10.2.400 from 10.2.300. I don’t remember exporting any of the workflows and re-importing them. But, that’s not to say that someone else didn’t after the upgrade. I would think that all the workflows would be in the database.
Hi, If you think files are missing I would re-run the installer, but take a backup of your database before you do just in case.
In my experience you should be able to uninstall then reinstall but in practice it can be dicey. The reinstall shouldnt cause an issue and should leave your db alone, but you can never be 100% sure.
Also it sounds basic but before you do anything else reboot the service connect server and try starting the services again if you haven’t already. I know it sounds basic but sometimes windows installers can cause havok and lock accounts/processes.
This has worked for me in the past…
Feel your pain mate but I would recommend running backups as soon as the server is back up and I would also re-import all of your .Net references because I have seen strange behavior between versions.
Some weekend work and it is fixed after an uninstall-reinstall. Interestingly Epicor Support strongly advised against doing that myself, so I won’t recommend it as the solution, but it did work.
It looks like Service Connect doesn’t like running as a local account any more, and changing the account is problematic if none of the tools will run. Installing again with a new domain account fixed the core problem, and I had a dev copy running on another server to retrieve missing components from so it seems OK now. A lot of the key bits are actually stored as files rather than in the database, I find, which was news to me.
Remote access seems borked now, though. I can’t get client machines to see the new installation, which seems to be https related. So that’s the next challenge, though not so much of a panic, fortunately.