Tuesday, February 19, 2013

Solution hungs through CA while deploying

Issue: I do have 3 web server and two app server. I ran solution deployment at one of a app server but the status gets hung while viewing through central admin. When I clicked on that solution I found that the solution get deployed at all the server except one of a app server. In ULS log of that defective server I got the following error message: Exiting the process because the timer could not be initialized after multiple attempts. The timer service could not initialize its configuration, please check the configuration database. Will retry later. I already clear the cache at all servers and the GUID of the cache folder is also okay. The service account have right permission at server level.

Resolution:
 1) Cleared the cache files.
2) Compared the OWSTimer.exe.configfiles at defective server and correct server
3) Restarted the timer services
4) Rebooted the server defective server
5) Compared the cache file GUID name
6) Compared the cache file GUID with the cache ID available in REGEDIT.
7) Checked the services through central admin.
8) Checked the health console through central admin 9) Removed and added the server from farm and it resolved.

File Checkout Issue

1) SharePoint 2007 have issues that files are locked out continuously and not able to edit/discard check out. A) clear the IE cache & local machine temp files. If the issue persist then ask the user to check in the file. Keep the version of list/library to maximum 10 numbers. If the issue still persist then save as file for local then change the file name & upload. Do the file edit. or Open a new file--> select open --> enter the url of the file & then do the changes