Uniobjects should still work, I donbt think there is a need to change to .net.
I suppose the obvious question is what has changed ? - Can you still telnet to the account in question? Have the permissions of the voc file changed at all (remember the unidata services run as system and it is this that needs permission to the relevant files)? Have you enough licences at connect time? Are all the correct Unidata services running (i.e. including uni rpc etc)? Is there a firewall blocking the port? You may be able to switch logging on at the udcs side (not sure how to do it in windows) and see if a connection is coming through and what the error is there. Can you connect to another Unidata host ? HTH Symeon. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Parkinson Sent: 29 August 2007 00:33 To: [email protected] Subject: [U2] Uniobjects error 39027 I'm sure this question must have been asked many many time and you folk out there have probably encountered it yourself. I have an application written in VB6 which has been working fine and now when the app tries to connect to the Unidata account it throws out the connection with error 39027 which I cannot find any documentation for anywhere. I have tried reinstalling Unidata with no luck. I am using Unidata 7.1.6 on Windows 2003 Server Sp1 Has anyone experienced this and if so how did you resolve it? It's driving me mad!!!! Kind regards Paul Parkinson ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
