Discussion Forum for StarTeam Users


Re: stcmd - error: Bad packet


[ Follow Ups ] [ Post Followup ] [ Discussion Forum for StarTeam Users]

Posted by Mark Juras on October 21, 2000 at 21:20:54:

In Reply to: Re: stcmd - error: Bad packet posted by Steven L on October 18, 2000 at 16:46:47:

: : When trying to use stcmd against a StarTeam 4.2 Server,
: : the client exits with the following:
: : Error Occured:
: : Bad Packet

: : And nothing else. This can mean a number of
: : things, but what kind of behaviour
: : causes stcmd to respond like this?
: : I have been searching for a troubleshooting
: : guide for StarTeam, but I have been unable
: : to locate one.

: This error occurs usually when the endpoint specified in the -p switch is not pointing to a TCP/IP SOCKETS protocol, but rather TCP/IP RPC. By default, a StarTeam server runs with the following ports:
: TCP/IP (RPC) - 49200
: TCP/IP (Sockets) - 49201

: In this case, if your stcmd command is trying to connect to port 49200, you will get the 'bad packet' error.

: Sockets is the only supported protocol for the StarTeam command line interface.

OK. Where is the comprehensive troubleshooting guide, or at least an informative list of StarTeam error Messages and their meanings /resolutions. (I wish!)


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

Comments:


[ Follow Ups ] [ Post Followup ] [ Discussion Forum for StarTeam Users]