mitchel.sellers@gmail.com wrote
The installation date item is a good thing to have in if you are doing an upgrade, It prevents machine keys from being changed by the install, and helps identify an upgrade. I am still very curious as to why the 4.4.0 scripts tried to execute on upgrade, when I did my 4.5.0 -> 4.5.1 upgrades ONLY the 4.5.1 data scripts ran, and that is all that should be run for you....
Just read through your guide again, and I know I didn't miss anything. Followed it to the letter. As I've said before, I did the upgrade twice, the second on a fresh 4.5.0 CrystalTech install and it still failed. Wonder if there's something amiss in the CT install procedure??
John wrote
If it runs the 4.4.0 script again then it is probably because that is what version it thinks the DB is at (Versions table).
The output of that upgrade looks like new install to me. Maybe the {objectQualifier} or {databaseOwner} were different so it tried to install a fresh copy (still should have worked though).
Just checked the Version table:
| VersionId |
Major |
Minor |
Build |
| 1 |
4 |
4 |
0 |
| 2 |
4 |
4 |
1 |
| 3 |
4 |
5 |
0 |
The {objectQualifier} was unchanged at 'dnn' and the {databaseOwner} was also unchanged at 'dbo'. Checked the download package again, definitely the Upgrade version.
Thanks for the help chaps, if you have any ideas, I'm listening; I'm not sure I'm going to attempt the upgrade again just yet though :)