uninstalling Epserver Mail 4.4

Vote:
 

Following the uninstallation guide: http://world.episerver.com/Documentation/Items/Tech-Notes/EPiServer-Mail-441/Uninstall-EPiServer-Mail-441/

 

And its not working. Getting 500-Internal server error. Is there a more comprehensive guide to do this the right way? Or any sugesstions?

 

Running:

CMS 6R2

Compoer 4 R2 (4.1)

Episerver Mail 4 sp1 (4.4)

 

Reason: I want to upgrade to Eiserver Mail 5 but there isnt a option to upgrade thus leaving us to uninstall version 4.4 first.

#55561
Dec 07, 2011 16:16
Vote:
 

Hi Nicklas.

Did you solve this?

#69751
Apr 04, 2013 16:18
Vote:
 

If you have done this and you're facing some error message, please share the actual error message.

#69765
Apr 05, 2013 9:51
Vote:
 

After we have installed EPI Mail 5 R2 on a EPI Server CMS 6.2 R2 site we do get a Server 500 Error. No complains during the installation.

#69772
Apr 05, 2013 13:02
Vote:
 

What I meant was to check what the actual error message says as just the http status code doesn't really explain what is happening.

Check the logs, alternatively turn off the EPiServer globalErrorHandling and ASP.NET customErrors settings in configuration as necessary to allow the actual error message to be returned in the response.

#69775
Apr 05, 2013 13:27
Vote:
 

It says error 500.19.
There is a duplicate 'system.web.extensions/scripting/scriptresourcehandler' section defined.

Can I Email you some screenshots?

#69914
Apr 09, 2013 16:56
Vote:
 

Based on the error message above it seems like the problem is that there is a duplicate config section (system.web.extensions/scripting/scriptresourcehandler) registered in your web.config (either conflicting with another entry in web.config itself or maybe in machine.config(?)).

 

I think the mentioned section is new to machine.config in .net 4.0(?), though. Is this site running in a .net 4 application pool?

If so, you'll want to remove the duplicate entries (compare web.config to %windir%\microsoft.net\framework\v4.0.30319\config\machine.config).

#69921
Apr 09, 2013 18:25
Vote:
 

Thanks for your proposal. We have removed duplicated entries and we came a little bit further. But now we get this error: [NullReferenceException: Object reference not set to an instance of an object.]
   EPiServer.Common.Configuration.ConfigurationSectionBase`1.GetInstance(String sectionName) +232
   EPiServer.Common.Configuration.EPiServerCommonSection.get_Instance() +16
   EPiServer.Common.Settings.LoadEntityProviders() +460
   EPiServer.Common.Settings.LoadSettings() +242
   EPiServer.Common.InitializationModule.Initialize(InitializationEngine context) +5
   EPiServer.Framework.Initialization.InitializationEngine.InitializeModules() +338
   EPiServer.Framework.Initialization.InitializationEngine.Initialize(HostType hostType) +83
   EPiServer.Framework.Initialization.InitializationModule.Initialize(HostType hostType) +158
   EPiServer.Framework.Initialization.InitializationModule.FrameworkInitialization(HostType hostType) +62
   EPiServer.Global..ctor() +54
   EPiServer.Templates.Global..ctor() +4

And yes, our site runs in a .NET 4 application pool.

#69934
Apr 09, 2013 23:07
Vote:
 

That's a little odd. The episerver.common config section is registered and exists in web.config, doesn't it?

#69946
Apr 10, 2013 9:08
Vote:
 

Now it's very close. :)
The one thing that now is a problem is that our site wants to reference two different versions of the same file. We have a reference to Microsoft.Practices.EnterpriseLibrary.Data (ver 5. 0) and EPi Mail (Common Data) seams to have a reference to an old version (2.0) of the same file. Of course the bin-folder only can have one of this. But what's the way to solve this issue? Any suggestions?

#69963
Apr 10, 2013 10:48
Vote:
 

Is it possible to put at least one of the version in the GAC?

#69967
Apr 10, 2013 11:02
This thread is locked and should be used for reference only. Please use the Legacy add-ons forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.