Skip to main content

This feature has been disabled by your administrator - Office 2013

I got this rather nagging error while trying to customize a List in our SharePoint Online site using Infopath 2013.

It turned out that you have to do some registry hack to get this working.

Change the value of registry key SignInOptions under HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\SignIn\ to 0.

You may also want to change the UseOnlineContent key under HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Common\Internet\ to 2.

If you cannot find these keys in registry a new DWORD can be created.

There is a blog post from Sahil Malik which helped me solve this issue:
http://blah.winsmarts.com/2013-5-Registry_keys_to_administer_Office_365_in_your_Organization.aspx

Here is the Microsoft document on this:
http://technet.microsoft.com/en-us/library/jj715259(v=office.15).aspx

These settings are best handled through Group Policy and you may want to check with your IT/Network team before doing these changes.
Labels:

Comments

Anonymous said…
You may need to change the SignInOptions under

HKCU\Software\Policies\Microsoft\Office\15.0\Common\SignIn\

This is what I had to do since it is being set by a GPO.

This article defines the values.

http://technet.microsoft.com/en-us/library/jj683102%28v=office.15%29.aspx
December 23, 2014 at 12:15 AM
Anonymous said…
Do you have a fix if your GPO automatically overrides the value you set in the following registry:

HKCU\Software\Policies\Microsoft\Office\15.0\Common\SignIn\
April 18, 2015 at 4:33 AM
Post a Comment

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more