Informix/NT Problem Initializing Security System

Does anyone have any recent or definitive guidance on this particular problem? I think many of us are having it in one form or another. The symptoms are this: I install IDS (7.22 Workgroup in my case) on a NT server system. It comes up okay. No unusual problems talking to it locally as informix (or whatever the magic Informix user is), and no unusual problems talking to it from other systems, Windows or UNIX. Performance pretty good. But if I try to connect to the server from a normal unprivileged user logged into the server system itself, it fails. If I try dbaccess, I immediately get "Unable to access the security system". If I try from other sources, I often get the -406 message, which has nothing to do with running out of memory. If I then give that normal user administrative privilege, the problem goes away. Take away administrative privilege and the problem comes back. Sort of decreases the chance that it's a problem with registry, or path, or setnet32, or services, or hosts.equiv. I thought it might be a .DLL that had a security problem, but I forced Read/Execute access on everything in %INFORMIXDIR%, no help. I'm beginning to suspect there is some hidden, secret user right that Informix is looking for. Anyone know any special incantations? I see a lot of posts with some version of this problem, but few answers. Maybe this is just Informix' way of telling me that I really don't want to run the web server on the same system as the database server. Thanks in advance, dwight rudolph

I'm replying to my own post, but I have a little more information. I downloaded the current "client SDK" for NT from intraware and installed it. Afterwards, the problem with dbaccess was still there, but my perl scripts using DBI:Informix started working from the web account. There are words in the release notes for this version of client SDK that talk about problems with versioning of files between the server and the clients, and how previously there would be problems much like I saw when one had both the server code and the client code on the same NT system. They say (I guess correctly) that they've renamed things in this latest release, and ESQL/C programs using shared libraries should now be okay. Statically linked programs - which I assume includes dbaccess - are still broke. I don't really need to run dbaccess from within a CGI script, so I think this fixes my problem. In article <76uefh$3f5$1@news-2.csn.net>, dwight@rudolph.com says... > >Does anyone have any recent or definitive guidance on this particular > problem? >I think many of us are having it in one form or another. > >The symptoms are this: >I install IDS (7.22 Workgroup in my case) on a NT server system. It comes up >okay. No unusual problems talking to it locally as informix (or whatever the >magic Informix user is), and no unusual problems talking to it from other >systems, Windows or UNIX. Performance pretty good. > >But if I try to connect to the server from a normal unprivileged user logged >into the server system itself, it fails. If I try dbaccess, I immediately > get >"Unable to access the security system". If I try from other sources, I often >get the -406 message, which has nothing to do with running out of memory.