DNS Configuration for SharePoint Apps

When you trying to add an app from store you might get below error. In order to fix this there are two things to be done.

Task 01. Configure App Managements and Subscription Settings service in SharePoint

Task 02. Configure DNS server to support app URLs

Below blog post will be focused on Task 02 where you configure DNS record in DNS server.

image

 

  • Open DNS using MMC then right click your domain and select add new CNAME

clip_image001

  • Once you got prompted to enter record details add *.app as the alias name and as FQDN of target host as your domain name (in my case its silab.int)

clip_image002

  • After successful addition of DNS you will find the record as below.

clip_image003

  • Now from the DNS end you are ready to go. Verify the entry by ping blablablaa.app.silab.int

image

  • Make sure you configure the App Management and Subscription Settings services (both) in SharePoint before adding the app URLs.

image

Thank you Smile

Enjoy SharePointing Open-mouthed smile Open-mouthed smile Open-mouthed smile

Advertisements

Register-SPWorkflowService The remote server returned an error: (404) Not Found

This errors pops out if you have installed SharePoint Server 2013 on Windows Server 2012 R2. Its true that SharePoint 2013 now supports Windows Server 2012 R2 after the SP1 update.

Even though you have SP1 (​15.0.4569.1000) you still will get the error when registering workflow service.

image

  • If it shows “Workflow is Not Connected” you have to register the workflow service in SharePoint.
  • In order to register run “Register-SPWorkflowService -SPSite “http://SPSite” -WorkflowHostUri “http://ServerName:12291″ -AllowOAuthHttp” in elevated SharePoint Management shell

clip_image002

  • If the workflow service in running on a Windows Server 2012 R2 server you will get an error (Register-SPWorkflowService : The remote server returned an error: (404) Not Found) as shown above.
  • In order to fix download the Web Platform Installer (http://www.microsoft.com/web/downloads/platform.aspx) then search for Workflow Manager CU2 and proceed with installation.

clip_image003

clip_image004

clip_image005

clip_image006

clip_image007

clip_image008

Thanks you. Smile

Enjoy SharePointing Open-mouthed smileOpen-mouthed smileOpen-mouthed smile

Download Service Pack 1 for Microsoft SharePoint Server 2013 (Updated)

Microsoft released an updated and fixed version of Service Pack 1 (SP1)( http://support.microsoft.com/kb/2880552 ) for SharePoint 2013 on April 22.
A list of all the new associated Knowledge Base articles on the updated SP1s for SharePoint Foundation 2013, SharePoint Server 2013, Project Server 2013, and Office Web Apps Server 2013 are available from this TechNet blog post.(http://blogs.technet.com/b/wbaer/archive/2014/04/08/service-pack-for-sharepoint-server-2013-1-recalled.aspx)

The post notes that these KB articles are different from those associated with the recalled (http://support.microsoft.com/kb/2817429) SP1. Customers who previously deployed SharePoint 2013 SP1 are advised to download the updated SP1 and install it over the existing SP1. Customers who didn’t deploy the original SP1 bits should just use the uploaded bits.

There is no update to the slipstreamed ISO from MSDN, MPN and the Volume Licensing Service Center “as it was not affected by the issue,” according to Microsoft officials.

Much awaited SharePoint Server 2013 Service Pack 1 has been released Smile

Download Link: http://www.microsoft.com/en-us/download/confirmation.aspx?id=42008
  http://www.microsoft.com/en-us/download/details.aspx?id=42008
KB Article http://support.microsoft.com/kb/2817429
TechNet Blog Article http://blogs.technet.com/b/office_sustained_engineering/archive/2014/02/25/announcing-the-release-of-service-pack-1-for-office-2013-and-sharepoint-2013.aspx

Test SharePoint Outgoing Mail

Use below commands SharePoint Management Shell in order to verify that SharePoint Outgoing mail works fine. Make sure you have added Outgoing Mail Server and Sending mail account under Outgoing email setting in Central Admin.

01. $site = New-Object Microsoft.SharePoint.SpSite(http://webSite)

02. $web = $site.OpenWeb()

03. $sent = [Microsoft.Sharepoint.Utilities.SpUtility]::SendEmail($web,0,0,”admin@domain.com”,”Test mail subject”,”test mail body”)

04. $sent

If the result from 04 is true. Outgoing E-mail is configured and working perfectly.

The amount of data that was returned by a data connection has exceeded the maximum limit that was configured

If you are using Info Path to develop web forms you might have faced this issue. Follow below steps as described in “Resolution” in order to overcome this issue.

Issue:
When you try to get data from Data Connection for e.g. web service. You get the following error:
“The amount of data that was returned by a data connection has exceeded the maximum limit that was configured by the server administrator. Form elements, such as drop-down lists may be blank.”

 

Cause:
The Default data connection response size if set to 1500kb for Form Services, If the response from the data connection size exceeds the default limit the warning will be shown on screen.

 

Resolution:
01. Click on General Application Settings in Central Administration
02. Click on Configure InfoPath Forms Services under InfoPath forms Services

03. Change the Response Size in kilobytes (Increase the number).

Access Denied on Sites after migrating SharePoint 2010 to SharePoint 2013

After migrating the Farm from SharePoint 2010 site to SharePoint 2013 platform (Under Same domain) using the “Mount-SPContentDatabase” command, users were unable to login or access denied. When grant permission again you might note that now that particular user can access the site.

And you might also have note a prefix (i:0#.w|) has been added to username.

Solution: You have to convert the authentication method of the SharePoint Web Application from Classic to Claims

This is where PowerShell becomes really nifty. You can use PowerShell to get the conversion done.

$WebApp = Get-SPWebApplication “http://WebAppURL”

Convert-SPWebApplication -Identity $WebApp -To Claims –RetainPermissions -Verbose

$WebApp.MigrateUsers($true)

For more details on Migrate from classic-mode to claims-based authentication in SharePoint 2013 you can refer this TechNet Article: http://technet.microsoft.com/en-us/library/gg251985.aspx

Happy SharePointing !!! Open-mouthed smile