I'm confused by the fact that you copied folders from your Web Import Services installation to your Web Access folders. Web Import Services is a separate installation that does not even need to be on the same machine as the Web Access machine. The Web Import Service machine is what should be used in the URL in DocuSign, and Web Access should not come into play at all when debugging the DocuSign Connect Service.

The integration is basically two parts:

1) An integration in Web Access that allows users to request signatures from DocuSign

2) The DocuSign Web Import service, which receives documents from DocuSign and imports them to the Laserfiche Server referenced in the Import Service config file.

If the documents were originally sent out from within Web Access and are configured to return to the same Laserfiche server, the signed documents will be added to the original documents as a new version

That's my mistake, I thought the Web Import Services and Web Access were tied together, as there was mention of DocuSign options, through Web Access, once it was installed successfully.

I went ahead and tried installing Web Import Services on a DMZ machine.  Once this was done, I tried browsing to http://localhost/DocuSignConnectService/diagnostics/testlogin locally, and I'm still getting the same error.  

I'm using the DocuSign and LaserApp Integration from the Web Access 9.2.0.67 CD.

Marty

So does it look like I'm using the correct version of the installation?  Based on the test URL, I don't see anything similar to that after doing a clean install on a different machine.  

Thanks in advance for any help or suggestions you might be able to offer on this - much appreciated.

If you can't connect to that URL locally, there is something at play other than a firewall issue. It might be best to open a support case so they can help troubleshoot. To be clear, you are getting a 404 at that URL?

A couple of things to look at on the Web Import Service Machine

1. If you have not configured the LaserficheUserName and LaserfichePassword in the DocuSign Web Import Services config.xml, the integration will use windows authentication as the App Pool user. Make sure the app pool user for DocuSignConnectServiceAppPool is set to a Windows user that has permission to
   1. Log in to Laserfiche
   2. Access the DocuSignConnectService folder in Program Files.
2. Check the event viewer for errors from DocuSign Connect Service

Sorry about the confused regarding the integration. I'll see if we can make some clarifications in our documentation. 

Okay, so I've made a little bit of progress, however I'm still getting errors.

Based on the information presented above, I was able to get a username and password that has unrestricted access to the repository, and I was able to get a successful connection message (see attached).  However, despite having the Web Import Services config.xml set to a user that has full access to the repository, when I try to send a document from DocuSign for signing, I'm still consistently getting a 404 error, saying the link is unavailable.

Now, from the documentation, they say that the URL needs to be set up as: https://servername/DocuSignConnectService/receivepdf. 

Looking at the file structure, and the way IIS has a default page set in Web Access, it appears Web Access defaults to the following folder:

C:\Program Files\Laserfiche\Web Access\Web Files

Looking at the original installation location, the DocuSign integration piece was actually installed in the following location (using the Web Import Services installation under Web Access):

C:\Program Files\Laserfiche\Web Import Services\DocuSignConnectService

Is there a way I can point an absolute path to the default installation folder (i.e. going up a couple of folders from the default IIS folder for Web Access, such as ..\..\Web Import Services\DocuSignConnectService), or is there a way I could specify C:\Program Files\Laserfiche\Web Access\Web Files\DocuSignConnectService as the default installation directory for the DocuSign portion of the Web Import Services installation?

Thanks again for your assistance.

Marty Gaffney - Network Technician

Town of Okotoks

I cannot see any attachment. Try again?

The fact that it you got a success message is a good sign;  it indicates that your virtual directory is probably in the correct place. The next step would be to try accessing the test login URL from a machine not in the internal network, like http://yourmachinename/DocuSignConnectService/diagnostics/testlogin. If you get a 404, then there's a firewall or some similar issue.

The Web Import Services virtual directory /DocuSignConnectService should not be related at all to the default path for Web Access or the physical location for Web Access, unless you have modified physical path settings in IIS for the website the Web Import Services is installed under, or the DocuSignConnectService.

I would be wary of installing an application inside of the Program Files folder for another application. The paths you mentioned look correct, and trying to install this within the Web Access folder seems more likely to cause problems then to solve them.

Since you say you got a successful log in using http://localhost/DocuSignConnectService/diagnostics/testlogin, your virtual directory is probably exactly as it should be.

However, if you are still concerned, I recommend checking your settings in IIS rather than installing inside the Web Access folder, which is not the intended configuration.

First, try checking the physical path for the default website, or whatever website the DocuSignConnectService application appears under:

Then you should check that the physical path for the DocuSignConnectService application is correct:

Two additional clarifications:

1) The Autorun package for Web Access:

does indeed contain the installer for the DocuSign Import service, but the Web Access installer:

does not. The Web Access Autorun package section for "Optional Components" allows you to easily launch installers for separate products like Web Accelerator and the SharePoint integration that are related to Web Access but are still distinct products and are not required to be installed on the same machine.

2) Some more information about virtual paths might be useful.

First, a full virtual path may not always correspond to a full physical path. For example, the physical folder DocuSignConnectService in a working installation does not actually have a folder within it titled diagnostics, despite the fact that the URL says /DocuSignConnectService/diagnostics.

Second, as implied in my previous post, an application (such as DocuSignConnectService) can (and probably will) have a different physical path than other applications and the default website physical path.

Okay, I think I'm getting close... 

I realized (similar to problems I was having with Laserfiche Forms) that the URL I was using wasn't pointing to the correct location (it was pointing to <servername>/laserfiche, not just servername).  When I tested the correct path, I was able to get a connection, but NOW, when I try to connect through DocuSign (specifying this new address), I get the following error instead:

The remote server returned an error: (405) Method Not Allowed.

Having a look at the error message, it looks to be tied to having/using the WebDAV portion of IIS, however there doesn't appear to be any sign of this role being installed.  Might there be something else I could check to try and eliminate this error?

Marty

p.s. - The default Web site locations are correct, and I installed the DocuSign component from the location specified on the installation DVD.

Yes, if you have set up your web server such that https://yourURL  will go to https://yourserver/laserfiche  you would definitely have issues with the DocuSign Web Import, because DocuSign would try to send to https://yourserver/laserfiche/DocuSignConnectService . Now I understand where your earlier questions were coming from. Installing DocuSign within the folder for Web Access still won't fix the issue, though, so if you can just use https://yourservername/DocuSignConnectService/receivepdf  , then I'd recommend doing so.

I'm not sure what's causing the 405, but I do think it's progress. It might be best to continue troubleshooting through Support, since it seems likely to be a configuration issue and you have some non-default settings on your web server that make it tricky to reproduce.

I've been working back and forth with someone with DocuSign support, and I've been able to resolve the 405 error we're experiencing.  However, in Web Access, when I try to go into Settings / DocuSign Account / General, and I try to enter in the Email address I'm using for the DocuSign connection, click Validate, and enter in the password I'm using for the DocuSign Web site (as well as the APIUserEmail settings under WebAccessConfig.xml), I get the following message:

Web Access is not associated with a valid DocuSign API user account. Contact your administrator to configure Web Access for DocuSign.

Speaking with DocuSign, they also mentioned that, if possible, they would like to open a support case so we might be able to work on this together?  

Please let me know if this might be a possibility - thanks!

Marty Gaffney - Network Technician

Town of Okotoks

Sure, go ahead and contact your reseller to open a support case.