Emerson Exchange 365

Graphics Studio-Edit lock required

I have suddenly started having a ton of problems with Graphics Studio. Displays won't open "Failed to open Item"... then I close it since it's just spinning circle. That's when i get "Edit lock required".

I have restarted Graphics Studio. Rebooted the server. I check the Active Connections in DeltaV Live Administration.. nothing seems to be working. I was able to sometimes get it to work by unpublishing , but that doesn't seem to last long. The next time i open it will then give me the "edit lock required" right away and it just spins.. waiting "Loading...."... 

TreyB

• 24 Jan 2024 5:16 PM
• Cancel

4 Replies

• Matt Stoner

  

  • 24 Jan 2024 5:58 PM

  What DeltaV Version are you using and what Workstation hotfix is loaded (i.e. DeltaV_15LTS_WS_01_CSS and can be found in the Help About on DeltaV explorer and the box below the DeltaV version/build info)?

  • Cancel
• TreyB

  

  • 24 Jan 2024 6:10 PM

  In reply to Matt Stoner:

  DeltaV_1431_WS_31_CSS
  DeltaV v14.3.1 Build 7288

  • Cancel
• Matt Stoner

  

  • 24 Jan 2024 7:26 PM

  In reply to TreyB:

  You might consider getting the latest which is WS_34 and maybe some fixes between these hotfixes addresses the issue you are seeing.

  • Cancel
• Andre Dicaire

  

  • 25 Jan 2024 12:12 AM

  In reply to TreyB:

  Have to agree with Matt. I'm also running WS31 and have seen a couple of edit locks hit me, Logging a call will start with recommendation to apply latest hotfix. Although I'd like to know what the issue is, investigating an older version hotfix will still require GSC to reproduce on the latest Hotfix. If they can't reproduce, that will be your fix. So why delay the inevitable?
  
  The problem may still persist at WS34, an in this case, you can better help GSC reproduce. Ideally, if you log a call, the GSC engineer would confirm if the issue is a known issue and marked as resolved in WS34. You can review the Software Release update KBA for resolved and known issues. But in the end, your best bet is to apply the hotfix and see if that helps. But if there is no mention of any similar issue being recorded/resolved between WS31 and WS34, the issue may still be there, but applying the hotfix reset something and it goes dormant.
  
  My take is you log the call, confirm release notes indicate a resolution or not, provide GSC with appropriate logs from your system if they request them, and apply WS34. Or skip to applying WS34 and only log a call with GSC if the problem is still there. I like option one because it more completely frames the issue and provides more information to investigate pre and post WS34. But Option B puts you in control, at least for now.

  Andre Dicaire

  • Cancel