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

Question

Question

Root Element is missing issue

asked on February 19, 2016 Show version history

I'm getting this error when I try to load the client. I can still get in but none of the business processes are available. The system change was we upgraded our license for RIO. Here's the error message.

 

Error Code: 6000
Error Message: Root element is missing.
Unknown error. [6000:0x80131940]

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

LF.exe (9.2.1.562):
    Call Stack: (Current)
        PreloadBusinessProcesses
        CLFApp::AddAttachedRepository
        CLoginDialog::AttemptLogin
        CLoginDialog::LoginToServer
        CLoginView::LoginHandler
    Additional Details:
        Exception: 0x80131940 [6000] (Root element is missing.) (PreloadBusinessProcesses at BusinessProcessUtil.cpp:135)
    Call History:
              CGroupProvider::raw_GetAllGroupIdentifiers
              CBusinessProcessManager::GetStartingInstructionsDocument
              CBusinessProcessManager::GetBusinessProcessSecurityEvaluator
              CGroupProvider::raw_GetAllGroupIdentifiers
              CGroupProvider::raw_GetAllGroupIdentifiers
              CGroupProvider::raw_GetAllGroupIdentifiers
              CBusinessProcessManager::GetStartingInstructionsDocument
              CBusinessProcessManager::GetBusinessProcessSecurityEvaluator

1 0

Replies

replied on March 8, 2016

For the benefit of other readers.  According to Development, this issue was caused by an invalid Business Process Definition.

For the specific issue mentioned in this thread, it was resolved by running the following SQL query:

delete from bizproc where bizproc_id=30

Note that the resolution is specific to the db used by Brian Jackson.  If other users encounter this issue, we will need to see the SQL db used by their LF repository.
 

1 0
replied on February 22, 2016

What version of the Laserfiche Client are you running?

replied on February 26, 2016 Show version history

Your VAR has already opened a case for this issue.  The thread will be updated once the case is resolved.

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

Sign in to reply to this post.