It may be possible to try something else here. We used to have situations where we needed to import customisations to an upgraded environment but had dependencies on incompatible old solutions so couldnt move the solution across.
It's entirely unsupported but if you exported the default solution, extracted the zip file and had a look through the 3 main xml files, you can possibly find some of the bits of this solution hanging about (search on GUID etc). I am pretty sure there were numerous links between the customisations and solution xml files. You can then chop stuff out, re-save and re-zip.In my scenario, it was then possible to import the doctored solution (after MANY attempts and digging more and more lines out (an xml file tells you where the import is failing)) to a cleanly installed new version as i had cut the dependencies to the old solutions out.
In your scenario, importing the doctored solution back into the same environment to then upgrade it possibly wont work though. Still might help find the bad bits to consider your next move.
Goes without saying, importing a doctored solution anywhere risks breaking stuff. I only ever used this to get customisations across versions for testing. Wouldnt trust it beyond that.Jamie
If you've found this thread useful, dive deeper into User Group community content by role