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; } } }

TeamSite 7.1 installation issue

Balaji03

Hi,

We have installed TeamSite 7.1 on a Windows 2003 Server. We were able to successfully install TeamSite module and we did not get any error message during installation. But, when we try to access the URL as http://localhost:9080, we are not getting the login page of TeamSite. We found an error message in servletd_out.log, which says "SEVERE: Could not connect to broker URL: tcp://localhost:3035. Reason: java.net.ConnectException: Connection refused". I have attached the servlet log output.

Regards,
Balaji.

Find more posts tagged with

Comments

ReggieRWalker

Hi,

We have installed TeamSite 7.1 on a Windows 2003 Server. We were able to successfully install TeamSite module and we did not get any error message during installation. But, when we try to access the URL as http://localhost:9080, we are not getting the login page of TeamSite. We found an error message in servletd_out.log, which says "SEVERE: Could not connect to broker URL: tcp://localhost:3035. Reason: java.net.ConnectException: Connection refused". I have attached the servlet log output.

Regards,
Balaji.

Balaji - This isn't, by chance, a 64-bit server, is it?

Rick Poulin

1) Why are you accessing TS on port 9080? That's the Admin console only. You should be going to port 80.
2) While the (graphical) installer did not report errors, that doesn't mean none occurred. I don't recall the exact path, but there should be a X:\iwinstall folder containing installer logs on whichever drive you installed to.
3) The service that runs on port 3035 is the event subsystem. You'll probably want to check the config for that (in iw-home/eventsubsys) and the relevant logs to see why that service is unhappy.

maddy

is 64 bit server supported platform for installing TeamSite 7.1?

cute_guy

Balaji - This isn't, by chance, a 64-bit server, is it?

Hi Reggie,

Yes, this is a 64-bit server.

ReggieRWalker

Hi Reggie,

Yes, this is a 64-bit server.

7.1 is not supported on 64-bit yet. We had the exact same issue. Once we re-imaged the VMs to 32-bit version, the install was successful. This is what I got back from Support on supported versions:

As you've noted already, we don't currently have support for 64 bit OS
on Windows in TS. Here's what we have so far for support on TeamSite v
7.1:

Windows 2003 Server R2, Enterprise Edition, 32-bit,
Windows 2003 Server SP2, Enterprise Edition, 32-bit,
Windows 2008 Server, Enterprise Edition, 32-bit,

It is noted though that you can use these 32bit OS's on the 64bit
hardware so you're ready when the 64bit OSs are support.

We start support for the 64 bit OS in OD but only for Windows 2008.
Here's what Windows OS's are supported in OD 7.1:

Windows 2000 (SP2 or later)
Windows 2003, Enterprise Edition, 32-bit (on x86 or x86-64 hardware)
Windows 2003 Server SP1, Enterprise Edition, 32-bit (on x86 or x86-64
hardware)
Windows 2003 Server SP2, Enterprise Edition, 32-bit (on x86 or x86-64
hardware)
Windows 2003 Server R2, Enterprise Edition, 32-bit (on x86 or x86-64
hardware)
Windows 2008 Enterprise Edition, 32-bit (on x86 or x86-64 hardware)
Windows 2008 Enterprise Edition, 64-bit (x86-64 hardware)

On LiveSite 7.1 were support the following:

Windows 2003 SP1 and SP2 32-bit (on x86 and x86-64 systems),
Windows 2008 32-bit (x86 and x86-64 systems)

I'm still trying to confirm if there have been any changes to this
support under our recently release 7.2 products (though most likely not
as dot releases are normally fixes and minimal enhancements note major
changes).

So I believe in listing what's supported I've also answered your
question about what can you use in the Windows 2003 side of the house.

As always, Eng is doing there best to work at including other versions
of OS's in future releases but it's to early to get a firm answer on
WHEN the 64 bit OS's will come into play here. Until it's completely
tested and certified to work, they won't release any info on it.

HTH