Re: Error 25591: Transport control received invalid connection ... seipcpip

Joerg Spilker <js@jetsys.de> wrote: >"Art S. Kagel" wrote: >> OOOPPSS, I did not notice this is SE! You must start a listener process: >> $INFORMIXDIR/lib/sqlexecd sqlexecd_se >> with the environment setup like a local shared memory client. > >sorry, i think you misunderstood my original message. Of course i've >started a listener process for the infse_net connection like you >explained above. Connecting with dbaccess to infse_net is not a problem. >What doesn't work is the local connection via named pipes (i think that >what seipcpip means). Connecting to infse_local gives me Error 25591. The seipcpip connection uses unnamed pipes, not named pipes. If you use the seipcpip protocol in the second column, the name in the fourth column of the sqlhosts file is the name of the program to be executed, either as an absolute name or as a name relative to $INFORMIXDIR/lib. In this case, it has nothing to do with anything in /etc/services whatsoever, and there are no uniqueness requirements either. Since the program to be executed is sqlexec, the fourth column in sqlhosts should read sqlexec unless you know enough about what you're doing not to be asking questions in the first place. You do not need to start any listener process to use seipcpip connections. You do not need any network connectivity to use it either (beyond, probably, a hostname that works). Yours, Jonathan Leffler (jleffler@informix.com) #include <disclaimer.h> Guardian of DBD::Informix v0.62 -- http://www.perl.com/CPAN "I don't suffer from insanity; I enjoy every minute of it!"