I'd check a couple of things.
If this is a new EPiServer update you've tried to install, try manually deleting everything in your /bin/ folder before doing a fresh compile in VS.
When rolling back, if your website is still active (the IIS process), the zip files in your /modules/ folder might not have been rolled back, as the IIS process are using them.
If everything else fails, try deleting everything in your ASP.NET temp folder. The path should be something like:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
Ron, did you manage to resolve this? I am struggling with the same exception and would be helpful to understand what helped you resolve this.
Hi Manish, What did it for me was disable the Content Collaboration addon. This plugin made the whole system unstable. After that Episerver worked again. But since then there were quite a bit of upgrades so i don't know about the current situation. Good luck with these errors.
Thanks Ron. Managed to resolve it.
Turns out that rootPath for publicModules under epiServer.Shell config section was incorrect in our case.
I just stumbled upon a problem that completely breaks my Episerver CMS solution.
I had a fine working CMS implementation (checked into source control), but after reading about a 'content collaboration' nuget package i tried to install that in the solution. Sadly....the whole solution now falls apart, and what's even worse, even if i go back to my previous version it still falls apart!
Can anyone help me with this since the project now came to a complete halt. Probably something is also changed in the database, since i can't get the solution running anymore..... HELP!
The error reads 'Value cannot be null. Parameter name: type'
The rest reads like this: