I've looked in the web.config, no dups that I can see. When I restored the code from backup, that file was restored also, so it should be the same as what worked previously. I'm not sure what a "nested" web.config is, but I looked for web.config files in other folders and there are none.
If I use the SQL management tools, the SQL "dbo.version table is:
version, major, minor, build, date
| 1 |
4 |
4 |
0 |
10/2/2007 6:26:05 PM |
| 2 |
4 |
4 |
1 |
10/2/2007 6:26:10 PM |
| 3 |
4 |
5 |
0 |
10/2/2007 6:26:12 PM |
| 4 |
4 |
5 |
1 |
10/2/2007 6:26:13 PM |
| 5 |
4 |
5 |
2 |
10/2/2007 6:26:14 PM |
| 6 |
4 |
5 |
3 |
10/2/2007 6:26:14 PM |
| 7 |
4 |
5 |
4 |
10/2/2007 6:26:14 PM |
| 8 |
4 |
5 |
5 |
10/2/2007 6:26:14 PM |
| 9 |
4 |
6 |
0 |
10/2/2007 6:26:16 PM |
| 10 |
4 |
6 |
1 |
10/2/2007 6:26:16 PM |
| 11 |
4 |
6 |
2 |
10/2/2007 6:26:16 PM |
I'm assuming this means the database did get upgraded when the upgrade script ran, and I suspect this might be why rolled-back code barfs with some functions, notably the "host->host settings" but I think some other functions are failing too. Perhaps there is some way to spoof the database or roll back whatever changes were done to the database? failing that, is there a way to force the upgrade script to run again, or will that cause even more problems?
I tried installing the upgrade again, but it won't run at all. 4.5.5 won't let me use the host->settings but at least it runs for the most part, and users can access the portal.