Hi Oleg
I've checked all our code and found that the code 351 mentioned only
in a client code (lib/OpenSRS/XML_Client.pm)
and it means
#if I have a bad public key, then server doesn't response to, so it
#will be empty buf or if connection died then buf is empty
if (not $buf){
return { is_success => 0,
response_text => "No response from server",
response_code => 351,
};
}
that is in a function read_data when client is trying to pull some
information.
If you can send a domain name to Charles (off-list), then we will check it
tomorrow and can tell what and why
E.Pirogov
OpenSRS Developer
On Mon, 29 Apr 2002, Oleg Chebotarev wrote:
> My clients have noticed the following problem:
> (And we were able to recreate it) 2 step sequence.
> 1. Register new domain
> (including creation of new profile)
> (Submit all data, cc, and etc)
> (Domain is registered at a registry)
> (Compete success)
> 2. Register new domain
> (existing profile)
> they submit domain registered at step 1
> username they used to establish new profile in step 1
> password they used to establish new profile in step 1
> As result the get an error number 351.
> I know that it is not auth issue (it produces 415).
> We have this issue with OSRS 2.48, 2.53, 2.53 patched,
> and OSRS-SF 1.59.
> After we noticed it in 2.48 release we had installed from scratch 2.53
> and then installed from scratch 1.59 SF.
> I spoke with tech support couple weeks ago and he said that profile
> that was created some time ago might have some bad data that it could
> not be pulled up. But we are seeing it on every newly created profile.
> Does anybody know what Error 351 is and how to solve it.
> Thank you,
> Oleg
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - your guide to health and wellness
> http://health.yahoo.com
>
