Martin, No mention of your platform here but one thing to check is the environment. On UD on Linux, the uniobjects connections are child processes of the unirpcd process and as such inherit their enivronment from Unirpcd. One option would be to put something like "env > /tmp/myfile.txt" into $UDTBIN/startunirpcd just before it actually starts the daemon and compare the output on your production and replication machines. Other things could be udtoptions not set, missing cataloged routines etc.
On windows I have no idea how the windows services inherit their environment but you could call a simple subroutine from uniobjects that does nothing but dump its environment out to somewhere you can see it including UDT options. File ownership might be worth checking as well. Cheers, Adrian Auckland, NZ On Mon, Jun 15, 2009 at 9:39 AM, Martin Scholl <[email protected]>wrote: > I program in Visual Basic 6 and use UniObjects to access U2. > > I tried to move a client’s application to the replication server this > weekend. Everything seemed to work fine until I got a call from the client > that there was a strange error message. > > After investigating in debug mode, I found that a subroutine call returned > error 30102. This error is not documented in uoaif.txt. > > I recompiled and recatalogued the subroutine to no avail. Other subroutine > calls work fine. I am at my wit’s end here. > > > > Martin Scholl > > www.HIPAAsuite.com > > 18910 New Hampshire Ave > > Brinklow, MD 20862 > > Phone: 301-924-5537 > > Cell: 301-613-9572 > > [email protected] > > > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > >
_______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
