why there are always some unexpected registry error since 24th of Dec when using API to register?
Posted By rainer08/01/2015 13:02
rainer replied s_c_sg
Hmm....this seems to happen pretty deterministic after 10 requests for a domain....and it works again after about three minutes.
Reply Quote
Like
0 Replies
Posted By teamdynadot12/02/2015 00:46
teamdynadot replied s_c_sg
Are you getting the "system_busy" error message as well v_s_mumbai_in_1? Do you usually receive the error during drop times?
Reply Quote
Like
0 Replies
Posted By v_s_mumbai_in_111/12/2015 18:54
v_s_mumbai_in_1 replied s_c_sg
SO WHAT IS THE SOLUTION FOR THE SAME?
Reply Quote
Like
0 Replies
Posted By v_s_mumbai_in_102/19/2016 17:48
v_s_mumbai_in_1 replied s_c_sg
Yes, correct its during drop times.
But there is no SYSTEM BUSY error.
How can you help me in this?
Reply Quote
Like
0 Replies
Posted By v_s_mumbai_in_102/19/2016 17:47
v_s_mumbai_in_1 replied s_c_sg
Yes, correct its during drop times.
But there is no SYSTEM BUSY error.
How can you help me in this?
Reply Quote
Like
0 Replies
Posted By b_godzilla_us04/01/2016 19:55
b_godzilla_us replied s_c_sg
When you say "Spending" do you mean how much is being currently purchased or Year's culmulative domains purchase? After all, someone could "buy" 100 domains but give 99 of them back within the grace period, ending up not having a high yearly amount. So which?
Bronxgodzilla
Reply Quote
Like
0 Replies
Posted By teamdynadot04/07/2016 22:52
teamdynadot replied s_c_sg
Spending is calculated daily, so its whatever amount spent in the last 365 days.
Reply Quote
Like
0 Replies
Posted By b_godzilla_us04/15/2016 01:40
b_godzilla_us replied s_c_sg
Now that makes sense. Thanks!
Reply Quote
Like
0 Replies
Posted By teamdynadot02/20/2016 18:33
teamdynadot replied s_c_sg
This is common during drop times as many people use the API for drop catching domains, particularly higher spending accounts who generally have priority over the API connections. The API connection is based on spending.
Reply Quote
Like
0 Replies
Posted By teamdynadot04/20/2016 22:44
teamdynadot replied s_c_sg
No problem!
Reply Quote
Like
0 Replies
Posted By b_godzilla_us12/27/2008 19:49
b_godzilla_us replied s_c_sg
Don't know what you mean. I've registered several and in midst of transferring several more in past 5 days and everything going smooth as silk. I love this place. Perhaps you are running into internet or browser-related obstacles?
Reply Quote
Like
0 Replies
Posted By teamdynadot12/27/2008 21:08
teamdynadot replied s_c_sg
Which registry error are you getting for the API? Is it the "system busy please try again" error? That means too many people are trying to access the registry at the same time, and we are out of connections for that registry.
For more info about the API:
http://www.dynadot.com/domain/api.html
Dynadot Staff
[This post has been edited by dynadot_staff on Dec 27, 2008 1:08pm.]
Reply Quote
Like
0 Replies
Posted By s_c_sg12/29/2008 19:10
s_c_sg replied s_c_sg
During registry, the displayed error is "error, unexpected registry error". 3 out of 5 domains will have this error.
Reply Quote
Like
0 Replies
Posted By forumname12/30/2008 15:07
forumname replied s_c_sg
i get the same error.
i suspect this is due to dynadot's connections to the registry all being used up by people attempting to catch domains.
Reply Quote
Like
0 Replies
Posted By d_r_cooper_city_us03/20/2009 19:37
d_r_cooper_city_us replied s_c_sg
Any update on this error? It only occurs during the main drop time from 2:00pm to 3:30pm EST. The exact error returned is "unexpected registry error". This has been going on for months. Thanks
Reply Quote
Like
0 Replies
Posted By teamdynadot03/21/2009 05:17
teamdynadot replied s_c_sg
It means that we are out of connections. During drop times the api server is swamped with requests. You can try again if you get that error.
Dynadot Staff
[This post has been edited by dynadot_staff on Mar 20, 2009 10:18pm.]
unexpected registry error