# Well, now, this was interesting ...
**URL:** https://boards.straightdope.com/t/well-now-this-was-interesting/64389
**Category:** About This Message Board
**Created:** [May 4, 2001, 9:40pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389 "2001-05-04T21:40:03Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Ice\_Wolf](https://boards.straightdope.com/u/Ice_Wolf)
#### Post date: [May 4, 2001, 9:40pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/1 "2001-05-04T21:40:03Z")
> [@](#):
>
> Warning: 1 is not a MySQL result index in admin/db\_mysql.php on line 82
>
> Warning: Oops, php3\_SetCookie called after header has been sent in global.php on line 731
>
> Warning: Oops, php3\_SetCookie called after header has been sent in global.php on line 734
>
> There seems to have been a slight problem with the database. Please try again by pressing the refresh button in your browser.
>
> An E-Mail has been dispatched to our Technical Staff, who you can also contact if the problem persists.
>
> We apologise for any inconvenience.
Received on the screen just a few minutes ago, while trying to access MPSIMS.
What does this mean?
---
### Author:  [@techchick68](https://boards.straightdope.com/u/techchick68)
#### Post date: [May 4, 2001, 10:44pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/2 "2001-05-04T22:44:12Z")
It means that PHP and MySQL had a moment of bad gas, recommendations are for the server to lay off beans and bananas. AKA a database compilation error (I believe.)
---
### Author:  [@waterj2](https://boards.straightdope.com/u/waterj2)
#### Post date: [May 4, 2001, 10:47pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/3 "2001-05-04T22:47:36Z")
> [@](#):
>
> Warning: 1 is not a MySQL result index in admin/db\_mysql.php on line 82
>
> Warning: Oops, php3\_SetCookie called after header has been sent in global.php on line 731
>
> Warning: Oops, php3\_SetCookie called after header has been sent in global.php on line 734
>
> There seems to have been a slight problem with the database. **Please try again by pressing the refresh button in your browser.**
>
> An E-Mail has been dispatched to our Technical Staff, who you can also contact if the problem persists.
>
> We apologise for any inconvenience.
What you need to know is bolded. The rest basically says, “whoops, something screwed up, sorry.” Happens every once in a while. Hit refresh and go on with life. It always works for me after I do that.
---
### Author:  [@Ice\_Wolf](https://boards.straightdope.com/u/Ice_Wolf)
#### Post date: [May 5, 2001, 9:34am UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/4 "2001-05-05T09:34:04Z")
I actually tried MPSIMS again, got no joy, thought, “Oh, well”, and – as **waterj** put it: “got on with life.” I didn’t go into the shock-horrors: just wanted to know, without e-mailing tech staff and probably not being able to understand their lingo, what it meant. Whatever got screwed up – did it involve 3 lines of the program? Wow.
“Oops” probably has meaning of its own in techie-speak. But doesn’t it _just_ sum up the whole deal? My applause to the techie who put that there.
---
### Author:  [@handy](https://boards.straightdope.com/u/handy)
#### Post date: [May 5, 2001, 5:21pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/5 "2001-05-05T17:21:21Z")
that happens to me sometimes, its usually the board being too busy I assume. Of course, IM sure to get a coldburn for that comment.
---
### Author:  [@Ice\_Wolf](https://boards.straightdope.com/u/Ice_Wolf)
#### Post date: [May 5, 2001, 5:43pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/6 "2001-05-05T17:43:08Z")
Not from me, **handy** , not from me. Ta for the input.
---
### Author:  [@Chronos](https://boards.straightdope.com/u/Chronos)
#### Post date: [May 5, 2001, 7:38pm UTC](https://boards.straightdope.com/t/well-now-this-was-interesting/64389/7 "2001-05-05T19:38:19Z")
Well, I don’t know SQL programming, but in my experience with C and BASIC, it’s almost unheard of for a program to have a problem that spans more than one line. What is common, though, is for a program to have a one-line error that the computer thinks is a multi-line error. Often, the line that has the error isn’t even one of the ones the computer suspects. Lots of luck, then, to the programmer who’s trying to find it.