Session ID stored in mySQL is kills my store

[bravely]

First of all - I had my store working perfectly. I was ready to open it on Monday. As a final step I had my hosting company change my server so that I could have access to SSL. Now I have reinstalled exactly as before and I'm having a big problem. If I configure OSC to store sessions in mySQL, the store works fine, but as soon as a session is written to the database, it crashes the entire store. It just gives "server has encountered an error". I know it's a session problem because I can go into the database and erase the session entry and the store works fine again until another session ID is entered. I have an exact copy of this store running on another backup server and it works perfectly off of mySQL session ID's.

 

I know you are thinking "just save the session as a file" but I cannot do that because it raises a whole slew of problems doing it that way.

 

Does anyone know what could be causing this?

 

BTW. I checked the session entries in the database and they appear to be properly formed.

[bravely]

Here's an example of a session ID that kills the store. Does this look correct?

 

sesskey:

bfc009af8ef6f6cb715c374c32f3c92c

 

expiry:

1038180046

 

value:

cart|O:12:"shoppingcart":3:{s:8:"contents";a:0:{}s:5:"total";i:0;s:6:"weight";N;}language|s:7:"english";languages_id|s:1:"1";currency|s:3:"USD";navigation|O:17:"navigationhistory":2:{s:4:"path";a:1:{i:0;a:4:{s:4:"page";s:16:"product_info.php";s:4:"mode";s:6:"NONSSL";s:3:"get";a:2:{s:5:"cPath";s:2:"23";s:11:"products_id";s:2:"42";}s:4:"post";a:0:{}}}s:8:"snapshot";a:0:{}}

[bravely]

PS. I have tried using both my original snapshot from 10/29 and also a recent snapshot from 11/22. Both versions are encountering the same problem.

 

PPS: How come I can't edit my original posts?

[bravely]

OK, today's my birthday, so if anyone could help me out with this it will make my day!