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

Question

Question

Receiving error “Could not create required control. [6720]" when trying to e-mail document from client 9.0.3.798.

asked on August 15, 2014 Show version history

 

I have not done a full uninstall / reinstall of the client and wanted to see if anyone knew of a quick fix to this issue.  I'm assuming maybe there is a corrupt DLL?  Please advise.

 

Thanks

1 0

Answer

APPROVED ANSWER
replied on August 15, 2014

You may want to try running a repair of the Client installation, but if that doesn't address it, then an uninstall and reinstall would be the next step. If there's still an issue, you can contact Laserfiche Support to open a case.

2 0
replied on June 15, 2016

Was upgraded to 10.1 last week and began having the issue.  Had it once before with LF 9.

Error - Could not create required control 6720 when trying to email or export a pdf from Laserfiche.

Our IT department (Jade) along with Molly from MCCI worked to repair the installation of LF 10.1. 

They confirmed that a utility like CC Cleaner can unregister a dll, which can cause error 6720 and the inability to email or export (download in 10.1) pdfs.

Jade indicated that CC Cleaner had been run on the system the week before.

After the repair (no PC restart was required).  I was able to export and email pdfs. 

Thanks Molly and Jade! 

I hope someone else will find this helpful.

 

Error 6720.JPG
Error 6720.JPG (53.44 KB)
2 0

Replies

replied on April 21, 2015

FYI...Had this same error today.  User was trying to email a document from the LF Client (9.1) and this error was coming up.  A repair on the client install resolved the issue.

1 0
replied on August 29, 2014

We have a client with the same issue - did a repair/reinstall resolve the issue?

0 0
replied on August 29, 2014

Same user at same client started getting the error again today.  The reinstall did fix the issue the first time but is there a bug in the latest release of LF 9 that causes the e-mail function to fail?

0 0
replied on May 15, 2015

I have a customer that is seeing this error reoccur about every 6 to 8 weeks on the same workstation.  Does anyone know what is causing it?  I am assuming it is the DLL used to create the PDF because they can export to tiff without the error.  What DLLs are involved in PDF creation?  My customer wants to try just re-registering the DLL(s) instead of repairing/reinstalling the whole client.

0 0
replied on May 15, 2015

I've seen this happen when someone runs a registry cleaning application like CCleaner. It detects some registry entries that Laserfiche sets as being invalid (false positive) and the user unknowingly allows the application to delete these entries.

A repair of the Client is recommended because it will correct the issue completely, but if you want to manually register DLLs (assuming this is with the lastest 9.2 Client), then you may want to start with

  1. PdfExporter92.dll
  2. itextsharp.dll
  3. O2S.Components.PDFRender4NET.dll
  4. O2S.Components.PDFView4NET.dll

Note that these DLLs are in the Windows Assembly so you'll need to use regasm /codebase and the full path of those DLLs. Also, not all may be required just for exporting a file as a PDF as some (and maybe more that I haven't yet listed) are used for page generation from PDFs and other tasks.

4 0
replied on February 21, 2017

I can confirm that this appears to be caused by CCleaner.

Careful who you trust to clean your equipment! Better to leave it up to the software developers.

1 0
replied on May 15, 2018

I just installed ccleaner and now I'm having this same issue, when I try to repair in Programs I get

“The installation source for this product is not available. Verify that the source exists and that you can access it”

I figure I may need to run a repair using the installation of 9.1 instead but I cannot find this install I found 8.0 and 9.2 installs on the server.

anyone know how I can get 9.1?

 

0 0
replied on December 1, 2015
0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.