I am certainly going to continue trial and error testing with this problem. I know how to cause this problem but if I can eliminate it at will it would be helpful in knowing that the solution is correct and not just a fluke.
I had been deleting old log files as I went along to prevent myself from accidentally reading an old log file. You are absolutely correct about how error messages can be misleading.
One of the problems with this error was it never produced a bad session/time stamp error on my Vista machine it only generated that error on the XP machine. Another one was unable to insert character data into the database. Both of those errrors were easily bypassed by manual insertion of the needed data. I was thinking the whole time that I had just made an update mistake which may not have been the case.
|