Bug Stomp
Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!
Posts 745 - 757 of 8,681
Posts 745 - 757 of 8,681
You'll just have to be happy being magical. Inconsistant past log-in times are the least of my worries right now.
I actually had the feeling that the worst was behind us 
*sigh* Another bug. I know you just LOVE hearing about them. This one popped up in the part where the online user list is supposed to be, but the chat/forums/transcripts thing at the top appeared correctly.
Error Occurred While Processing Request
Error Diagnostic Information
ODBC Error Code = S1000 (General error)
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 10 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
The error occurred while processing an element with a general identifier of (CFQUERY), occupying document position (103:2) to (103:75).
Date/Time: 05/16/02 11:40:57
Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Remote Address: 216.117.22.123
HTTP Referrer: http://www.personalityforge.com/botland/index.cfm? CFID=1663&CFTOKEN=56085331
Error Occurred While Processing Request
Error Diagnostic Information
ODBC Error Code = S1000 (General error)
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 10 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
The error occurred while processing an element with a general identifier of (CFQUERY), occupying document position (103:2) to (103:75).
Date/Time: 05/16/02 11:40:57
Browser: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Remote Address: 216.117.22.123
HTTP Referrer: http://www.personalityforge.com/botland/index.cfm? CFID=1663&CFTOKEN=56085331
That* bug is the nasty one that had the site down for about 4 days. It's a SQL Server 7 bug. I'm trying to get them to upgrade me to SQL Server 2000. It looks like it's passed, but it's not something I can permanently fix without upgrading.
Aaaand it looks like I fixed the "StartAt" error that Skysaw & Onyx were talking about. Now I can take a break!
Aaaand it looks like I fixed the "StartAt" error that Skysaw & Onyx were talking about. Now I can take a break!
Just got that big nasty bug again, only lately it's been popping up in message windows too. I know you can't fix it but let's face it, I had nothing better to do than post about it. 
can't get at the language centre to correct typos. Is anyone else experiencing the same thing? I click on the key phrase and either nothing happens or it leaps to the top of the page and THEN nothing happens.
I have been experiencing computer whimwhams unrelated to the PF, could that be part of it?
I have been experiencing computer whimwhams unrelated to the PF, could that be part of it?
A me/you issue:
The programmed response is: Were you even supposed to (subj)? (For did I)
A: Did I already tell you I have a pine spittlebug for a pet?
B: Were you even supposed to already tell you you have a pine spittlebug?
It corrects the second I/You but not the first.
The programmed response is: Were you even supposed to (subj)? (For did I)
A: Did I already tell you I have a pine spittlebug for a pet?
B: Were you even supposed to already tell you you have a pine spittlebug?
It corrects the second I/You but not the first.
Sounds like it might be, unless someone else can substantiate these problems..
Skysaw- yes. Xnone happens when all else fails, so there's nothing to match to when getting the (subj) in any other section. It needs to find a match in order to goto.
I think the database is going to be upgraded to SQL Server 2000 soon, which will alleviate that bug. There were some SQL-type errors earlier that might have indicated that the upgrade was in progress. I'll let you know when we're up to v.2000.
Skysaw- yes. Xnone happens when all else fails, so there's nothing to match to when getting the (subj) in any other section. It needs to find a match in order to goto.
I think the database is going to be upgraded to SQL Server 2000 soon, which will alleviate that bug. There were some SQL-type errors earlier that might have indicated that the upgrade was in progress. I'll let you know when we're up to v.2000.
I understand, Prof. I just wanted a possible choice when no keyphrases were found to be a forced jump to a particular subject. I'll try a different approach.
Yeah.. my bot's conversations have been pretty much composed of xNones... if not just one-sided conversations...
» More new posts: Doghead's Cosmic Bar