Tuxedo Services won't start.
Jason Jonas
Ravi,
If you're still having problems, try this:
Ensure the TUXIPC service is started. Go to Start->Settings->Control
Panel->Services and check it. This process provides IPC resources to
Tux on the NT platform and tlisten will not start if this process is
not started.
Next, try starting the tlisten process from the command line using the
following command:
start tlisten -l //localhost:3050
Check the ULOG file for a message like:
INFO: Listener Process Started
If you see the following in the ULOG:
ERROR: Could not establish listening endpoint //localhost:3050
Then another process is listening on that port. Try a different port.
Once you find an available port, you can config a new listener process
at that port by clicking on start->settings->control panel->bea
tuxedo->listener tab. You will have to remove the old one and then add
a new one using the port you've identified.
Hope that helps.
Jason
ChandraS
Dear all,
I found the solution already. Seem that the Tuxedo 6.3 is not compatible
with NT SP5, then I use SP4 and finally there's no such errors again.
Thanks alots for all your help.
Regards,
Chandra
Ravi Pinto <ravi...@my-deja.com> wrote in message
news:7pue3q$8vt$1...@news.beasys.com...
>
> In article <7prviu$hhq$1...@news.beasys.com>,
> "Chandra" <Chandr...@yahoo.com> wrote:
> >
> > Hi all,
>
> Hi Chandra,
>
> > Does anyone use Tuxedo before? I install Tuxedo 6.3 on my NT box,
> after
> > finishing the installation, the Tuxedo Services (port 3050) won't
> start. I
> > am curious that this port has been using by another NT application.
> Does
> > anybody know how to handle it/ has this experience?
> >
>
> Though, I have not worked on Tuxedo on NT per se, here are a couple
> of things you could try.
> 1. Check the output of netstat -an from a MS-DOS prompt windows and
> check the listing before starting up tuxedo service. If you see port
> 3050 already listed, then some process is using this port and you would
> need to assign a different port to Tuxedo.
> 2. You could check up Tuxedo logfile named as ULOG.MMDDYY. This file
> should point to the error message. In case, you want help making sense
> out of it, you could post relevant portion to the newsgroup and we will
> help you out.
>
> > I am get frustrated that if this doesn't solved, I will have to
> scracth the
> > whole machine.
> >
> > Thanks in advance,
> > CHandra
> >
> >
>
>
> --
> Ravi Pinto, Bombay, India.
> mailto:ravi...@my-dejanews.com
> UNIX -- C -- Informix -- Tuxedo
>
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>