Troubleshooting the Excel import operation

You do not have to check every graphic display in an application to verify that text was imported correctly. If errors occurred while importing text, they are displayed automatically from a log file called ImportErrors.txt in the Strings folder. The folder is
C:\Users\Public\Public Documents\RSView Enterprise\Strings
.
Each time errors occur while importing text into an application, the error file is overwritten.
The import feature checks in the spreadsheet for these items in the order they are listed:
  1. language columns whose language does not exist in the application
  2. component types that are invalid
  3. server names that do not exist in the application
  4. component names that do not exist in the application
  5. descriptions that do not exist in the application
  6. duplicate string references that are pointing to strings that do no exist in the spreadsheet
If errors occurred while importing text, or if the import was canceled, a message appears in the diagnostics list, and in the diagnostics log file. As well, a message is logged to the file ImportErrors.txt.
Error Messages
Errors occurred while importing strings from <
ExcelFile.xls
>
One or more errors have occurred in the import operation. This message is logged to FactoryTalk Diagnostics.
String import was interrupted by the user.
The import operation has been interrupted or cancelled by the user. This message is logged to FactoryTalk Diagnostics and to the file ImportErrors.txt.
When any of the following errors occur, the message 'Errors occurred while importing strings from <
ExcelFile.xls
>is logged to FactoryTalk Diagnostics, and the error message in bold above the description is logged to ImportErrors.txt.
Unable to import strings as Microsoft Excel is not installed.
This message is logged to ImportErrors.txt when the user has pressed the Finish button in the Select Files step of the String Import Export wizard, but does not have Microsoft Excel installed on the local computer. The import will not be started.
<RFC1776> does not exist in this application. No strings for this language were imported.
The language associated with one of the columns in the spreadsheet does not exist in the application. None of the strings for the language will be imported into the application, but the import will continue.
<Component Type> is not valid. No strings for this component were imported.
The component type of a string in the spreadsheet is not valid. None of the strings for the languages associated with the string definition will be imported into the application, but the import will continue.
<Server Name> does not exist in this application. No strings for this server were imported.
The server name for a string definition in the spreadsheet does not exist in the application. None of the strings for the languages associated with the string definition will be imported into the application, but the import will continue.
<Server Name> is unavailable. No strings for this server were imported.
The server name for a string definition exists in the application, but the HMI server being referenced is not available. None of the strings for the languages associated with the string definition will be imported into the application, but the import will continue.
<Server Name>_<Component Type>_<Component Name> does not exist in this application. No strings for this component were imported.
The component name for a string in the spreadsheet does not exist in the application. None of the strings for the languages associated with the string definition will be imported into the application, but the import will continue.
<Server Name>_<Component Type>_<Component Name>_<Description> does not exist in this application. No strings for this description were imported.
The description for a string in the spreadsheet does not exist in the application. None of the strings for the languages associated with the string definition will be imported into the application, but the import will continue.
<Optimized Duplicate String Reference> is pointing to a string that does not exist in the spreadsheet. No strings with this optimized duplicate string reference were imported.
An optimized duplicate string is referencing a string that does not exist in the spreadsheet. The string will not be imported into the application, but the import will continue.
Unable to save <DisplayName>. No strings for this component name were imported.
A graphic display or global object cannot be saved, but the import will continue..
Unable to import strings into <HMIServerName> as the currently logged in user does not have write access to the area.
For FactoryTalk View SE network distributed applications, the currently logged in user does not have Common\Write security access to the area that contains the HMI server whose strings are being imported. No strings referencing this HMI server will be imported. The import will continue trying to import strings for any remaining HMI servers in the application.
Unable to import strings as the currently logged in user does not have write access to the application.
For FactoryTalk View SE local and ME applications, the currently logged in user does not have Common\Write security access to the application. No strings for the application will be imported.
Unable to import one or more strings as one or more cells were not formatted as text or numeric values.
A server name cell, a component type cell, component name cell, a description cell, or a reference column, is not formatted as a string or numeric value. None of the language switchable strings on that row will be imported into the application, but the import will continue.
Unable to import one or more strings as one or more header cells were not formatted as text or numeric values.
A header cell is not formatted as a string or numeric value. The import will be stopped.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal