1

Here is the text from the appdata log.txt:

2010-10-28 11:42:04,532 - ERROR - Kinovea.Root.Program - Unhandled Crash.
2010-10-28 11:42:04,563 - ERROR - Kinovea.Root.Program - Configuration system failed to initialize
2010-10-28 11:42:04,563 - ERROR - Kinovea.Root.Program - System.Configuration
2010-10-28 11:42:04,563 - ERROR - Kinovea.Root.Program -    at System.Configuration.ConfigurationManager.PrepareConfigSystem()
   at System.Configuration.ConfigurationManager.RefreshSection(String sectionName)
   at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
   at System.Configuration.SettingsBase.SetPropertyValueByName(String propertyName, Object propertyValue)
   at System.Configuration.SettingsBase.set_Item(String propertyName, Object value)
   at System.Configuration.ApplicationSettingsBase.set_Item(String propertyName, Object value)
   at Kinovea.Services.PreferencesManager.set_ReleaseVersion(String value)
   at Kinovea.Root.RootKernel..ctor()
   at Kinovea.Root.Program.Main()

Not sure where exactly to take this.  I see many have encountered issues before with older versions, but that was something that appeared to be corrected.  Any ideas?

2

There is also a crash log for every instance:

Configuration system failed to initialize
System.Configuration   at System.Configuration.ConfigurationManager.PrepareConfigSystem()
   at System.Configuration.ConfigurationManager.RefreshSection(String sectionName)
   at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
   at System.Configuration.SettingsBase.SetPropertyValueByName(String propertyName, Object propertyValue)
   at System.Configuration.SettingsBase.set_Item(String propertyName, Object value)
   at System.Configuration.ApplicationSettingsBase.set_Item(String propertyName, Object value)
   at Kinovea.Services.PreferencesManager.set_ReleaseVersion(String value)
   at Kinovea.Root.RootKernel..ctor()
   at Kinovea.Root.Program.Main()

same gist.

Thanks in advance for time and assistance.

3

To further elaborate this is an older XP machine within a work network on a single-domain implementation, though there are no group policies or anything of that nature that would inhibit this software from properly operating.

4

I'll look deeper into this later but as a start can you provide the Kinovea and .NET version ?
You may find this at the top of the log.txt file.

It is a strange error since Kinovea doesn't use a .NET config file.

5

That is the entire context of the log file, I will have to check the framework version later since the user is currently utilizing their machine, but Kinovea is the latest version and it never worked, it just crashes upon loading.

6

.net framework 4.0 and previous versions, of course

7

Ok, if it never worked it might not change anything but could you go to:

C:\Documents and Settings\[your user name]\Local Settings\Application Data\

(note that this is not the same place than the log and preferences files, it's under Local Settings.)

- Do you have a Kinovea folder there ?
- If so, does it contain one or more subfolders ? something like "Kinovea.exe_Url_zp3dzp…"

You can safely delete the whole "Kinovea" directory there, it will be generated back. Try to launch Kinovea again.

This folder contain a "user.config" file with some more info like the recent file history.
A problem with this file is the most likely cause of "Configuration system failed to initialize" error.

If it still doesn't work and the directory actually exists, try to get a hold of the user.config file (inside subdirectories). 
Please attach it to the bug 225 ("Upload File" section) or post the content here, thanks!

8

Oh, it looks like this was reported earlier in bug 217.

Can you please re-confirm that you do have the .NET 2.0 still installed on the machine, because it would seem that it is mandatory to have it installed.
The .NET 4.0 or .NET 3.5 alone are not sufficient.
(Currently the installation program only checks for 2.0 or later, it should be updated to mandates 2.0).

9

All .NET Frameworks are installed appropriately, there is no Kinovea directory within Local Settings, I am assuming it has not had a chance to build config files and settings since it crashes immediately upon opening.

10 (edited by joan 2010-11-01 16:48:10)

I just realised by the look of the log text that you are using version 0.8.7.
The log is actually more complete in the recent experimental versions. It contains the inner exception text, which will be more precise than just "Configuration system failed to initialize" and that will greatly help understand the actual problem.

I should upload version 0.8.11 in a few hours, please try to install it and paste the error text again. Thanks and sorry for the inconvenience!

edit:
0.8.11 is available up here.

11

5921 - DEBUG - [1] - Program - Kinovea starting.
6218 - DEBUG - [1] - Program - Application level initialisations.
6796 - DEBUG - [1] - Program - Show SplashScreen.
11577 - ERROR - [1] - Program - Unhandled Crash -------------------------
11577 - ERROR - [1] - Program - Message: Configuration system failed to initialize
11577 - ERROR - [1] - Program - Source: System.Configuration
11577 - ERROR - [1] - Program - Target site: Void PrepareConfigSystem()
11577 - ERROR - [1] - Program - InnerException: System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:\WINNT\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 146)
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
11577 - ERROR - [1] - Program - Stack:    at System.Configuration.ConfigurationManager.PrepareConfigSystem()
   at System.Configuration.ConfigurationManager.RefreshSection(String sectionName)
   at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
   at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
   at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
   at System.Configuration.SettingsBase.SetPropertyValueByName(String propertyName, Object propertyValue)
   at System.Configuration.SettingsBase.set_Item(String propertyName, Object value)
   at System.Configuration.ApplicationSettingsBase.set_Item(String propertyName, Object value)
   at Kinovea.Services.PreferencesManager.set_ReleaseVersion(String value)
   at Kinovea.Root.RootKernel..ctor()
   at Kinovea.Root.Program.Main()


This is the new error log.  I just installed it on a similar PC with no issue, though the other PC is only updated to a version of .NET 3.5

Could it somehow be .NET 4.0 that is conflicting with 2.0, which is clearly the root of the issue here.

12

Apparently it would be the 3.5 framework that misbehaved during install and changed the config file innapropriately.

There seem to be others with the same issue, a bug is open at Microsoft but they can't reproduce: Microsoft Connect.

Some other threads about the same issue
http://stackoverflow.com/questions/1292 … sexception
http://community.sharpdevelop.net/forum … 24166.aspx

Apparently the work around is to repair the config file with ServiceModelReg.exe (didn't quite get what was the suggested technique…) or to remove the serviceModel block in the machine.config file, or replace it with a working one. (backup first!)

There doesn't seem to be any way for a program to detect this and repair automatically.
If I understood correctly, this issue prevents any .NET 2.0 application to work.
I'm not even sure that removing the .NET framework and reinstall it would make the problem go away.
sad