You cannot use SharePoint. Your system administrator has turned off the feature. Outlook 2013

When the user tries to connect to outlook from SharePoint calendar, then below error appears.

"You cannot use SharePoint. Your system administrator has turned off the feature".

Microsoft Windows SharePoint Services features are turned on in Microsoft Office Outlook 2013. In cases where administrators do not want their Outlook 2013 users to have access to Windows SharePoint Services features, it is possible to turn off these features.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Solution:

1. Run REGEDIT

2. Go to HKEY_CURRENT_USER/Software/Microsoft/Office/15.0/Outlook/Options/wss

3. Double-click on the disable and set the Value data to 0 (0 for enable and 1 for disable) click ok.

Infopath Error: The form template is browser-compatible, but it cannot be browser-enabled on the selected site

When we set the InfoPath to open in the browser by setting the following properties.

Form Options -> Compatibility -> Web Browser Form

And also the Form Library Settings to Open in browser.

 And when we try to publish the InfoPath form, then it will give the below warning message.

"The form template is browser-compatible, but it cannot be browser-enabled on the selected site"

In order to avoid this error, make sure that the site collection feature "SharePoint Server Enterprise Site Collection features" is enabled.

 When it is enabled, then we will not get this warning message.

 

Infopath Issue: Web page cannot be displayed

Recently when we have upgraded from SharePoint 2007 to SharePoint 2013, we have found one strange issue with opening the InfoPath Forms.

When we try to edit the InfoPath template by going to the Form Library -> Advanced Settings, then it thrown the below error as "Webpage cannot be displayed".

This issue occurs for one user who is trying to open the form in InfoPath 2010 version. This issue didn't occur for the users who has the InfoPath 2013 version.

I found the below blogs which are helpful to resolve the issue.

https://social.msdn.microsoft.com/Forums/exchange/en-US/c47561bd-d7f0-441f-bc27-3b6e1f0457a0/cannot-view-infopath-form-on-sharepoint-2013-since-i-removed-skydrive-for-business-and-installed?forum=sharepointcustomization

https://blogs.technet.microsoft.com/office_integration__sharepoint/2014/02/24/the-webpage-cannot-be-displayed-when-trying-to-openedit-an-office-file-from-a-sharepoint-2013-site/

In the first article, they have mentioned to change the registry key.

So, please follow the below steps to change the registry key.

Go into the registry by typing regedit from the Run line and rename the SharePoint.OpenDocuments.5 key (ex. SharePoint.OpenDocuments.5.old) under HKEY_CLASSES_ROOT.


 

Issue with Email address/Sending Email in Infopath Form

If the user tried to send an email through the Send Email Data Connection, where we specify the To/CC field mapped to a 'DisplayName' from the person or group field in the InfoPath Form.

It works most of the time, but I have seen there are some users whose email address is not resolved and so it always throws error that its not able to find the email address of that user.

This issue occurs if the user has an account in more than one domain, then they get this error message. User who have only one account in intranet domain, their account name resolves and email is sent.

Please check the below blogs talking about the same issue.

https://support.microsoft.com/en-us/kb/968479

http://answers.microsoft.com/en-us/ie/forum/ie11-iewindows8_1/the-form-cannot-be-submitted-because-some-of-the/549e5d02-3402-4209-a3ed-ca82ef3a4805?auth=1

To resolve this issue, get the email address of the user from the person or group field using user profile service and give that email address field in the Send Email Data Connection.

Name of the Requestor Email Address text box is C070EmailAddress.

Name of the Requestor people picker field is C070Group

For the "Get Email" button, add the rules as shown below.

Here the first action is Set a Field's value.

Here the AccountName is from the User Profile web service data connection.

 

 

And here the "AccountId" is the AccountId from the C070Group people picker field.

 

 

 

Next action is "Query for Data" and here select the "GetUserProfileByName" data connection.

 

 

 

Next action is a Set Field's value. Here Set the "C070EmailAddress" text box field value with the WorkEmail which got retrieved from the user profile web serivce data connection.

 

 

 

Here is the step on how to get the value of the WorkEmail for that user.

 



 



 

Then save the rule. When you preview the form, if you enter the user in the people picker box (C070Group), and click on button "Get Email", then it will retrieve the email address for the entered user from the user profile.

 

Issue with UserGroup Service in Infopath Form

When InfoPath give the error as "Unable to connect to the web service.
http://sharepoint.daks.com:1111/sites/InfoTest/_vti_bin/UserGroup.asmx?WSDL

This issue occurs if the user is not able to see the membership of the group.

Check the below article.

http://www.infopathdev.com/forums/p/23009/79618.aspx

Because i was using the GetUserCollectionFromGroup to check a user's membership in a group, I needed to enable the option in the SharePoint group to allow everyone to view the group membership.  Once I turned that on, it appears that my users are no longer getting the error message.  Now that I've fixed it, it seems to make sense...how can you check if you're a member of a group if you can't see the group membership?
Hopefully this will help someone else out somewhere down the line.

User Access issue after upgrading the SP 2010 site to SP 2013

Users coming from a SharePoint 2010 system that try to access SharePoint 2013 after a migration receive a “this site has not been shared with you” message. This mean that they are not able to authenticate to SharePoint 2013.

In SharePoint 2013 there is a new authentication mechanism called Claim based authentication. Be default through the UI all Applications are created in this mode.

I created a PowerShell script that loops through all of your SharePoint 2013 web applications and upgrades each one to claim’s based authentication.

Script:

 Param(

    [string]  $account = $(Read-Host -prompt "UserAccount")

    )

Add-PSSnapIn Microsoft.SharePoint.PowerShell

foreach ($wa in get-SPWebApplication)

{

    Write-Host "$($wa.Name) | $($wa.UseClaimsAuthentication )"

    #http://technet.microsoft.com/en-us/library/gg251985.aspx

    $wa.UseClaimsAuthentication = $true

    $wa.Update()

    $account = (New-SPClaimsPrincipal -identity $account -identitytype 1).ToEncodedString()

    $zp = $wa.ZonePolicies("Default")

    $p = $zp.Add($account,"PSPolicy")

    $fc=$wa.PolicyRoles.GetSpecialRole("FullControl")

    $p.PolicyRoleBindings.Add($fc)

    $wa.Update()

    $wa.MigrateUsers($true)

    $wa.ProvisionGlobally()

}

For more information, refer the msdn blog: http://technet.microsoft.com/en-us/library/gg251985.aspx

Common SharePoint Issues & Solutions

• PROBLEM:  When attempting to deploy a solution from Visual Studio you get an access error that includes this code – “SPUserCodeV4″

• SOLUTION: Go to Central Administration -> System Settings. Under the “Server” heading go to “Manage Services on Server.” Look for “Microsoft SharePoint Foundation Sandboxed Code Service” and enable it. If that doesn’t work, go to the Security item in the sidebar. Under the “General Security” heading, go to “Configure service accounts.” Each service has to have a user account assigned to it. Silly. I know. Select “Windows Service – Microsoft SharePoint Foundation Sandboxed Code Service” from the dropdown, and leave YourBelovedandVeryImportantCustomer\spadmin as the account.

• PROBLEM: When running a user control that contains UserProfileManager, you get an error that says the object cannot be found

• SOLUTION: UserProfile Service has to be started in Central Admin. Follow the directions above, but enable both UserProfile services. You will be prompted to assign an account. Leave the account as YourBelovedandVeryImportantCustomer\spadmin. Reset IIS.

• PROBLEM: All your list searches return null. OR a programmatic list update fails.

• SOLUTION: Look at how you are creating your SPWeb item. If you are setting it equal to a local site, make sure the list is on that site. Here’s some handy code to get to the top level of the site without any items to dispose:

using (SPSite site = new SPSite(SPContext.Current.Site.Url))  {     using (SPWeb web = site.OpenWeb())     {         SPList list = web.List["TheNameOfYourList"];     } } *Edit: SPContext objects should not be disposed, see Jason's absolutely correct comment below!

• PROBLEM: On a filtered list, you cannot select a value if it is the only row.

• SOLUTION: This one eluded me for a little while. In the “Miscellaneous” category of the web part editor panel, there is a “Send first row to connected web parts…” item. Initially this seems to just control when in the page life the data is sent. HOWEVER… In typical SharePoint non-logic logic…  this actually means “select first row by default.” The data binding event occurs regardless, except the datarow is empty if there is no selected row. Oh SharePoint, you poorly-worded rascal!

• PROBLEM: ”File Not Found” error. OR User Profile service cannot be accessed at all.

• SOLUTION:

• If you are only experiencing the first issue do this:
• Go to Central Admin > Application Management > Manage Services on Server
• Start the following:
• Microsoft SharePoint Foundation Web Application
• Managed Metadata Web Service
• SharePoint Server Search
• If you still have a file not found error, restart IIS.
• If you STILL have a file not found error, restart SharePoint Web Services in IIS Manager manually
• If you are having user profile service issues, do the above, then check the following:
• Go to Start > Administrative Tools >  Services
• Both forefront identity managers need the following settings -
  • Make sure they are both disabled (SP will start them automatically)
  • Right click the service name and go to properties. Click the “Log On” tab. Chck “This Account” and put the farm account in. On our server its UCLA\SPAdmin, password is “password”
• Go to Start and enter “MMC” in search. Open the management console.
  • Go to “Add snapins” in the file menu
  • Add “Certificates”
    • Select Computer account for the account
    • Select local machine for the machine
  • In The following three places, look for security certificates that begin with “Forefront”
    • Personal > Certificates
    • Trusted Root Certification Authorities > Certificates
    • Trusted People > Certificates
  • If none of the certificates exist, that’s fine. If they do, delete them.
• Follow the steps in Spence Harbar’s post here:  To delete the current user profile service and create a new one.
• After all this reset IIS.
• If you still can’t connect, check Central Admin > Application Management > Service Application – Configure Service Application Associations
  • Make sure the web app has the User Profile Service proxy enabled.

After you delete your current service, you may want to delete the Application Pool so that you can create a new one with a logical name. (The default is “User Profile Services Application” and it’s a pain to have to create new pools with new names all the time, but it’s nice to just clear the old one out and try again) Run PowerShell as an administrator, and enter do the following: enter Add-PSSnapin Microsoft.SharePoint.PowerShell enter Get-SPServiceApplicationPool Copy the name of the pool you want to delete enter Remove-SPServiceApplicationPool “Name of my pool” Keep the quotes around the name

• • If you are still experiencing problems, you may want to restart all the associated machines.
    • If you do this, you may need to:
      • go to the your DB machine and open the sql config manager. Make sure all the services are started
      • On both the APP and WFE machines, make sure user profile service and all of the sharepoint services started back up.
    • If you get an error that the configuration database is unavailable from Central Admin, then you need to double check all the services on the DB machine from sql config manager. If you miss a single one, you may not be able to access SQL.

Restart Microsoft SharePoint Foundation Web Application Service. Error

I wanted to share some information in case you are planning to restart “Microsoft SharePoint Foundation Web Application” service or any other service and got stuck with status showing “Stopping” you can use power shell command mentioned below.

I had a situation when “Microsoft SharePoint Foundation Web Application” service was Showing “Stopping” status for more than 7 hours and even reboot and IIS reset did not do anything. I was able to restore service in normal condition using command mentioned below.

Note: In case you are planning to restart “Microsoft SharePoint Foundation Web Application” service better back up your IIS and Virtual directory folder to be on the safe side.

If you have the same situation where some service is stuck use power shell to stop it

$svc = Get-SPServiceInstance | where {$_.TypeName -like "*Foundation Web*"}
$svc.Status = "Offline"
$svc.Update()

You can use PowerShell to start it again

$svc = Get-SPServiceInstance | where {$_.TypeName -like "*Foundation Web*"}
$svc.Status = "Online"
$svc.Update()

In order to get virtual directories back run this PowerShell command

$wa = Get-SPWebApplication http://webAppUrl
$wa.ProvisionGlobally()