PI Event Frames Generatorのサービス追加エラーについて

Adding the answer text translated to English by Google. I had the same issue where our production tags were transferred to a test system, and then interfaces were installed new. The configuration of the Syncade batch interfaces did not match the production system (Interface ID and PointSource did not match). I had to remove the services, reconfigure them to match the production system, and recreate the services. They then ran as expected.

After checking the log and setting contents, the cause was found.   When you create a PIEFGEN interface It seems that PI Points such as "PIEFGen_X_YYYYYYYYY" are automatically created.   When I try to create a second PIEFGEN interface It seems that the PI Point of "PIEFGen_X_YYYYYYYYY" already exists and could not be created. PIEFGEN2> 2> 1> Failed to add PIPoint: 'PIEFGen_1_DeviceStatus'. COM Error [0x80040434]: Failed to create point on server. [-10550] Tag Already Exists in Table (tag: PIEFGen_1_DeviceStatus)   The Interface ID seems to be used for the PI Point name created automatically such as "PIEFGen_X_YYYYYYYYY". It seems that the second interface was not created normally because the Operational Settings were the following settings. First interface Interface ID: 1 PointSource: PIEFGEN1 Second interface Interface ID: 1 PointSource: PIEFGEN2   So I changed the settings of the second interface to the following and re-created the service so that it works properly. Second interface (after change) Interface ID: 2 PointSource: PIEFGEN2 With the above settings, PI Point “PIEFGen_2_DeviceStatus” has been created automatically.

Adding the answer text translated to English by Google. I had the same issue where our production tags were transferred to a test system, and then interfaces were installed new. The configuration of the Syncade batch interfaces did not match the production system (Interface ID and PointSource did not match). I had to remove the services, reconfigure them to match the production system, and recreate the services. They then ran as expected.

After checking the log and setting contents, the cause was found.   When you create a PIEFGEN interface It seems that PI Points such as "PIEFGen_X_YYYYYYYYY" are automatically created.   When I try to create a second PIEFGEN interface It seems that the PI Point of "PIEFGen_X_YYYYYYYYY" already exists and could not be created. PIEFGEN2> 2> 1> Failed to add PIPoint: 'PIEFGen_1_DeviceStatus'. COM Error [0x80040434]: Failed to create point on server. [-10550] Tag Already Exists in Table (tag: PIEFGen_1_DeviceStatus)   The Interface ID seems to be used for the PI Point name created automatically such as "PIEFGen_X_YYYYYYYYY". It seems that the second interface was not created normally because the Operational Settings were the following settings. First interface Interface ID: 1 PointSource: PIEFGEN1 Second interface Interface ID: 1 PointSource: PIEFGEN2   So I changed the settings of the second interface to the following and re-created the service so that it works properly. Second interface (after change) Interface ID: 2 PointSource: PIEFGEN2 With the above settings, PI Point “PIEFGen_2_DeviceStatus” has been created automatically.