Odd SQL 2008 R2 behavior - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

Odd SQL 2008 R2 behavior

Author

Topic

djj55
Constraint Violating Yak Guru

352 Posts

Posted - 2010-09-28 : 09:04:40

I posted this on another forum and mr denny found a couple problems (thank you) however I am still getting the memory dumps. Thought I would post here and see if a new set of eyes could help.

The problem is a memory dump starts and repeats until the system is no longer responding.

2010-09-07 00:01:00.30 spid68 DBCC TRACEON 3226, server process ID (SPID) 68. This is an informational message only; no user action is required.
2010-09-07 03:00:34.02 spid59
Memory Manager KB
---------------------------------------- ----------
VM Reserved 10616976
VM Committed 10597536
Locked Pages Allocated 0

This goes through the current (non system) spid's and starts again, over and over.

No error just the memory dump.

At 12:01 AM I run DBCC TRACEON (3226, -1) which I thought turned off 3226.
The problem did not start until 3 am.

I had a bad day when I set that up and thought it was odd that you used TRACEON to turn it off but thought I read I needed to do it that way.

Well I started using the TRACEOFF but it dumped again last night.

Note that I set TRACEOFF at midnight while the dump did not happen until 4:32 AM

The log shows the Log Shipping, transaction log file back ups then it just starts the memory dump.

On the Windows 2008 R2 server side at 2:49 I got
Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16385, time stamp: 0x4a5be01a
Exception code: 0xc0000005
Fault offset: 0x0000000000039389
Faulting process id: 0xca8
Faulting application start time: 0x01cb59c74be900e1
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\ole32.dll

At 4:35 it shows
Error: 17887, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

I have added the lock page authentication.

Also we have not downloaded the latest set up updates (hope to this weekend).

Any thoughts? Any suggestions?

Thank you,

djj

djj55
Constraint Violating Yak Guru

352 Posts

Posted - 2011-03-07 : 09:23:55

Contacted MS. The answer was that the max memory needed to be set. The default is set to a very large number which meant that all the memory was being used not leaving any for the OS. We set a max that to allow the OS to have some memory and have not had trouble since.

djj

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources