1 of 1 people found this helpful
Brett, all the environments have the same Control-M patch level?
Your client have installed the same patch?
Thanks for the response Walter.
With the client open, FILE >> ABOUT shows version...
Is there a way to see what version the environments are on without having to go to a Sys Admin?
They should all be at the same level.
Just to note a few things:
I only have this error in our DEV environment. It was running fine up until a few days ago. To my knowledge, nothing was done/updated in that environment by our Sys Admins.
This may have been coincidental, but I started to see this error after I lost connection to the environment from a session that I had some objects checked OUT. Those objects are STILL checked out, preventing others from editing them.
Also, this just happened to be at the same time as my Windows AD user password was warning me it was about to expire. I have since reset that a few times.
Others are able to log into this environment just fine.
Oddly, when others try to check out that same object, they see this...
...but browsing our entire jobs folder, it does NOT show that object checked out by anyone, as it normally does.... (user's name would appear in the highlighted area)
Sorry for my slow response...
I tried to open the configuration manager to get the version, and it appears I don't have access to this. I could request this info from our Sys Admins if it'd truly help, however late last week, the issue I was having suddenly started working. Sys Admins claimed that the didn't do anything to fix it, and nothing changed that they were aware of, except a Control-M agent on a separate server (different from the authentication server) was re-loaded. I don't know if that triggered some sort of user credentials refresh, but they said that shouldn't have had any impact on my issue.
So for now, it's resolved for me, but would love additional thoughts on what do to do if this happens again. This was the 2nd time that a person in my organization got the error. Both times it seemed to resolve itself after a week or so, but no one knows how, why, or what resolved it.
Was a solution ever found for this error?
No solution was found for this error. It just started working again one day. So I'm just guessing that something out of my control on the back-end must've changed and fixed it, or triggered a reset/refresh of the authentication piece. If ever found the real cause/solution for this error, I'd still like to know, as this is bound to happen again.