Re: Problem with INet/PC 5.01
Posted in 1995
Topics: Installation, Setup & Upgrades, Connectivity: ODBC / JDBC / .NET, Networking & sqlhosts Configuration
Richard Spitz (spitz@GANS1X.ana.med.uni-muenchen.de) wrote: : Dear Informixers, : after installing INET/PC 5.01 WE1 on my PC (Windows f. Workgroups 3.11, : MS-TCP/IP32), I get the following problem: : When I try to connect to the Online database on the UNIX host from : Q+E Database Editor 5.0.3 (the only Informix-aware application I am : running), I get the error message "Cannot open file crhrep2.iem". : I cannot find this file anywhere on my PC, and it is also not on other : PCs in my workgroup that are running this configuration successfully. : When I just copied another ".iem"-file into "crhrep2.iem", I got the : error message "Unknown error 24532". : I am completely lost. Can anybody help me please? : Regards, Richard : -- : +----------------------------+-------------------------------------------+ : | Dr. Richard Spitz | INTERNET: spitz@ana.med.uni-muenchen.de | : | EDV-Gruppe Anaesthesie | Tel : +49-89-7095-3421 | : | Klinikum Grosshadern | FAX : +49-89-7095-8886 | : | 81366 Munich, Germany | | : +----------------------------+-------------------------------------------+ Hi there, We faced the same problem when trying to install I-NET 5.01 /Windows with Q+E ODBC for the first time. The solution as always was walking around since this error messg should've been interpreted as "Transport DLL not found" or staff like that. Proven for SunSelect PC-NFS, Wollongong PathWay TCP/IP transports yet for Win 3.1 it required to make two entries in %WINDIR%\\infromix.ini's [INET_CONNECTION] and [INET_PROTOCOL] sections coinside. Here you are the meaningful portion of tuned informix.ini file. [INET_CONNECTION] host=donkey user=informix protocol=tcp-ip <<<<<<<<<<<<<< !!! <<<<<<<<<<<<<< Service=donkey_infmx Passwd= [INET_PROTOCOL] tcp-ip=INETWSOK.DLL <<<<<<<<<<<<<< !!! <<<<<<<<<<<<<< ipx=INETIPX.DLL [ENVIRONMENT] .. You can achieve this as well via INFORMIX Logon Box -> [Options] -> ProtocolType => tcp-ip (not anything else!). Alternatively you can ensure that your Informix-NET <-> WinSock 1.1 interface is OK under WFW 3.11. See I-NET's README for instance. BTW ... the hint came to us from Munich, Informix Germany Tech Supp. Hope this might be of help, Gregory Barron, Jet InfoSystems