Logging into Kinetic - User gets sent to TEST MODE screen

Kinetic ERP
1

I have 1 user who is logging into THIRD Environment and when he does -his system never asks the User or password - it goes straight to a Blank screen with the words “TEST MODE” in a red box at the Center Top of his screen. No one else has this problem. We have Uninstalled and re-installed, with no success. He can REMOTE to his desk and his Epicor does work - This is just on his laptop locally.

1 Like
2

I’ve seen it. I don’t know how it happened. I don’t know how it went away.

:popcorn:

3 Likes
3

We had a user experience this same “Test Mode” screen issue. We are not sure what the cause is but, a reinstall resolved the problem for us.

2 Likes
4

I also found that opening a second session of Epicor and logging in seems to work as normal. We just left the “test mode” screen open for the time being.

4 Likes
5

I can confirm that this “trick” does work.
I haven’t gotten to trying to root cause or correct it yet.
I do know that we had a sudden power outage at the end of the day yesterday and it would appear that at least for this specific user, something did not close out as expected.

1 Like
6

The reinstall is a permanent fix Michael :+1:

2 Likes
7

FWIW,

  We have seen this on remote users when they don't connect to our VPN first.
1 Like
8

If found that you can also delete this folder. For some reason this folder will cause issues in the Kinetic client, I’m not sure why.

C:\ProgramData\Epicor

Once this folder is deleted, then the client should open normally again.

3 Likes
9

I have a user with this same issue and the fix was to delete this folder on the user’s PC.

C:\ProgramData\Epicor

Then when the open the client, it should work as normal.

1 Like
10

I confirm that if running Cloud hosted, that if you delete the environment folder that is located:

C:\ ProgramData \Epicor \YourEnvironmentID

Then, that resolves the issue as the environment folder is recreated on login.

Thanks everyone and hope that this info is useful to others at some point in time.

2 Likes
11

Awesome. Even easier fix. Does it change anything else for the user? Personalizations or anything?

1 Like
12

Cache in the old classic client, was stored here.

1 Like
13

@jott Not that I am aware. In fact, if I recall correctly, this was prescribed in cases where the users was not picking up changes in personalization or customization.

Yes, @utaylor for the maybe not so “smart-client”.
I guess running the web client they’d ask you to go delete all your temporary internet files, lol

3 Likes
14

Good point Michael!

15

We did the same (thanks for the tip). After we were in after the second session, we cleared out the cache on that user and then closed both sessions.

We logged back in again and now it seems to be fine.

1 Like