PCS and MGC issues

Issue Number

Description

IMS 3456786

After upgrading to PCS 8.1.2 on a node that has both System Platform 2023 R2 or 2023 R2 SP1 and Recipe Management 2023 R2, the RMPEventSvc service does not start and you are not able to view Recipe Management events in the OCMC Logger. The Logger also shows continuous warnings related to the PCS agent.

Workaround: On the server running System Platform and Recipe Management 2023 R2, modify the file aaEventsEventService.aaSDEF by adding the <LaunchAssembly> property.

Full path of the aaEventsEventService.aaSDEF file:
C:\Program Files (x86)\Common Files\ArchestrA\Services\aaEventsEventService.aaSDEF

1. Add <LaunchAssembly> property immediately after the <BinaryName> property.

   <LaunchAssembly>RMEventsEventServiceHost\RMEventsEventServiceHost.exe</LaunchAssembly>

2. After you update the file, reboot the machine.

IMS 2829309

If you are using the connected experience for security and you close the browser window where you signed in when starting an OMI ViewApp, you may see one of these symptoms when signing out of the ViewApp:

• The sign out option may not appear

• No users may show as signed in

• If there are multiple connected users, you may be able to sign out as a different user

• You may see a message saying that sign out did not succeed even though it did

  Workaround: Either have the System Administrator change the authentication browser option in the configurator (found under Common Platform > System Manager Server > Advanced > Authentication) to use the embedded browser pop-up dialog box, or keep the sign-in browser window open the entire time you are using the OMI ViewApp. Sign out then functions correctly.

IMS 2658043

In an installation which uses workgroups and has MultiCast-DNS enabled, upgrading from an earlier version to PCS 8.0 (for example, during an upgrade to System Platform 2023 R2) causes an issue with the PCS certificate. This causes secure communication with the SMS to fail. The SMS falls back to using non-secure communication. This causes error messages to be written continuously to the logger on all remote nodes.

Workaround:

Perform the following procedure on all nodes, including the SMS node:

3. Open the Configurator and, under Common Platform, select System Management Server.

4. Select No System Management Server configured and select Configure.

5. Close the Configurator and reboot the node.

6. After the reboot, open the Configurator again and set the System Management Server back to the correct selection: This machine is the System Management Server on the SMS and Connect to an existing System Management Server on all other nodes. Select Configure.

7. Close the Configurator and reboot the node.

IMS 1586624

The logger will repeatedly display error/exception messages from the "view" component if a multi-galaxy pairing is broken for any reason, and then an InTouch HMI Managed ViewApp is launched that contains cross-references to tags in another galaxy.

Workaround: Since the exceptions are caused by the broken galaxy pairing, simply pair the galaxies again. The exceptions will no longer be logged.