SI
SI
discoversearch

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: ViperChick Secret Agent 006.9 who wrote (1990)7/30/1998 4:41:00 PM
From: Peter V  Respond to of 32918
 
same here, lisa



To: ViperChick Secret Agent 006.9 who wrote (1990)7/30/1998 5:23:00 PM
From: SI Brad  Read Replies (1) | Respond to of 32918
 
Lisa,

The bug was fixed for about a week and apparently has returned. It's a bizarre MSFT SQL Server issue. I'm working on it.

The problem is with an insertion into the SI database of a new message of a specific size...the message fails to insert for a short period of time.

It is happening to about 1 out of every 30 messages submitted. If it happens to you, please wait 1-2 minutes and try to submit the message again. It will eventually go through.

Brad



To: ViperChick Secret Agent 006.9 who wrote (1990)8/3/1998 12:28:00 AM
From: SI Brad  Read Replies (4) | Respond to of 32918
 
Bug update for "requested page not found"

It looks like the intermittent posting problem is under control again. Now it appears that fewer than 1 in 1000 posts are experiencing a failure of some kind, and after a failed submit the second try always works.

I won't get into the technical details of what was going on (and hopefully no one will ask!).

I'm not ignoring the other threads of thought going on here...between the gnarly bug and moving the site I've been preoccupied lately.

We're going to switch operations over to Seattle by next weekend. There shouldn't be but 1-2 hours of downtime in the middle of the night. I'll post again here (and on the member homepage) the exact time of the shutdown 24 hours before it happens.

Brad