Desktop Connector Error Report

[MichaelT_123]

Hi TF360 Network Gurus in the Clouds, 

Could you please check ... how Desktop Connector Error Report is launched.

I experience the inundations of its dialogs  and corresponding OS CMD's  Windows, particularly in situation of a network connection drop.

I hope that 'a simple' management of the respective thread should fix the issue.

Addendum:

The accumulated  Desktop Connector Error Report can't be closed wholesale using Window's 

 'Close all windows' command.

Regards

MichaelT 

[logerqk]

MichaelT, Thanks for this feedback.  It sounds like you are referring to the Desktop Connector automated crash recovery mechanism.  This mechanism kicks in when the product crashes.  Can you please provide some example CER #'s that we can use to investigate further.

Thanks,

Kevin

[MichaelT_123]

Hi Mr KevinL,

Your assumption is correct. The Desktop Connector is causing the problem.

When a network connection is abruptly down … it goes into berserk mode, profusely generating… Error Report Dialog box and some auxiliary subprocesses.

It is so energetic that the new one appears on the desktop every 0.5 seconds, so the screen looks like … an unsolved Solitaire! The whole Windows system also became unresponsive (including the Resource Manager).

On top of this idiosyncratic development, some highly optimistic software development Guru placed a nodal dialogue within the malicious thread , asking the user to reconfirm willingness to close the Error Dialog Box, ... faster than 0.5 sec. It is an insult to many, as most ( by a 6-sigma measure) F360 users are sane enough to know the consequences of such simple action and do not need preschool warnings, and don't have fast enough reflexes. Generating nodal dialogue boxes also has another side effect. It prohibits closing processes owning such soft apps.

Regarding sending CER, … it is not an option with no network and the system crashes.

However, diagnosing the problem might be as simple as after hitting a finger with a hammer. No doctor is necessary to identify the problem.

In our particular case:

• Find the piece of code launching the CER thread
• Establish a counter on it and control its lifespan
• Similarly with the auxiliary subprocesses, … use timeout or communicate
• AVOID putting nodal dialogue boxes in the critical threads
• Particularly in such a context as being implemented in CER
• … most people are not idiots ( I am staunch optimist ). They don't need additional confirmations.

On the final words … I am somewhat optimistic that the problem will be solved easily and without hesitation. … just put Lighter Gu (गु) and Heavier Ru (रु) in charge.  

Regards

MichaelT

[logerqk]

MichaelT, we appreciate your passion and your feedback.  The experience you have described has been accepted for investigation by the product team.  

Thanks again!

Kevin

[logerqk]

MichaelT, for the issue of the Desktop Connector crashing on startup I will provide two possible known causes of this that you may try to resolve the root issue:

Reset DC Folders section in this article

Downgrade Autodesk Identity Manager to version 1.14 following this article