Big problem (Das Konfiguationssystem konnte nicht initialisiert werden)

sombra

Hi,

after updating to version 1.3.9 and new start of windows 7 I become following error message:

"Das Konfigurationssystem konnte nicht initialisiert werden".

Boxcryptor dont start, all files are encrypted in my dropbox. But I dont have access to the files, because Boxcryptor dont start.

New install of application didnt help.

Suggestions?

sombra

Nothing helped, so I delete version 1.3.9 and installed again the version 1.3.2. Now everything runs fine.

I have tried after deinstalling version 1.3.2 completely to install version 1.3.9, but no chance.

So I still work with version 1.3.2. Is there a workaround for this problem?

Robert

Hi Sombra,

Can you post the debug log when this problem occurs in v1.3.9? To create the debug file do the following:
1) Quit BoxCryptor
2) Type into the Windows startmenu "boxcryptor.exe /debug"
3) Reproduce the error
4) Quit BoxCryptor
5) The "BoxCryptor.log" is located on your desktop

Even if there should be a problem with your BoxCryptor installation, you can always access your encrypted files with the portable version which does not require any installation. Since v1.3.9 it is included in the regular installer.

--Robert

sombra

Hi Robert,

so far, so good. But how should I make this with the debug, if I can´t install the version 1.3.9?

Or do you mean, I should install 1.3.9, create a debug file and then start bc, to see what the program logs?

Sorry that I am asking, but I don´t know much things about this.

Regards.

Boris

Hi sombra

Yes you first have to install 1.3.9 again. After that follow Robert's instructions.

Best regards
Boris

sombra

Ok, I tried it now again here the problem is the same.

Here is the log:

====================
21:21:6387 | Operating System: Microsoft Windows NT 6.1.7601 Service Pack 1
21:21:6437 | .NET version: 4.0.30319
21:21:6437 | BoxCryptor v1.3.9.0 started!
21:22:6400 | System.Configuration.ConfigurationErrorsException: Das Konfigurationssystem konnte nicht initialisiert werden. ---> System.Configuration.ConfigurationErrorsException: Das Stammelement ist nicht vorhanden. (C:\Users\********\AppData\Local\Secomba_GmbH\BoxCryptor.exe_Url_m2bmoumszvtcpodowd1pzfb4cpcaj10p\1.3.9.0\user.config) ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
bei System.Xml.XmlTextReaderImpl.Throw(Exception e)
bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
bei System.Xml.XmlTextReaderImpl.Read()
bei System.Xml.XmlTextReader.Read()
bei System.Configuration.XmlUtil..ctor(Stream stream, String name, Boolean readToFirstElement, ConfigurationSchemaErrors schemaErrors)
bei System.Configuration.BaseConfigurationRecord.InitConfigFromFile()
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
bei System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
bei System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
bei System.Configuration.ClientConfigurationSystem.OnConfigRemoved(Object sender, InternalConfigEventArgs e)
--- Ende der internen Ausnahmestapelüberwachung ---
bei System.Configuration.ConfigurationManager.PrepareConfigSystem()
bei System.Configuration.ConfigurationManager.RefreshSection(String sectionName)
bei System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
bei System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
bei System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
bei System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
bei System.Configuration.SettingsBase.get_Item(String propertyName)
bei System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
bei System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
bei BoxCryptor.Properties.Settings.get_firstRunDate()
bei .(String[] )
====================

I hope this will help to find the problem...

sombra

Still awaiting a answer...

Robert

Hi sombra,

Sorry, I thought the problem has been "solved" for you by downgrading to v1.3.2 and you did not need an answer anymore. It seems that the file which stores the BoxCryptor settings (like the drive letter) could not be correctly upgraded to the new version. We have corrected this problem in the current development version.

A workaround could be to delete the whole C:\Users\********\AppData\Local\Secomba_GmbH folder and then start BoxCryptor. BoxCryptor will then start like on a completely fresh installation and you will have to configure it again (e.g. by opening the existing BoxCryptor Folder).

Best regards,
Robert