You are viewing limited content. For full access, please sign in.

Question

Question

Can Laserfiche Web Import for Docusign run on WIndows Server 2016?

Installation and Upgrades
Updated December 28, 2018
asked on August 27, 2018

We're migrating data centers and trying to build a new Docusign Import server using Windows Server 2016, but even though we passed the prerequisites test, it says that IIS is not installed.

The system requirements don't mention Server 2016, but I was hoping to not have to roll out another 2012 server at this stage if at all possible.

0 0

Answer

SELECTED ANSWER
replied on December 28, 2018

Is DocuSign installed to Default Web Site in IIS, or another website? If you open IIS manager, do you see a 'DocuSignConnectService' virtual directory? Have you tried using the fully qualified domain name instead of localhost?

 

Also, I'm assuming you get the same think if you use the URL: https://localhost/docusignconnectservice/diagnostics/testconnect ?

 

The 404 sounds more like an IIS configuration problem than an installation issue. If the virtual directory is somewhere in IIS, the installer probably isn't the culprit. Outside of installing and filing out the config.xml (specifically, the login info), there aren't any additional steps necessary to get the DocuSign Connect Service working on Server 2016.

0 0

Replies

replied on August 28, 2018
0 0
replied on September 6, 2018

This did the trick.  The install completed.

 

Thanks for the assist.

0 0
replied on September 6, 2018

Just to update the thread, Laserfiche tested the DocuSign integration internally and confirmed that it works on Windows Server 2016. 

 

That said, I did have to follow the KB that Pava posted for the install to proceed smoothly. 

0 0
replied on December 18, 2018

We're struggling to complete this install.  Although we followed the KB to complete the install, the site is not responding as expected when we use the "https://localhost/DocuSignConnectService/diagnostics/testlogin" test URL.

We simply get a page as follows:

The webpage cannot be found

 HTTP 404

More informationMore information

This error (HTTP 404 Not Found) means that Internet Explorer was able to connect to the website, but the page you wanted was not found. It’s possible that the webpage is temporarily unavailable. Alternatively, the website might have changed or removed the webpage.

For more information about HTTP errors, see Help.

-----

We removed and reinstalled the app, and verified that config.xml file matches our old server.

Is there any other steps we need to follow to get this running on Windows Server 2016?

0 0
SELECTED ANSWER
replied on December 28, 2018

Is DocuSign installed to Default Web Site in IIS, or another website? If you open IIS manager, do you see a 'DocuSignConnectService' virtual directory? Have you tried using the fully qualified domain name instead of localhost?

 

Also, I'm assuming you get the same think if you use the URL: https://localhost/docusignconnectservice/diagnostics/testconnect ?

 

The 404 sounds more like an IIS configuration problem than an installation issue. If the virtual directory is somewhere in IIS, the installer probably isn't the culprit. Outside of installing and filing out the config.xml (specifically, the login info), there aren't any additional steps necessary to get the DocuSign Connect Service working on Server 2016.

0 0
replied on December 28, 2018

Working with a resource from our VAR, we discovered the HTTPS binding had been modified during diagnosing.  Resetting that binding to the proper public name and certificate resolved the issue.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...