error Unable to find members table! when upgrading

[Nozema]

I'm getting the error: "Unable to find members table!" when upgrading from 1.1.4 to 2.0 Beta 3.

This is right after I clicked continue on step 2.

[IchBin™]

Did you choose the upgrade package and not the update package?

[Nozema]

Because it said "Using modifications, or not using SMF 2.0 Beta 3? No problem, this is what you need." I used the Large upgrade.

When I got the error I als tried Small update (which I should't use, if I read it wright?) which gave the same error.

[Deaks]

nozema do you still need help with this?

[Nozema]

Jep, I haven't tried anything since then. I just want to test it on my test site, I run Mambo with the SMF bridge. I just wanted to test it before getting it into the real site.

[Nozema]

No one a clue

[metallica48423]

Thats certainly odd.

make sure that EVERYTHING gets overwritten properly.  theres no reason it shouldnt be able to find that particular table.  But some column names have changed so it could be just an upload mistake.

[Nozema]

Hi Metallica (good taste btw )

I'll try it again this weekend, but when I uploaded my fire ftp didn't hang or gave me any messages.

I'll let you know this weekend, thanks in advance for the effort!

[IchBin™]

Probably wouldn't hurt to try another FTP client if you have the same error again.

[pensoftware]

Yes, this happens to me too as stated in my topic: http://www.simplemachines.org/community/index.php?topic=232411.0

You can easily fix this error by going into upgrade.php and removing the "die()" that gives the error.

[metallica48423]

that seems like it would only circumvent the problem... really should try and find what's causing the problem and fix that rather than try to silence the error

[jummijammi]

While there might be several reasons for this "Unable to find members table!" message when running upgrade to 2.0 Beta 3, I located one.

First when everything failed and there was no help found here I also tried a similar approach as pensoftware suggested. I fixed the code fragment throwing the error. I did set the $db_collation value to correct value manually. That gave rather funny result, the converted did run without errors but it did nothing.

As I have many sites using the SMF software I had a change to compare. The first two were converted without any problems. I was actually surprised how the converted was able to make its work even I had made a lot heavy of modifications both to code and tables.

The third did not covert. No matter what I did. But finally I saw that in the Settings.php file the value $db_prefix was different in the forum that converted and in the one that did not.

When it was in the form
$db_prefix = 'smf_';
everything worked but when it was in the form
$db_prefix = '`databasename`.smf_';
nothing worked.

I have no idea why the other was different. It worked perfectly fine. Only when I tried to convert the problem appeared.

[metallica48423]

Nozema, did the above information help you?

[grantiago]

jummijammi -- thanks your solution worked for me!

[Aleksi "Lex" Kilpinen]

Nozema, I guess you don't need help with this anymore?

[N3RVE]

I'm going through old 'unresolved' topics, do you require any further support?
If they are none, please mark this topic as solved to indicate otherwise, reply if you require additional assistance

-[n3rve]