Brian,

that was just a first idea - and I said that it is NOT the suggested upgrade path, which can be found here. The installer does not check it, as it is not the "mandatory" but the "suggested" upgrade path. Depending on the installed extensions this could be something else as well.

I still think it is (or was) an issue with the .Net-framework. Sourabh said in his last post "I have tried by changing the framework but It still showing the same issue." He did not answer on my last post for five days, so I think registering the framework to the website has solved his problem. It would have been nice when he had written something like "Thanks, that was the solution", or posting his solution when he had found something else, but this is something you cannot expect from most of the people here.

Happy DNNing!
Michael

Sourabh,

I am glad it works for you now - and thanks for posting the solution.

Could you just tell which extension made the problems? Maybe updating the extension with the DNN Update could help - this is quite easy to do, just copy the install package of the extension in the approprate folder under the "install" folder (modules, skins...) before you start the upgrade process.

Happy DNNing!
Michael