WordPress database error Table wp_options doesn’t exist

Oh,my god!
I met the same thing…
I’m trying to solve it .

Having the same problem.

downloaded
tar.gz within the last hour.

windows xp
xampp 1.6.1
php 5.2.1
mysql 5.0.37

from apache error log
[Fri Sep 19 09:53:33 2008] [error] [client 127.0.0.1] WordPress database error Table ‘wp-db.wp_options’ doesn’t exist for query INSERT INTO wp_options (option_name, option_value, autoload) VALUES (‘cron’, ‘a:2:{i:1221832413;a:1:{s:17:\\”wp_update_plugins\\”;a:1:{s:32:\\”40cd750bba9870f18aada2478b24840a\\”;a:3:{s:8:\\”schedule\\”;s:10:\\”twicedaily\\”;s:4:\\”args\\”;a:0:{}s:8:\\”interval\\”;i:43200;}}}s:7:\\”version\\”;i:2;}’, ‘yes’) made by add_option

Downloaded wordpress 2.6.2 zip file 10 mninutes ago.

Installed WordPress successfully on
windows xp
xampp 1.6.6
php 5.2.5
mysql 5.0.51

Might want to review one of the articles presented in https://codex.www.ads-software.com/Installing_WordPress#Installing_WordPress_on_your_own_Computer

I am getting the same error.

wordpress-2.6.2
Windows 2003 IIS6
PHP 5.2.6
MySQL 5.0.51a Community Server

WordPress database error Table ‘aaa.wp_options’ doesn’t exist for query INSERT INTO wp_options (option_name, option_value, autoload) VALUES (‘cron’, ‘a:2:{i:1221983113;a:1:{s:17:\”wp_update_plugins\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:10:\”twicedaily\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:43200;}}}s:7:\”version\”;i:2;}’, ‘yes’) made by add_option
WordPress database error Table ‘aaa.wp_options’ doesn’t exist for query INSERT INTO wp_options (option_name, option_value, autoload) VALUES (‘random_seed’, ’68fdbc15596b13cba6bbf21053c3e9c3′, ‘yes’) made by add_option
WordPress database error Table ‘aaa.wp_options’ doesn’t exist for query INSERT INTO wp_options (option_name, option_value, autoload) VALUES (‘auth_salt’, ‘FqGWJ5lOXLAT’, ‘yes’) made by add_option

If you use phpMyAdmin, are any WordPress tables created in your database?

Wonder if this might be related
https://trac.www.ads-software.com/ticket/7724

I think I have the same problem, how do I fix this? I don’t understand how to implement the attachments in ticket 7724.

Ihks – Read anil’s answer here:
https://www.ads-software.com/support/topic/206999?replies=13#post-871638

I replaced update.php with that info, but now it ends up as nameless page when i goto the installation page. Hmm, previous verisons was just to install, how come it should be so hard to install the new version? O_o

THIS IS REDICULOUS, NO ANSWER IN SIGHT, SEARCHED ALL FORUMS, AND MNAY MANY PEOPLE EXPERIENCING THE SAME ISSUE. IF SOMEONE FIGURES OUT THIS PLEASE POST OR EMAIL ME.

I’d just like to take the time to thank the developers of WordPress for their fantastic efforts. These people put in many hours of their own time, using skills and knowledge that’s taken them a good bit of effort to learn themselves, all while asking for nothing in return. In my eyes, that’s a really big plus in these days and times, what with everything going on in the world. Now for the question at hand.

I haven’t tested anil’s solution and probably won’t, since the install script looks like it’s only used during initial installation or upgrades. I did experience the same issue though, but was able to get past the install screen by directly making a simple modification to the content in the MySQL database (see WAMP on VISTA, minor WP install issue?). That said, I’ll bet dollars to donuts that those experiencing the same problem can use the same work around to eventually end up at the login screen, and in-turn, the admin screen. All you’ve got to is modify the encrypted password in the database that the installation script creates on install.

I realize a number of folks have little or no experience with tools like phpMyAdmin and/or MySQL databases, but they’re really not that hard to learn. And you probably want to learn how to use tools like them, especially if you’re going to use a free product like WordPress that might have an over-looked kink or two in its source code. Issues *always* arise during code development that take time and a great deal of testing to sort out. Sometimes that testing ends up extending itself into the release phase, during which actual users come across errors that the developers didn’t experience before releasing their product(s). I suspect something like that has happened here.

If you’re finding that anil’s solution isn’t working for you after copying and pasting his code into the installation script, download and install a copy of a tool like phpMyAdmin (The phpMyAdmin Project), export a copy of your WordPress database for safe keeping, then delete it from MySQL. That’ll help prevent the installation script from hanging when it looks to see if a WordPress installation already exists. Then run the installation script again and let everyone know if anil’s fix worked.

janco