Cannot install | Episerver Developer Community

Cannot install

Member since: 2007
 

Upgraded our R1 SP3 site using EPiServer Mail 4.3 to R2 and are now trying to install EPiServer Mail 4.4 without any luck. When I get to the first step to choose a site there are no sites to select from. The text is a little confusing as it states to select an EpiServer Mail application.

According to the installation instruction there doesn't seem to be any prerequisits to be performed to be able to install it on the site. What seems to be the problem?

#30808 Jun 23, 2009 9:10
  •  

    Sorry for the confusion, EPiServer Mail requires an EPiServer CMS site to install and as there is no upgrade between 4.3 and 4.4 (migration required) sites with 4.3 are also disqualified during installation.

    See http://world.episerver.com/en/Download/Categories/Version-Relations/EPiServer-CMS-5-Relations/ for details on the compatible CMS versions and http://world.episerver.com/en/Articles/Items/Migrating-StarCommunity-31-to-EPiServer-Community-32/ for how to migrate.

    #30813 Jun 23, 2009 10:17
  • Member since: 2007
     

    If I understand this correctly... I have to install a new site on our server and on this install EPiServer Mail 4.4 and then move our live site consisting of thousands of pages and all the VPP files to the new site to be able to get EPiServer Mail to work?

    If that is the case, how do I perform this the easiest way? What about licensing violation during twosite installation?

    #30825 Jun 23, 2009 14:03
  • Member since: 2007
     
    I also recieve a lot of error messages from StarSuite in the Event viewer after upgrade (Object Reference not set as an instance of an object). How do I get rid of those?
    #30828 Edited, Jun 23, 2009 14:15
  •  

    Well, you don't necessarily need to move all your content to a new site.

     

    What you absolutely do need during the migration is to have two separate databases, one with the 4.3 structure and one with the 4.4 structure.

    Is EPiServer Mail 4.3 in a separate database from CMS?

    If that is the case you may just want to temporarily remove the <EPiUI>/Mail, bin/EPiServer.Mail.*, bin/StarSuite.* files, install 4.4 onto the site, using a new DB, and then run the migration script from the 4.3 to the 4.4 database to get your Mail content into the 4.4 installation.

    If Mail and CMS are sharing DB, you would probably want to also restore a backup of this database, remove the StarSuite and Mail related tables and stored procedures before installing 4.4, that way you can install 4.4 into this shared database (and then migrate the 4.3 data as mentioned above).

    I hope this explanation made sense.

     

    Regarding the StarSuite error messages, I can't really tell what is wrong without knowing the actual message, but there's a significant chance that these messages will go away after migrating to the new version anyway, so it may not be worth it putting too much energy into that issue before seeing if that is the case.

     

    #30829 Jun 23, 2009 14:54
  • Member since: 2008
     

    There is also a EPiServer Mail 4.3 - 4.4 upgrade instruction in the Create+ upgrade instructions - look under the documention section for the document.

     

     

     

     

    #30832 Jun 23, 2009 16:58
  • Member since: 2007
     
    Yes, all works after a bit of tweaking. The one thing that took the most time to figure out was the placement of the staticfile handlers towards the other handlers that gave a nice confusing errormessage. Thanks alot for yur help
    #30833 Jun 23, 2009 18:07
  • Member since: 2007
     

    Darn, called 'hej' too soon. After installing EPiServer Mail there were added two membership providers in web.config:

    EPiServerCommonMembershipProvider & EPiServerCommonIntegrationMembershipProvider

    However since we use a custom membership provider for some of our users we use the multiplexing provider. And here it gets weird:

    Case 1: Using the EPiServerCommonIntegrationMembershipProvider
    This has a provider property that points towards MultiplexingMembershipProvider which is the new one as stated in the Hot Fix 1 - EPiServer Common. This multiplexing provider has two providers: SqlServerMembershipProvider and our own custom membership provider.
    Result: Our custom membership provider works but if I as admin or anyone else that is set up in the SqlServerMemebrshipProvider recieve an error message:

    Invalid use of read only object - Clone() it before making modifications.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: EPiServer.Common.Exceptions.FrameworkException: Invalid use of read only object - Clone() it before making modifications.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [FrameworkException: Invalid use of read only object - Clone() it before making modifications.]    
    EPiServer.Common.EntityValidator.ValidateIsNotReadOnly(ICloneable cloneable) +66 
    EPiServer.Common.Data.FrameworkFactoryBase.UpdateEntity(IFrameworkEntity entity, Int32 id, Boolean add) +78
    EPiServer.Common.Data.FrameworkFactoryBase.UpdateEntity(IFrameworkEntity entity) +37
    EPiServer.Common.Security.Internal.SecurityHandler.SecurityHandler_UpdatedUser(ISecurityHandler sender, IUpdateUserEventArgs args) +77
    EPiServer.Common.Security.SecurityHandler.OnUpdateUser(IUpdateUserEventArgs args) +22
    EPiServer.Common.Security.Internal.Data.SecurityFactory.UpdateUser(User user, SecurityHandler securityHandler) +1009
    EPiServer.Common.Security.Internal.SecurityHandler.UpdateUser(IUser user) +353 EPiServer.Common.Web.Authorization.Integrator.SynchronizeUser(MembershipUser membershipUser, String password, Boolean enableCreateNew) +1058 EPiServer.Common.Web.Authorization.Multiplexing.IntegrationMultiplexingMembershipProvider.ValidateUser(String username, String password) +79
    EPiServer.Common.Web.Authorization.IntegrationMembershipProvider.ValidateUser(String username, String password) +32
    System.Web.UI.WebControls.Login.AuthenticateUsingMembershipProvider(AuthenticateEventArgs e) +60
    System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +119
    System.Web.UI.WebControls.Login.AttemptLogin() +115
    System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +101
    System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +37
    System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +118
    System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +166
    System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
    System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
    System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565

    Case 2: Using the 'new' MultiplexingMembershipProvider
    Result: Site does not load: shows this:

    ClassFactory not initialized

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: EPiServer.BaseLibrary.ClassFactoryException: ClassFactory not initialized

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [ClassFactoryException: ClassFactory not initialized]    
    EPiServer.BaseLibrary.ClassFactory.get_Instance() +75
    EPiServer.BaseLibrary.ClassFactory.IsRegistered(Type baseType) +11
    EPiServer.CacheManager..cctor() +189 [TypeInitializationException: The type initializer for 'EPiServer.CacheManager' threw an exception.]
    EPiServer.Web.FriendlyUrlRewriteProvider.ConvertToInternal(UrlBuilder url, Object& internalObject) +357
    EPiServer.Web.UrlRewriteModule.HttpUrlRewriteToInternal(UrlBuilder url) +313 EPiServer.Web.UrlRewriteModuleBase.BeginRequestEventHandler(Object sender, EventArgs e) +158
    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
    [TypeInitializationException: The type initializer for 'EPiServer.DataAbstraction.UnifiedPathInfo' threw an exception.]
    EPiServer.DataAbstraction.UnifiedPathInfo.Load(String path) +338
    EPiServer.FileSystem.DefaultAccessControlList..ctor(String path) +65
    EPiServer.Web.Hosting.DirectoryAccessControl..ctor(String virtualPath) +28
    EPiServer.Web.Hosting.UnifiedDirectory.get_DirectoryAC() +176
    EPiServer.Web.Hosting.UnifiedDirectory.QueryAccess() +79
    EPiServer.Web.Hosting.UnifiedDirectory.QueryDistinctAccess(AccessLevel access) +17
    EPiServer.Web.Hosting.VirtualPathVersioningProvider.GetDirectory(String virtualPath) +177
    EPiServer.Web.Hosting.VirtualPathHandler.InitializeProviders(ProviderSettingsCollection providers) +399
    EPiServer.Web.InitializationModule.InitializeVirtualPathProviders(VirtualPathElement vpElement) +72
    EPiServer.Web.<>c__DisplayClass32.<Initialize>b__18() +22 EPiServer.Web.InitializeEngine.Initialize() +184
    EPiServer.Web.InitializationModule.Initialize(EPiServerSection config, Settings settings, ConnectionStringSettingsCollection connectionStringSettings) +1267
    EPiServer.Web.InitializationModule.<StaticInitialization>b__2() +34
    EPiServer.Web.InitializeEngine.Initialize() +184
    EPiServer.Web.InitializationModule.StaticInitialization() +737
    EPiServer.Web.InitializationModule.Application_BeginRequest(Object sender, EventArgs e) +310
    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

     

    Overall the site is extremely instabil all the time and changing one little thing can make the whole site to stop working. Does these error messages say anything on what the problem might be? One thing i noted was that during trying around different settings I got one message stating that it needed assembly from EPiServer R1 and checking my web.config there are alot of add assembly that refers to Version 5.1.422.4. Could this be something? Can I delete those or change version to 5.2.375.133?

    #30835 Edited, Jun 24, 2009 9:42
  •  

    Okay, can you just confirm that Common 2.3 Hotfix 1 is fully installed? (That is, at least the fixed EPiServer.Common.Web.Authorization.dll was installed, and optionally EPiServer.Common.Web.Authorization.Multiplexing.dll too?)

    And what does the membership provider / role provider sections look like?

     

    #30836 Jun 24, 2009 11:06
  • Member since: 2007
     

    Copied both the dll:s to the bin folder and changed the MultiplexingMembershipProvider to this

    <add name="MultiplexingMembershipProvider" type="EPiServer.Common.Web.Authorization.Multiplexing.IntegrationMultiplexingMembershipProvider, EPiServer.Common.Web.Authorization.Multiplexing" provider1="SqlServerMembershipProvider" provider2="ECIDMembershipProvider" roleToSynchronize1="*" />

    #30837 Jun 24, 2009 11:09
  •  
    Is the MultiplexingMembershipProvider the default membership provider? The stack trace suggests that another provider is used...?
    #30839 Jun 24, 2009 11:15
First   1 2   Last 
This thread is locked and should be used for reference only. Please use the Legacy add-ons forum to open new discussions.
Please login to post a reply