question

SHAREPOINTER avatar image
0 Votes"
SHAREPOINTER asked JoyZ commented

OWSTIMER.EXE ERRORS IN LOGS WHEN INSTALLING PATCHES

Hi,

I am looking at an issue on a SP 2013 farm which will not let patches - SP1 install.

You can not remove language packs from add/remove programs, psconfigui.exe will not run

Installing the SP1 patch causes these errors in the logs:

"03/25/2021 17:03:51.02 OWSTIMER.EXE (0x06C0) 0x0720 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job MySite-Instantiation-Interactive-Request-Queue). Parent No 81d3fd3e-4957-4036-b82d-b1caa7583e0f"
"03/25/2021 17:03:51.02 OWSTIMER.EXE (0x06C0) 0x0720 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Timer Job MySite-Instantiation-Interactive-Request-Queue 47c8b79f-f68e-809e-45ce-623349ab99fe"
"03/25/2021 17:03:51.02 OWSTIMER.EXE (0x06C0) 0x0720 SharePoint Portal Server Personal Site Instantiation aj58q Medium <LogTimerJobInstance> Starting timer My Site Instantiation Interactive Request Queue (e94a6caa-b0f5-4897-b489-585ca50c7803) for web application: HLHNSCSites. Function: MySiteInstantiationJob:Execute 47c8b79f-f68e-809e-45ce-623349ab99fe"
"03/25/2021 17:03:51.02 OWSTIMER.EXE (0x06C0) 0x0720 SharePoint Portal Server Personal Site Instantiation aj58r Medium <LogTimerJobInstance> Finishing on timer My Site Instantiation Interactive Request Queue (e94a6caa-b0f5-4897-b489-585ca50c7803) for web application: HLHNSCSites. Function: MySiteInstantiationJob:Execute 47c8b79f-f68e-809e-45ce-623349ab99fe"
"03/25/2021 17:03:51.02 OWSTIMER.EXE (0x06C0) 0x0720 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job MySite-Instantiation-Interactive-Request-Queue). Execution Time=1.9560927255063 47c8b79f-f68e-809e-45ce-623349ab99fe"
"03/25/2021 17:03:52.02 OWSTIMER.EXE (0x06C0) 0x0724 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job MySite-Instantiation-Non-Interactive-Request-Queue). Parent No 0d89643e-d228-4513-bc0d-277e76c1696f"
"03/25/2021 17:03:52.02 OWSTIMER.EXE (0x06C0) 0x0724 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Timer Job MySite-Instantiation-Non-Interactive-Request-Queue 47c8b79f-76cd-809e-45ce-6b77bf08ff9d"
"03/25/2021 17:03:52.02 OWSTIMER.EXE (0x06C0) 0x0724 SharePoint Portal Server Personal Site Instantiation aj58q Medium <LogTimerJobInstance> Starting timer My Site Instantiation Non-Interactive Request Queue (9fd3251e-b81f-45f8-b2b7-044b64418f55) for web application: Onlinebld. Function: MySiteInstantiationJob:Execute 47c8b79f-76cd-809e-45ce-6b77bf08ff9d"
"03/25/2021 17:03:52.02 OWSTIMER.EXE (0x06C0) 0x0724 SharePoint Portal Server Personal Site Instantiation aj58r Medium <LogTimerJobInstance> Finishing on timer My Site Instantiation Non-Interactive Request Queue (9fd3251e-b81f-45f8-b2b7-044b64418f55) for web application: Onlinebld. Function: MySiteInstantiationJob:Execute 47c8b79f-76cd-809e-45ce-6b77bf08ff9d"

There are other log entries very similar to the above related to owstimer.exe.

Any tips or ideas please?

Does Microsoft not have any detailed diagnostic tools to actually find out what is wrong here?


@trevorseward

office-sharepoint-server-administration
· 6
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Those aren't errors, that is normal timer job activity. You're correct in that you cannot remove SharePoint patches once installed. You should provide the MSI installer logs from when you attempt to install a patch.

0 Votes 0 ·

Thank you so much - i do not know where the msi logs are but now you tell me this i might actually be able to find them and post back...

I'll do that tomorrow...

@trevorseward

0 Votes 0 ·

https://docs.microsoft.com/en-us/troubleshoot/windows-client/application-management/enable-windows-installer-logging

That guide will also tell you how to get more verbose logging (if your error is simply "1603", that's the generic MSI failure code).

0 Votes 0 ·
Show more comments

1 Answer

JoyZ avatar image
0 Votes"
JoyZ answered JoyZ commented

Hi @stevehowlett,

As Trevor said, your release log has nothing to do with patch failure errors.

Find logs similar to the following:

   04/27/2018 02:23:25.28 OWSTIMER (0x79CC)   0x5EF8  SharePoint Foundation Upgrade   SPUpgradeSession    ajxnm   ERROR   Exception: Invalid object name 'Webs'.  dc7e619e-f035-9008-21b8-f23cd60a3c44

If you can't find anything, follow trevor's suggestions to check the Windows installer log.


If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for repeating what Trevor already said...

0 Votes 0 ·

Hi @SHAREPOINTER

From the log error "The detection failed, this can be due to a corrupted installation database", please try solution in this article:

https://social.technet.microsoft.com/Forums/office/en-US/cfa66cd3-2aa2-44ee-9393-ffae41d4f70c/the-detection-failed-this-can-be-due-to-a-corrupted-installation-database?forum=sharepointadminlegacy

If the issue still exists, we suggest you to open a support ticket about it. It needs more detailed investigation with support team instead of simple troubleshooting via replies in forum. And we will appreciate it if you can update your findings here.

0 Votes 0 ·

Thank you very much i will do just that - good idea.

0 Votes 0 ·
Show more comments