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.
Type : System.ArgumentException, mscorlib, Version=188.8.131.52, Culture=neutral, PublicKeyToken=b77a5c561934e089
Message : No permission set is defined with the name of "Pages".
Source : Unity_ILEmit_DynamicClasses
Help link :
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)
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
WindowsIdentity : IIS APPPOOL\MyWebsite
Requested URL : https://mywebsite.dev.local/customer-service/warranty
Title:Enterprise Library Exception Handling
App Domain: /LM/W3SVC/1/ROOT-1-131376464202843446
Process Name: c:\windows\system32\inetsrv\w3wp.exe
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?
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.
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)
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.
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...
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...............
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?
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
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...
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)