Emerson Exchange 365

• Not Answered

DeltaV 14.3 Simulate Standalone: Unable to run recipes in BOI Error Message "cannot communicate to phase logic (Unsol)"

Please note We have a working DeltaV configuration that is in great shape and running awesome on the Plant system. However when we import this configuration to our simulation system, the status of the Phase Server Status (DeltaV) is always BAD. (screenshot below). I am not sure why all those phases are showing up as Bad because on the Production System they are perfectly Ok. I have imported other databases and I had the same issue. I have created brand new databases and still the same problem. All the phases have been verified and have no errors. I am not sure whether DeltaV V14.3 Standalone Simulate allows to run and simulate Recipe. Initially I thought it could be licensing issue however on license verification, it says "OK" for current configuration.

 Procedure we followed

1. Create a brand new database V14.3 
2. Import Batch Configuration
3. Assign the Unit and Its modules & phases to a Node. (Download Unit & Phases)
4. Enable the Batch Executive and assign the area associated with that Node. (Download Batch Executive, Download Equipment,, Download Unit and all associated Phases again)
5. Start the batch executive and DeltaV Phase server Status is always "BAD". (screenshot attached)

Appreciate any feedback Thanks

Please see the error log from windows:

• BatchExecutive

hbhullar

• 20 Feb 2021 8:29 PM
• Cancel

3 Replies

• MAXIM MICHEL

  

  • 19 Jan 2022 10:27 AM

  In the ProPlus, open the D:\DeltaV\DVData\Download\USERT.scr file in Notepad. Check if DVBATCHADMIN account is present. If the account is present, check if the user is disabled or locked out (in Computer Manager>Local Users and Groups if in a workgroup, Active Directory Users and Computers if in a domain).
  If it is missing, perform the following:
  
  1. From Database Administration of Proplus, create a new blank database.
  2. Make that blank database the Active one, then create a FHX export from DeltaV Explorer.
  3. Make your old database Active in Database Administration.
  4. Import the blank database on top of your current database. Download setup data the ProPlus.
  5. It will re-populate the missing DVBATCHADMIN account.
  
  This worked for me.

  • Cancel
• Pat Grider

  

  • 7 Mar 2023 12:41 AM

  In reply to MAXIM MICHEL:

  Me too! I think my mistake was that I imported the Production database into my (new) Sim Standalone *before* updating System Preferences to enable Batch, so that perhaps the DVBATCHADMIN account didn't get set up as a DeltaV account during the import. I'm not sure if this is what happened or not. But, I was able to repair the problem by following Maxim Michel's 5-step procedure.

  • Cancel
• Purnendu Saptarshi

  

  • 28 Nov 2023 2:25 PM

  I had similar issue, however, the difference was that the BEX status was GOOD and phase status BAD. Tried/Checked solutions here, and they didn't really apply.
  After some troubleshooting, I boiled down to 2 main options:
  1. Corrupted Installation of DeltaV
  2. Database issues.
  
  Solution followed and thoughts:
  1. Unassigned everything from BEX (recipes and areas)
  2. Disabled BEX
  3. Performed Extended Database clean
  4. Reassigned everything back and downloaded.
  
  This resolved the issue.
  
  
  Additional comments:
  1. I may not have had to unassign/assign work. But I did it organically as it was the easier/quicker thing to do prior to Extended database clean.
  2. Performing extended database clean might just work if that is performed.

  Purnendu Saptarshi

  Automation Engineer | Skellig Automation US LLC | Greater Boston Area, MA

  • Cancel