Hosted Apps returns "An unexpected error has occurred." for HTTPS but works for HTTP

Hosted Apps returns "An unexpected error has occurred." for HTTPS but works for HTTP

Issue: I set up a new Hosted Apps configuration using a separate dedicates domain name with a wildcard certificate.  Everything works fine for HTTP access but when I access via HTTPS I just get a "An unexpected error has occurred" message in the browser.

Cause: The App request URL and the App service response URL for the requested App must be on the same protocol (either HTTP or HTTPS)

In my case the App request URL was over HTTPS but the App service response URL was over HTTP (i.e.). because that is the URL (Protocol) set in the DEFAULT ZONE of that web application.

The App service respond using the Default zone protocol. This is a security measure to avoid CROSS-DOMAIN attacks when the app is requested or launched.

Resolution: please follow the below steps to resolve the issue.

1.   ​If the Site/App is browsed over HTTP and you experience the above behavior (a blank Page), set the Default zone URL of that web application to HTTP and try again.

2.   If the Site/App is browsed over HTTPS and you experience the above behavior (a blank Page), set the Default zone URL of that web application to HTTPS and try again.

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Hardware and software requirements for SharePoint 2013

Hardware and software requirements for SharePoint 2013

The information in this article applies to SharePoint Foundation 2013 and SharePoint Server 2013. For information about the features that each version supports, see the SharePoint 2013 Product Page.

Some of the hardware requirement values in this article are based on test results from SharePoint 2010 Products and still apply to SharePoint 2013. This article will be updated with appropriate values and republished when new data becomes available. Hardware requirement values obtained from SharePoint 2010 Products that are listed in this article do not apply to search in SharePoint 2013.

This article links to SharePoint 2010 Products guidance where that guidance is still valid. The SharePoint 2010 Products guidance is not applicable for search in SharePoint 2013 because the search architecture has changed significantly.
The hardware and software requirements in this article refer to physical and virtual servers in a SharePoint farm.

Find the below Detailed Link from the MS

http://technet.microsoft.com/en-in/library/cc262485%28v=office.15%29.aspx

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The search service is not able to connect to the machine that hosts the administration component.

The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component in search application ‘Search Service Application′ is in a good state and try again.”

Error :- The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component ‘XXXXXXXXXXXX′ in search application ‘Search Service Application 8′ is in a good state and try again.”

Solution: please follow the below steps to resolve the issue.

1.Change the app pool of the search service to "SharePoint Web Services Default". in the properties of the search service.
  CA-->Manage Service Applications-->Select "Search Service Application"

2.in the ribbon control choose "Properties".
then change the below both service’s app pool to  "SharePoint Web Services Default" 

App Pool For Search Admin Web Service,
Application Pool for Search Query and Site Settings Web Service

Note:For more issues and resolutions on search,check the post categories of search

  

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

June-CU 2014 issues in SharePoint 2013

June-CU 2014 issues in SharePoint 2013

Be sure  that all Update for SharePoint 2013 require SharePoint Server 2013 SP1 OR March 2013 PU for SharePoint 2013 to be installed first.

Previous releases of the SharePoint Server 2010 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hot fix Download Available link in the KB article for the release. 

If any of the Cab file is missed we see the error “Installation of the package failed”

All the below files need to download and put in the same location only.

 

 

 

NOTE!
The March PU Is not required prior to install SP1 on top of RTM version! - See more at: http://expertsharepoint.blogspot.de/search/label/Cumulative%20Update?updated-max=2014-07-16T15:52:00%2B08:00&max-results=20&start=1&by-date=false#sthash.niQtnuJU.dpuf

NOTE!
The March PU Is not required prior to install SP1 on top of RTM version! - See more at: http://expertsharepoint.blogspot.de/search/label/Cumulative%20Update?updated-max=2014-07-16T15:52:00%2B08:00&max-results=20&start=1&by-date=false#sthash.niQtnuJU.dpuf

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.