Is anybody else getting this message??
#1
Thread Starter

My Feedback: (145)
I am getting this error message when accessing the jets forum frequently lately-
Microsoft OLE DB Provider for SQL Server error '80040e14'
There is insufficient system memory to run this query.
/forum/tt.asp, line 377
Anybody else or just me. Thanks, Scott
Microsoft OLE DB Provider for SQL Server error '80040e14'
There is insufficient system memory to run this query.
/forum/tt.asp, line 377
Anybody else or just me. Thanks, Scott
#2
Senior Member
Joined: Apr 2002
Posts: 858
Likes: 0
Received 0 Likes
on
0 Posts
From: Morecambe, UNITED KINGDOM
Yes i get it, must be a problem with RCU all the other forums i go on are OK
Suppose it could be high traffic problem
Suppose it could be high traffic problem
#4

#7
Senior Member
My Feedback: (1)
Joined: Jul 2003
Posts: 1,057
Likes: 0
Received 0 Likes
on
0 Posts
From: SeaTac - Angle Lake, WA
I got the same message several times. It means that the Jet Forum and the number of user's have outgrown the server and DB that to forum runs on. Time for a bigger and stronger server box
#8

My Feedback: (21)
yeah bro', I just changed my avatar addy.
I left 0430 on Tue arrived Wed and went straight to work on Thursday.
I'm looking forward to getting my routine established so I can get out to the local jet fields. over the next couple of weeks. Heading to key west in July. gonna get S hit street on Duval face.
glad you had fun @ the Willow. wish I could've made it.
take care
buck
I left 0430 on Tue arrived Wed and went straight to work on Thursday.
I'm looking forward to getting my routine established so I can get out to the local jet fields. over the next couple of weeks. Heading to key west in July. gonna get S hit street on Duval face.

glad you had fun @ the Willow. wish I could've made it.
take care
buck
#12
Banned
This was earlier today. we had a RAID drive failure and the new one is auto-rebuilding on the fly. if it happens again PM me or email me at support at rcuniverse dot com for fastest response to this issue. This isn't a load issue but a combination of the drive failure causing other issues. Things should be getting back to normal and I have a sql DBA coming in over the next week to work on some additional perforance tuning as well as some advanced backup strategies to ensure we are well covered for every case scenario of what could ever go wrong



