Hi,
I recently installed WATERCAD on my personal desktop because I needed to record a lecture for my class. I have some major concerns about the behavior of CONNECTION Client
1. It refuses to exit. When I exit the software, it comes back. I do not like the persistence of the CONNECTION client on my personal computer.
2. It does not uninstall from my computer. I tried to uninstall both WATERCAD and CONNECTION client but doesn't seem to help. CONNECTION Client is stuck at "Creating Restore Point" and WATERCAD uninstallation is stuck at "Initializing"
Is there a way to get these software off my computer?
Hi Glenn,
As I had mentioned in my original post, CC keeps auto-starting even if I "exit" from the tray. It only stays off if I "end tasks" for licensing server and connection client from the task bar. I am not sure why CC needs to stay in the tray when I am not actively running any Bentley software.
Can you open the CC, run the log collector, and send me the data? Also, is there a reason why you need to exit out when not using it? I don't normally go into my installed applications that need it and the CC doesn't pop up on my machine. That said, if i sign out it doesn't try to open unless I open an application that needs it.
Thanks
Thank you for your help. I pm'd you my log file. I understand that I can leave CC in the background but I'd rather not. I like being aware of what programs are running in the background and prefer to have control over what I choose to run.
As you can see from my boring signature, I can't fix it. Only offering what works for me. I would not be surprised if it is scanning the machine and it does report back activity (don't know if it is more than use of SES software). It complains if it doesn't get a login at least once a month.
I remove their software on a very frequent basis without problems. Of course, CC is required if you use any SES license managed by CC which it appears you do.
Bill
You are no different than many/all power users, we like to know what's happening on our machines; which Bentley doesn't seem to accept or acknowledge.
Our workaround was to write a quick script to kill the two processes (CC and Licensing): we added the script to the machine startup on a timer (to allow the processes to start first) - this kills them initially. Then we put a shortcut on the desktop to allow users to manually kill them after each Bentley software use (if they want).
I guess the developer next-step would be to attach the script to a system 'close-software' event.. but that was a bit too 'next level' for us.