The database error you mention is a session issue and has been fixed in 9.70.
The reason for it is that even though the session ID is made of 4 parts each containing random characters and numbers up to 8 charters long looking like:-
cd4ee523-4a18-c41535f1-40575-5893f6a
It seems that ASP's randomising is not that random, and even though each group is built individually some session ID's were the same as others causing an error when entering it to the database.
To fix this issue a 10 digit number is now added to the end of each session ID which is created from the double-precision number representation of the date down to the milli second so that it would now be virtually impossible for the session ID to match another.