Ow. This took me a really long time to figure out today. In a test environment of an iMIS 15 upgrade from 10.6 at a client's office, the upgrade process was failing immediately in the very first script that looks to see what version of SQL Server is being used. I tried many, many things trying to make sense of it, failing to find the cause of the problem.
Finally, the light bulb came on. Their sa password has some special characters in it. Namely an ampersand and a carat (& and ^, respectively). Those special characters are not handled by the dbupgrader correctly and so the correct password was not being passed to osql.
In subsequent testing, I found that EITHER of those two characters will cause a problem with the upgrader. The ampersand will cause the upgrader to fail immediately. The carat will cause each of the ten separate scripts to run, but each will fail individually.
I don't know if there are additional characters that would cause a problem. I wouldn't be surprised if the percent sign is another problem since it's used for marking the beginning and end of variables within the .cmd files. But I've done enough testing on this topic for today.
(Submitted as SMR 167565.)
Comments