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

Discussion

Discussion

Cannot unlock a repository in 10.4

posted on March 29, 2022 Show version history

During an attempt to point our repository to a different DB instance, things did not go well, so in an attempt to prevent further damage, I locked the repository via the mmc console.  After I did that, the contents and properties of the repository disappeared.  Subsequent attempts to access the repository result in a login prompt (Windows authentication or Password authentication) and neither work, resulting in the 9526 "The repository cannot be mounted at the current time because it is being mounted or unmounted.  Please wait until the current operation completes".  We've waited and waited and nothing changes.  Under Action/All Tasks, there is no option to Unlock the repository.  We have restarted the LaserFiche Server service several times to no avail.  We've even rebooted the server itself.

Trying to restore our configuration to a usable repository.

0 0
replied on March 29, 2022

Thank you Samuel!  Yes I have our Provider engaged - will be meeting Wednesday morning.  In the meantime, I see this entry repeated in the Admin event log:

Log Name:      Laserfiche-ContentRepository-Service/Admin
Source:        Laserfiche-ContentRepository-Service
Date:          3/29/2022 4:01:46 PM
Event ID:      150
Task Category: None
Level:         Error
Keywords:      
User:          FACT\XSVC-LaserFiche
Computer:      CL-U-LF-01.fact.local
Description:
An error occurred when executing an SQL query, retrieving the results of a query, or otherwise communicating with the database server. Session ID=0; Dialog ID=0; Repository="TBS-UAT"; Function=SysRepMount; Message="[Microsoft][ODBC Driver 11 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53]. "; Statement="Statement independent operation: Connect."; SQL Variable=""; SQL State="08001".
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Laserfiche-ContentRepository-Service" Guid="{82fc23fe-4b0a-435c-82e6-01c7077098af}" />
    <EventID>150</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2022-03-29T21:01:46.290726800Z" />
    <EventRecordID>526134</EventRecordID>
    <Correlation />
    <Execution ProcessID="6104" ThreadID="6160" />
    <Channel>Laserfiche-ContentRepository-Service/Admin</Channel>
    <Computer>CL-U-LF-01.fact.local</Computer>
    <Security UserID="S-1-5-21-436991440-3635180986-696182921-48659" />
  </System>
  <EventData>
    <Data Name="sessionID">0</Data>
    <Data Name="dialogID">0</Data>
    <Data Name="repository">TBS-UAT</Data>
    <Data Name="func">SysRepMount</Data>
    <Data Name="message">[Microsoft][ODBC Driver 11 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53]. </Data>
    <Data Name="stmt">Statement independent operation: Connect.</Data>
    <Data Name="sqlvar">
    </Data>
    <Data Name="sqlstate">08001</Data>
  </EventData>
</Event>

I also see this, but the LFDS cannot connect without a functioning repository, I assume:

Log Name:      Laserfiche-ContentRepository-Service/Admin
Source:        Laserfiche-ContentRepository-Service
Date:          3/29/2022 4:03:49 PM
Event ID:      191
Task Category: None
Level:         Error
Keywords:      Laserfiche license events
User:          FACT\XSVC-LaserFiche
Computer:      CL-U-LF-01.fact.local
Description:
There was an error downloading an updated license file from the Laserfiche Directory Server. Could not successfully connect to LFDS and download the license file.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Laserfiche-ContentRepository-Service" Guid="{82fc23fe-4b0a-435c-82e6-01c7077098af}" />
    <EventID>191</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000800000000000</Keywords>
    <TimeCreated SystemTime="2022-03-29T21:03:49.371307000Z" />
    <EventRecordID>526141</EventRecordID>
    <Correlation />
    <Execution ProcessID="5448" ThreadID="9248" />
    <Channel>Laserfiche-ContentRepository-Service/Admin</Channel>
    <Computer>CL-U-LF-01.fact.local</Computer>
    <Security UserID="S-1-5-21-436991440-3635180986-696182921-48659" />
  </System>
  <EventData>
    <Data Name="message">Could not successfully connect to LFDS and download the license file.</Data>
  </EventData>
</Event>

 

Seems like a catch-22 situation?

 

1 0
replied on March 29, 2022

Did you move LFDS to a new server too?

 

2 0
replied on March 29, 2022

Yes we did - great catch!!!  My LFDS is connecting again - I think that was most of my issue.  My VAR will work with me during the day tomorrow.  Many thanks Miruna!

0 0
replied on March 30, 2022

No problem. The Laserfiche Server reads the location of LFDS from its license and it pings it periodically to double-check its license is valid. The error was saying the Laserfiche Server can't find LFDS, so it can't verify its license hasn't been revoked.

If you move LFDS to a different machine, you'll want to either relicense the Laserfiche server so it gets the new location or add a DNS alias with the old LFDS server name to the new LFDS server so the various Laserfiche apps find it when they check their license.

2 0
replied on March 29, 2022

Hi Randle,

Are you able to work with your Solution Provider for assistance and to open a support case on your behalf if necessary?

The behavior you're describing is strange as locking a repository shouldn't have anything to do with it mounting/unmounting, so something else is likely going on. If you wish to further investigate yourself first, the Laserfiche Server event logs are likely to have more detailed error messages on the mount/unmount issue. You'll find those in Event Viewer under Application and Services logs -> Laserfiche -> ContentRepository -> Service -> Admin

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

Sign in to reply to this post.