SW support has been working with me but no solution has been found yet. Case#: 293935 After upgrading to 10.2, I have been experiencing web page timeouts, followed by the Module engine crashing. Support rep has taken quite a few steps to get things running better. When it's working, the website response is much better now, due to these actions. But then, after 30 minutes, sometime less, sometimes more, the module engine crashes, and I get several errors in the event viewer. Support rep is leaning towards the problem being related to DB performance, which is a possibility. But the problem I have with that is that everything had been running very smoothly before the upgrade to 10.2. Server specs. poller: 2008 r2 2x quad core xeon 2.4 Ghz processors. 16 gigs of ram DB server: 2008 r2 2x quad core xeon 2.66 Ghz processors. 16 gigs of ram Unfortunately, the DB is on raid 5 disk, not raid 10. (upgrading is probably not an option. politics ) If any other SW support tech could take a look at the case and offer any help, I would be very appreciative. As of now, our Orion server is on the edge of being useless, and we rely on it heavily for monitoring and reporting. thanks, Jeremy event view errors: -System -Provider [ Name] SolarWinds.Orion.IpSla.BusinessLayer -EventID4001 [ Qualifiers] 0 Level2 Task0 Keywords0x80000000000000 -TimeCreated [ SystemTime] 2011-12-14T17:20:23.000000000Z EventRecordID507314 ChannelSolarWinds.Net ComputerGDLLSDSRVSHC174.ls.gdls.com Security -EventData Service was unable to open new database connection when requested. Exception Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. Connection string - Data Source=GDLLSDSRVSHC173;Initial Catalog=NetPerfMon;User ID=SolarWindsNPM;Password=*******;Connect Timeout=20;Load Balance Timeout=120;Workstation ID=GDLLSDSRVSHC174 ------------------------------------------------------------------------------------------------------------------ Followed by this error: -System -Provider [ Name] SolarWinds.NPM.BusinessLayer -EventID0 [ Qualifiers] 0 Level2 Task0 Keywords0x80000000000000 -TimeCreated [ SystemTime] 2011-12-14T17:28:14.000000000Z EventRecordID507315 ChannelSolarWinds.Net ComputerGDLLSDSRVSHC174.ls.gdls.com Security -EventData Unhandled exception: Exception of type 'System.OutOfMemoryException' was thrown.

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

NPM Module engine constantly crashing after upgrade to 10.2.

SW support has been working with me but no solution has been found yet.

Case#: 293935

After upgrading to 10.2, I have been experiencing web page timeouts, followed by the Module engine crashing. Support rep has taken quite a few steps to get things running better. When it's working, the website response is much better now, due to these actions. But then, after 30 minutes, sometime less, sometimes more, the module engine crashes, and I get several errors in the event viewer.

Support rep is leaning towards the problem being related to DB performance, which is a possibility. But the problem I have with that is that everything had been running very smoothly before the upgrade to 10.2.

Server specs.

poller: 2008 r2 2x quad core xeon 2.4 Ghz processors. 16 gigs of ram

DB server: 2008 r2 2x quad core xeon 2.66 Ghz processors. 16 gigs of ram

Unfortunately, the DB is on raid 5 disk, not raid 10. (upgrading is probably not an option. politics )

If any other SW support tech could take a look at the case and offer any help, I would be very appreciative.

As of now, our Orion server is on the edge of being useless, and we rely on it heavily for monitoring and reporting.

thanks,

Jeremy

event view errors:

-	System

-	Provider

[ Name]

SolarWinds.Orion.IpSla.BusinessLayer

EventID

4001

[ Qualifiers]

Level

Task

Keywords

0x80000000000000

-	TimeCreated

[ SystemTime]

2011-12-14T17:20:23.000000000Z

EventRecordID

507314

Channel

SolarWinds.Net

Computer

GDLLSDSRVSHC174.ls.gdls.com

Security

-	EventData

Service was unable to open new database connection when requested. Exception Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. Connection string - Data Source=GDLLSDSRVSHC173;Initial Catalog=NetPerfMon;User ID=SolarWindsNPM;Password=*******;Connect Timeout=20;Load Balance Timeout=120;Workstation ID=GDLLSDSRVSHC174

------------------------------------------------------------------------------------------------------------------

Followed by this error:

-	System

-	Provider

[ Name]

SolarWinds.NPM.BusinessLayer

EventID

[ Qualifiers]

Level

Task

Keywords

0x80000000000000

-	TimeCreated

[ SystemTime]

2011-12-14T17:28:14.000000000Z

EventRecordID

507315

Channel

SolarWinds.Net

Computer

GDLLSDSRVSHC174.ls.gdls.com

Security

-	EventData

Unhandled exception: Exception of type 'System.OutOfMemoryException' was thrown.

Find more posts tagged with

Accepted answers

All comments

jcooler

Thinking that the raid configuration might be part of the issue (we do experience intermittent high Disk write queue lengths), I stopped the netflow service, as this one probably causes the heaviest I?O to the DB. I figured that might help things out temporarily. It did not help. About 10 minutes after stopping the service, the webpage timed out and we got the errors noted above in the event log.

With Netflow stopped, the disk queues on the DB server look much better, but the problem still occurs. Leading me further to believe that this is not the cause of the problem.

charliedontsurf

Did you solve this issue? I am having a similar problem since upgrading to 10.2.1:

Exception Exception of type 'System.OutOfMemoryException' was thrown.

vsta

Hello,

Any update on this topic?

jcooler

I ended up wiping by DB and starting over clean. There was no resolution, after 2 months of troubleshooting, so I just bit the bullet and did it. I left the old DB in tack, so that I could run SQL scripts to update most of the custom fields and what not.