+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / Turning on feather caused "Unable to upgrade database schema" warnings and error

Turning on feather caused "Unable to upgrade database schema" warnings and error

7 posts, 1 answered
  1. Bryson
    Bryson avatar
    13 posts
    Registered:
    14 Jan 2016
    29 Jan
    Link to this post

    I'm using sitefinity 8.2.5903.0. Telerik.Sitefinity.Frontend runtime version is 4.0.30319. I turned on the Feather module under Administration->Modules & Services. After waiting for Sitefinity to initialize again I got these messages

    Also this was added into my SystemConfig.config:

    <add startupType="OnApplicationStart" version="1.4.390.0" name="Feather" />

    Warning 1:

    HandlingInstanceID: 09105095-62f9-4bd8-9bc9-eb3e1ec79615 An exception of type 'System.Exception' occurred and was caught. ---------------------------------------------------------------- 01/29/2016 10:49:19 Type : System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : Unable to upgrade database schema metadataSource provided by 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider': The provider 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider' database schema version (410) is higher than the currently running version (390). Downgrade is not allowed. Source : Telerik.Sitefinity Help link : Data : System.Collections.ListDictionaryInternal TargetSite : Boolean ReplaceMetadata(Telerik.Sitefinity.Data.OA.OpenAccessConnection, Telerik.OpenAccess.Metadata.MetadataContainer, System.String, Telerik.Sitefinity.Data.OA.ISitefinityMetadataSource, Telerik.Sitefinity.Data.IOpenAccessMetadataProvider) HResult : -2146233088 Stack Trace : at Telerik.Sitefinity.Data.OA.OpenAccessConnection.OptimizedMetadataUpdateStrategy.ReplaceMetadata(OpenAccessConnection connection, MetadataContainer newMetadataContainer, String moduleName, ISitefinityMetadataSource sitefinityMetaDataSource, IOpenAccessMetadataProvider provider) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.UpdateMetadata(MetadataSource metadataSource, String moduleName, IOpenAccessMetadataProvider provider, IEnumerable`1 combinedModules) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.Extend(MetadataSource metadataSource, String moduleName, IOpenAccessMetadataProvider provider, Boolean safeMode, IEnumerable`1 combinedModules) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.RegisterProviderInternal(IOpenAccessMetadataProvider provider, Boolean forceDatabaseInit, Boolean safeMode) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.RegisterProvider(IOpenAccessMetadataProvider provider, Boolean safeMode) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.InitializeProvider(IOpenAccessMetadataProvider provider, String connectionName, Boolean safeMode) at Telerik.Sitefinity.Data.Decorators.OpenAccessDecorator.InitializeDatabase(DataProviderBase dataProvider, NameValueCollection config) at Telerik.Sitefinity.Data.Decorators.OpenAccessDecorator.Initialize(String providerName, NameValueCollection config, Type managerType) at Telerik.Sitefinity.Data.DataProviderBase.Initialize(String providerName, NameValueCollection config, Type managerType, Boolean initializeDecorator) at Telerik.Sitefinity.Data.DataProviderBase.Initialize(String providerName, NameValueCollection config, Type managerType) at Telerik.Sitefinity.Data.ManagerBase`1.InstantiateProvider(IDataProviderSettings providerSettings, Type providerType, ExceptionPolicyName policy, ManagerBase`1 manager) Additional Info: MachineName : PC8582 TimeStamp : 1/29/2016 3:49:19 PM FullName : Telerik.Sitefinity.Utilities, Version=8.2.5903.0, Culture=neutral, PublicKeyToken=b28c218413bdf563 AppDomainName : /LM/W3SVC/2/ROOT-2-130985559927631905 ThreadIdentity : WindowsIdentity : DQE\bhair Requested URL : http://127.0.0.1/ Inner Exception --------------- Type : System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : The provider 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider' database schema version (410) is higher than the currently running version (390). Downgrade is not allowed. Source : Telerik.Sitefinity Help link : Data : System.Collections.ListDictionaryInternal TargetSite : UpgradeParams CheckForUpgrade(Telerik.Sitefinity.Data.IOpenAccessMetadataProvider, Telerik.Sitefinity.Data.OA.OpenAccessConnection, System.String, Telerik.Sitefinity.Data.OA.ISitefinityMetadataSource, Telerik.Sitefinity.Metadata.Model.SchemaVersion) HResult : -2146233079 Stack Trace : at Telerik.Sitefinity.Data.OA.OpenAccessConnection.MetadataUpgradeFacade.CheckForUpgrade(IOpenAccessMetadataProvider provider, OpenAccessConnection connection, String moduleName, ISitefinityMetadataSource sitefinityMetaDataSource, SchemaVersion schemaVersion) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.MetadataUpgradeFacade.UpgradeSchema(ISchemaHandler schemaHandler)   

     

    Warning 2:

    HandlingInstanceID: 6e090d3e-057f-48a0-b4b2-c64fafc67f24 An exception of type 'System.Exception' occurred and was caught. ---------------------------------------------------------------- 01/29/2016 10:49:22 Type : System.Exception, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : Unable to upgrade database schema metadataSource provided by 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider': The provider 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider' database schema version (410) is higher than the currently running version (390). Downgrade is not allowed. Source : Telerik.Sitefinity Help link : Data : System.Collections.ListDictionaryInternal TargetSite : Boolean ReplaceMetadata(Telerik.Sitefinity.Data.OA.OpenAccessConnection, Telerik.OpenAccess.Metadata.MetadataContainer, System.String, Telerik.Sitefinity.Data.OA.ISitefinityMetadataSource, Telerik.Sitefinity.Data.IOpenAccessMetadataProvider) HResult : -2146233088 Stack Trace : at Telerik.Sitefinity.Data.OA.OpenAccessConnection.OptimizedMetadataUpdateStrategy.ReplaceMetadata(OpenAccessConnection connection, MetadataContainer newMetadataContainer, String moduleName, ISitefinityMetadataSource sitefinityMetaDataSource, IOpenAccessMetadataProvider provider) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.UpdateMetadata(MetadataSource metadataSource, String moduleName, IOpenAccessMetadataProvider provider, IEnumerable`1 combinedModules) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.Extend(MetadataSource metadataSource, String moduleName, IOpenAccessMetadataProvider provider, Boolean safeMode, IEnumerable`1 combinedModules) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.RegisterProviderInternal(IOpenAccessMetadataProvider provider, Boolean forceDatabaseInit, Boolean safeMode) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.RegisterProvider(IOpenAccessMetadataProvider provider, Boolean safeMode) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.InitializeProvider(IOpenAccessMetadataProvider provider, String connectionName, Boolean safeMode) at Telerik.Sitefinity.Data.Decorators.OpenAccessDecorator.InitializeDatabase(DataProviderBase dataProvider, NameValueCollection config) at Telerik.Sitefinity.Data.Decorators.OpenAccessDecorator.Initialize(String providerName, NameValueCollection config, Type managerType) at Telerik.Sitefinity.Data.DataProviderBase.Initialize(String providerName, NameValueCollection config, Type managerType, Boolean initializeDecorator) at Telerik.Sitefinity.Data.DataProviderBase.Initialize(String providerName, NameValueCollection config, Type managerType) at Telerik.Sitefinity.Data.ManagerBase`1.InstantiateProvider(IDataProviderSettings providerSettings, Type providerType, ExceptionPolicyName policy, ManagerBase`1 manager) Additional Info: MachineName : PC8582 TimeStamp : 1/29/2016 3:49:22 PM FullName : Telerik.Sitefinity.Utilities, Version=8.2.5903.0, Culture=neutral, PublicKeyToken=b28c218413bdf563 AppDomainName : /LM/W3SVC/2/ROOT-2-130985559927631905 ThreadIdentity : WindowsIdentity : DQE\bhair Requested URL : http://127.0.0.1/ Inner Exception --------------- Type : System.InvalidOperationException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : The provider 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider' database schema version (410) is higher than the currently running version (390). Downgrade is not allowed. Source : Telerik.Sitefinity Help link : Data : System.Collections.ListDictionaryInternal TargetSite : UpgradeParams CheckForUpgrade(Telerik.Sitefinity.Data.IOpenAccessMetadataProvider, Telerik.Sitefinity.Data.OA.OpenAccessConnection, System.String, Telerik.Sitefinity.Data.OA.ISitefinityMetadataSource, Telerik.Sitefinity.Metadata.Model.SchemaVersion) HResult : -2146233079 Stack Trace : at Telerik.Sitefinity.Data.OA.OpenAccessConnection.MetadataUpgradeFacade.CheckForUpgrade(IOpenAccessMetadataProvider provider, OpenAccessConnection connection, String moduleName, ISitefinityMetadataSource sitefinityMetaDataSource, SchemaVersion schemaVersion) at Telerik.Sitefinity.Data.OA.OpenAccessConnection.MetadataUpgradeFacade.UpgradeSchema(ISchemaHandler schemaHandler)   

    Error 1:

    Unable to upgrade database schema metadataSource provided by 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider': The provider 'Telerik.Sitefinity.Frontend.FilesMonitoring.Data.OpenAccessFileMonitorDataProvider' database schema version (410) is higher than the currently running version (390). Downgrade is not allowed.

     

    Please help. No idea how to fix this.

  2. Bryson
    Bryson avatar
    13 posts
    Registered:
    14 Jan 2016
    29 Jan
    Link to this post

    For the time being, I removed 

    <add startupType="OnApplicationStart" version="1.4.390.0" name="Feather" />

    from SystemConfig.config.

    If someone could explain to me what I need to do so I can utilize the mvc widgets and templates provided by feather I'd really appreciate it.

  3. Velizar Bishurov
    Velizar Bishurov avatar
    143 posts
    Registered:
    01 Dec 2016
    03 Feb
    Link to this post
    Hi,

    The error you are receiving is most probably caused by Feather having been turned on once already (with version 1.4.410.0) and now there is an attempt to turn it on again with version 1.3.390.0.

    You can check the Telerik.Sitefinity.Frontend reference in the project and see what is the current version of the dlls. If it is 1.3.390.0 use the Feather nuget package to update it to 1.4.410.0.

    After that remove the version attribute of the Feather entry in the SystemConfig.config and restart the project. The entry should look like so:

    <add name="Feather" />

    If the assembly version is already 1.4.410.0 build the project and remove the version attribute from the Feather entry as above. After that restart the application.

    The reason to build is that Sitefinity uses the dll files that are in the bin folder and usually the Feather references come from a nuget package. In order to have the proper version of the dll files in the bin folder the project must be built.

    Regards,
    Velizar Bishurov
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
  4. Velizar Bishurov
    Velizar Bishurov avatar
    143 posts
    Registered:
    01 Dec 2016
    05 Feb
    Link to this post
    Hi,

    Have you been able to investigate whether Feather is turned on? Did removing the version attribute help resolve the issue?

    Regards,
    Velizar Bishurov
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
  5. Bryson
    Bryson avatar
    13 posts
    Registered:
    14 Jan 2016
    05 Feb
    Link to this post

    Eventually, I updated the Feather nuget package then turned on the Feather module. Everything was fine.

    First time I updated Feather.Core package, saw everything else update then turned on the Feather module. Doing these actions caused it to spit out these error when it sitefinity reinitialized.

  6. Velizar Bishurov
    Velizar Bishurov avatar
    143 posts
    Registered:
    01 Dec 2016
    09 Feb
    Link to this post
    Hello,

    The Feather.Core nuget package is designed to be used in external assemblies to allow creating widgets in such. Upgrading it, however, does not execute the required PowerShell scripts to upgrade the Feather module in Sitefinity. This is the reason for the errors.

    Regards,
    Velizar Bishurov
    Telerik
     
    Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal and vote to affect the priority of the items
     
    Answered
  7. Bryson
    Bryson avatar
    13 posts
    Registered:
    14 Jan 2016
    09 Feb
    Link to this post

    That answers a lot. Somewhere in your docs I read you could do either upgrade Feather or Feather.Core

    Thank you!

7 posts, 1 answered