Sharepoint Patches Issues in Index Server

Issue

Unable to install the security patches , it gives , and error "  Installation is not detected "  We are trying to install KB2810059 , KB2760408 , KB2760777

Product / Version / Service Pack: SP 2010

Operating System / Service Pack: win 2008 R2

Farm Configuration: 14.0.6137.5002

Database Used:

Additional technologies:

Resolution

Once we are able to  install the above mentioned patches on the STG Index server  ,and complete the configuration wizard , we will consider this case to be resolved.

Troubleshooting Done

Ø  Created the EA

Ø  When we are trying to install the patches, we are getting error, installation is not detected.

Ø  The patches were installed successfully on the other server of the farm

Ø  We earlier tried to remove the server from the farm from CA

Ø  We ran the configuration wizard , and removed the server from the farm

Ø  We ran the ROI scan , and got the o/p

Review Items

============

Error:                       Product {90140000-1140-0411-1000-0000000FF1CE} - Microsoft Office Web Apps Shared Coms Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509144.msi

Error:                       Product {90140000-1080-0411-1000-0000000FF1CE} - Microsoft Shared Coms Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509152.msi

Error:                       Product {90140000-1080-0409-1000-0000000FF1CE} - Microsoft Shared Coms English Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\250904c.msi

Error:                       Product {90140000-10B0-0411-1000-0000000FF1CE} - Microsoft Project Server Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\250913d.msi

Error:                       Product {90140000-1103-0411-1000-0000000FF1CE} - Microsoft Document Lifecycle Components Japanese Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\25091a7.msi

Error:                       Product {90140000-1103-0409-1000-0000000FF1CE} - Microsoft Document Lifecycle Components English Language Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509098.msi

Error:                       Product {90140000-1123-0000-1000-0000000FF1CE} - Microsoft Access Services Server: Local cached .msi appears to be missing: C:\Windows\Installer\2509101.msi

Error:                       Product {90140000-10F3-0000-1000-0000000FF1CE} - Microsoft Visio Services Web Front End Components: Local cached .msi appears to be missing: C:\Windows\Installer\25090e6.msi

Error:                       Product {90140000-1014-0000-1000-0000000FF1CE} - Microsoft SharePoint Foundation 2010 Core: Local cached .msi appears to be missing: C:\Windows\Installer\25090a8.msi

Error:                       Product {90140000-1144-0000-1000-0000000FF1CE} - Microsoft Office Web Apps Web Front End Components: Local cached .msi appears to be missing: C:\Windows\Installer\25091ed.msi

Error:                       Product {90140000-1015-0411-1000-0000000FF1CE} - Microsoft SharePoint Foundation 2010 1041 Lang Pack: Local cached .msi appears to be missing: C:\Windows\Installer\250914a.msi

Error:                       Product {90140000-1015-0409-1000-0000000FF1CE} - Microsoft SharePoint Foundation 2010 1033 Lang Pack: Local cached .msi appears to be missing: C:\Windows\Installer\2509021.msi

Ø  We see lot of missing installer file , we tried to install the same from a working server

Ø  Cscript Oputil.vbs /repaircache /srestorelocation=\\servername\c$\windows\installer

Ø  After which the same got copied successfully

Ø  We ran the config wizard , which was successful with some error.

Ø  We checked the upgrade log and it was referencing to a content database

Ø  We detached the content database  , and ran the upgrade , we still got some error about the logs been full in the database

Ø  We changed the recovery model from simple full

Ø  Ran the configuration wizard and it was successful.

Additional Information

http://blogs.technet.com/b/patrick_heyde/archive/2010/08/30/sharepoint-2010-patching-upgrade-part-2-which-patch-level-build-level-is-installed-amp-what-s-their-history.aspx

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

USER PROFILE CONFIGURATION IN PRODUCTION SERVER

In the previous implementation, the profile import job, that was carried out during SharePoint user profile service had some inconsistencies due to which the address book on SharePoint showed up mixed names like instead of displaying . This operation is required to fix the same. This task does not require any outage and can be included within the same nightly batch job.

SharePoint 2010 Production Server User Profile Services Configuration Steps

Note: Before going to make any change in User Profile Application first disabled the My Sites Scheduler from Central Administration Monitoring.

Step 1: Login to the SharePoint 2010 Production Application Server.

Server Name: SharePoint Application Server

Step 2: Open the Central Administration à Go to “Application Management” à Click “Manage Service Application” à Click “User Profile Service Application”

Step 3: In “User Profile Service Application” à Click “Configure Synchronization Connections” under “Synchronization”

Step 4: Delete Existing Connect ion.

Note: If unable to delete the use below command to delete the Connection.

1.    PS C:\Users\ServiceAccount> Get-SPDatabase > C:\Database.txt

2.    PS C:\Users\ServiceAccount> $syncdb=Get-SPDatabase

Note: Find out Sync database name using first command path

3.    PS C:\Users\ServiceAccount>$syncdb.Unprovision()

4.    PS C:\Users\ServiceAccount>$syncdb.Status='Offline'

5.     PS C:\Users\ServiceAccount>$upa=Get-SPServiceApplication

Note: Using Get-SPServiceapplication command to find out user profile application ID

6.     PS C:\Users\ServiceAccount> $upa.ResetSynchronizationMachine()

7.     PS C:\Users\ServiceAccount> $upa.ResetSynchronizationDatabase()

8.     PS C:\Users\ServiceAccount> $syncdb.Provision()

 Step 5: Change NetBIOS Setup from False to true

1.  Using below Power Shell command to find out User Profile Application Name.

Command:  PS C:\Users\ServiceAccount> Get-SPServiceapplication

2.    Using below command to find out Netbios setup true or False.

Note: If output false then using PS command to change.

 PS C:\Users\ServiceAccount> (Get-SPServiceApplication ).NetBIOSDomainnamesEnabled

3.     PS C:\Users\ServiceAccount> $upsa = Get-SPServiceApplication -Id

4.     PS C:\Users\ServiceAccount> $upsa.NetBIOSDomainNamesEnabled=1

5.     PS C:\Users\ServiceAccount> $upsa.Update()

6.     PS C:\Users\ServiceAccount> (Get-SPServiceApplication ).NetBIOSDomainnamesEnabled 

Step 6: Stop and Start the User Profile Synchronization Service

1.  Go to Central Administration à Click “Manage Services and Server” under System Settings

2.  Stop and Start the “User Profile Synchronization Service” Services.

Step 7: Create the new Connection in User Profile Services

1.  Go to the User Profile Application (Refer Step 1)

2.  Click “Create New Connection” and parameter information as below.

1.1      Connection Name – DOMAIN NAME

1.2      Forest name: ********

1.3      Specify a domain controller: DomainName.corp.nai.org

1.4      Account Name: DomainName\ServiceName

1.5      Account Password: xxxxxxxxx

3.  Click to “Populate Containers”

4.  Find out NAI and select and uncheck Windows7.0 Machines.

5.  Finally Click Ok

Step 8: Back to the User Profile Application Page and click Start Full Profile Synchronization.

Step 9: Two times you have complete the full start Profile Synchronization and one time Incremental.