Quantcast
Channel: All Forums
Viewing all articles
Browse latest Browse all 26858

help needed with IIS v8 website root directory

$
0
0

Hello guys,

I've been trying to redeploy my website from an old server ( IIS v6 on Windows Server 2003 standard x64) to a new server (IIS v8 in Windows Server 2012 standard x64).

I know what is causing the problem, but I can not find the solution. There is a configuration problem with the IIS version 8 on the new server. Either IIS or ASP.NET is treating the website root directory as C:\inetpub\wwwroot, whereas it should be C:\inetpub\wwwroot\jasperpublishing

because of this, IIS can not  locate the DLL’s which are normally in C:\inetpub\wwwroot\JasperPublishing\bin.

As a workaround and to try to progress further with the problem, I have created a copy of the DLL’s in the C:\inetpub\wwwroot\bin directory and some of the webpages are beginning to run ok.

However, this website has .aspx.cs code, components under the usercontrols_Products and similar directories, Images, PDF’s and Javascript which will not work properly unless IIS recognises the website root directory to be C:\inetpub\wwwroot\JasperPublishing and not C:\inetpub\wwwroot

<div> <div>The following is the section dealing with JasperPublishing in "C:\Windows\System32\inetsrv\config\applicationHost.config" The physical path mapping associated with the virtualDirectory appears to be correct.</div> <div>
</div> </div> <div><site name="JasperPublishing" id="4" serverAutoStart="true">
    <application path="/" applicationPool="JasperPublishing">
        <virtualDirectory path="/" physicalPath="C:\inetpub\wwwroot\JasperPublishing" />
    </application>
    <bindings>
        <binding protocol="http" bindingInformation="82.165.172.217:80:www.jasperpublishing.com" />
    </bindings>
</site></div>

Would be grateful for any help from the community, been battling this for 3 days ;(



Viewing all articles
Browse latest Browse all 26858

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>