Troubleshooting & FAQs

SigningHub FAQs

SigningHub is an enterprise level application and has been designed to cater the signing needs of diverse groups of people.

At times SigningHub does not respond in a way you actually looked for, or you are not able to perform a certain activity. Well that’s very much an reprehensible case considering the system's magnitude and its technical configurations.

So in the light of foreseeable events, we have produced a set of frequently asked questions (FAQs) that will assist you getting smooth transactions over SigningHub. We therefore encourage you to visiting Ascertia's Partner Portal for frequently asked questions before contacting SigningHub support for your everyday queries.

---

1. If SigningHub Enterprise Admin module is installed on Windows 2012 R2, then the HTTP 403.16 error code may occur when you access the SigningHub Admin console from web browser. Follow these instructions to solve this issue:

   1. Open registry and add the key: KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL

   2. Create a new key with Value Type: REG_DWORD (32-bit)

   3. Set Value Name: ClientAuthTrustMode

   4. Edit the field and set Value Data: 2

1. If you are interested to know more details about it, browse the Microsoft KB.

---

1. If you receive the HTTP error code 500.19 whilst accessing Admin, Web or API then:

   1. Open IIS Management Console

   2. Go to Application Pools

   3. Select a site and click Advanced Setting

   4. In General, make sure that Enable 32-Bit Applications is set to False.

---

1. If you cannot start ADSS Signing Server from Windows Services panel on Azure, then make sure that you are not starting those services under Windows user that you have created while creating the Azure instance. You must create another Windows user with Administrative rights and start the services under that user.