The expected version of the product was not found on the system

When Trying to install a update you get "The expected version of the product was not found on the system."

I came on my test environment across this problem when trying to install the latest update I’ve got the error message: “The expected version of the product was not found on the system” this can occur on Project 2007 and 2010.

Running the following command from the command prompt will do the trick 

1. Run --> CMD

2. Go to Exe Path

3. Run “FileName.Exe PACKAGE.BYPASS.DETECTION.CHECK=1″

PS: Make sure to run the Package bypass command with Caps

Install and Download SharePoint 2013 prerequisites offline (manually)

This article applies in a situation when you don’t have internet access in your SharePoint server , I have placed all the direct download links for the installers you might need.

This article assumes you are having a new fresh installation of windows server 2008 R2 SP1

If you tried to run the installer , The following should be installed (but you cant install them directly from here since you don’t have internet)

in this case  you can download and install SharePoint 2013 Prerequisites offline and run them manually as below:

I have placed what needs to be installed on a clean Window server R2 SP1 , you should not need more than this:

Prerequisite	Direct Link
Microsoft .NET Framework 4.5 (Full Stand alone package)	http://go.microsoft.com/fwlink/?LinkId=225702 Or Download tFx45_Full_x86_x64.exe from stand alone section from http://msdn.microsoft.com/en-us/library/5a4x27ek.aspx
Windows Management Framework 3.0	http://www.microsoft.com/en-us/download/details.aspx?id=34595
Microsoft SQL Server 2008 R2 SP1 Native Client	Download 1033\x64\sqlncli.msi from http://www.microsoft.com/en-us/download/details.aspx?id=26728
Windows Identity Foundation (KB974405)	http://go.microsoft.com/fwlink/p/?LinkID=226830
Windows Identity Extensions	http://go.microsoft.com/fwlink/?LinkID=252368
Microsoft Sync Framework Runtime v1.0 SP1 (x64)	http://go.microsoft.com/fwlink/p/?LinkID=224449
Windows Server AppFabric	http://go.microsoft.com/fwlink/?LinkId=235496  (Note: don’t install WindowsServerAppFabricSetup_x64_6.1 this is not the correct version that SharePoint installer seeks) Download it but don’t install it by yourself since it needs configuration, hence install all other prerequisites in this article (except this one) then let the prerequisite installer to install AppFabric and configure it manually for you by running the following command from command prompt: prerequisiteInstaller.exe /appfabric:[Full AppFabric Installer path] D: is the CD drive where SharePoint installer is placed
Microsoft Information Protection and Control Client	http://go.microsoft.com/fwlink/p/?LinkID=219568
Microsoft WCF Data Services 5.0	http://www.microsoft.com/en-us/download/details.aspx?id=29306
Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763	Download AppFabric1.1-RTM-KB2671763-x64-ENU.exe from http://www.microsoft.com/en-us/download/details.aspx?id=29241 You need to Install AppFabric from above first then run this update, dont run this update if appFabric above is not installed yet

Configure SSL for SharePoint 2013

In this tutorial I will show you how to configure SSL for SharePoint 2013.

Prerequisites:

1. IIS 8
2. SharePoint 2013
3. Windows Server 2012
4. HTTP Web Application on Port 80

Steps:

1. Create Self Signed Certificate on IIS 8
2. Import Self Signed Certificate to SharePoint Certificate store
3. Add Self Signed Certificate to trust management in Central Administration
4. Configure IIS Binding
5. Configure AAM
6. Notes
7. Issues

Note: Make sure to perform these steps with admin privileges.

Step 1: Create Self Signed Certificate on IIS 8

Open IIS Manager and then go to Server name and choose IIS Section “Server Certificates”

Click on Create Self-Signed Certificate… on Actions pane

Specify a name like “SharePointSelfSignedCert” and click Ok

Double click on this created Certificate and go to details Tab and click copy to File…

Click Next (Welcome…),

Select No, do not export the private key and click Next ,

Select DER encoded binary and click Next,

Specify the location for the certificate and Click Next and then finish (Imported).

Step 2: Import Self Signed Certificate to SharePoint Certificate store

Open Manage Compute Certificate on Windows Server 2012 and go to SharePoint node and then right click All tasks >> import …

Click Next and then specify the location of exported certificate in previous step and then Click Next,

Make sure Certificate store is SharePoint and Click Next and then finish (Exported)

Step 3: Add Self Signed Certificate to trust management in Central Administration

Go to Central Administration >> Security >> Manage Trust (to inform SharePoint to trust this certificate also).

And Click New

And a name and specify the location for the certificate and Click Ok.

Step 4: Configure IIS Binding

Go to IIS Manager and choose your web application and then click on Binding in Actions pane

Click Add..

Type: Https

SSL Certificate: SharePointSlefSignedCert (which created previously).

Click Ok.

Step 5: Configure AAM

Go Central Administration >> Alternate Access Mapping and Choose your web application

And click on Edit Public URLs and then add HTTPS URL

And Click Save.

Now try to brows your site with HTTPS URL

Notes:

1. Don’t use Self-Signed Certification in production sites (you need to use commercial Certificates).
   http://www.digicert.com/ssl-certificate-installation-microsoft-iis-7.htm
2. If you add the Self-Signed Certificate to Trusted Root Certification Authorities then Certification error will disappear.
3. IIS 8 and windows server 2012 introduce New Feature Called “Server Name Indication-SNI” which allows an IIS 8 to host multiple SSL sites and certificates on a single IP Address based on Host Headers.
   http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-server-name-indication-sni-ssl-scalability
4. You can use URL Rewirte module in IIS 8 to redirect from HTTP to HTTPS or vice versa.
   http://www.iis.net/learn/extensions/url-rewrite-module/creating-rewrite-rules-for-the-url-rewrite-module
   http://ruslany.net/2009/04/10-url-rewriting-tips-and-tricks/ 
5. SSL Certificates required for Federation Services.
6. Test the SSL implementation using https://www.ssllabs.com/ssltest/ and make changes as in this articlehttps://www.hass.de/content/setup-your-iis-ssl-perfect-forward-secrecy-and-tls-12

Issues:

 

Issue #1: Mixed HTTP and HTTPS Content

If you login with HTTPS URL and then redirect the user to HTTP , the browser will ask the user again to login with HTTP URL.

Fix:

Go To Central Administration

Open Alternate Access Mapping (AAM)

Select your will application from the dropdown menu on top right

Click on Edit Public URLs and remove HTTPS URL

Click on Add Internal URLs and add HTTPS URL and select the same zone as HTTP URL

Firewall settings for SharePoint Farm

Some times in SharePoint when we access web sites, search and configure alerts we see network related errors even though we configured everything is good. There could be so many reasons for that. One could be Firewall. In this article I am providing the steps how and where to check for the firewall issue.

On each SharePoint 2013 Server, we will need to set a firewall rule to allow SharePoint intra-farm traffic and HTTP/HTTPS traffic. Alternatively, you can disable the Windows Firewall if you choose and if you have another firewall solution.

You can set the Windows Firewall rules by navigating to the Control Panel, then click System and Security, then click Windows Firewall, and finally click Advanced settings. In the Inbound Rules area, ensure that the server allows connections on port 80 (HTTP) and port 443 (HTTPS). Add the ports listed in the table below for the SharePoint 2013 inter-farm communication by following these steps: 

   

1.    In the Windows Firewall with Advanced Security window, click Inbound Rules.

2.    In the Actions panel, click New rule…

3.    In the New Inbound Rule Wizard window, select Ports as the Rule Type and click Next.

4.    Select the appropriate choice between TCP and UDP, and enter the desired port(s) for the Specific local ports. Click Next.

5.    Click Next. On the Profile screen, click Next.

6.    On the Name screen, enter the desired name and click Finish.

                    

                      

Rule Name	TCP or UDP	Ports
SharePoint Web Traffic	TCP	80,443
SharePoint Search Index	TCP	16500-16519
SharePoint Farm Communication	TCP	32843,32844,32845
SharePoint Profile Synchronizing (TCP)	TCP	5725,389,88,53
SharePoint Profile Synchronizing (UDP)	UDP	389,88,53,464
SharePoint User Code Service	TCP	32846
SharePoint SMTP Service	TCP	25

SharePoint Server Search  Administration Medium Could not find or connect to host controller on server

Issue: After we configure everything in related to search, when we try to find the search we see the error “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond”

Event:

0x0BD8        SharePoint Server Search   Administration   Medium   Could not find or connect to host controller on server SERVER. Exception: Could not connect to net.tcp://SERVER/ceres/hostcontroller/nettcp. The connection attempt lasted for a time span of 00:00:21.0369864. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.181.14.21:808.    Server stack trace:      at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)     at System.ServiceModel.Channels.ClientFramingDupl…        ff78fc9b-4b6c-b08b-52a2-ff7745f71f1f

Resolution: After I go through the Events and run the traces I come to know that the issue is related to network. I deep on diving the issue I could identify that something is blocking to search.

1.   Ensure to check the Fire wall settings.

2.   Check to stop the firewall and search. This will work but not recommended in production servers.

3.   Ensure that to create a new rule allowing Inbound traffic on TCP Port 808 on all SharePoint Servers

Go to->Windows firewall with advanced security->click on Inbound->create new rule to allow                                

                                   
                                     
              
                                           

Issue: After we configure everything in related to search, when we try to find the search we see the error “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond”

Event:

0x0BD8        SharePoint Server Search   Administration   Medium   Could not find or connect to host controller on server SERVER. Exception: Could not connect to net.tcp://SERVER/ceres/hostcontroller/nettcp. The connection attempt lasted for a time span of 00:00:21.0369864. TCP error code 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.181.14.21:808.    Server stack trace:      at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)     at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)     at System.ServiceModel.Channels.ClientFramingDupl…        ff78fc9b-4b6c-b08b-52a2-ff7745f71f1f

Resolution: After I go through the Events and run the traces I come to know that the issue is related to network. I deep on diving the issue I could identify that something is blocking to search.

1.   Ensure to check the Fire wall settings.

2.   Check to stop the firewall and search. This will work but not recommended in production servers.

3.   Ensure that to create a new rule allowing Inbound traffic on TCP Port 808 on all SharePoint Servers

Go to->Windows firewall with advanced security->click on Inbound->create new rule to allow