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

Forums / Bugs & Issues / Sitefinity 5 on Windows 10 Creators Update

Sitefinity 5 on Windows 10 Creators Update

17 posts, 0 answered
  1. Daniel
    Daniel avatar
    0 posts
    Registered:
    09 Sep 2014
    26 Apr
    Link to this post

    Hello,

    Since my machine was automatically updated to Windows 10 Creators Update, our Sitefinity 5 site hasn't worked locally.

    Whenever I go to hit a Sitefinity managed URL, I am redirected to the Licensing page, where I am prompted to add a license.

    I upload the license which has been working on the previous Windows 10 Anniversary Update, and I get a 'Configuration Error' Exception, where 'No permission set is defined with the name of "Pages"':

    ----------------------------------------
    Timestamp: 26/04/2017 2:14:57 AM
     
    Message: HandlingInstanceID: 43de22f5-a844-43b0-8caf-2a687da78303
    An exception of type 'System.ArgumentException' occurred and was caught.
    ------------------------------------------------------------------------
    04/26/2017 10:14:57
    Type : System.ArgumentException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Message : No permission set is defined with the name of "Pages".
    Source : Unity_ILEmit_DynamicClasses
    Help link :
    ParamName :
    Data : System.Collections.ListDictionaryInternal
    TargetSite : System.Linq.IQueryable`1[Telerik.Sitefinity.Pages.Model.PageNode] GetPageNodes()
    HResult : -2147024809
    Stack Trace :    at DynamicModule.ns.Wrapped_OpenAccessPageProvider_cbb93fabcea54f7f962fa06a38024e5d.GetPageNodes()
       at Telerik.Sitefinity.Web.SiteMapBase.Initialize(String name, NameValueCollection attributes)
     
    Additional Info:
     
    MachineName : DANIELMSI
    TimeStamp : 26/04/2017 2:14:57 AM
    FullName : Telerik.Sitefinity.Utilities, Version=5.0.2500.0, Culture=neutral, PublicKeyToken=b28c218413bdf563
    AppDomainName : /LM/W3SVC/1/ROOT-1-131376464202843446
    ThreadIdentity :
    WindowsIdentity : IIS APPPOOL\MyWebsite
     
     
    Category: ErrorLog
     
    Priority: 0
     
    EventId: 90020
     
    Severity: Error
     
    Title:Enterprise Library Exception Handling
     
    Machine: DANIELMSI
     
    App Domain: /LM/W3SVC/1/ROOT-1-131376464202843446
     
    ProcessId: 14284
     
    Process Name: c:\windows\system32\inetsrv\w3wp.exe
     
    Thread Name:
     
    Win32 ThreadId:2632
     
    Extended Properties:
    ----------------------------------------

     

    This only started happening after the Win10 CU update, which seems to have included .NET 4.7 as an in-place replacement for all other .NET Frameworks. I'm guessing the root cause is something to do with the license check, although without further information I can't tell.

    Anyone else seen this, and does anyone have any ideas on how to get past this?

    Thanks,

    Daniel

  2. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    28 Apr
    Link to this post

    I have had a ticket in on this for a couple weeks.  They only fix is to rollback the update... I don't know what the plan is, but they said Windows 10 isn't supported which is just insane :/

     

    Let's hope they can resolve this quickly in a hotfix it something.

  3. Keivan Kechmiri
    Keivan Kechmiri avatar
    38 posts
    Registered:
    16 Aug 2009
    28 Apr
    Link to this post

    Hi, I'm having the same problem but with Sitefinity 10 and Another error message at startup.

    Any new on this (I can't roll back so this is a real problem)

  4. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    28 Apr in reply to Keivan Kechmiri
    Link to this post
    Is it like a policy at work where you can't? Because LITERALLY the only fix is to uninstall it.  Please put in a ticket so they know it's not just me with the issue.
  5. Evan
    Evan avatar
    0 posts
    Registered:
    30 Jul 2011
    16 May
    Link to this post

    We have seen the same "class" of problems with SiteFinity 8.1 after the Creator Update: our projects will start, then fail to initialize the SecurityManager with a "key already exists" error.

    The issue cropped up for two members of our team with the Creator Update, while the same code (and a fresh checkout from source) works fine for team members who are still on Anniversary.

    We are in the process of rolling back, but the rollback broke our Visual Studio installs... so now we watch progress bars.

  6. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    16 May in reply to Evan
    Link to this post
    Apparently a fix is coming around the end of the week.
  7. Stephen2
    Stephen2 avatar
    94 posts
    Registered:
    05 Feb 2012
    4 days and 11 hours ago
    Link to this post

    Oh man, this just got us we think...  New staff member spending hours trying to debug, then he found this thread.

    My only concern is that we've installed off an ISO that maybe has Creators update rolled into it??  Hope we can roll back...

     

  8. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    4 days and 11 hours ago in reply to Stephen2
    Link to this post

    The only thing borked for me on a rollback was a couple baked in Windows store apps like Skype...

    I would rather though wait a day or 2 to see if the fix comes with the friday release... 

  9. Stephen2
    Stephen2 avatar
    94 posts
    Registered:
    05 Feb 2012
    4 days and 10 hours ago
    Link to this post

    Yeah, just confirmed we can't roll back the update, because it was baked into the latest Win10 ISO image.

    Brett is researching any workaround, but we think it might be reinstall Windows time...............

     

     

  10. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    4 days and 10 hours ago
    Link to this post
    In my ticket I asked the awesome support agent to get someone to give us an update here
  11. Turbo
    Turbo avatar
    3 posts
    Registered:
    31 Jul 2012
    4 days and 7 hours ago
    Link to this post

    Steve, in your ticket, did they share what they were going to do?

    Obviously, we run sites that run from  Sitefinity 5.1 through 10, so if there's a patch, we're going to have to get it for any version we currently support.

    If someone from SF doesn't post here by tomorrow, we'll throw in a ticket as well. I can't believe this hasn't manifested itself internally at SF during the demo builds?

     

  12. CanberraNet
    CanberraNet avatar
    0 posts
    Registered:
    05 Dec 2014
    4 days and 6 hours ago
    Link to this post

    Just installed .net 4.7 on a server 2012 R2 and am getting the same 'An item with the same key has already been added' with sitefinity 8.1

    Not sure what to do.

     

    EDIT:  uninstalling .net 4.7 (Update for Microsoft Windows (KB3186539)) fixed it

  13. Keivan Kechmiri
    Keivan Kechmiri avatar
    38 posts
    Registered:
    16 Aug 2009
    4 days and 3 hours ago in reply to CanberraNet
    Link to this post

    Just a quick update, I have a direct connection with both people at Progress and Microsoft (.NET team) and both are parties are discussing and working on a solution. Progress are working on a new version and Microsoft are looking at (at least for me a test of a .NET "fix"). 

     

    Regarding timeframe dont really know my guess next week (just my personal guess)

  14. Velizar
    Velizar avatar
    0 posts
    Registered:
    05 May 2015
    3 days and 23 hours ago
    Link to this post
    Hello everyone,

    We are aware of the problem with the Creators update. The issue strives from changes in the .NET Framework 4.7 that comes with this update and as such it is quite hard to create fix. A fix must pass a set of tests to ensure there is no other regression. During the development of the fix some other problems were also discovered that slowed down the release of the fix. It is also important to note that a fix must also ensure compatibility with operating systems not running .NET 4.7 which is not an easy task on its own.

    On top of that the behavioral changes caused by the .NET update differ depending on the Sitefinity version which further complicates the story as the fix would need to be different for each version.

    With the above information in mind it is crucial to understand that it is a serious effort from our side to fix this particular problem for .NET 4.7 and we are doing the best we can. Even though the issue seems trivial it alters a vital part of the Sitefinity initialization process and developing a fix for that is not very trivial.

    At the moment we are preparing to release an internal build for Sitefinity 10.0 tomorrow (Friday, 19th of May) and a hot-fix will follow-up early next week. We will continue our efforts in investigating what are the possibilities to deliver fixes for older versions.

    Regards,
    Velizar Bishurov
    Telerik by Progress
  15. Steve
    Steve avatar
    3037 posts
    Registered:
    03 Dec 2008
    3 days and 23 hours ago in reply to Velizar
    Link to this post
    Thanks for the update, I dont think anyone assumes it's trivial though.  Sucks on your end getting hit by things out of your control (like the chrome drag\drop issue a few months back)
  16. Daniel
    Daniel avatar
    0 posts
    Registered:
    09 Sep 2014
    3 days and 12 hours ago in reply to Velizar
    Link to this post

    Thanks for the update. Definitely agree, it's not your fault at all, it's all on Microsoft for forcing these stupid in-place framework updates that break things. Why they couldn't do a side by side install is beyond me ¯\_(ツ)_/¯

    Hopefully there's some good news for those of us still on Sitefinity 5.

    Thanks,

    Daniel

  17. Velizar
    Velizar avatar
    0 posts
    Registered:
    05 May 2015
    2 days and 22 hours ago
    Link to this post

    Hello everyone,

    An update from our side.

    Due to some unexpected turn of events the release of an internal build for Sitefinity 10.0 has been postponed for Monday next week (22nd of May). The good news is that we are also preparing to release fixes for versions 7.0 - 9.2.  We hope to be able to finish the release of those by the end of next week.

    It is still unclear whether a fix for versions below Sitefinity 7.0 is at all possible. 

    Regards,

    Velizar Bishurov

    Telerik by Progress

17 posts, 0 answered