Custom module conflicts with existing TeamViewer

Options

Hi all,

My company has created a custom module that is integrated in our application.

Because of the popularity of TeamViewer some customers have TeamViewer already running on their machine and then starting our custom module ends in an error saying that TeamViewer is already running.

Is there a way to avoid this problem, for example automatically start a session with the existing running TeamViewer instead of starting the custom module?

Thanks for any help.