(imported topic written by SystemAdmin)
Lately, the “BESClientUI is not running” fixlet has had a high degree of relevance in our environment. This is not something that we have seen a lot of in the past. If we deploy the fixlet, the issue appears to resolve only to become relevant again a few days later.
Any reason why this would suddenly become an issue?
We recently updated servers and relays to 7.1.1.315.
Most clients are still at 7.0.9.164.
Could this be the culprit?
(imported comment written by rharmer91)
Bump
We seem to be having the same issues… The rights on the BESClientUI need to have “System” on them, and they don’t for most (10K) of our clients.
Rich
(imported comment written by BenKus)
Hey guys,
Rich, it seems like you have identified and fixed the issue by adding “SYSTEM” permissions? That is very strange because they should already have that permission…
If you guys have a reproducible case, we would love to see it…
Ben
(imported comment written by Fredrik23)
Hi,
I have the same, it seems that more then 10% of out enviroment is relevant for this, and i never found it to be a issue before?
I checked one of the clients and it had been fixed and then relevant again?
What information do you need?
The besclientui.exe runs as user logged in and not system?
Besversion 7.1.1.35 on W2k, XP, vista and windows2003.
// Fredrik
(imported comment written by BenKus)
Hey guys,
Our senior agent developer pointed out today that this Fixlet can potentially give false-positives because there is a time period between when the user logs in and the BESClientUI is launched… So if the agent happened to check this Fixlet during this time period, it would report relevant for a little while…
I think we will need to go back and revise or remove this Fixlet because it might be causing more trouble than it is helping… Updates will be coming soon…
Ben
(imported comment written by BenKus)
Hey folks,
OK… So here is what we did:
Ben