Thanks to the gentleman who recommended that I include the full path in the
connection string, the problem is solved.
I can connect with the .Net objects again.
Maybe the addition of a new Unidata account created the problem - who knows.
thanks to all
grs
---
u2-users mailing l
> Mark and Nick,
>
> Thanks for your suggestions below. This is a home development system,
> if the rpc daemon has changed I do not know how. However, I will check
> both of your suggestions when I get home.
>
or it could be a Windof-Problem
I have this problem, every few weeks that for no reas
Check the UV.ACCOUNT file and verify that your account still exists.
You can also use the full path to the account instead of the account
name. I usually put the full path in for the account name.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listse
Mark and Nick,
Thanks for your suggestions below. This is a home development system, if
the rpc daemon has changed I do not know how. However, I will check both
of your suggestions when I get home.
Same for the Demo account - I have not touched it and can access it from
telnet and the UniAdmin.
-users@listserver.u2ug.org
Subject: [U2] UODOTNET Connection Error
I have an XP client connecting to a 2003 Server running Unidata 7.1. The
following was working about
Aa month ago, in fact I have never had any problem connecting to the
server. This program (IBM's example program) worked in the
Just a thought. Has the port the rpc daemon runs on changed?
Thanks,
Nick Cipollina
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of George Smith
Sent: Friday, November 04, 2005 9:30 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] UODOTNET
I have an XP client connecting to a 2003 Server running Unidata 7.1. The
following was working about
Aa month ago, in fact I have never had any problem connecting to the
server. This program (IBM's example program) worked in the past now I am
getting the following error trying to connect to the De
