Can not generate the URL

Hi nehme, For the first glance on the issue, I want to ask which environment you are currently developing with? Because from the API you are calling "https://apps.e-signlive.ca/api/packages/-XN_Sbs1bSm9Hbs1x3dqpUWdBUk=/documents/signed_documents.", it's CA prod. Is this the correct environment? Duo

And the API "/api/packages/{packageId}/documents/signed_documents" is used for signing all document. Is the SDK function you called is correct? Can you share the code you are currently using? Duo

Hello Duo, Yes I am using prod CA. I am using this code: eslClient.SignDocuments(packageID); which will sign the documents for the sender automatically. Same code is working in sandbox but it is not working in production. Thanks, Nehme

Hi Nehme, So what's your workflow? Did you generate URLs for your signers and sign documents programmatically for your sender? Can you successfully generate the signing URLs? And did you assign a signing order for your signers/sender? Given that, I will have a test on CA PROD environment and let's see what's the cause of the issue. Duo

Hello Duo, The workflow is like this: 1. generate URLs for your signers and sign documents programmatically for your sender. 2. Yes there is signing order for signers/sender. 3.While generating the url, I am getting the above error, but the package is created at https://apps.e-signlive.ca Thanks, Nehme

Hi Nehme, I've tested in CA PROD with the code in attachment where I send a new package, generating signing url and then signDocuments, there's no error at my side. So I guess it's not a problem with GetSigningUrl()/ SignDocuments() functions or because of the change of environment. Can it because of the way your create your package from template? Can you try creating a simple package and repeat the workflow? Duo

Hello Duo, Thanks for your details. I check the issue, it is after import the templates from sandbox to production, the issue is with the sender id. This is what is causing the problem. Any suggestions about this matter? Thanks, Nehme

Hello Duo, I am getting the URL now, but while trying to sign it, I am getting the attached error. What is the problem? Thanks, Nehme

Hi nehme, Can you create a signing url and sign it without programmatically SignDocuments() for your sender? To narrow down the cause of the issue? Duo

Hello Duo, Same issue. Using prod CA, with SDK 11.19 dll. Thanks, Nehme

Hi nehme, If that's the case, can we talk about the way how you create the package in CA prod? Because as we discussed in previous thread, the templates created in new environment have a different id with the ones in old environment, same things happens to the senders (they have the same personal information while different role & signer ID) So how do you handle this? Duo

Hello Duo, You have already sent me a tool to import the templates from sandbox to production. I have done this by using the tool you send me. Thanks, Nehme

Hi nehme, Let me put it in this way, when you calling PackageId newPackageId = eslClient.CreatePackageFromTemplate(new PackageId(templateId),package); in your CA prod to create a package from template, how you identify the template ID as it's different from the one in your old environment? Duo

Hello Duo, I have everything in Config file, so when I shift to prod I use the template ID in production. There is no issue here in this. I am able to generate the URL with no problems, but while signing I am getting the message I have sent you a pic in this post. Thanks, Nehme

Hi nehme, I will do a more delicate test on your workflow and then I will come back to you. Or alternatively, you can contact our support team at [email protected] and file in a ticket for yourself on this issue, then we can set up a troubleshoot meeting with you. Duo

Hi nehme, Sry for missing your point. I just found that when using Migration Tool, if you have your sender involved in the template, he/she won't be copied to the new environment. It's a defect of the program and I will fix it asap. Is this the cause of your issue? Duo

Hello Duo, Thanks for your details. What about now, I have already imported the templates in production.. Any solution for this? Thanks, Nehme

Hi nehme, I will fix the issue and make sure it passed the test at my side. Then you can delete all templates in your production environment and repeat the migration process again. Does this work for you? DUO

Hello Duo, It is so hard. Our users they did lot of changed and many adjustments in fields and positioning, so so hard to delete them. Any solution for the existing templates in production? Thanks, Nehme

Hi nehme, First, can you confirm the cause of the issue before we looking for solutions? Because from your description, it seems any solutions on your product account needs to be applied carefully in case ruining the modified templates, right? Duo

Hello Duo, Yes you are right. But as I told you the production URL was generated fine, but while signing it the problem shows up. Thanks, Nehme

Hi nehme, Just for more information, after package was created in prod environment, can you sign manually instead of calling function for your sender and signer? Duo

Hello Duo, I have already stopped the automatic signing for the sender, but still getting the same issue. Thanks, Nehme

When did you receive this 500 error? when creating package? Can I have the error message in your debug output? Duo

Hello Duo, Package already created with no issues. When trying to sign it, I am getting this error. Also I attached it POST https://apps.e-signlive.ca/packages/yptFvZOMS5nUvKVSzPqgJ3m2HVg%3D/documents/6c4e884a27c2172acf97671e4008e6661b4bb16723ee684e/actions? 500 (Internal Server Error) send @ jquery.min.js?v=1537380370422:4 ajax @ jquery.min.js?v=1537380370422:4 a.ajax @ jquery-migrate.min.js:2 k @ ESR.min.js?v=1537380370422:2 (anonymous) @ ESR.min.js?v=1537380370422:2 i @ jquery.min.js?v=1537380370422:2 fireWith @ jquery.min.js?v=1537380370422:2 A @ jquery.min.js?v=1537380370422:4 (anonymous) @ jquery.min.js?v=1537380370422:4 load (async) send @ jquery.min.js?v=1537380370422:4 ajax @ jquery.min.js?v=1537380370422:4 a.ajax @ jquery-migrate.min.js:2 online @ ESR.min.js?v=1537380370422:4 f @ ESR.min.js?v=1537380370422:2 (anonymous) @ augment.js:447 d @ ceremony.js?v=1537380370422:2 c @ ceremony.js?v=1537380370422:3 b @ ceremony.js?v=1537380370422:3 props.click @ jquery-ui.js:8550 dispatch @ jquery.min.js?v=1537380370422:3 q.handle @ jquery.min.js?v=1537380370422:3 Thanks Nehme

Hi nehme, I think we need a troubleshooting session. Can you make a ticket at [email protected] and we can set up a join me session at some time. And can you have a test in this way: 1.use your web portal and create the transaction from your template as the attachment shows, 2.fill in the signer info ,3.send it and try signing it again. Duo

+attachment