backed up dbase, not connecting to board

[jamesNorth]

This started with an Htt 500 error

So I have a back up of the dbase, which I uploaded to an new one,

I installed SMF 2.* latest version, my old board was 1.7 I think

I have the new SMF installed with the dbase links and password,
but
None of the data is showing, the board works, just no dBase is there,

I know there is a thread but sorry I cant find it, and Im sure Im being stupid.. but Im exasperated now

Hellppppppppp 
Thank you

[Aleksi "Lex" Kilpinen]

There isn't really enough details here to properly answer this - Started with a HTTP 500, and then what?
A HTTP 500 error is a server side error, and should leave an entry in the server logs.

An imported 1.x DB will not work with 2.x files straight. You will need to upgrade it, using the relevant 2.x large upgrade package and following the instructions in Upgrading SMF

[jamesNorth]

An imported 1.x DB will not work with 2.x files straight. You will need to upgrade it, using the relevant 2.x large upgrade package and following the instructions in Upgrading SMF

Ah, thank you Lex, I think thats the missing piece of the jigsaw I needed,

The 500 error was when my problems started, it lost the dbase and I couldnt get to the server, so upgrade and start again was the logical choice,

[jamesNorth]

mmmm this is more tricky,
I can down load the dbase direct from the phpmyadmin, I cannot get to my original smf 1..... as I get server 500,
I cannot get to the server,

Ive uploaded the dbase to a new one, and a new smf 2.

thats where I am stuck now,
should I try to find an old smf 1.... or ?

the data has uploaded, Im stuck with how to get the smf2.  to see it,

It mentions, backup_ renaming if I need to do that from smf 1.... im screwed,

[Aleksi "Lex" Kilpinen]

For the upgrade, you don't necessarily really need to be able to access the forum index - but before I go guessing, and making things worse, it could help if we knew what the 500 error is about.

The upgrade script is designed to run in place on a working SMF - but if the error is simply because the version is too old to run on the server, you could still be able to fix it simply by following the Upgrade process in place where it is now. (Of course, backing up absolutely everything first is always a good idea.)
Relevant wiki topics:
How do I backup my SMF forum?
Upgrading SMF

Moving the forum elsewhere first, is not necessarily a good idea unless you can get it to run at the new location on the old version first so you can correct all settings and make sure everything moved over correctly. But, finding a host with old enough PHP versions to run 1.x could also be a challenge these days.
Relevant wiki topics:
How do I move my SMF forum to a different host?
What is repair_settings.php?

[jamesNorth]

Thank  you, yes, I agree, but I seem to be running at this too late,

The Server issue, no idea, I dont have access to any info on that, I suspect its a shared server, but the guy who was running it may have passed,

"Backup database with the prefix "backup_"
Selecting this option will get the upgrade tool to copy all data in the database before upgrading within the original database."

I have the site on my local hard drive, so I will try to get the original to work, but I assume what ever stopped it working in the first place, isn't fixed so Im not sure how fruitful that will be, but desperate times ect

Thank you once again for your help and instuctions.

In the words or Arni, "Ill be back" 

If anyone wants to help play, there is a $ beer donation

[Aleksi "Lex" Kilpinen]

I have the site on my local hard drive, so I will try to get the original to work, but I assume what ever stopped it working in the first place, isn't fixed so Im not sure how fruitful that will be, but desperate times ect

You see, if the only reason it isn't working on the old server is the 500 error - it could simply be the server has been updated so that it doesn't support SMF 1.x anymore. Also, if the forum really is still on 1.x and you move it to a new server that has modern software on it, it could cause the same issue in reverse - 1.x would be too old to run.
On the other hand, it could also be something as simple as a corrupted file or an easily corrected config issue on the server. That is why the error could make a difference.