I have a page with a ReportViewer control that works on my development machine (vs2008) but not in IIS 6.0. What do I need to change in my web.config or in IIS 6.0 to fix it?
Install the Microsoft Report Viewer 2008 SP1 Redistributable on the new server.
Related
I upgraded my machine to windows 10 release 2.0 from Windows 7 and installed Visual Studio 2017 which I earlier used was VS 2012. My application is not working after setting up IIS 10.
Getting this below error:
HTTP Error 403.14 - Forbidden
The Web server is configured to not list the contents of this directory.
Is there something extra that needs to be configured for IIS 10?
From the asker in an edit to his question:
Running Visual Studio in admin mode solved the problem.
I have a VB.net app developed before 2010 with visual web developer express 2008. The app is running with IIS 7 (.NET framework 2.0) on MS server 2008. Without changing code in vb.net app, is there a way I can enable ssl with only configuration of IIS7? I can add https to IIS and generate my CA. I don't have visual studio and can not use VS for ssl.
I'm trying to run WCF Service based on 3.5 Framewor on Windows 8 with Visual Studio 2012 and IIS Express.
Service hosting fails with error "HTTP Error 404.17".
I'm trying with default Visual Studio WCF template setting framework 3.5.
Works fine if I select frameworks 4.0 or 4.5.
Is there a way to make 3.5 services works fine with IIS Express?
Http activation is enabled in Windows Features.
Tried install, re-install, remove and install Service Model via:
Framework64\v3.0\Windows Communication Foundation> .\ServiceModelReg.exe -i
Still not working.
Regards,
Dmitry
I have a ASP.NET web app (.NET 3.5 SP 1) compiled on a Windows XP x86 (32 bit) box. The app currently runs on a Windows 2003 (IIS 6) server. I'm planning to move the application to a Windows 2008 R2 (64 bit) server. I was wondering if anyone has had any experiences with a similar migration? Does a x86 ASP.NET web app work out-of-the-box on Windows 2008 R2 (IIS 7.5)?
Cheers :)
Rowan
You should be able to make the transition with minimal work. We did it before. We can talk offlist if you'd like, lemme know.
You shouldn't have too many problems - we build and develop on XP x86/IIS 5.1 and deploy to a 64-bit Server 2008/IIS 7 platform. Just make sure you've got a staging environment to test on (even if it's just a Windows 7 installation for IIS 7).
well, according to what I've found googling around, it's imposible... (maybe with with windows xp 64...)
but I thought that maybe someone could find a way to achieve it, or at least some workaround...
http://www.iisanswers.com/IISFAQ.htm
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.inetserver.iis&tid=14654991-875f-4cc6-a853-7e9f3bb96bc3&cat=en&lang=en&cr=&sloc=en-us&m=1&p=1
--
ps: I need to debug classic asp code, and my production environment is windows 2003, while my development machine is windows xp...
--
edit:
just to clarify, I can already debug classic asp code in iis 5 with vs 2003 and 2008, it's just that I stumbled upon a (very silly) bug that only appeared on iis 6 (when IIS 5 received and empty http status, it just assumed 200, while iis 6 kept asking for my credentials in an infinite loop, it was very silly in deed, but took me a lot of time -and cursing- to discover it)
IIS 6 cannot be installed on Win XP. However, debugging classic ASP code is possible on Windows XP / IIS 5.1 using Visual Studio 2003 and up. You will need to configure IIS 5.1 to "enable ASP server-side debugging" (disabled by default):
IIS settings http://www.freeimagehosting.net/uploads/f1a6f781b9.png
Here is a more detailed article on how to debug classic ASP pages in Visual Studio - link
(NOTE: When running on XP Pro/IIS 5, you need to attach to dllhost.exe instead of w3wp.exe)
You posting in your 2nd link is correct. And read the faq. That spells out why it can't be done.
One option you can do is have a virtual machine of Server 2003 running on your laptop.