Please can someone help, I am tearing out what little hair I have left.
I had to move a clients Magento from one 1and1 server to another and am getting the above error message when trying to access the site. Whilst 1and1 server support have tried to be helpful their Magento knowledge is limited and I am not getting very far.
Initially I was told to just upload the Magento files and database to the new server after which I was getting the above error report. After three days of trying to get help at 1and1 someone said that I should have installed Magento first through Plesk and then uploaded the files. I duly did this and prior to uploading the original files Magento was actually working with the basic installation page and I could get access to Admin but after uploading the files and the database I am back to square one.
I have checked over and over again the local.xml with the settings in Plesk and as far as I can see the database settings are correct.
Please can someone help as I have a client who is quickly losing patience and to be honest I can't blame him!
Can you check your database credentials?
Maybe your current configuration is trying to access to an old remote database server?
You are lookign the right file.
Also you'll need to clear cache.
Are you being able to connect to the database using the credentials placed on your file but using the command line?
Tried connecting database using ssh and that worked fine. Listed all tables.
So must be a Magento problem somewhere
On Magento 1, normally, th eonly place to find database credentials is /app/etc/local.xml
Maybe you can check the file and credentials?
Can you perform an search through your files looking for the old user or password? (Maybe can be hardcoded at some place?)
That's because Magento reads all the *.xml files into that directory.
Your original file was being read after (because the name) and the credentials were overwritten.
Extra files has something like *.xml.additional so those files won't be used. On Enterprise versions you'll find a file called enterprise.xml too.
(I've learned that in the hard way too, you're not alone here)