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

Question

Question

Could not create required control. [6720] on opening client

asked on August 26, 2014

I have a user that is receiving the following error when he opens his Laserfiche Client:

Error Code: 6720

Error Message: Could not create required control. [6720]

 

------------ Technical Details: ------------

 

LF.exe (9.0.3.798):

    Call Stack: (Current)

        PreloadBusinessProcesses

    Additional Details:

        Exception: 0x80041a40 [6720] (Could not create required control.) (PreloadBusinessProcesses at BusinessProcessUtil.cpp:149)

    Call History:

        PreloadBusinessProcesses

         GetServerVersion

         CBusinessProcessManager::LoadBusinessProcesses

          CBusinessProcessManager::GetBusinessProcessSecurityEvaluator

 

I have tried running a Repair, uninstalling and re-installing, trying a different version of the Client, and also running repairs on .Net on his PC but the error persists. 

 

If he clicks "ok", then he is able to brows the client and open documents normally. The only thing that seems to be effected is his ability to start a business process on a document. The problem is only for this one user so I assume there has to be something missing on his PC, but not sure what.

 

 

1 0

Answer

APPROVED ANSWER
replied on August 26, 2014

The component it is trying to load is Laserfiche.Workflow.BusinessProcess, but a repair should fix it. Please open a support case so we can further troubleshoot the problem.

3 0

Replies

replied on November 21, 2016 Show version history

Hi Guys,

 

Did you manage to get to the bottom of this? I've got the same issue, I've also tried a repair and this is on V10.1.1.254.

 

Cheers!

 

Error:-

 

Error Code: 6720
Error Message: Could not create required control. [6720]

------------ Technical Details: ------------

LF.exe (10.1.1.254):
    Call Stack: (Exception)
        CBusinessProcessManager::GetBusinessProcessSecurityEvaluator
        CBusinessProcessManager::LoadBusinessProcesses
        PreloadBusinessProcesses
        CLFApp::AddAttachedRepository
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Call Stack: (Current)
        PreloadBusinessProcesses
        CLFApp::AddAttachedRepository
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Additional Details:
        Exception: 0x80041a40 [6720] (Could not create required control.) (PreloadBusinessProcesses at BusinessProcessUtil.cpp:136)
    Call History:
            GetOptionString ([Settings]EnableBusinessProcesses)
             CAttachedRepository::GetProfileValue
              CAttachedRepository::LoadAttributePrefix
              CAttachedRepository::LoadAttributePrefix
            PreloadBusinessProcesses

0 0
replied on November 21, 2016

Please open a support case. We will need you to re-install the client with MSI logging enabled.

0 0
replied on December 1, 2016

Hey Chris / Bob,

 

We just worked through this issue and have resolved it (for us anyways).  We were doing custom installs of Laserfiche rather than 'typical' and the custom install was not checking for .NET 3.5 as a prerequisite.  If you do a typical install it will install it, but custom evidently does not.  

 

If you look in the LF client installation folder under \en\Support you will see a .NET 3.5 installation file.  All we had to do was install it on the stations that were having issues and the problem went away immediately.

0 0
replied on December 5, 2016

Thanks Shaun,

 

Interestingly, the latest windows 10 update seems to un-install .net 3.5..... one to watch out for..... ;)

 

1 0
replied on December 13, 2016

FYI - Re-installing .net 3.5 resolves the error.

1 0
replied on December 13, 2016 Show version history

Chris, is that Windows machine in the insider preview program? I've had Windows updates uninstall IIS and Message Queuing, but I was hoping they wouldn't do that outside of the Insider Preview program.

Do you know which update it was?

0 0
replied on December 13, 2016

Hi Miruna,

 

No this is a box standard Window 10 Pro machine. The update which un-installed .net 3.5 was the Feature update to Windows 10, version 1607. I installed it on 17th November 2016. Hope this helps give you a heads up.

 

Cheers!

0 0
replied on December 13, 2016

Interesting. Google search suggests that Windows updates were responsible for this at least twice this year. And the steps for installing it got worse in Win 10: https://support.microsoft.com/en-us/kb/2734782

Thanks for the heads up, we'll get a KB article published.

0 0
replied on December 13, 2016

It was a real pain to re-install. Had to use the OS disk in the end!

0 0
replied on December 13, 2016

Yeah, I can't believe they removed the group policy that allowed you to install it through Programs and Features and left only the ISO+command line option.

2 0
replied on August 29, 2017 Show version history

The .net Framework 4 is already installed and i am having the same error.

is 3.5 version necessary or can we use version 4 ?

Please advise.

0 0
replied on September 5, 2017

It as to be 3.5 I believe

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

Sign in to reply to this post.