Error when trying to login with specific user account

When a specific user tries to login to epicor, they get the following error.
‘The requested service. ‘net.tcp://server/environment/Ice.BO/ShellLayout.svc’ could not be activated’

I can login with my account from her system without issue. Her account gets the same error on my system.
I don’t see anything on the Epicor app server log, or the task agent log. I tried clearing the client cache on her system to no avail.

Any suggestions would be most helpful.

what binding method does the App use?

UsernameWindowsChannel

Does it matter who is logged into the desktop?

In other words, when you said you could login from the users machine, the user was logged in into the domain, on that machine. Then from the users desktop, launching the client, and entering your credentials was successful?

Or did you login to the users machine with your AD credentials, before launching the client?

On her machine she was logged into the domain as herself, and her epicor account does not work but mine does. Then on my pc logged into the domain as myself my account works and hers does not.

I assume the server/environment portion of net.tcp://server/environment/Ice.BO/ShellLayout.svc in the error message, was your redaction of the actual values. That correct?

Or does the error actually say server/environment ?

You are correct. The address is the actual server name/ and the environment. Not ‘ServerName\Environment’

FYI, We are having some service issues with our test environment and need to restart the server\task service but we wont be able to until tonight because the test and live environments are on the same server. I don’t know if that’s part of the issue, not sure how it would only affect a single account.

Try looking if the user has any personalization and clear those. Had a similar problem and that always seems to clear it.

2 Likes

Try having the user select the “Classic Shell”

I would second this. You can look for a record for her user also in Ice.ShellLayoutPersonal.

@EpicorAnon Is there a personalization for the login?

@ckrusen You rock… Classic mode worked and she can login. Hopefully after the server restart tonight everything is working again.

Thanks for all the help…

FYI,
Issue update. I had a call into Epicor for this issue and they also suggested restarting the app pool. I did try it and it did not resolve the issue. Over night we did a full server reboot. Then we stopped and restarted the Task Agent service and all the app pools and that has fixed this issue.