XD Publishing services are down getting error 44:63, 55:63, 500 etc.





I can't update a shared link.


I'm receiving Error 44:63


 


<The Title was renamed by moderator>
Hi everyone,
 
Sorry for the trouble and inconvenience that this issue has caused you. The issue related to publishing services is now fixed. 
Please let us know if you're still facing issues while updating or creating prototype links. 
 
Thanks,
Harshika
we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: hi guys do the software distribution rename to . old and catroot2 to .oldto allow recreate, restart the server, make sure the services are working bits, cryptsvc, windows installer, windows updateit worked for me this is a known issue, we are currently working on it and it should be fixed in the 3.0 patch. hi alexander,  

  

thank you pointing this out.  

  

we have fixed the problem in radtreeview and the fix will be included in the forthcoming q1 release.  

stay tuned for the official announcement in the next couple of days.   

  

i updated your telerik points for your involvement.  

  

best wishes,  

 veselin vasilev   

the telerik team
  

instantly find answers to your questions on the new [telerik support portal](http://www.telerik.com/support).  

[check out the tips](http://blogs.telerik.com/supportdept/posts/08-12-22/new_support_resources_search_facilities_on_telerik_com.aspx) for optimizing your support resource searches. [image] t\_t:

1738508

those domains are pending name server update, [@t\_t](/u/t_t), that has to happen prior to transferring the domain to cloudflare registrar, good tip here, [community tip - fixing “pending nameserver update”](https://community.cloudflare.com/t/community-tip-fixing-pending-nameserver-update/75415) . i suspect that the resource\_exhausted message may have originated from a back-pressuring committer node ([code](https://github.com/digital-asset/daml/blob/926fb5997a795e7f80443a9a3ba7898b1568d158/ledger/participant-integration-api/src/main/scala/platform/apiserver/services/apisubmissionservice.scala#l155-l157)). if that’s the case, i believe the approach should be the same: change the configuration if you need and make sure to handle those errors with the appropriate retry strategy. hi marlou,  

  

as i mentioned in my response to your support ticket, this problem is already fixed in the current release - q2 2009 sp1.   

  

greetings,  

 fiko   

the telerik team

  

instantly find answers to your questions on the new  [telerik support portal](http://www.telerik.com/support).
  

watch a [video](http://tv.telerik.com/telerik/support/using-telerik-support-resources) on how to optimize your support resource searches and [check out more tips](http://blogs.telerik.com/supportdept/posts/08-12-22/new_support_resources_search_facilities_on_telerik_com.aspx) on the blogs. thanks a lot

in mexico, the practice of entering the administrator password to confirm changes is not so common.

but sure enough, i think it was layer 8 bug A segmentation fault in this case probably means you accessed one of the arrays out of bounds. Start up a debugger and keep a watch on your indices. do you have any add-ons installed? if so, please turn them off and try again. add-ons are known to interfere with duolingo.