ATLASSIAN COMPANION does not "start"...

laurent dumont March 10, 2021

Hello,

 

We have installed ATLASSIAN COMPANION 1.2.5 with SCCM on 2.000 computers.

Statistically, ATLASSIAN COMPANION does not start on 20% of them (impossible to use ATLASSIAN COMPANION from CONFLUENCE 7.9.1).

For some of them, we have these logs :

"info: adc:core 2021-03-02T09:44:43.383Z Initialised logging with level "info"
info: adc:core 2021-03-02T09:44:43.385Z Electron userData path initialised to C:\Users\char41886\AppData\Local\Atlassian Companion
info: adc:core 2021-03-02T09:44:43.385Z Companion launched with argv: [C:\Program Files (x86)\Atlassian Companion\Atlassian Companion.exe]
info: adc:settings 2021-03-02T09:44:45.573Z Loading settings store from C:\Users\char41886\AppData\Roaming\Atlassian Companion\settings.cache
info: adc:manifest-controller 2021-03-02T09:44:47.555Z enabling manifest: file
info: adc:manifest-controller 2021-03-02T09:44:47.555Z enabling manifest: feedback
info: adc:manifest-controller 2021-03-02T09:44:47.555Z enabling manifest: license
info: adc:auto-updater 2021-03-02T09:44:48.211Z Application was installed via MSI, not watching for updates
info: adc:settings 2021-03-02T09:44:48.549Z opening settings store
info: adc:initialiseApp 2021-03-02T09:44:48.552Z app is ready
info: adc:file-manager 2021-03-02T09:44:48.595Z clearing file manager cache
info: adc:browser 2021-03-02T09:44:48.596Z launching websocket
info: adc:fileWindowController 2021-03-02T09:44:48.597Z init file window
error: adc:initialiseApp 2021-03-02T09:44:48.718Z Failed to clear temporary files
error: adc:initialiseApp 2021-03-02T09:44:48.719Z Error: ENOENT: no such file or directory, scandir 'C:\Users\char41886\.atlassian-companion'
error: adc:initialiseApp 2021-03-02T09:44:48.719Z Error: ENOENT: no such file or directory, scandir 'C:\Users\char41886\.atlassian-companion'
info: adc:browser 2021-03-02T09:44:48.724Z direct websocket launched successfully on port: 31459
info: adc:analytics 2021-03-02T09:44:48.726Z event companion.start {"new":false} 84df64f9-48d7-4375-b5f7-293ed45da7f8
info: adc:initialiseApp 2021-03-02T09:44:49.030Z generating tray menu from manifests
info: adc:electronCacheData 2021-03-02T09:44:49.044Z Removed old userData files from Windows roaming profile at C:\Users\char41886\AppData\Roaming\Atlassian Companion"

 

We don't understand why this folder "...\.atlassian-companion" is not created.

 

Many thanks in advance,

laurent

1 answer

0 votes
laurent dumont March 10, 2021

Hi,

 

We have checked the atlassian companion folder. There is a difference between a computer where atlassian companion is working (263 files and 323 Mo) and a computer where not (256 files and 186 Mo). Is it an installation problem with SCCM ?

 

Many thanks,

laurent

Alex K
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 10, 2021

Hi @laurent dumont ,

It may be a permission issue where Companion cannot create the directory at "C:\Users\char41886\.atlassian-companion".You could try running Companion with administrative privileges. If that doesn't resolve the issue, could you try creating that directory manually and re running Companion? 

laurent dumont March 11, 2021

Hi,

 

Thank you for your feedback. We have found the cause of our problem. In some cases, SCCM does not install correctly ATLASSIAN COMPANION on a computer where a previous version of ATLASSIAN COMPANION is already present. We have changed our SCCM script and everything is now fine.

 

Regards,

laurent

Like Alex K likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events