How are you using the same config files? Are you overwriting the files created by the deployment centre or amending them? If overwriting then try amending them instead, you may be removing some of the shell nodes.

Also, if possible compare the config files to see how they are different. I hope this helps,

Mark

Actually I have tried both ways & didn't help! I used deploymnet center & create a new website, the dashboard is working, as long as I modify it to have my website's settings, I get incorrectlink page.

/Maryam

Hmm, It still sounds like it might be config related. I know this is not very helpful, but have you tried changing the settings gradually until it stops working? This might narrow down which setting is causing the issue?

Mark

As long as I use the same config on my website I will get the incorrect link for episerver shell. I'm just guessing if there is any security issue related?

/Maryam

Check your web.config. It should contain location section for your EPiServer UI path:

<location path="YourEPiServerUIPath">
  ...

episerver.shell section should contain something like this:

  <episerver.shell>
    <publicModules rootPath="~/modules/" autoDiscovery="Minimal" />
    <protectedModules rootPath="~/YourEPiServerUIPath/">
      <add name="Shell" />
      <add name="CMS" />
    </protectedModules>
  </episerver.shell>

Also please check episerver.config file. Does it contain virtual path provider registration for EPiServer Shell? By default is looks like this:

<add name="EPiServerShell" virtualPath="~/YourEPiServerUIPath/Shell" physicalPath="C:\Program Files (x86)\EPiServer\Framework\6.2.267.1\Application\UI" type="EPiServer.Web.Hosting.VirtualPathNonUnifiedProvider,EPiServer" />

And one more question: do you have additional binding configured for EPiServer UI on your site?

For example public site is available on http://yoursiteurl/, but EPiServer UI url is http://yoursiteurl:secretPort/YourEPiServerUIPath/

As I have mentioned before there is no problem in the config files. I compared it with another blank EPiServer CMS 6 r2 v. There should be somethingelse that it's missing which I couldn't find it till now!

Hi Maryam,

Have you resolved this then? If so what was missing?

Mark

No, I couldn't find the solution yet!

/Maryam

Finally we found the solution to this... The old secureadmin folder (which used to be included in the project) was still in the solution, hindering the "real" shell from loading. Note to self: After migration, make sure all old EPiServer-related folders are removed!

Thx a lot. Had exactly the same problem