Could you post your episerverframework.config file? Did you change anything in web.config?

Frederik

Hi Frederik,

thanks for your fast replay (:

No, there isn't any difference between EpiserverFramework.config in the "Alloy" site and in our  "migrated" site. All configs are the same.

Lets explain what we did, because my previous explanation is not very clear :

1) created new alloy with commerce (runs)

2) copy alloy in the same dir and rename it

3) update the site path in IIS from Alloy to the "migrated" site. Change the name of the domain

4) remove all Alloy's controllers, views, models, viewmodels

5) change the assemply's name and namespace

6) add our lib and the old controllers, views, models, ...

7) change the Alloy CMS' database with a fresh CMS database and change the connection string.

except connectionstrings all other config files are the same

Is it possible to be a problem with VPP or other path? Is it problem that now the root dir of the site is renamed?

Yes, most likely the problem is the appData path. Is the path correct? You could try explicitly specifying it, example: C:\EPiServer\VPP\AppDataAlloy.

Frederik

On second thought, even if the appData path is wrong, you should still see the util/login.aspx page since this is located under Program Files.

Do you have this in episerverframework.config:

<add virtualPath="~/Util/" physicalPath="C:\Program Files (x86)\EPiServer\CMS\7.0.586.1\application\util"
      name="UtilFiles" type="EPiServer.Web.Hosting.VirtualPathNonUnifiedProvider, EPiServer.Framework" />

And this in web.config:

<location path="util">
    <system.web>
      <pages enableEventValidation="true">
        <controls>
          <add tagPrefix="EPiServerUI" namespace="EPiServer.UI.WebControls" assembly="EPiServer.UI" />
          <add tagPrefix="EPiServerScript" namespace="EPiServer.ClientScript.WebControls" assembly="EPiServer" />
        </controls>
      </pages>
      <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
    </system.web>
    <system.webServer>
      <handlers>
        <clear />
        <add name="AssemblyResourceLoader-Integrated-4.0" path="WebResource.axd" verb="GET,DEBUG" type="System.Web.Handlers.AssemblyResourceLoader" preCondition="integratedMode,runtimeVersionv4.0" />
        <add name="PageHandlerFactory-Integrated-4.0" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.PageHandlerFactory" preCondition="integratedMode,runtimeVersionv4.0" />
        <add name="SimpleHandlerFactory-Integrated-4.0" path="*.ashx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.SimpleHandlerFactory" preCondition="integratedMode,runtimeVersionv4.0" />
        <add name="WebServiceHandlerFactory-Integrated-4.0" path="*.asmx" verb="GET,HEAD,POST,DEBUG" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" preCondition="integratedMode,runtimeVersionv4.0" />
        <add name="wildcard" path="*" verb="*" type="EPiServer.Web.StaticFileHandler, EPiServer.Framework" />
      </handlers>
    </system.webServer>
  </location>

You have probably solved this a long time ago but I ran into the same issue today in a EPiServer 7.5 project. It turned out I was missing the modulesbin folder (with the needed EPiServer dll files).

Check if your login.aspx is in this location C:\Program Files (x86)\EPiServer\CMS\6.1.379.0\Application\Util\login.aspx

OR

in this location C:\Program Files\EPiServer\CMS\6.1.379.0\Application\Util\login.aspx.

Wherever it is, make sure your episerver.config is pointed to that location.

That was the issue with me.