Tuesday, December 30, 2014

Some farm products and patches were not detected on this or other server, if products are patches missing locally



Some farm products and patches were not detected on this or other server, if products are patches missing locally                 
                                           
                                 

Issue: After patching a SharePoint 2013 Farm  with SP1, Attempted running SharePoint Products configuration wizard and receive this error message:

"Error: Some farm products and patches were not detected on this or other servers.  If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard. If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again."

Cause: To enforce consistency, SharePoint 2013 checks installed product version automatically on running Products configuration wizard. If any server is missing a specific patch, You get this error message and SharePoint would not let the SharePoint Configuration Wizard to proceed.

Solution: This could be of many reasons, In this article I am providing all the solutions which can be applied to resolve the issue.

Solution 1:Ensure the CU is installed properly to the server, If not try re-installing the CU.

Solution 2:Ensure to run the below command to force the registry for the updates.
1.    From SharePoint Shell, run the 2 commands below on each SharePoint server.
2.    Get-SpProduct – -Local 

3.    (Get-SpServer $env:ComputerName).NeedsUpgrade 
4.    Confirm “True” is returned

Continue with running the SharePoint Products Configuration Wizard

Solution 3:Ensure to follow the below steps.

1.    Central Admin-> select Monitoring from the left-hand navigation and click the Review Job Definitions link under Timer Jobs
2.    On the Job Definitions page, scroll down and locate the “Product Version Job”
3.    Click on the Product Version Job link to open the job definition. Click on Run Now at the bottom of the page
4.    Now run the SharePoint 2013 Products Configuration Wizard again

Solution 4: If for very sure, have installed patches in all servers with similar installers, you can bypass the check by below command:

psconfig.exe -cmd installcheck -noinstallcheck


Solution 5: Ensure the LP'S,Service packs for LP and CU's are installed same in server as compare with other servers.
 


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.

Changing of IP address for the existing SharePoint farm



Changing of IP address for the existing SharePoint farm

Description: Changing of IP address for the existing SharePoint farm is the most common scenario for the SharePoint administrators. What will happen to the farm if change of IP address to existing?

Explanation: Changing of IP address to existing farm will not be break anything with SharePoint. But be sure to consider below while changing the IP.

1.   Change your DNS records to point to the new IP address for all Web Applications
2.   Change the IP addresses for the SQL Server and SharePoint
3.   Check IIS on your SharePoint Server(s) to see if the new IP address is correctly configured for all Web
Applications on all the servers in your farm.

Note: replicating SharePoint VMs and their backend SQL Server VMs is probably not supported due to timer job synchronization/time synchronization issues.
  


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.

how to create service application proxy for existing service application (or) Object reference not set to an instance of an object



how to create service application proxy for existing service application (or)
Object reference not set to an instance of an object.

Issue: issue with User Profile service application which was stopped working.

Solution1:Please follow the steps to solve above issue.

1.    you have to delete your service application proxy from central administration -> manage service applications page.

2.    run this on Power shell. this will show you all service applications of your farm

Get-SPServiceApplication

3.    get the name of User Profile Service Application or you can copy name from central admin also.

$upa = Get-SPServiceApplication -Name “User Profile Service Application”

4.    then  need to create new service application proxy.

 New-SPProfileServiceApplicationProxy  -Name “User Profile Service Application Proxy”  -ServiceApplication $upa  -DefaultProxyGroup

Do an IISRESET.

Solution 2:if the above doesn’t fix the issue. Reset the application pool account for Token Service.

 


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.

ShareThis

X