WordPress MU

I have installed the WP-MU, but as soon as I finished it, I receive the following errors:

-------------------------------------------
Fatal Error
Could Not Find Blog!
Searched for 192.168.0.200/wason/wpmu/ in wordpress::wp_blogs table. Is that right?
Please check that your database contains the following tables:
wp_blogs
wp_users
wp_usermeta
wp_site
wp_sitemeta
wp_sitecategories
-----------------------------------------------

But I found that my Mysql database have contain the above databases.

Could anyone help me out?

Thank you very much

I have saw that a lot of people have this problem. Nobody cannot help me to solve this problem?

Have you tried re-installing?

Not a resolution to the overall problem but may work as a quick fix.

Same problem here.... :(( is there admin could help us??

Try changing your siteurl in from the dashboard blog submenu screen

It worked for me.

I had siteurl as http://www.____.ca

I deleted the www and had only ____.ca in the siteurl field and it loaded up properly.

Unforturnately, I have no URL address.
By the way, It is not a good solution, right?

Could anybody who successfully installed the software tell us the method to manage it.

Thank you

I have soloved the problem.

I encounter the problem duce to my installation on apache with the port is 8080,not the standard one:80. And hence the page could not be found.

However, I think this is a bug. You see, not all server run at 80 port

I am having the same problem, but it doesn't appear everywhere. It comes up when I go to the import menu, login (if I remove the sessionID from the link it goes in fine), logout, or submit any changes through the dashboard forms.

I am not currently using a virtual host, could this be related to the problem? I'm going to try that out next...

FWIW, I would say that this has to be a bug because a quick Google search of "Could Not Find Blog!" brings up hundreds of sites that have this error.

"I am not currently using a virtual host, could this be related to the problem? "

Yes. If you search the forums, you'll also find countless other threads saying that the non-vhost option has bugs and isn't really supported.