<div>
You just need to remove line 17 from the config file in the above screenshot. Most likely that line is already inherited from a parent config file, so it's being flagged as a duplicate.<br />
<br />
Remove the line or comment it out and it should fix the issue.
</div>


<div>
I took that line out and what I get is a directory listing for the actual web page rather than the website. &nbsp;See screenshot.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/03_w11/839540/IISerrorafterN-Wsadvice.jpg" target="_blank" title="IIS error after taking out the line to add an entry in default documents for login.asp (264 KB)"><img alt="IIS error after taking out the line to add an entry in default documents for login.asp" class="file-block lazyload" style="max-width: 742px;" data-src="https://filedb.experts-exchange.com/incoming/2014/03_w11/839540/IISerrorafterN-Wsadvice.jpg" /></a><br />
Next steps? &nbsp;Things I'm overlooking or doing wrong?
</div>


IIS error after taking out the line to add an entry in default documents for login.asp

IISerrorafterN-Wsadvice.jpg

<div>
Ok, so you may need to modify the default document for the website.<br />
<br />
1) Open IIS manager and click on the site you're trying to fix<br />
2) In Features View, double-click Default Document.<br />
3) In the Actions pane, click Add. Here you need to specify the first page that should be loaded when browsing your website (i.e. index.html, index.asp, etc.). Click OK when done.<br />
<br />
Now try to browse the website again and hopefully it will load the correct webpage.
</div>


<div>
I had already tried that, and while it does load a page similar to my last screenshot, it still isn't working correctly.<br />
<br />
I used the Microsoft IIS Web Deploy 3.5 tool to migrate the site from II6/Server 2003 to IIS7/Server 2008R2 and the site is in tact and all the files are in the same tree structure on the new hard drive as they were in the old server but still getting the same error. <br />
<br />
I've enabled parent paths and still can't access it.
</div>


<div>
Do you see your default page in the list in the screenshot above? If so, click on it and does the page load correctly?<br />
<br />
How is this particular website nested? Is it a virtual directory or application?<br />
<br />
Where is the applicable default document referenced? (i.e. in your default parent config located at &quot;%windir%\System32\inetsrv<wbr />\config\ap<wbr />plicationH<wbr />ost.config<wbr />&quot; or a child config)<br />
<br />
If possible, try removing the reference to your default document from parent levels and specify it locally at the child site.
</div>


<div>
I will get back to you with answers to your questions tomorrow or next week. &nbsp;Thanks for the help, and sorry for the delay.
</div>


<div>
After working out the previous error, I think I have the issue narrowed down to what is actually wrong. &nbsp;I'll post a screenshot and see if you have any idea on this one now.<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/03_w12/841129/newerror.png" target="_blank" title="providernotfound? (42 KB)"><img alt="providernotfound?" class="file-block lazyload" style="max-width: 789px;" data-src="https://filedb.experts-exchange.com/incoming/2014/03_w12/841129/newerror.png" /></a>
</div>


newerror.png

<div>
Looks like it's throwing an exception when trying to connect to a database.<br />
<br />
You may need to enable 32-bit applications in IIS:<br />

<div class="bullet">
In IIS Manager, select the IIS Server
</div>
<div class="bullet">
Actions -&gt; View Application Pools
</div>
<div class="bullet">
Select the application pool for your web site
</div>
<div class="bullet">
Under Edit Application Pool, click Advanced Settings
</div>
<div class="bullet">
Set Enable 32-bit Applications to True (default is False)
</div>
<br />
If that doesn't work, you'll need to post the lines of code that attempt to connect to the database.
</div>


<div>
Enabling 32-bit applications was already set before I made the original post; I verified this again though just to make sure and it is set right.<br />
<br />
Here are the lines of code that are attempting to connect to the database.<br />
<br />
<b>constConnectionString = &quot;Provider=SQLNCLI10;Server<wbr />=SERVERNAM<wbr />E.TEST.LOC<wbr />AL;User Id=sa;Password=password;Da<wbr />tabase=cor<wbr />rectdataba<wbr />sename&quot;</b><br />
<br />
Server 2008 R2 Standard for the OS
</div>


<div>
Have you installed the SQL Server Native Client on your web server? You'll need to have that installed before you can use the provider &quot;SQLNCLI10&quot;.<br />
<br />
Here's the download page for it: <a href="http://msdn.microsoft.com/en-us/sqlserver/ff658533" rel="ugc nofollow">http://msdn.microsoft.com/en-us/sqlserver/ff658533</a>
</div>


<div>
I don't think I've done that... your link takes me to a page that allows me to download the Native Client but it's bunched in with a lot of other downloads. &nbsp;Which one exactly am I looking for?
</div>


<div>
Also, do I still need the Native Client if the SQL server is a separate server from my web server?
</div>


<div>
I'll give it a try right now.
</div>


<div>
That did the trick. &nbsp;Thank you for persevering with me through this.
</div>


<div>
Installed SQL Server Native Client (64 bit) and was able to browse to my website.
</div>


<div>
<div class="content wysiwyg-content">
I have an old Server 2003 web server running IIS 6. &nbsp;I need to move this server and all of its applications to a new web server running Server 2008 R2 with IIS 7. &nbsp;I've already got the new server up and running with IIS 7 installed as well as all required features. &nbsp;I made the same drive (Letter E:) that the old server had for the actual storage housing the web server folders and literally copied and pasted all of the data onto this drive so the structure and web.configs as well as the configuration.asp pages are the same. &nbsp;However, I get the attached error (see screenshot) when I try to browse to this website from IIS 7 by name or by IP on the new server. &nbsp;Can anyone help me decipher this?<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2014/03_w11/839340/IISerror.jpg" target="_blank" title="IIS7HTTPError500.19 (129 KB)"><img alt="IIS7HTTPError500.19" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2014/03_w11/800_839340/IISerror.jpg" /></a>
</div>
</div>


IISerror.jpg

I have an old Server 2003 web server running IIS 6.  I need to move this server and all of its applications to a new web server running Server 2008 R2 with IIS 7.  I've already got the new server up and running with IIS 7 installed as well as all required features.  I made the same drive (Letter E:) that the old server had for the actual storage housing the web server folders and literally copied and pasted all of the data onto this drive so the structure and web.configs as well as the configuration.asp pages are the same.  However, I get the attached error (see screenshot) when I try to browse to this website from IIS 7 by name or by IP on the new server.  Can anyone help me decipher this?



IIS 7 - HTTP Error 500.19 (web server migration)

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.

Microsoft IIS Web Server

Active Server Pages (ASP) is Microsoft’s first server-side engine for dynamic web pages. ASP’s support of the Component Object Model (COM) enables it to access and use compiled libraries such as DLLs. It has been superseded by ASP.NET, but will be supported by Internet Information Services (IIS) through at least 2022.

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.