Question

Error logging in

  • 10 June 2024
  • 4 replies
  • 46 views

Badge +1

we’’re getting these errors connecting on certain computers, others work fine with the same accounts. Any help would be greatly appreciated

 

ERROR [12524] [2024-06-10 09:02:37] <AccountServerApi.cs GetResponseString 412>: AuthWindow WebResponse has an WebException: The underlying connection was closed: An unexpected error occurred on a send.
ERROR [12524] [2024-06-10 09:02:37] <AccountServerApi.cs GetResponseString 413>: The underlying connection was closed: An unexpected error occurred on a send. -    at System.Net.HttpWebRequest.GetResponse()
   at DocuSign.PrintDriverApplication.Api.AccountServerApi.GetResponseString(WebRequest webRequest)
ERROR [12524] [2024-06-10 09:02:39] <AccountServerApi.cs GetUserDetailsViaAccountServer 184>: Value cannot be null.
Parameter name: s -    at System.IO.StringReader..ctor(String s)
   at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
   at DocuSign.PrintDriverApplication.Api.AccountServerApi.GetUserDetailsViaAccountServer(UserInfo userInfo)

 


4 replies

Userlevel 5
Badge +12

@cjmx 

You are getting this issue related to the connection and authentication process when attempting to connect with the DocuSign API. 

Try sending a basic request to DocuSign's API from the affected computers to see if they can establish any connection at all. This can help isolate whether the issue is with the connection setup or the specific API request.

Badge +1

@JohnSantos 

connections are established.  I noticed this on a non-working workstation there’s a device not migrated event. Is this a problem?

 

Userlevel 5
Badge +12

@cjmx  What do you mean it is a non-working workstation? Can you try to re-install the Print to DocuSign driver.   It does not look like it was properly transferred to the current system configuration during a system upgrade or installation process.

Badge +1

@JohnSantos  non-working as in docusign doesn’t allow the sign in and gives the error I originally posted.  Yes, we’ve tried reinstalling the driver several times.   

Reply