[COMPASS-5447] Compass is not launching Created: 21/Jan/22  Updated: 29/Oct/23  Resolved: 02/May/22

Status: Closed
Project: Compass
Component/s: Compass
Affects Version/s: 1.26.0, 1.29.4, 1.29.5, 1.29.6, 1.30.1
Fix Version/s: 1.31.3

Type: Bug Priority: Critical - P2
Reporter: Jeff Kling Assignee: Maurizio Casimirri
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows server 2019


Attachments: PNG File Screenshot 2022-01-18 142238.png    
Issue Links:
Related
is related to COMPASS-5599 MSI installer not working in Win 10 Closed
Documentation Changes: Not Needed
Sprint: Iteration Yonkers, Iteration Zanzibar, Iteration Anemone

 Description   

Problem Statement/Rationale

MongoDBCompass is not launching the GUI. It spawns multiple tasks in Task Manager, but never opens the GUI.  It is doing this on two of our servers, with versions 1.26.x through 1.30.1. The second server is a brand new install and new fresh install of mongodb 5.0. MongodbCompass was installed through the mongodb installer.

Steps to Reproduce

Install it and it never opens the compass GUI.

I've tried uninstalling and deleting all compass files I can find and reinstalling previous versions but each version fails to show the GUI and spawns memory eating tasks- getting up to 2 GB in size.

Expected Results

It should open the GUI.

Actual Results

It spawns multiple tasks in Task Manager, but never opens the GUI.  The memory usage continues to grow until I kill the process. 

It is doing this on two of our servers, with versions 1.26.x through 1.30.1.  The second server is a brand new server and new fresh install of mongodb 5.0.

h3. Additional Notes

It would be helpful in the compass documents to add a section for walking through a complete uninstall for situations where the GUI just hangs and never opens.



 Comments   
Comment by Githook User [ 09/May/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Githook User [ 02/May/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Githook User [ 02/May/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Githook User [ 29/Apr/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Githook User [ 28/Apr/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Githook User [ 28/Apr/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Githook User [ 28/Apr/22 ]

Author:

{'name': 'Maurizio Casimirri', 'email': 'maurizio.cas@gmail.com', 'username': 'mcasimir'}

Message: fix(hadron-build): update winstaller COMPASS-5447, COMPASS-5599 (#3018)

  • fix: update winstaller
  • use rev order id
  • unique upload url
  • use build id in artifacts url
  • manually sign windows artifacts
  • wait sign
  • fix config test
  • use mongosh signing code
  • replace imports with require
  • fix export
  • add signtool.exe
  • try signtool
  • fix signtool download
  • log signtool env
  • fix signed path
  • use filename without spaces
  • setup file without spaces
  • remove spaces from windows setup filename
  • try embed signtool.exe
  • try to sign with winstaller again
Comment by Felicia Hsieh [ 18/Mar/22 ]

martin@the-wallers.net How is the CPU, RAM, disk usage? Are you running Compass in a container?

Comment by Jeff Kling [ 16/Mar/22 ]

Compass (beta) 1.31.0-beta.11 has been opening and displaying the GUI so far.

Comment by Felicia Hsieh [ 16/Mar/22 ]

As a workaround, please use command-line mongosh or mongo shell and see if you can connect.

Comment by Martin Waller [ 16/Mar/22 ]

Hi,

I'd like to report this issue too please. We have it installed and a few servers running Windows Server 2019 and getting the same symptoms. The problems render MondoDB useless. I was wondering if anyone was talking a look at it?

Martin

Comment by Jeff Kling [ 08/Mar/22 ]

I installed the Beta and it opens.  I'll give some test throughout the week and will let you know what happens.

 

thanks!

Comment by Jeff Kling [ 08/Mar/22 ]

Hi Felicia,

This is the only Electron app on the server. It was built specifically to host the database and a web application in iis.

I can try the beta and report back, and we are currently community users to evaluate the package and do not have paid support so I so not think we can log a case.

Thanks for the file locations!

Jeff

 

Comment by Felicia Hsieh [ 03/Mar/22 ]

Hi Jeff,

Compass is also an Electron application. Are you aware of any other Electron applications that might be running on the same workstation as Compass?
With the newest Compass (beta) 1.31.0-beta.11, are you still seeing this issue? It's available at:
https://github.com/mongodb-js/compass/releases/tag/v1.31.0-beta.11

The Compass files in Windows are at:

  • Binary/Executable: Your chosen directory
  • Favorite Connections: %UserDataFolder%\MongoDB Compass\Connections. Typically C:\Users
    {username}\AppData\Roaming\MongoDB Compass\Connections
  • Pipelines:  %UserDataFolder%\MongoDB Compass\SavedPipelines. Typically C:\Users{username}
    \AppData\Roaming\MongoDB Compass\SavedPipelines
  • Log Files: %APPDATA%\Local\mongodb\compass. Typically C:\Users
    {username}\AppData\Local\mongodb\compass
  • Installer file: Typically in Download directory
  • Embedded mongosh files: %APPDATA%\Local\.mongodb\mongosh
  • User Preferences: %UserDataFolder%\MongoDB Compass\AppPreferences\General.json. Typically C:\Users {username}

    \AppData\Roaming\MongoDB Compass\AppPreferences\General.json

Are you able to open a MongoDB Support Portal case at https://support.mongodb.com/welcome?

Comment by Jeff Kling [ 02/Feb/22 ]

Sorry for the delay-  We are not using Citrix.  I've also asked a similar question on the mongodb boards.

 

Complete uninstall of Compass

Comment by Felicia Hsieh [ 24/Jan/22 ]

I'm sorry to hear this is happening. Are you using Citrix in your environment?

Generated at Wed Feb 07 22:39:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.