Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

SI - Site Forums : Silicon Investor - Welcome New SI Members! -- Ignore unavailable to you. Want to Upgrade?

To: c.horn who wrote (10515)	12/7/1999 8:58:00 PM
From: Carolyn	Read Replies (1) \| Respond to of 32968

I got the same thing in this reply. What is going on? EVERY time I click on Next 10 that awful GSP Error comes up.

To: c.horn who wrote (10515)	12/7/1999 9:12:00 PM
From: bluejeans	Read Replies (2) \| Respond to of 32968

I think the answer is right here:<g> We write free software bitmechanic.com

To: c.horn who wrote (10515)	12/8/1999 5:05:00 AM
From: Green Receipt	Respond to of 32968

sounds like a new programmer is on the staff now...

To: c.horn who wrote (10515)	12/8/1999 12:39:00 PM
From: Lizzie Tudor	Read Replies (1) \| Respond to of 32968

I can top that... There was a problem posting your message. * fsUtilMsgPreviewSubmit: Can't allocate space for object 'Syslogs' in database 'qcomstock' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment. Severity 17, State 2, Procedure 'gargantua updateSnapshot', Line 3 Please back up and try again. Really basic logfile extension stuff. There is a product (BMC, I think) called the "database patrol" that warns you before this is going to happen and pages someone.