Troubleshooting for Asset Builder

Install template Equipment classes

No.

Trouble

Check contents

Troubleshooting method

Failed to install template Equipment classes

The configuration database for the following applications must be the same:

· Assets

· Hyper Alarm Server

Asset Integration

· Hyper Historian

· Hyper Historian Asset

Integration

In the application setting,

perform the identical setting of the databases for the following applications:

· Assets

· Hyper Alarm Server

Asset Integration

· Hyper Historian

Asset Integration

Setting screen

No.	Trouble	Check contents	Troubleshooting method
1.	An error message: "Mitsubishi Electric templates are not correctly installed in the Assets configuration, or Assets configuration is not available in this project. Mitsubishi Electric templates are needed to generate the asset configuration. Please close this dialog, install Asset Builder templates from the menu on Equipment classes of Assets and try again.” is shown.	Assets settings must be available in the project in which you are running Asset Builder.	Open the “Configure Application(s) settings” in Workbench and apply the available settings to Assets.
2.		Check Workbench for preinstalled manufacturer-provided template Equipment classes. Manufacturer supplied template Equipment classes are as follows: “Assets” > “Equipment classes” > “Mitsubishi Electric Templates”	Right-click “Assets > Equipment classes” and run “Install Asset Builder templates”.
3.	An error message: "The selected language is not available in the 'Language Aliasing' configuration. Do you want to add the language to the configuration?" is shown.	The language selected in “Select Language” must be present in “Language Aliasing”.	Click “OK” in the dialog box to register the “Language Aliasing” language during instance creation.
4.	An error message: "The asset path is not in the correct format. Please provide a three-levels asset path (i.e. /Plant Name/Cell Name/Unit Name)" is shown.	The “Assets Equipment Path” has three levels of Assets paths.	Set the “Assets Equipment Path” to the “Three-level Assets” path.
5.	An error message: "Cannot start Asset Builder Task. Could not find file '{0}'" is shown. *%0: File Name	The file specified by the “Import Source” must exist.	In the “Import Source”, set the existing file.
6.	An error message: "The device path is not in the correct format. Please specify the device and (optionally) the folder (i.e. "/Device" or "/Folder/Device")" is shown.	The “MELSEC Device Path” is set to the appropriate format.	If the device name is not preceded by “/”, enter it.
7.	An error message: "Language Aliasing configuration is not available in this project. Language Aliasing are needed to generate the proper language configuration. Please close this dialog, install Language Aliasing in the current project and try again" is shown.	“Language Aliasing” settings are available in the project where Asset Builder will be running.	Open the “Configure Application(s) settings” in Workbench and apply the available settings for “Language Aliasing”.
8.	An error message: "The path does not contain a valid FADB file" is shown.	The Import Source contains an “.fadb” file.	Specify the “.fadb” file in the “Import Source”.
9.	An error message: “Asset Builder license not found. Please contact your Sales Representative to trial and purchase Asset Builder Workbench configuration functionality” is shown.	Asset Builder license is enabled.	Purchase Asset Builder license and activate it on ICONICS Web Licensing(https://licensing.iconics.com)

Asset Builder Task

No.	Trouble	Check contents	Troubleshooting method
1.	Asset Builder Task fails and the log displays an error message about Assets.	Verify that the Assets settings are available.	Open the "Configure Application(s) settings" in Workbench and verify that the application settings in Assets are available.
2.	Asset Builder Task fails and the log displays an error message about Language Aliasing.	Verify that the “Language Aliasing” settings are available.	Open the "Configure Application(s) settings" in Workbench and verify that the Language Aliasing settings are available.
3.		The total number of characters in the path entered in “Assets Equipment Path” and the total number of characters in the Process Automation tag name must not exceed 255 characters.	Enter the total number of characters in “Assets Equipment Path” and the total number of characters in the Process Automation tag name so that it does not exceed 255 characters.
4.	Asset Builder Task fails and the log displays an error message about Mitsubishi Electric FA.	Verify that the Mitsubishi Electric FA setting is available.	Open the “Configure Application(s) settings" in Workbench and verify that the application settings for Mitsubishi Electric FA are available.
5.	Asset Builder Task fails and the log displays an error message about the FADB file (ENVIRONMENT.csv, TAGMAP.csv).	The FADB file has been successfully output from GX Works3 and has not been edited.	Generate FADB again from GX Works3 and execute Asset Builder again.
6.		The version of GX Works3 that output the FADB file must be Ver. 1.077F or later.	Generate FADB from GX Works3, version 1.077F or later, and execute Asset Builder again.
7.	Asset Builder Task fails and the log displays an error message about the FacePlateList.csv file.	The FADB file has been successfully output from GX Works3 and has not been edited.	Generate FADB again from GX Works3 and run Asset Builder again.
8.		The version of GX Works3 that output the FADB file must be Ver. 1.077F or later.	Generate FADB from GX Works3, version 1.077F or later, and execute Asset Builder again.
9.		The user operating Workbench must have read/write permissions on the path selected in the “Project Output Folder”.	The user operating the Workbench assigns read/write permissions to the path selected in the “Project Output Folder”.
10.		Existing FacePlateList.csv is not opened by another application.	Close all applications that open FacePlateList.csv.
11.	Asset Builder Task fails and the log displays an error message about generating output paths.	The user operating Workbench must have the permission to create folders in the path selected in the “Project Output Folder”.	Assign the user operating the Workbench permission to create a folder in the path selected in the “Project Output Folder”.
12.	Asset Builder Task fails and the log displays an error message about copying screen files.	The template screen file must exist in: ”C:\ProgramData\ICONICS\AssetBuilder\Templates\Process Automation Version1”.	If the template screen file does not exist in: “C:\ProgramDat\ICONICS\ AssetBuilder\Templates\Process Automation Version1”, install GENESIS64 again.
13.	Asset Builder Task fails with an error message: "CPU Type mismatch between the device '{0}' ({1}) and the device specified in the FADB file ({2}). Please check the FADB file and try again" is shown. * %0: Device Name %1: CPU type of the specified device %2: CPU type of FADB file	The MELSEC CPU type specified in the “MELSEC Device Path” must match the CPU type in the FADB file.	In “MELSEC Device Path”, select the same CPU type like the one in the FADB file.
14.	Another issues than those listed above or cases that cannot be resolved as written above.	-	Get the “Workbench Point Manager”. Out-proc Service logs in TraceWorX and reviews the logs.