Is IIS required?
-
I was told IIS is required to be installed on a cluster in order to install SQL 2005. Is this true? The cluster is not going to have reporting services installed.
Thanks...JC III
-
IIS is not required. Some Web-related features may not be installed if IIS is not installed, but if you are planning this server only as a database server, it is fine.
Regards,Yelena Varsha
-
Thanks for the info. Strange that our so called "SLQ 2005 expert" would say it was required for the installation. What about if it's being installed on a cluster (i.e. CI\Instance_name)?
Sorry to beat this subject so hard but the person is adamant it is required but has not indicated why.
Other than reporting services, are there any other web related services that get installed during the SQL2005 installation?
Thanks again....JC III
-
It is my understanding the Reporting Services is the only component of SQL Server 2005 that requires IIS.
I have installed SQL Server 2005 on several production and develpment servers and SSRS is only installed on one server with IIS. IIS is not installed on any of the other systems and they are running fine.
-
if you don't have IIS it will flash a warning before installation. that is probably what he meant
-
I know during the preliminary check SQL will indicate that it did not detect IIS and that some services will not be available but I'm being told IIS is required to be installed in order to perform the installation.
-
No. It is not. I have installed SQL Server 2005 on several servers that do not have IIS installed.
-
I know the cluster with 2005 where IIS is not installed.
I normally too tell that IIS is a prerequisite because I don't want to do additional installations later. I ask a person to think if he or she will ever need IIS or Reporting Services before I install. Because if you install later, then you have to re-apply OS patches and Service Packs and SQL Server Service Packs and all updates on the top of it.
Regards,Yelena Varsha
-
We have some SQL Servers at a web-hosting site and they all require IIS for the hosting company's maintenance tools. IIS is not required for SQL Server, but perhaps there is some other infrastructure constraint in your environment that requires it.
Or maybe your expert is running his own hosting company on the side
-
Thanks for all the replies.
The "expert" indicated he had IIS installed because it makes for a "Clean install". Meaning an install with no errors, even informational ones. Hard to imagine expending all those resources (we have to remove it too) just so your install log does not show any errors.
Thanks again...
-
I have a question regarding IIS but it's not quite related to the current discussion. I had Reporting Services ran fine until .NET Framework 1.1 was installed. After this Framework was installed, any file with .aspx, .asp, extension cannot be executed. When I enter http://localhost/reports/home.aspx into the URL, I got the error message:
The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.
Please try the following:
- Open the localhost home page, and then look for links to the information you want.
- Click the
Refresh button, or try again later. - Click
Search to look for information on the Internet. - You can also see a list of related sites.
HTTP 500 - Internal server error
Internet Explorer
Any file with .htm, .html, extension is still ok. I don't know why this .NET Framework 1.1 installation caused this problem. Does anybody have this problem before?
Can anybody help?
Thanks!
-
Tell the "expert" it is a security risk to install services that are not going to be used. That is why Microsoft made it optional to install or not.
-
If you installed SQL 2005 on to a W2003 server, .Net 1.1 is already there. The SQL 2005 install will install .Net 2.0 if it is not already on the box.
I have seen some postings about issues where .Net gets broken if you force a .Net 1.1 install on a box that already has .Net 2.0 or above. Google should help you find these, and if there is a workround other than re-installing the OS.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
-
The fact is that after I installed Win2k3 server, .Net Framework 1.1 was not there. I agree that .Net FW 2.0 was installed from SQL 2005 installation. I had to install .net FW 1.1 separately because one application required it even though the server already got FW 2.0 and 3.0. It sounds ridiculous but it's true.
I got the feelings that .net got broken after I installed FW 1.1 on a system that already had FW 2.0. If you could include some links to the workaround solution to this issue, that would be appreciated.
Thanks!
-
In IIS Manager go to your website properties and click on ASP.NET tab. Make sure the correct version is selected in "ASP.NET Version" Then go to the Documents tab and make sure the correct files names and extensions are added to the list user "Enable Default Document"
Also do the following according to my old records:
"......you need to do the following to enable ASP.NET (maybe you have already done it) - Install IIS - In the IIS Manager click on Web Server Extension node on the left, and see what is allowed on the right: ASP.NET and Active Server Pages should be allowed and click Allow button if you need to enable additional things like WebDav or Internet Database Connector - In the command prompt run the following to enable Web Projects from Visual Studio: Change directory to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322 (or whatever Framework version you have, it will be 2.0 after SQL 2005 install) Run: aspnet_regiis -i -enable
Regards,Yelena Varsha
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply