5 replies to this topic

[holdandmodify]

Permanently getting IPS Driver Errors after a server move. I can connect fine to the database, so I'm pretty certain my changes to the global config file are correct.

This unpleasant MySQL error is causing the IPS Driver Errors according to the logs:

Error Number: 1064
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
IP Address: *.*.*.*
mySQL query error: SELECT * FROM ipb_skin_sets WHERE set_skin_set_id=

I assume this is truncated somehow - otherwise it's clear that the WHERE clause should fail as there is no value assigned. But not sure how a server move could be the cause of this.

I made sure that the ipb_skin_sets table is identical to the one on the old server. I was briefly able to enter the ACP at some point and started updating the cache just in case. But it didn't complete the procedure and then started giving the errors again. I have tried repairing all the skin tables, but to no avail.

Edited by holdandmodify, 20 July 2010 - 12:12 AM.

[AndyF]

Rebuild your skin caches.

If it fails, if possible compare your old database (if its still on the old server) to the newly imported one on the new server, I would guess your skin_cache talbes are truncated.

If its no better, go to the skin manager, very top right button and create a new skin set. This will make a copy of the default classic blue skin. If this fails, re-import your database again.

[holdandmodify]

Thanks, I made sure that all the skin tables were of identical size. And the content also looked to match 100 percent. I can't access the ACP on the new server at all. However, I did some more cleanup on the old server - updating caches etc. and ran a new backup. And I'm now going for a new database import and a new upload of all the files. I'm using the SQLDumpsplitter to split the database as it's too large to be imported in one go (the host has a 200 MB limit). I tried splitting it differently this time and made sure that the individual SQL files looked alright and weren't truncated in a bad place. Will see how it goes.

[holdandmodify]

The problem was solved (fingers crossed) by doing a new import. In case anyone experiences anything similar: I also noticed that after the first import I couldn't access phpMyAdmin immediately through the control panel. I got an Access Denied error. However, it worked if I told it to open in a new window. After the reimport (in only 2 chunks as opposed to 4) I could go into phpMyAdmin directly from the control panel without seeing that error.

[AndyF]

Thanks for posting back with your findings

An old .htaccess file can cause odd issues too, but I tend to remove any that are not relevant (such as ones generated by IPB for directory protection etc) and re-add them afterwards once I'm sure its working properly.

[AndyF]

The issue this topic was opened for has now been resolved.