Getting an error every time you start WWWinamp v4.1?
12 October 2007Are you getting the following error every time you start WWWinamp?
C#:
-
System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:\WWWinamp\WWWinamp.exe.Config line 67)
-
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)
-
--- End of inner exception stack trace ---
-
at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
-
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
-
at System.Configuration.ConfigurationManager.get_AppSettings()
-
at ENusbaum.Applications.WWWinamp.Classes.AppConfiguration.get_configWWWinampStartHTTP()
-
at ENusbaum.Applications.WWWinamp.Forms.frmMain.Form1_Load(Object sender, EventArgs e)
This is WWWinamp's friendly way of saying that you do not have the Microsoft .NET Framework v3.0 installed. You can download it from Microsoft here.
Cheers! 
Posted in C# Programming, Microsoft .NET 3.0 / WinFX, WWWinamp | Trackback |
del.icio.us |
Top Of Page
2 Responses to “Getting an error every time you start WWWinamp v4.1?”
December 21st, 2007 at 9:46 am
I’ve got this message (only line 1-5) and now removed all the sytem.serviceModel settings from the config file and it starts up now.
December 21st, 2007 at 10:15 am
Although this could be considered a ‘work around’, it’s not a fix. What you’re doing is removing all the configuration information for the WWWinamp WCF Endpoint, basically making it useless. Also, if you try to enable the WCF endpoint in the future, you will receive another error.
I still stand by my original suggestion that installing the .NET 3.0 Framework is the best solution to this issue.