Groups | Blog | Home
all groups > sql server reporting services > march 2005 >

sql server reporting services : Windows 2003 IIS & Error Installing of Reporting Services (IIS)


Eric S.
3/8/2005 4:23:08 PM
I am running a Windows 2003 Enterprise server with IIS installed, and I have
created a default website on it at port 80.

I have followed all the preq requirements. (IIS, ASP.NET, Framework 1.1,
etc.)

However everytime I try to install the reporting services, I receive the
following error message:
----------
Internet Information Services 5.0 (IIS) or later is not installed, or it is
configured in a way that is incompatible with a Reporting Services
Installation.
----------

Can anyone shed some light on this?

Regards,

Eric S.
Ravi R
3/8/2005 4:39:54 PM
I am not sure what exactly is the problem, but may be the following.

did u configure the win2k3 as an Application Server ? You need that for
RS.
I think the default role when u install Win2k3 is of a File Server.

Ravi
Eric S.
3/8/2005 4:53:03 PM
Yes I do have it setup as an "Application Server" under the "Manage you
Server" within the Control Panel, and I did verify that I do have the
"Application Server" component checked under Windows Components.

Very frustrating.

Eric S.

[quoted text, click to view]
Eric S.
3/8/2005 5:29:03 PM
Reference
http://www.visualjason.net/PermaLink.aspx?guid=ad8689ce-83e9-4f6c-aaa8-6fc712689ec1

--------------------------------

Well, it looks like my Default web site had somehow been re-created with a
new identifier (not the 1 that RS was expecting). I don't think there is a
way to create a web site with a specific identifier (especially 1), so I took
a lower-level approach.

Now, I wouldn't recommend this in a production environment, but since this
is a test server, I opened up the metabase.xml file and did a global search
and replace to replace the Default web site's identifier with 1.

---------------------------------

That fixed the issue for me.

Regards,

Eric S.

[quoted text, click to view]
Lance
3/10/2005 8:21:48 AM
FYI: I ran into this exact problem last week, but I still had various
sercurity-related problems after doing the same metabase hack (rename
to '/LM/W3SVC/1/') and had to remove Sql Reporting and IIS, then
reinstall from scratch.

What a pain! I dont see any way to override the Website identifier,
and don't see any legitimate reason to restrict it to a certain web
instance. Especially when in the "real world" its possible and often
preferable to have a web farm that serves-up several sites so that you
can share the hardware resources without dedicating it to a single
purpose such as Sql Reporting.

I guess this is my question in all this is ranting; Does anyone know of
a way, during or after setup, to override this behavior and install to
a different website instance?

Thank you,

~Lance
http://weblogs.asp.net/lhunt/
Tim Coker
4/15/2005 10:08:04 AM
An easier way to change site identifiers is:

cscript adsutil.vbs move w3svc/<id of site to be moved> w3svc/1

adsutil.vbs is in the adminscripts folder of your inetpub

Hope this helps someone else.
Tim C

[quoted text, click to view]
AddThis Social Bookmark Button