I successfully installed and worked on my database on JabRef. However, unexpected restart was required and since then I was not able to start my Jabref.
Several installs and uninstalles have been done. But still I am not able to get it on my screen.
Installation is smooth, no warning. I have latest Java installed on my machine.
I can see Jabref is running from from the Windows Task Manager (background process) and consumes about 95MB of my Memory.
Can anyone help me on this issue?
Hi, I am now able to run my Jabref after the uninstalled the v3.6, and then installed the v3.5.
However, I am not able to open my database created using v3.6
another observation.
After installing the v3.5, I updated it to v3.6, I can get it run but still unable to open my databse.
Can anyone help me?
Do you get any errors (in form of a dialog or in Help > Error console)?
Could you please append your bib file here or send it to developers@jabref.org so that we can have a closer look and debug the problem.
Hi I managed to get it run, but after few days I had to forced-shutdown my machine while Jabref was still opened. And now, it is all empty even though the file size is 75KB.
I have basically lost all of my work here. It is so unstable.
I have attached the file, hopefully anyone can help me to retrieve the file.
I cannot upload file as I am a new users here. Here is the file on google drive.
https://drive.google.com/open?id=0BwEwLKVQxoOiblNEY2E5cTBqNUk
I am afraid your file is not a BibTeX file…
But, in the same directory as your file, you may have a backup file, automatically created by JabRef. It bears the same name, but has an extension .bak.
Modifying it from .bak to .bib should give you access to your data.
Thanks for your reply mlep.
I do have the *.bak file and have renamed it to *.bib.
But still I could not retrieve the latest database I have created before my laptop crashed.
It seems that I have to redo everything from scratch again.
I am very sorry that you lost your data. To prevent this from happening, we implemented an autosave feature, which automatically saves each change you are doing. Just wait for 3.7 to be released (probably next week) or use the latest development snapshot at http://builds.jabref.org/master/.
The autosave feature is documented at http://help.jabref.org/en/Autosave
JabRef is great. I use it since 2007, but now i’ve got the same problem described above:
Windows 10 + JabRef 3.8.2: installations is always fine, but it freezes as soon as I open the program (I can’t even maximize or minimize the window).
Can anyone help?
Best regards,
Dimitri.
Hi!
Sounds like your settings are somehow corrupted.
Do you know how to run the jar-File of JabRef using the command line? If yes, you could just call JabRef with the following parameters to reset your prefs:
java -jar JabRef.jar -d all
Another approach would be to “create a shortcut” for the JabRef.exe file and add the parameter “-d all” after the JabRef path of the shortcut properties. I can only provide you a screenshot of a German Win10 but it might help you as well:
Before you perform this step it would also be possible to save your current preferences - saving potentially complex configurations you’ve done - and also enabling us to debug why you cannot startup JabRef at the moment.
If you want to to this you’ll have to use the following command suffix: -x C:\somefolder\somefile.xml where C:\somefolder\somefile.xml must be an absolute path starting from an existing disk.
Regards,
Matthias
Hi Matthias.
Thank you very much, it’s working now. Just for the record, when I used the command:
java -jar JabRef-3.8.2.jar -d all
e I got the following message from my prompt:
fev 14, 2017 10:28:33 AM java.util.prefs.WindowsPreferences
ADVERT-NCIA: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(…) returned error code 5.
Setting all preferences to default values.
I think it maybe worth saying that my W10 is in Brazilian Portuguese. I you want me to send some kind of log for some sort of debbuing, just let me know.
Best regards,
Dimitri.
