nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TS 7.2 Installation Issue

drewwarren

I'm having an issue with Port 80 being busy during a 7.2 install on the TeamSite Web Ports configuration screen. IIS is installed on the server and running. The server is also built as a virtual machine on VMWare and I am using RDP to connect to it. Does anyone know what to do to get beyond this step?

Find more posts tagged with

Comments

msrinivas

Stop IIS or configure it to use port 81 and then run the installer.

HTH

Adam Stoller

Stop IIS or configure it to use port 81 and then run the installer.

HTH

TS installation used to do this for you (if you selected the option to configure IIS) - does it no longer do this for the 7.2 installer?

It's trivial enough to do manually before running the installer, but it was convenient to have it done automatically...

msrinivas

On Win 2008 I had similar issues. The installer was not able to create the TSIMP_xxxx id and had issues with configuring IIS. I eventually gave up and used Apache as preview web server and disabled IIS. Windows 2008 has some crazy security settings and you almost need to be a certified sys admin to know all of it.

filter between tables.png

2 table same DS1.rptdesign

database.csv.txt

Rick Poulin

Drew,

I agree with previous posts -- you'll probably have to resort to configuring IIS manually.

For the record though, could you please provide your environment details, so that if people run into the same issue in the future they can see if their circumstances are different. Specifically, Windows and IIS versions would be useful.

drewwarren

I'm running Windows 2008 R2 with IIS 7. However it seems even though I had selected to stop IIS in a previous install screen and to have it configure IIS automatically, it did not seem to be stopping IIS before the current install screen that I am having issues on. I went and manually stopped IIS as per previous post and I can now advance through install.

Thanks for the help.

OS_BIRT_4.2.2_TopDateAsDefault_v2.rptdesign

Adam Stoller

I'm running Windows 2008 R2 with IIS 7.

I haven't looked through the manuals, but I don't recall there ever being an announcement that TeamSite works with IIS7 - it is quite possible that the method the installer used for configuring IIS6 may not work with IIS7. You might want to double-check the manuals and/or with Support about that.

Shivangi Malot

The release notes say Teamsite 7.2 compatible with IIS 7 for preview

but our Teamsite7.2 Installation is failing

with following error at 'final configurations' process
"The install process was un sucessful

com.interwoven.wcmservice.iwovregistry.common.ConfigException:IR Service not up. "

We are doing installation on
Windows 2008 R2 64 Bit
IIS 7
MS SQL Server 2008 database.

Initially IIS did not stop automatically, but this post helped and we stopped IIS manually.

krice

I had the same issue with port 80 being busy on a Windows 2008 server. I ended up setting the install port to 800, doing a manual IIS config and then changing the port to 80 afterwards. The only issue I have now is, I can access 7.2 from the server however I cannot access it from my desktop (yet I can access 81, 8080, etc).

Rick Poulin

What do you mean by "can't access"? I'm guessing you get prompted for credentials... which implies that you didn't properly configure anonymous access in the directory security piece. If you get no response at all, then it could be a firewall thing on your network (most likely), or IIS has been configured to ignore incoming connections from anything but localhost (less likely).

Frederik

i suspect the port you provided during install gets stored in a number of config files... you may need to figure out where, and correct it (800 -> 80).

Sorry, this is just from the top of my head though.

on the main issue:
We did a TS 7.2 install on Win2003 and the installer stopped and reconfigured the IIS just fine. I did notice that it quietly assumes that there are some IIS admin scripts under a specific/default folder (C:\Inetpub\AdminScripts), and if those aren't there, it won't report the failure on the Setup GUI. (only in the installer.log)

krice

Actually regardless what the port is, I cannot access it outside of the local server (ie, RDP into server and then http://servername Smiley Tongue

ort/) locally it works perfect, outside of that its a no, go... however if I try http://servername:81 (IIS) it gets there fine.

nraval

We had same issue to access Teamsite other than local machine

we modified iwwebd.conf.template located in the E:\Interwoven\TeamSite\iw-webd\conf directory

We searched for the word listen and modified the statement Listen 80 to Listen **.***.**.***:80 ( server IP Address). We ran the command iwreset –a, and immediately able to connect to the site from our desks.

Regarding IIS 7 access you might need some firewall rule to open port 80

krice

Thanks nraval that worked like a champ, I appreciate the suggestion!

Shivangi Malot

I am facing following issue with
Teamsite 7.2 installation on Windows 2008 64 bit Server

Not able to load http://servername:80/iw-cc
Getting http 404 error

Please Suggest

---
- Teamsite was Sucessfully installed
- Able to access Jboss server http://dlumlnts72:8080/web-console
- IIS is running on port 81
- All Services including Web Deamon are starting
- Modified iwwebd_conf.template file to point to **.***.***.***:80 (server IP)

Rick Poulin

If you remote desktop to the box, can you hit http://localhost:80 ?

Yes: Firewall or DNS issue -- talk to your network admins
No: Apache config issue (post the contents of your iwwebd.conf)

Shivangi Malot

i hv taken a remote desktop connection to server machine
Still I cannot hit http://localhost:80
it gives http 404 error

attached is iwwebd.conf file.

Also, when i do a iwreset -a, it opens the iwwebd_conf.ipl file and services do not start untill i manually close this.

Rick Poulin

Just to confirm, the 404 error you're seeing is an Apache 404 and not an IIS 404 right? (you can tell by the styling of it, unless you're using IE and have the "friendly error messages" enabled.)

I see nothing obvious in your config, assuming that the IP of your TS server is 10.207.248.133. Remember that the /iw-cc resource is passed through to that webapp in JBoss (C:\Interwoven\ApplicationContainer/server/default/deploy/iw-cc.war/ in your install) so next, I'd check to make sure JBoss in running (in your install, on port 8080) and that you can access that directly.

nested tables.rptdesign

Shivangi Malot

i can access Jboss on http://10.207.248.133:8080
10.207.248.133 is the server ip
i can see iw-cc.war deployed in application container using jboss web console http://10.207.248.133:8080/web-console

the error seems to be coming from jboss- JbossWeb/2.0.1.GA

Rick Poulin

OK so it sounds like
http://10.207.248.133:8080/iw-cc/command/iw.ui
will throw that same 404. In which case, iw-cc wasn't properly deployed or there's something off in the server.xml for JBoss. You might want to try running install_webapps.ipl to fix this.

If that URL returns the right page, then we're back to something misconfigured with iwwebd.

nraval

i hv taken a remote desktop connection to server machine
Still I cannot hit http://localhost:80
it gives http 404 error

attached is iwwebd.conf file.

Also, when i do a iwreset -a, it opens the iwwebd_conf.ipl file and services do not start untill i manually close this.

Run iwreset -a in CMD opened in Administrator account

you can right click on CMD.EXE link and Run As administrator

and may be your *.ipl not configured to run with iwperl

TestXML.rptdesign

Shivangi Malot

Thanks Rick,

after running install_webapps.ipl the http 404 error went off and i am able to access Teamsite using http://10.207.248.133/iw-cc

But now the above link is not accessible outside CMS server. it gives a session time out error after trying to load it for 2-3 mins

I have modified the iwwebd.conf.template file to make it Listen to 10.207.248.133:80 port , also tried by making Listen to 0.0.0.0:80
There is no firewall configured on the server.

Plz suggest.

Thanks nraval,

The perl file is now getting executed directly after i include the iw-home/iw-perl/bin path into PATH environment variable

Rick Poulin

But now the above link is not accessible outside CMS server. it gives a session time out error after trying to load it for 2-3 mins

Try the same type of thing from your remote box. If http://10.207.248.133:8080/iw-cc works, then it's Apache ignoring requests from the outside. If that doesn't work, there might be something else on your network preventing access... you might have a NAT set to disallow access over port 80 (though that would be odd). You should confirm with your network guys that there's nothing between you and the server that's preventing access over port 80.