Locked iModel that cannot be unlocked. #20
Unanswered
PeterJBassett
asked this question in
Q&A
Replies: 2 comments 4 replies
-
Hello Akshay
I’m sorry, but deleting the cached bim-lock file cleared the lock, and I didn’t think to keep a copy.
Peter
From: Akshay Madhukar ***@***.***>
Date: Tuesday, 6 February 2024 at 19:52
To: iTwin/community ***@***.***>
Cc: Peter Bassett ***@***.***>, Author ***@***.***>
Subject: Re: [iTwin/community] Locked iModel that cannot be unlocked. (Discussion #20)
CAUTION: EXTERNAL EMAIL. Don't click on links or open attachments unless you recognize the sender and know the content is safe.
Do you still have the bim-lock file that was causing the issue?
—
Reply to this email directly, view it on GitHub<#20 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOUUAYTZZFYSQBSWF7C4MBLYSKCXRAVCNFSM6AAAAABCPKVWAGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGOBXGMYTS>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello I am working on the FutureOn iTwin connector used by Shell. There is a problem that one of Shell's iModels is locked, and the usual methods of unlocking are not working.
The iModel is:
ContextId: c9e70df2-1133-44ae-9018-e2d4bb682fc6
iModel Id: 833f4130-22fa-459c-ac80-e9a8ea7863de
Attempting to sync to this iModel raises the following error log:
The connector is using the following iTwin versions:
Beta Was this translation helpful? Give feedback.
All reactions