Service Connect: Import .NET Ref: Failed to retrieve UD Fields information

Kinetic ERP
1

Getting SC backup after the upgrade this weekend. When reimporting, I get this error:

Failed to retrieve UD fields information:
Exception of type System.ApplicationException: Failed to load Ice.Core.Session.dll or one of its necessary types
Exception of type System.TypeLoadException: Could not load type ‘Ice.Core.Session+LicenseType’ from assembly ‘Ice.Core.Session, Version=5.0.100.0, Culture=neutral, PublicKeyToken=’.

I’ve reimported a bunch of times, and never got this error. Does anyone have any insight. I need this up before tomorrow…

2

Ice.Core.Session.dll corrupt?

3

Well, hopefully this is because the “All Clear” hasn’t been sent yet by Epicor. Fingers crossed that’s it. I will report here once a solution is found.

4

We used to get this after every upgrade. We decommissioned SC over a year ago now so the details are foggy. Believe you just have to upgrade the kinetic client that is on your service connect server.

5

Hello and thank you for responding. I upgraded the client install without issue and can login, but for some reason I still get this error. Perhaps I need to reinstall the client? Any help would be appreciated.

6

Did you log a support case? Usually the process of typing the error message into the subject of a new support case surfaces any relevant KB articles.

7

Not yet, but we will be doing this. When I pull these DLLs in as our ‘serviceconnect’ user it fails with the error above. When I use a power user account, the DLLs pull in just fine. The ‘serviceconnect’ user has power user rights as well… I don’t understand why one user would work but the other doesn’t?

8

Impersonation priveliges? Just guessing.

1 Like
9

Do you use SSO? We had to create a different Sysconfig that was defaulted to basic to get the UD fields to import.

1 Like
10

We do not. Epicor updated us that we need the new version of Service Connect: 12.0.100. Struggling to find where to download the update, but hopefully this is the fix.

11

Updating the version of Service Connect resolved the issue. Cheers!