cancel
Showing results for 
Search instead for 
Did you mean: 
davedbs
Canine II

eClaims - account credentials are not configured

We repeatedly receive this message sporadically - sometimes just on one workstation - sometimes on 2 at the same time.  

Typically we have contacted support and they have gone through the process of re-entering the credentials, which will work for a time, and then seemingly at random this will happen again - and it will have reverted to old information or all 9's as if it had never been configured.

This has happened numerous times over several years and versions - we are currently on 9.6.2.131.  We are on an on-premise Windows Server for the database, and Windows 10 workstations for the clients.

An engineer suggested we should upgrade to 9.7 or 10, but was unable to be certain if the issue has been corrected in either of those 2 versions.  He suggested we post here to reach the development team to see if they have high confidence this has been resolved in 9.7 or 10.

Can someone please expand on this and let us know if it is fixed in 9.7 or 10?  Thank you!

Labels (1)
0 Kudos
Reply
davedbs
Canine II

Hello Is there any update on this?

0 Kudos
Reply
tshaw
Community Manager
Community Manager

Hello @davedbs
I just inquired with our escalations team about this. It will normally happen every time you do a reinstall of Winoms locally on a workstation you transmit claims from. If it is not a new workstation and you consistently have the settings reset, it may be a Windows permission issue in writing to the registry that your IT tech would need to check on. Let me know if you need further assistance and I'll have someone from our escalations team reach out. 

0 Kudos
Reply

Thanks for responding.  This happens sporadically on various workstations - not after a reinstall of WinOMS.  Each user is a local admin, so there should be no permissions issue.  Please have someone get in touch - thank you.  Also, the WinOMS support reps we have worked with seemed to think this is a WinOMS issue, and that it may have been fixed in 9.7 or 10.  Can someone in development comment on this?

0 Kudos
Reply