-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
un open dbeaver #29803
Comments
24.0.3 upgrade to 24.0.4 |
Could you try to reset workspace settings? |
delete files %APPDATA%\DBeaverData\workspace6.metadata.plugins Still unable to open I rolled back to 24.0.3 can be open |
I'd like to use the portable version. However, the software cannot be started after the overlay is upgraded. After I delete the program directory, I can normally start it directly after unpacking 24.0.4. It's not to delete %APPDATA%\DBeaverData\ |
I've extaly same Issue, tried to reset nothing helped: OS: Win: 11 Enterprise
|
Same problem here with the portable versions 24.0.4 and 24.0.5 on Windows x64. Build 24.0.3 works fine.
|
I use zip version and face same issue when upgrade to 24.0.4 or 24.0.5 |
thanks, i can open in 24.0.5 |
Hi everyone, are you trying to unpack the ZIP folder on the existing DBeaver installation? |
In my case, yes, as usual. |
We would highly recommend clearing the initial installation before unpacking. This should prevent this form of issue. |
Thanks, trying right now. Should one preserve only "configuration" and "data" folders? |
As I understand it, data is a portable workspace folder. If it is, you should save and preserve them both. Just to be sure I would recommend making temporary folder |
Fixed cleaning the installation directory. Moved data folder outside of the application folder so in the future I can update simply deleting entire application folder. Thanks for support. |
Description
Problems occurred when invoking code from plug-in: "org.eclipse.text".
.log
DBeaver Version
24.0.4
Operating System
Windows11
Database and driver
No response
Steps to reproduce
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: