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

Question

Question

Upgrade to LF9.1, now can't connect to remote server via the administration console

asked on February 7, 2014

I upgrade a LF9.0.2 server to LF9.1 yesterday, along with all clients. Since then, I've been unable to connect to that server via the Admin console. This is a cloud server, which prior to 9.1, I could connect to remotely. I can log into the repository via the LF9.1 client remotely though. I receive the below error via the admin console, although I'm never prompt to enter a username and password, so not sure how it can be incorrect.

 

Error Message:

The user login or password is incorrect.

The user account name or password is incorrect. [9010]

 

Error Details:

 

Error Code: 9010
Error Message: The user login or password is incorrect.
The user account name or password is incorrect. [9010]

------------ Technical Details ------------

LFSO:
    Call Stack: (Exception)
        CLFServer::GetAllNamedUsers
    Additional Details:
        HRESULT: 0xc0042332 (CLFNamedUserCollection::CreateForDispatch, LFNamedUserCollection.cpp:399)
         (LFSO/9.1.0.411)
LFAdmin.dll (9.1.0.413):
    Call Stack: (Current)
        CServerNode::RetrieveServerInfo
        CServerNode::Initialize
        CRegisterServer::OnOK
    Additional Details:
        Exception: 0xc0042332 [9010] (The user login or password is incorrect.) (CServerNode::RetrieveServerInfo at ServerNode.cpp:1313)
    Call History:
        CComponent::Notify
        CComponentData::AddMenuItems
        CComponentData::Command
        CRegisterServer::OnOK
         CRegisterServer::InsertServerIntoRegistry
         CServerNode::Initialize
          CBaseNode::GetServerAttributes
          CServerNode::RetrieveServerInfo

 

1 0

Answer

SELECTED ANSWER
replied on February 7, 2014

This is an issue with the 9.1.0 Desktop Administration Console. You can use the Web Administration Console for now or wait for and upgrade to the next release of Laserfiche which will address this issue.

1 0

Replies

replied on February 7, 2014

Hi Jerri, 

 

It sounds like before the upgrade that you may have had "Automatically login in the future" selected.

 

Are you able to right click on the repository and under all tasks select the option "Change User"?

 

Also try hitting "Login" from here, as that may bring up the prompt. 


Worst case scenario you may have to install Admin Console on a different machine that is already running the client so that you can get to the login prompt. 

 

Good luck, 

 

Ramsey

0 0
replied on February 7, 2014

I don't use the automatically login option, but good catch, I wouldn't have thought of that.

 

I have both the Admin Console and the client on my machine. I can login via the client perfectly. It's only the Admin Console giving me the headache!

 

In the Admin Console, if I right click on the server, I only get 4 options:All Tasks-Remove Server Registration, New Window from Here, Refresh, and Help.

 

I've tried removing the server registration and registering it again, but still the same issue. I even tried registering it via IP address, no help. I've rebooted both my pc and the server, no help.

 

I can refer to our network admin, but I think it's odd I'm only experiencing the issue since I upgraded.

 

Thank

Jerri

0 0
replied on February 7, 2014

Agreed, definitely an odd issue. Hopefully you'll be able to select the "Change User". 

 

You mentioned you right clicked on the server, but you need to right click on the repository name beneath the server, that is where you'll see those logout/login/chage user options. 

 

Unfortunately short of that option, I was unable to find a way to take my admin console out of auto login mode. 

0 0
replied on February 7, 2014 Show version history

When these releases come out why are these issues not mentioned in the change release?  If they are, where are they listed?  It would be great to know these things before we upgrade.

 

 

 

0 0
replied on February 7, 2014

This particular issue was discovered after 9.1.0 was released. This will be mentioned in the KB article for the next release as a fixed issue.

1 0
replied on April 28, 2014

I understand that this issue has been addressed with 9.1.1

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

Sign in to reply to this post.