Emerson Exchange 365

• Not Answered

DeltaV Operate not opening for more than one user

When a second user tries to open a DeltaV Operate session, it shows and error: Error number -2147212799 (80042201). iFix system not started. While the first user has successfully opened DeltaV Operate.

Other times it shows: Cannot open DeltaV Operate. The Application is already running. You must first close DeltaV operate in order to open it here.

The only way for this to work is to close the other user session.

Have you guys seen this anywhere on your system?

Paulo Alzate

• 1 Jun 2020 10:35 PM
• Cancel

5 Replies

• Andre Dicaire

  

  • 1 Jun 2020 11:09 PM

  On a DeltaV worsktation, there can only be one session of DeltaV Operate. The underlying program name is Workspace, and there can only be one session of Workspace at a time on the Workstation. There are two desktops (DeltaV Desktop and Windows Desktop.) If a user has Operate open on one of these, it cannot be opened on the other. you must close Operate in order to open it in the other desk top.
  
  When a user logs on, and Flex Lock has Auto switch Desktop enabled, the user is presented with the DeltaV desktop. IF they do not have privilege to access the Windows desktop, their only choice is to open Operate. If the previous user was in the Windows Desktop and had Operate Open, and did not close it, then the second user is unable to open Operate.
  
  if the previous user was in the DeltaV Desktop, then the new user will be able to take over the Operate session with his DeltaV privileges.
  
  If you are running an RD Server and attempting to open a Remote Session and you get these types of messages, it is because you have not properly licensed your Remote client and RDS client sessions. In this situation, the client sessions are not allowed to open their own session of Operate and the limit of one concurrent session still applies. The user has to log off of Operate to allow it to launch in another session.

  Andre Dicaire

  • Cancel
• Lun.Raznik

  

  • 1 Jun 2020 11:44 PM

  This indicates that you haven't enabled Remote Terminal Server (RDS) role before you have installed DeltaV.

  • Cancel
• Paulo Alzate

  

  • 5 Jun 2020 3:26 PM

  In reply to Lun.Raznik:

  I tried check on the RDS as everything was normal.
  The issue was resolved by tweeking the Registry and add an iFix delay value.

  • Cancel
• Lun.Raznik

  

  • 5 Jun 2020 4:29 PM

  In reply to Paulo Alzate:

  Would you mind sharing what registry key did you change?

  • Cancel
• Andre Dicaire

  

  • 5 Jun 2020 4:46 PM

  In reply to Lun.Raznik:

  When closing Operate, it takes several seconds for the Workspace process to close. If it is open, it will fail to launch a second instance within the same user session (DeltaV Desktop and Windows Desktop). If moving between desktops, one has to wait to be able to open Operate. So adding a delay to launch iFIX would address the situation where the Operate instance is closing in one desktop, and trying to open in the other, due to a user login.
  
  Before we go off changing registry settings, we should clearly understand the context of use and why this particular change works. What other consequences are there to adding this delay in the registry. Is this the right thing to do? Maybe it is, but further down the line, will this cause other negative behaviors? Can you say Unsupported?
  
  That said, I like the ingenuity to get a resolution. Let's be careful before rushing to hack the registry.

  Andre Dicaire

  • Cancel