Clustered Time Services
Hi,
I've got several time / schedule related services that are registered upon
server startup. We are moving from a single server instance to a several
clustered instances. As expected, I've run into an issue where each
scheduled service on each cluster is firing independently of the others and
thus I'm getting multiple notifications of each scheduled event.
My question is this... how do most shops handle this type of situation? We
want to have a scalable / failable? solution. I know I can take care of the
problem by only registering the scheduled objects in a single per server
properties file, but I lose any type of failover.
I'm thinking of starting the scheduled services on each server in the
cluster and binding a next run time into the JNDI tree. When a scheduled
event fires it would check the next run time to see if it can run its
schedule. If not it would reschedule itself to check later and effectively
go back to sleep. If it can run it would do so and increment the next run
time and reschedule itself to check later and go back to sleep.
Any thoughts???
Thanks in advance,
Steve...
See: http://e-docs.bea.com/wls/docs61/programming.html
Nalika wrote:
> Hi,
>
> In BEA online docs (
> http://e-docs.bea.com/wls/docs61/cluster/overview.html ) it describes about
> Non-Clustered Services and APIs as
>
> File services
> Time services
> WebLogic Events (deprecated in WebLogic Server 6.0)
> Workspaces (deprecated in WebLogic Server 6.0)
> ZAC
> etc...
>
> Can anyone have an idea of what these services means ?
> Please respond.
>
> Thanks
> Nalika
Similar Messages
-
Time service clustering in WLS8
Hi
Our product uses timer service on WLS 6.1, and timer is started by startup class.
Now we need to move our product to WLS8 cluste. My question is: although startup
class is clusterable, can timer service be clustered on WLS8? Or I can only start
the timer in one server instance? If the timer is implemented using a stateless
session bean which is deployed in the cluster, and one client in one managed server
in the cluster starts the timer by calling the stateless session bean, will WLS
support failover and load balancing of timer service?
Thanks
Chun
As Emily Lutella used to say: never mind!
It turns out the time service is simple, as we originally thought, and does
not distribute threads over scheduled trigger actions.
The mystery thread was started by a second server in the cluster going over
the wire to get to a bean on the first server.
---Paul O
Paul O'Rorke wrote:
We use the time service to schedule and process events at set times.
I just recently reviewed the documentation on this but still need a bit
more detail than I have seen, for example at
http://www.weblogic.com/docs51/classdocs/API_time.html
I am curious how multiple JVMs and threads may impact our scheduled
events.
We seem to have a situation where, when several events are scheduled to
occur at the same time, the first one waits on some resource such as an
EJB, possibly even getting into a deadlock with another thread that may
access the same resource(s), which may be running a JSP. But the time
service seems to move on, to process a second event scheduled for the
same time.
I would like to know more about how the time service allocates threads
to execute scheduled actions. For example, does it create a thread for
each action scheduled for a given time, or allocate a thread pool over
those actions?
If this is documented somewhere, I'd appreciate a pointer, otherwise
hopefully someone can provide more info here.
Thanks!
---Paul O -
The EJB 2.1 Timer Service & Clustering Behavior
With respect to WebLogic Server 9.0, does anyone know if The EJB 2.1 Timer Service will automatically restart a timer in the event of an entire cluster failure? Thanks,
-MattTim Farrell <> writes:
> Good question. Since theres little to no documentation on the new EJB Timer or the TimerService implemented in 9.0 I would also like to know this.
>
> In fact, drilling down further, I want to understand what happens in a cluster when one of the servers fails with Timers scheduled.
>
> 1. Do they migrate to other servers ?
No
> 2. How do they migrate ?
> 3. Will they migrate back to the original server when it comes back up ?
> 4. When will the docs get completed for this feature ?
Its possible that if you mark the server as migratable and have your
store using HA then migration would work, although I'm certain that
this has been tested.
andy -
Hi,
I have a question about load-balancing facilities for Time service. If I
schedule a TimeScheduleDef object to run at certain intervals, does the
run-time environment take care of load balancing it across multiple machines
on a cluster?
Thanks,
DeepakWebLogic Time is not a clustered service -- it is configured per server and
load balancing is performed.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
Deepak Goel <[email protected]> wrote in message
news:8gvrdb$n18$[email protected]..
Hi,
I have a question about load-balancing facilities for Time service. If I
schedule a TimeScheduleDef object to run at certain intervals, does the
run-time environment take care of load balancing it across multiplemachines
on a cluster?
Thanks,
Deepak -
Monitoring Weblogic Time Service
Hello
I built a number of java classes that implemented ScheduleDef and
Triggerdef.
Then these classes are scheduled using WebLogic Time Service.
The question is :
Is there a way to query WLS to find out how many of these classes are
currently
being scheduled? We need to find out which one are no longer running in the
system
so we can reschedule them. But we also need to know if one is already
scheduled and
therefore disallow the ability to schedule a 2nd instance in the server.
ThanksThey did state a reason. They expect these services to become part of J2EE.
You can still use them, or check out something like Flux from Sims
Computing.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"James McGovern" <[email protected]> wrote in message
news:[email protected]..
BEA has deprecated the time services classes without stating any reason.
Hopefully they will step up and come up with a replacement. -
Alternatives for Flux time services
BEA suggest to use the Flux package if you have the need for time services in your
application server. But this package is quite expensive.
Did anybody successfully use a cheaper time services package?
Cheers,
KoenIMHO ... If you've ever used Flux
(http://www.simscomputing.com/products/flux) then you'll know that it's
worth it. If your application does not need much time-services-related
functionality, and your application is not clustered, and guaranteed
delivery of job assignments is unnecessary for your application, and a
well-tested well-used product with a documented API isn't compelling, you
can always "roll your own". The Flux product isn't free, but it's a pretty
complete product, and Sims has put a lot of work into it.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Koen Van hamme" <[email protected]> wrote in message
news:3c4829fc$[email protected]..
>
BEA suggest to use the Flux package if you have the need for time servicesin your
application server. But this package is quite expensive.
Did anybody successfully use a cheaper time services package?
Cheers,
Koen -
Hi All,
I'm getting the below error in My SHarepoint 2013 search Administration page.
Crawler background activity - The search application 'Search Service Application 1' on server "" is not provisioned. Confirm that the Microsoft SharePoint Foundation Timer service and Central Administration service are running
on the server.
and when i click on Crawl Log and content source
it throws the below error
The search service is currently offline. Visit the Services on Server page in SharePoint Central Administration to verify whether
the service is enabled. This might also be because an indexer move is in progress
When i check the search status
Get-SPEnterpriseSearchServiceInstance, it shows all the components are online.
As of now search service application is online and search is working.But not sure why it throws the above error.
I have restarted timer service,search service in services.msc and cleared the sharepoint cache as well.
But no luck,This is happening in my prodcution environment.
Any help will be greatly appreciated.
There are the logs i have found
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.71 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.73 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djs2 High [Forced due to logging gap, cached @ 05/23/2014 13:03:22.76, Original Level: VerboseEx] {0} d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.79 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.80 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Server Search Administration djj1 High Unable to find application 'b9c8106c-c7ed-4eb3-96c9-ae1881ffb695' d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General 8nca Medium Application error when access /_admin/search/listcontentsources.aspx, Error=The search service is currently offline. Visit the Services
on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress. at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e) at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Runtime tkau Unexpected Microsoft.SharePoint.SPException: The search service is currently offline. Visit the Services on Server page in SharePoint Central
Administration to verify whether the service is enabled. This might also be because an indexer move is in progress. at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajlz0 High Getting Error Message for Exception Microsoft.SharePoint.SPException: The search service is currently offline. Visit the Services on
Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress. at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.ErrorHandler(Object
sender, EventArgs e) at Microsoft.Office.Server.Search.Internal.UI.SearchCentralAdminPageBase.OnError(EventArgs e) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep
step, Boolean& completedSynchronously) d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General aat87 Monitorable d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24q Unexpected SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts are present in the farm. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation DistributedCache ah24w Unexpected Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache'
- Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm. at Microsoft.SharePoint.DistributedCaching.SPDistributedCachePointerWrapper.InitializeDataCacheFactory()'. d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation General ajb4s Monitorable ViewStateLog: Failed to write to the velocity cache:
http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3-c3e4-4097-85fd-aa5248346d2e d4c6939c-b10d-4000-6d95-14caeefe67df
05/23/2014 13:03:22.82 w3wp.exe (0x46E70) 0x4CBA4 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://dca-app-617:90/_admin/search/listcontentsources.aspx?appid=e830c1b3%2Dc3e4%2D4097%2D85fd%2Daa5248346d2e)).
Execution Time=109.695855199474 d4c6939c-b10d-4000-6d95-14caeefe67df
Anil LokaPlease try below mentioned steps:
1. Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service Timer Job" > Disable
2. Then open windows administrative services (services.msc), stop SharePoint Timer Service
3. Clear SharePoint Timer configuration cache by following steps mentioned in below blog:
http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx
4. Start SharePoint Timer Service and give it a few seconds so that the new XML files from the location you deleted then are re-populated.
5.Central Administration > Monitoring > Review job definitions > Look for following timer job "Application Server Administration Service" Timer Job > Enable
Please ensure that you mark a question as Answered once you receive a satisfactory response. -
Dear Friends,
Just like there is a one time customer and vendor account group for vendor and customer who we deal with only once a while.
Is there something like one time service in MM.?
We have few services defined in AC01 and attached a valuation class to each service. What if we need to pay for some service (one time), there shouldn't be a need to create a service master.
When we create the PO for such one time service not defineed in AC01, it saves the PO, but does not allow us to perform the Service entry sheet.
Error it throws is: Account determination for entry CAAI KBS 0001 not possible. (CAAI - is our Chart of Accts), what is it that is related with key KBS in GBB of OBYC?
Thanks
Sanjayno answer, close file
Thanks -
I've been trying to get the javax.ejb.TimerService working. As stated in the J2EE 1.4 tutorial, it is possible to use the TimerService in an entity bean. In fact, it states that if I wanted a timer for each instance of an entity bean, to create the timer in the entity bean's ejbCreate(). However, I keep getting an IllegalStateException when attempting to do so. I have implemented TimedObject in the entity bean, so I'm a little confused. Here's my ejbCreate:
public String ejbCreate(String clientID, long timeout) throws CreateException {
setClientID(clientID);
TimerService timerService = context.getTimerService();
//dies on next line
Timer timer = timerService.createTimer(getTimeout(), "state 1");
return clientID;
Any help is appreciated....
Thanks
RajgetTimerService is allowed in ejbCreate but Timer Service Methods are not . You can use Timer Service methods in ejbPostCreate(), though.
-
Hi all,
in WebLogic 6.1 time services are deprecated
(http://e-docs.bea.com/wls/docs61/notes/issues.html#1031137). Own
threads are not allowed by the specification. How can I correctly
schedule items in WebLogic 6.1? Ideas?
Thanks,
DanielI don't know what BEA's opinion is on the use of the standard JMX
timer service (javax.management.timer) in WLS 6.1, but these
interfaces are very nice to use, and they appear to function
well.
Perhaps one of the BEA folks might want to comment on this approach.
Ben
On Mon, 30 Jul 2001 13:08:26 -0700, Michael Girdley <----> wrote:
You can still use 6.1 Time. It's only for client side. This will be fixed
in the final docs.
MG
Michael Girdley
BEA Systems
Learning WebLogic? http://learnweblogic.com
"Daniel Hoppe" <[email protected]> wrote in message
news:[email protected]..
Hi all,
in WebLogic 6.1 time services are deprecated
(http://e-docs.bea.com/wls/docs61/notes/issues.html#1031137). Own
threads are not allowed by the specification. How can I correctly
schedule items in WebLogic 6.1? Ideas?
Thanks,
Daniel -
In My Windows Server 2008 R2 OS in the Event Viewer there is an error pertains as Time-Service Warning ID 12 states-(Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator
for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize
with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.) What is this error?
And What is the remedy for this error?
System
Provider
[ Name]
Microsoft-Windows-Time-Service
[ Guid]
{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}
EventID
12
Version
0
Level
3
Task
0
Opcode
0
Keywords
0x8000000000000000
TimeCreated
[ SystemTime]
2011-12-10T05:11:30.401496700Z
EventRecordID
18594
Correlation
Execution
[ ProcessID]
1152
[ ThreadID]
2500
Channel
System
Computer
WIN-6JQT8F105TE.mumthaz.contoso.com
Security
[ UserID]
S-1-5-19
EventData
MumthazMuhsinHello,
See that: http://technet.microsoft.com/en-us/library/cc756545(WS.10).aspx
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft Student
Partner 2010 / 2011
Microsoft Certified
Professional
Microsoft Certified
Systems Administrator: Security
Microsoft Certified
Systems Engineer: Security
Microsoft Certified
Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified
Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified
IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer -
One time service's service order
Dear All,
One time service order's service is giving error msg that " enter all mandatory fields and asking for service code"
Actually we have configured that in 1 time service's service order , SO wont ask for service code and it will work without master data,
Please hlp.
ShreyaHi,
The Service Procurement process for Services without Service Master Record is described below:
FOR CREATION OF SERVICE PO:
1. Enter the Transaction ME21N, with Standard Document Type.
2. Choose Item category D and Account Assignment (say) K.
3. Enter the Short Text describes the Service at Item level in the field Short Text
4. Enter the Plant, Material Group, Organizational data etc.
5. At Item Detail screen, go to SERVICES Tab and maintain there also Short Texts which give some description that describes the Services for the Item Service activity.. maintain Qty, Value, UoM. when you proceed furher, system prompts you to enter the Cost center and G/L Acct for each service item. Then save the PO.
FOR SERVICE ENTRY:
1. Go to Transaction ML81N, choose Other Purchase Order tab, enter your PO Number, select Create Tab.
2.Under the PO No, in the Short Text field, maintain a short text Like "Fist part Entry"
3. At the item level, at the bottom of the screen, click Service Sel. Tab. System prompts a sub screen and there you select "From Purchase order radio button". Automatically navigates into Service selection screen, there you select your required Services.and click on Copy Services Tab.
4. With this action, your Services from the PO will be copied to the Service Entry Sheet. There you can change Quantities accordingly.
5. After this, click Flag icon on the top of the screen for Acceptance of Services and save the Entry sheet. Ure traffic light turns to Green and you'll get a Matl Document No.
After this you can proceed to MIRO for Invoice posting, just like normal PO.
Regards,
Kanth
K -
Once in a while i get the error
Event ID 6463
The timer service encountered an exception checking for the upgrade mode registry key. Requested registry access is not allowed.
This also happens when i restart the timer service.
I already cleared the SharePoint cache (xml's) but no success with that.
Environment is
SharePoint 2013 SP1 + CU Dec 2014This is a brand new SP13 with SP1 installation after binaries installation i also installed Dec 2014 CU and then created the SP farm.
The Apppool/Timer account is member of WSS_ADMIN_WPG.
Issue can be reproduced with restarting SharePoint Timer Service.
Hereby the Process Monitor output. Hence i filtered it on NOT SUCCESS and Path contains the word UPGRADE
11:37:57,4244851 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\UpgradeLogLevelOverride
NAME NOT FOUND Length: 144
11:37:57,6632057 OWSTIMER.EXE
6272 RegOpenKey
HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.15.0.Microsoft.Office.Access.Services.Moss.Upgrade__71e9bce111e9429c
NAME NOT FOUND Desired Access: Read
11:37:57,6632889 OWSTIMER.EXE
6272 RegOpenKey
HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.15.0.Microsoft.Office.Access.Services.Moss.Upgrade__71e9bce111e9429c
NAME NOT FOUND Desired Access: Read
11:37:57,7140763 OWSTIMER.EXE
6272 RegOpenKey
HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.15.0.Microsoft.PerformancePoint.Scorecards.Upgrade__71e9bce111e9429c
NAME NOT FOUND Desired Access: Read
11:37:57,7141089 OWSTIMER.EXE
6272 RegOpenKey
HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.15.0.Microsoft.PerformancePoint.Scorecards.Upgrade__71e9bce111e9429c
NAME NOT FOUND Desired Access: Read
11:37:57,7313089 OWSTIMER.EXE
6272 RegOpenKey
HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.15.0.Microsoft.SharePoint.Portal.Upgrade__71e9bce111e9429c
NAME NOT FOUND Desired Access: Read
11:37:57,7313403 OWSTIMER.EXE
6272 RegOpenKey
HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.15.0.Microsoft.SharePoint.Portal.Upgrade__71e9bce111e9429c
NAME NOT FOUND Desired Access: Read
11:37:59,2026527 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:37:59,2109400 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:38:05,3534303 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:38:05,3537846 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:38:05,3594290 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:38:05,3597316 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:38:05,3653094 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144
11:38:05,3656118 OWSTIMER.EXE
6272 RegQueryValue
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS\MS_InternalUse_Only_UpgradeableVersion
NAME NOT FOUND Length: 144 -
Timer Services restart every minute
Hi,
I have a SharePoint 2010 Standard Server with SP1. I find that the Timer Services start and stop every minute. The below log appears every time the timer service restart. Would anyone help to solve this? Thanks.
The timer service is starting
06/18/2014 16:07:34.23 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Topology 2myf Medium Disabling the configuration filesystem and memory caches.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Waiting for mutex to initialize type dictionary
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Obtained mutex
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering assemlies and sequences
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Using assembly manifest Microsoft.SharePoint.UpgradeAssemblyManifest.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 0, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPConfigurationDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPConfigurationDatabase], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 0, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2] for [Microsoft.SharePoint.Administration.SPContentDatabase], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPFarmSequence2] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPIisWebSiteWssSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceSequence] for [Microsoft.SharePoint.Administration.SPService], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPServiceInstanceSequence] for [Microsoft.SharePoint.Administration.SPServiceInstance], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence] for [Microsoft.SharePoint.SPSite], Phase: 0, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSiteWssSequence2] for [Microsoft.SharePoint.SPSite], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsServiceApplicationSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsServiceApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPSubscriptionSettingsDatabaseSequence] for [Microsoft.SharePoint.SPSubscriptionSettingsDatabase], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPUsageApplicationSequence] for [Microsoft.SharePoint.Administration.SPUsageApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPUsageDatabaseSequence] for [Microsoft.SharePoint.Administration.SPUsageDatabase], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServerSequence] for [Microsoft.SharePoint.Administration.SPWebServiceInstance], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebServiceSequence] for [Microsoft.SharePoint.Administration.SPWebService], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWebTemplateSequence] for [Microsoft.SharePoint.SPWebTemplate], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.SharePoint.Upgrade.SPWssWebApplicationSequence2] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 1, Order: 0.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.25 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Reading xml configuration files from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade
06/18/2014 16:07:34.26 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\dlcupgradeb2b.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\ExcelMobileViewerUpgradeConfig.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\ExcelServicesUpgradeConfig.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\GbwUpgrade.xml.
06/18/2014 16:07:34.28 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\GbwUpgradeB2B.xml.
06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\IpfsUpgrade.xml.
06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\MpsUpgrade.xml.
06/18/2014 16:07:34.30 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\MpsUpgradeB2B.xml.
06/18/2014 16:07:34.31 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OsrvUpgrade.xml.
06/18/2014 16:07:34.33 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OsrvUserProfilesUpgrade.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\OSSSearchUpgrade.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\PPSUpgrade.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SecureStoreServiceUpgradeConfiguration.xml.
06/18/2014 16:07:34.44 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SiteUpgraderConfigSPS.xml.
06/18/2014 16:07:34.45 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SPSUpgrade.xml.
06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\SPSUpgradeB2B.xml.
06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\Wdsrv_Upgrade.xml.
06/18/2014 16:07:34.47 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WebAnalyticsUpgradeConfiguration.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WSSSearchUpgrade.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WssUpgrade.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPXmlConfigurationManager] [DEBUG] [6/18/2014 4:07:34 PM]: Loaded xml configuration file: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Upgrade\WssUpgradeB2B.xml.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.53 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.DLC.Upgrade.DlcIisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 7.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Excel.WebUI.Mobile, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.62 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Excel.WebUI.Mobile.Upgrade.ExcelMobileViewerSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 11.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Excel.WebUI.Mobile, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Excel.Server.MossHost.Upgrade.ExcelServicesSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 11.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Excel.Server.MossHost, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.FarmUpgradeSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.ServiceUpgradeSequence] for [Microsoft.Office.InfoPath.Server.Administration.FormsService], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.InfoPath.Server.Upgrade.SiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 15.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.91 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.FarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 0, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.OsrvPrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.SessionStateServiceSequence] for [Microsoft.Office.Server.Administration.SessionStateService], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.StateDatabaseSequence] for [Microsoft.Office.Server.Administration.StateDatabase], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.SessionStateSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Registering [Microsoft.Office.Server.Upgrade.StateServiceSequence] for [Microsoft.Office.Server.Administration.StateService], Phase: 2147483647, Order: 3.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: End registering Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: Begin registering Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:34.97 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:34 PM]: No assembly manifest found.
06/18/2014 16:07:35.05 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 0, Order: 17.
06/18/2014 16:07:35.05 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.ProfileDatabaseSequence] for [Microsoft.Office.Server.Administration.ProfileDatabase], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.SocialDatabaseSequence] for [Microsoft.Office.Server.Administration.SocialDatabase], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileApplicationSequence] for [Microsoft.Office.Server.Administration.UserProfileApplication], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.UserProfiles, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.06 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.ServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceSequence2] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchSharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchServiceApplicationSequence] for [Microsoft.Office.Server.Search.Administration.SearchServiceApplication], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchAdminDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchAdminDatabase], Phase: 0, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchMetadataDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchPropertyStoreDatabase], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.Search.Upgrade.SearchGathererDatabaseSequence] for [Microsoft.Office.Server.Search.Administration.SearchGathererDatabase], Phase: 2147483647, Order: 10.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.PerformancePoint.Scorecards.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.64 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.66 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSDatabaseSequence] for [Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceDatabase], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.66 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Upgrade.BIMonitoringServiceApplicationSequence] for [Microsoft.PerformancePoint.Scorecards.BIMonitoringServiceApplication], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.PerformancePoint.Scorecards.Upgrade.PPSSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.PerformancePoint.Scorecards.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.SecureStoreService, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.70 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.SecureStoreService.Server.Upgrade.SecureStoreDatabaseSequence] for [Microsoft.Office.SecureStoreService.Server.SecureStoreServiceDatabase], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.SecureStoreService.Server.Upgrade.SecureStoreServiceApplicationSequence] for [Microsoft.Office.SecureStoreService.Server.SecureStoreServiceApplication], Phase: 2147483647, Order: 17.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.SecureStoreService, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.SharePoint.Portal.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.72 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.ApplicationRegistry.Upgrade.BdcO14SharedResourceProvider12Sequence] for [Microsoft.Office.Server.Upgrade.SharedResourceProvider12], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.FarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.73 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.IisWebSiteSequence] for [Microsoft.SharePoint.Administration.SPIisWebSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Taxonomy.Upgrade.MetadataDatabaseSequence] for [Microsoft.SharePoint.Taxonomy.MetadataWebServiceDatabase], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Taxonomy.Upgrade.MetadataApplicationSequence] for [Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.PrejoinedFarmSequence] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.MossSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Portal.Upgrade.WebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 5.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.SharePoint.Portal.Upgrade, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Word.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.75 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Word.Server.Service.Upgrade.QueueDatabaseSequence] for [Microsoft.Office.Word.Server.Service.QueueDatabase], Phase: 2147483647, Order: 11.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Word.Server.Service.Upgrade.ServiceAppSequence] for [Microsoft.Office.Word.Server.Service.WordServiceApplication], Phase: 2147483647, Order: 11.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Word.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.Office.Server.WebAnalytics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.80 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.StagerDatabaseSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsStagerDatabase], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WarehouseDatabaseSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWarehouseDatabase], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWebServiceSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsWebService], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsFarmSequence] for [Microsoft.SharePoint.Administration.SPFarm], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServiceApplicationSequence] for [Microsoft.Office.Server.WebAnalytics.Administration.WebAnalyticsServiceApplication], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Upgrade.WebAnalyticsSiteSequence] for [Microsoft.SharePoint.SPSite], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.Office.Server.WebAnalytics.Upgrade.WebAnalyticsWebApplicationSequence] for [Microsoft.SharePoint.Administration.SPWebApplication], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.Office.Server.WebAnalytics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Begin registering Microsoft.SharePoint.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: No assembly manifest found.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPSearchDatabaseSequence] for [Microsoft.SharePoint.Search.Administration.SPSearchDatabase], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPServerSequence] for [Microsoft.SharePoint.Administration.SPServer], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Registering [Microsoft.SharePoint.Search.Upgrade.SPSearchServiceSequence2] for [Microsoft.SharePoint.Administration.SPPrejoinedFarm], Phase: 2147483647, Order: 4.
06/18/2014 16:07:35.81 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: End registering Microsoft.SharePoint.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Ready to initialize the type dictionary
06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Type dictionary initialized.
06/18/2014 16:07:35.83 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPDelegateManager] [DEBUG] [6/18/2014 4:07:35 PM]: Mutex released.
06/18/2014 16:07:35.84 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypassInternal = 0
06/18/2014 16:07:35.84 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypass = 0
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence2] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypassInternal = 0
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPConfigurationDatabaseSequence2] [DEBUG] [6/18/2014 4:07:35 PM]: UpgradableBuildBypass = 0
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: CanUpgrade [SPConfigurationDatabase] returned: True.
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: NeedsUpgrade [SPConfigurationDatabase] returned: True.
06/18/2014 16:07:35.86 OWSTIMER.EXE (0x13F0) 0x0A84 SharePoint Foundation Upgrade fbv7 Medium [OWSTIMER] [SPUpgradeSession] [DEBUG] [6/18/2014 4:07:35 PM]: IsBackwardsCompatible [SPConfigurationDatabase] returned: True.I have the following finding from the Event Viewer.
Event 7022
The Forefront Identity Manager Synchronization Service service hung on starting.
Event 7024
The Forefront Identity Manager Synchronization Service service terminated with service-specific error %%-2146234334.
Event 7031
The SharePoint 2010 Timer service terminated unexpectedly. It has done this 4007 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.
Event 11016
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{000C101C-0000-0000-C000-000000000046}
and APPID
{000C101C-0000-0000-C000-000000000046}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
I found this
post talking about the solution of this problem. Can anyone help to explain the solution to me?
Also, I try to stop the user profile service and user profile sync service and restart both. The timer service restart problem has gone!! However, new error in the event viewer.
Event ID 3
Microsoft.ResourceManagement: System.InvalidOperationException: This Forefront Identity Manager system resource cannot be deleted.
at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception)
at Microsoft.ResourceManagement.WebServices.ResourceManagementService.Delete(Message request) -
90% of the system resource is consumed when timer service is running
Hi,
I have an development environment with 8GB RAM with SharePoint 2013 and SQL Server 2014, The SharePoint runs slow when Timer Service is running. Turning of the Timer Service speed up the environment.
Is it a know issue with SharePoint 2013? Is there any update/hotfix available pertaining to the issue.
Thanks,
AjeetHi Ajeet,
According to your description, my understanding is that the SharePoint Timer Service(OWSTIMER) consumes 90% of the server resource in your SharePoint 2013 single server.
For your issue, could you run Microsoft Net Monitor to see the contents of the packets that were being sent / received by the owstimer.exe process? Also please make sure your single server match the
hardware requirement:
http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#hwforwebserver
Here is a blog for troubleshooting timer service issue:
http://soerennielsen.wordpress.com/2009/01/14/fixing-the-timer-service-when-everything-breaks-down/
http://www.mysharepointadventures.com/2012/09/sharepoint-timer-job-service-consuming-all-memory-on-server/
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support
Maybe you are looking for
-
Setting up family sharing with new Apple ID
I have an apple ID with lots of music and apps on it. When my son (14) got an iPod Touch, we set it up using my apple ID so that he could access all the music and games I had already purchased without buying them again. We then associated his own e
-
Want to make a mostly text book.
I would like to make a book of mostly text. I'm composing a book of letters between my grandparents and would like to be able to type them into the photo boxes. Is there anyway to make these text boxes? The caption boxes don't allow for enough space
-
Original iphone used for itunes and now wont sync bc of no sim
HELP PLEASE. I had been using this iphone for itunes and decided to get all the pics off so did a restore. Now it won't let me do anything to it because there is no SIM card in it before. I could always hook it up and sync before but this time I d
-
Ringtones Selected for Sync with iPhone does not showup in iPhone
In iTunes library under ringtones I can see few files and I can play them as well (They are of type m4r format). However when I chose to Sync All Ringtones (or even specifically this) iPhone does not show this in its Custom tone list. This is happeni
-
Is Ardence RTX required when I use PCI-7831R with labview real-time module for RTX target
I am new in the labview real-time field. I want to use labview real-time module for RTX target on only one desktop. My card is PCI-78331R. Is Ardence RTX necessary? Why I cannot find my card in the MAX after I configured the RTX? Thank you very much