As above subject I am having a "simple" issue where enabling the Site Collection feature just fails and show me "An unexpected error has occured".
Note: enabling the Site Collection Feature Nintex Workflow 2013 for the Central Administration site however is succesful (but no I don't want to do that!)
Checking the logs this is what is showing, since this is a Dev machine there is no access to the internet which may be linked to the http://tempuri checking (?)
or is it Cache Service / Security Token ... ?
thanks for any tip
___ w3wp.exe (0x3004) 0x1378 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'https://localhost:32844/SecurityTokenServiceApplication/WindowsTokenCache.svc' Channel: 'Microsoft.SharePoint.Administration.Claims.ISPWindowsTokenCacheServiceContract' Action: 'http://tempuri.org/ISPWindowsTokenCacheServiceContract/IsUserHandleCached' MessageId: 'urn:uuid:6b116986-83d4-4ff8-85f1-1d1840a9add5' 9578ae9c-441a-2002-dd20-418829e8e851
PS: OMG ! sooooo confusing this posting a message to forum, why call it "build your own" your own what exactly ? :(
Solved! Go to Solution.
I suspect that might not be the error actually preventing the feature for activating. Is there by any other errors that are 'Unexpected' level instead of 'Medium'?
(strange I didn't receive email on that reply)
Eventually I found out that it was when I enable FBA Authentication on it.. weird...
Will know more when I have a separate environment ready.
Thanks for sharing the solution.
Normally, during the Nintex Workflow installation process in Central Admin, the ‘Activate for web application’ step will grant those permissions to the IIS account for each web application.
Yes you are correct james.
Just share my experience:
Last week i added the new service account for my new imported site from other sharepoint farm.
when i try to activate the nintex workflow feature in the site collection unknown error occured.
Check it to the ULS log, my new service account for that site dont have permission in the NWDB.