SharePoint 2010 CU and securtiy patch upgrade Issue

Issue : 

I faced as mentioned after installing the SP2 patch and trying to run PSConfig command. I have done a fair bit of patching but never encountered this issue. The PSConfig failed and referred to the upgrade logs as usual to find the error. The upgrade log error listed below was cryptic and did not provide any direct information on what was causing it.

Resolution : 

Error in configuration wizard while trying to add new SharePoint Server to an existing Farm [Scale out] after reset the Farm passphrase

Fixed with below refernce 

http://blogs.msdn.com/b/fabdulwahab/archive/2011/10/25/error-in-configuration-wizard-while-trying-to-add-new-sharepoint-server-to-an-existing-farm-scale-out-after-reset-the-farm-passphrase.asp

2. Null exceptions

3 : Timer job filed

4. Decided to installation SP2 in all servers with sp2 language packs

·         Installed SP2  Updates on WFE2  and APP Server

·         Ran Product Configuration Wizard and it failed

·         Tried PSConfig.exe -cmd upgrade -inplace b2b –wait  - This too failed at the last step

·         Tried psconfig -cmd upgrade -inplace b2b –force – this too failed at the last step

·         IISRESET to both SharePoint Servers

·         Restarted SharePoint Timer Service

·         Restarted SharePoint Search Service

·         Clear Config Cache on all the  servers  set 1 as a cache

·         Ran PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures – this one failed at the last step

That issue was with respect to Web Application, At the end we Deleted the Web App and Recreated it, Issue got resolved, and then PSCONFIG Works like.

Application Pool is auto stopped when browse web application in IIS7 In Sharepoint 2010

I spent a two day attempting to resolve why this was happening in particular WFE server. Every minute I opened my SharePoint site, I’ll get a 503 error and when I check the IIS Console, I discover that the corresponding application pool has stopped. I tried numerous different things, and I also tried the suggestion from this so many MSDN logs .

Resolution:

The first thing that I noticed was that Central Administration and web applications would not come up at all,

Ø    opened IIS and saw the App pools.

Ø  I right-clicked the application pool and started it.  As soon as I tried to browse to Central Administration, and web applications. The same error was repeated.

Ø  Started IIS reset  in both servers(WEF1 , WEF2)
Ø  WEF1  server running fine.
Ø  WEF 2server not started application pools ,,

Ø  After refreshing IIS, I saw that the application pool was stopped again!  Trying this several more times of course yielded the same results.

Ø  Looking through the SharePoint logs indicated a problem with SQL, but everything on the SQL side was functioning properly. Under 14/log files

Ø  However, in looking through the IIS logs, I first came across this error:  “Application pool has been disabled.  Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.” Error event 5059

Ø  opened the Services console (services.msc) and restart the Windows Process Activation Service (WAS), SharePoint related services

Ø  Looking at one of the “Warnings” listed in the IIS log, I saw the following message:  Warning 5029

“The identity of application pool ++++++++ is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request.  If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number”.

Ø  Decided to reboot the server , 

Ø  After rebooted the server we try to start application pools in the server but that didn't fix the problem.

Ø  Decided to remove WFE2 server from NLB configuration. 

v  After long research we found some issue  applicationHost.config and machine keys files became corrupted  on the server

v  This IIS Admin configuration 

Ø  Not sure how it happened or what caused it, Might be issue in last server updates

.

Ø  Decided to Changing the Application Pool on a Web Application.

http://blogs.technet.com/b/rycampbe/archive/2011/08/31/changing-the-application-pool-on-a-web-application-the-right-way.aspx

Ø  Created new web application pool  and trying to change the application pool identity to another our domain account with password

Ø  There was an error while performing this operation.

Details: Bad Data. (Exception from HRESULT: 0x80090005)

Ø  Decided to export/import encryption keys for IIS7 from WFE1 server to WFE 2 server.

http://forums.iis.net/t/1172423.aspx

exported iisConfigurationKey from 259 to 260 server but problem was not resolved.

Ø  Updated webapps password in applicationHost.config file  ,

Ø  Reset IIS

Ø  Web application pool’ ‘+++++++’ works again. J

Ø  Understand the exact problem :WAS password key files are corrupted.

     Restore old windows backup files in to the system location.

After restored old applicationHost.config  . Problem was resolved . all web application pools running properly with out any issues.

 Might be useful.

 

SharePoint 2010 or 2013 Roles, Responsibilities & Support Policies from a SharePoint Consulting Perspective

http://www.aiim.org/community/blogs/expert/sharepoint-2010-or-2013-roles-responsibilities-support-policies-from-a-sharepoint-consulting-perspective

Which services run on each server in SharePoint 2010 server setup ( 1 App, 2 WFE,1 Sql)

Front End Servers

Microsoft SharePoint Foundation Web Application
Search Query and Site Settings Service
SharePoint Server Search Service

Application Server

Access Database Service
Application Registry Service
Business Data Connectivity Service
Central Administration
Claims to Windows Token Service
Document Conversions Launcher Service
Document Conversions Load Balancer Service
Excel Calculation Services
Lotus Notes Connector (If required)
Managed Metadata Web Service
Microsoft SharePoint Foundation Incoming E-mail
Microsoft SharePoint Foundation Workflow Timer Service
PerformancePoint Service
PowerPoint Service
Search Query and Site Settings Service
Secure Store Service
SharePoint Foundation Search
SharePoint Server Search
User Profile Service
User Profile Synchronization Service
Visio Graphics Service
Web Analytics Data Processing Service
Web Analytics Web Service
Word Automation Services
Word Viewing Service

Slipstreaming Patches in SharePoint 2010 with SP2

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=295

illegal operation attempted on a registry key that has been marked for deletion sharepoint search 2007

Troubleshot steps to fix the issue:

1. Stop office serach service in CA 

2  Stop the OWSTIMER service on ALL of the MOSS servers in the farm.
3. Stop Proxy server settings in search administration (Un check check box)
4. Started the Search Query and Site Settings Service on all the servers in the farm that query happens on (in Central Admin, Manage Services on Server)
5. IIS reset in All servers.

Clear the SharePoint Configuration Cache

To clear the config cache on the farm, follow these steps:

1. Stop the OWSTIMER service on ALL of the MOSS servers in the farm.
2. On the Index server, navigate to:                          

Server 2003 location: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory. 
Server 2008 location: Drive:\ProgramData\Microsoft\SharePoint\Config\GUID and delete all the XML files from the directory.

3. Delete all the XML file in the directory. NOTE: ONLY THE XML FILES, NOT THE .INI FILE.
4. Open the cache.ini with Notepad and reset the number to 1. Save and close the file.
5. Start the OWSTIMER service on the Index server and wait for XML files to begin to reappear in the directory.
6. After you see XML files appearing on the Index server, repeat steps 2, 3 & 4 on each query server, waiting for XML files to appear before moving to subsequent servers.
7. After all of the query servers have all been cleared and new .xml files have been generated, proceed to the WFE and Application servers in the farm, following steps 2, 3, 4 and 5 for each remaining server.