We have installed Contour via the Umbraco Pro section in Developer\packages\Umbraco Package repository on Umbraco 4.7.2. We are running ASP.NET 4.0 and IS 6. We have purchased and installed a Courier Express licence. When we try to run Courier via a right click, we get the following error:
The given key was not present in the dictionary.
Error details
System.Collections.Generic.KeyNotFoundException: The given key was not present
in the dictionary. at System.Collections.Generic.Dictionary`2.get_Item(TKey
key) at Umbraco.Courier.Core.ItemProvider.get_DatabasePersistence() at
Umbraco.Courier.ItemProviders.DocumentItemProvider.AvailableSystemItems(ItemIdentifier
itemId) in c:\Program Files
(x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Providers\ItemProviders\ContentItemProvider.cs:line
41 at Umbraco.Courier.UI.Dialogs.CommitItem.OnInit(EventArgs e) at
System.Web.UI.Control.InitRecursive(Control namingContainer) at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint)
Having enabled error logging, the following error appears in the Contour logs:
15/06/2012 11:03:15: Can't import provider 'Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider' id: e0474ca8-e73b-11df-9492-0800200c9a66: FluentNHibernate.Cfg.FluentConfigurationException: An invalid or incomplete configuration was used while creating a SessionFactory. Check PotentialReasons collection, and InnerException for more detail.
---> System.ArgumentException: Keyword not supported: 'datalayer'. at System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey) at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules) at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString) at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous) at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(String connectionString, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions) at System.Data.SqlClient.SqlConnection.ConnectionString_Set(String value) at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value) at NHibernate.Connection.DriverConnectionProvider.GetConnection() at NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare() at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords(Dialect dialect, IConnectionHelper connectionHelper) at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update(ISessionFactory sessionFactory) at NHibernate.Impl.SessionFactoryImpl..ctor(Configuration cfg, IMapping mapping, Settings settings, EventListeners listeners) at NHibernate.Cfg.Configuration.BuildSessionFactory() at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() --- End of inner exception stack trace --- at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.GetMSSqlSessionFactory(String connectionString) in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:line 248 at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.CreateSessionFactory() in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:line 222 at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.onAppStart() in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:line 37 at Umbraco.Courier.Core.ProviderCollection`1.(IEnumerable`1 types)
Yes, we are using Sql Server (SQL 2008). I removed the datalayer=sqlserver from the app setting umbracoBdDSn. This has got me past that error, thanks. However, I'm now getting another error when I try an export, but I'll investigate further before posting.
Error running Courier - related to NHibernate?
We have installed Contour via the Umbraco Pro section in Developer\packages\Umbraco Package repository on Umbraco 4.7.2. We are running ASP.NET 4.0 and IS 6. We have purchased and installed a Courier Express licence. When we try to run Courier via a right click, we get the following error:
The given key was not present in the dictionary.
Error details
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Umbraco.Courier.Core.ItemProvider.get_DatabasePersistence()
at Umbraco.Courier.ItemProviders.DocumentItemProvider.AvailableSystemItems(ItemIdentifier itemId) in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Providers\ItemProviders\ContentItemProvider.cs:line 41
at Umbraco.Courier.UI.Dialogs.CommitItem.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Having enabled error logging, the following error appears in the Contour logs:
15/06/2012 11:03:15: Can't import provider 'Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider' id: e0474ca8-e73b-11df-9492-0800200c9a66: FluentNHibernate.Cfg.FluentConfigurationException: An invalid or incomplete configuration was used while creating a SessionFactory. Check PotentialReasons collection, and InnerException for more detail.
---> System.ArgumentException: Keyword not supported: 'datalayer'.
at System.Data.Common.DbConnectionOptions.ParseInternal(Hashtable parsetable, String connectionString, Boolean buildChain, Hashtable synonyms, Boolean firstKey)
at System.Data.Common.DbConnectionOptions..ctor(String connectionString, Hashtable synonyms, Boolean useOdbcRules)
at System.Data.SqlClient.SqlConnectionString..ctor(String connectionString)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnectionOptions(String connectionString, DbConnectionOptions previous)
at System.Data.ProviderBase.DbConnectionFactory.GetConnectionPoolGroup(String connectionString, DbConnectionPoolGroupOptions poolOptions, DbConnectionOptions& userConnectionOptions)
at System.Data.SqlClient.SqlConnection.ConnectionString_Set(String value)
at System.Data.SqlClient.SqlConnection.set_ConnectionString(String value)
at NHibernate.Connection.DriverConnectionProvider.GetConnection()
at NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare()
at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords(Dialect dialect, IConnectionHelper connectionHelper)
at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update(ISessionFactory sessionFactory)
at NHibernate.Impl.SessionFactoryImpl..ctor(Configuration cfg, IMapping mapping, Settings settings, EventListeners listeners)
at NHibernate.Cfg.Configuration.BuildSessionFactory()
at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory()
--- End of inner exception stack trace ---
at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory()
at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.GetMSSqlSessionFactory(String connectionString) in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:line 248
at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.CreateSessionFactory() in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:line 222
at Umbraco.Courier.Persistence.V4.NHibernate.NHibernateProvider.onAppStart() in c:\Program Files (x86)\teamcity\buildAgent\work\2d3247b08adc3338\Umbraco.Courier.Persistence.NHibernate\NHibernate.cs:line 37
at Umbraco.Courier.Core.ProviderCollection`1.(IEnumerable`1 types)
Any ideas?
are you using sql server? if so, then remove the datalayer="*" parameter from the connection string
Thanks Per,
Yes, we are using Sql Server (SQL 2008). I removed the datalayer=sqlserver from the app setting umbracoBdDSn. This has got me past that error, thanks. However, I'm now getting another error when I try an export, but I'll investigate further before posting.
Alan
is working on a reply...