SharePoint - Windows SharePoint Services Timer service terminated unexpectedly

Asked By Alex on 06-Jul-10 02:03 AM
Hi,

The Windows SharePoint Services Timer service of our MOSS 2007 farm has been
terminating unexpectedly very often.

I am also getting the following error.

Event Type:        Error
Event Source:    .NET Runtime 2.0 Error Reporting
Event Category:                None
Event ID:              5000
Date:                     7/5/2010
Time:                     8:15:06 PM
User:                     N/A
Computer:          SG4-WEB10
Description:
EventType clr20r3, P1 owstimer.exe, P2 12.0.6520.5000, P3 4ad3af43, P4
microsoft.sharepoint, P5 12.0.0.0, P6 4bda4aca, P7 82, P8 e, P9
system.outofmemoryexception, P10 NIL.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00   c.l.r.2.
0008: 30 00 72 00 33 00 2c 00   0.r.3.,.
0010: 20 00 6f 00 77 00 73 00    .o.w.s.
0018: 74 00 69 00 6d 00 65 00   t.i.m.e.
0020: 72 00 2e 00 65 00 78 00   r...e.x.
0028: 65 00 2c 00 20 00 31 00   e.,. .1.
0030: 32 00 2e 00 30 00 2e 00   2...0...
0038: 36 00 35 00 32 00 30 00   6.5.2.0.
0040: 2e 00 35 00 30 00 30 00   ..5.0.0.
0048: 30 00 2c 00 20 00 34 00   0.,. .4.
0050: 61 00 64 00 33 00 61 00   a.d.3.a.
0058: 66 00 34 00 33 00 2c 00   f.4.3.,.
0060: 20 00 6d 00 69 00 63 00    .m.i.c.
0068: 72 00 6f 00 73 00 6f 00   r.o.s.o.
0070: 66 00 74 00 2e 00 73 00   f.t...s.
0078: 68 00 61 00 72 00 65 00   h.a.r.e.
0080: 70 00 6f 00 69 00 6e 00   p.o.i.n.
0088: 74 00 2c 00 20 00 31 00   t.,. .1.
0090: 32 00 2e 00 30 00 2e 00   2...0...
0098: 30 00 2e 00 30 00 2c 00   0...0.,.
00a0: 20 00 34 00 62 00 64 00    .4.b.d.
00a8: 61 00 34 00 61 00 63 00   a.4.a.c.
00b0: 61 00 2c 00 20 00 38 00   a.,. .8.
00b8: 32 00 2c 00 20 00 65 00   2.,. .e.
00c0: 2c 00 20 00 73 00 79 00   ,. .s.y.
00c8: 73 00 74 00 65 00 6d 00   s.t.e.m.
00d0: 2e 00 6f 00 75 00 74 00   ..o.u.t.
00d8: 6f 00 66 00 6d 00 65 00   o.f.m.e.
00e0: 6d 00 6f 00 72 00 79 00   m.o.r.y.
00e8: 65 00 78 00 63 00 65 00   e.x.c.e.
00f0: 70 00 74 00 69 00 6f 00   p.t.i.o.
00f8: 6e 00 20 00 4e 00 49 00   n. .N.I.
0100: 4c 00 0d 00 0a 00         L.....


Hope that someone can give me some advice on how to resolve this.


Thanks,
Alex


bathawes replied to Alex on 08-Jul-10 06:37 PM
Looks like an our of memory exception.

These issues are typically caused by IIS application pool worker
processes using a lot of RAM on SharePoint WFE servers. This is more
of an issue if you are using 32-bit hardware as the address space is
limited and you have a 4GB physical limitation.

The long term solution is to upgrade to 64-bit and add some RAM
(assuming you are on a 32-bit WFE server).

Short term, I would check task manager on the affected server(s), then
modify the application pool recycling settings to mitigate the issue.
While an app pool recycle does lose session state, it is far less
severe than a OOM exception like the one you are getting.

HTH.

Benjamin Athawes
T: @benjaminathawes
W: http://mossblogger.blogspot.com
Alex replied to bathawes on 08-Jul-10 09:23 PM
Hi,

Our WFE servers are running Windows Server 2003 R2 x64 with 8GB of RAM.  Is
there something we can do to determine which app is causing the memory
issue?

Thanks,
Alex