Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

Error Importing CSV Tag Record N: {problem}? When Importing CSVs

Last Update: 11/12/2018

In the warning message, N is the number of the tag record in which the problem was found.

1. ' ' is not a valid tag name.
2. '_tagname' is not a valid tag name.
3. Device address 'W2,Short,0,R/W,100,,,,,,,,,,,' contains a syntax error...where CSV fields beyond the one meant for the device address are posted in the "device address" part of the warning message).


1. The tag name ended with a period. The server treats a period as a delimiter telling it that there is a tag group. If a tag name of "Data.Tag1" is created, the import will create a tag group named "Data" with a tag inside named "Tag1". If a name of "Data." is created (with a period at the end), the server will create a tag group called "Data" and then post "' ' is not a valid tag name." It will not create a tag, because there are no characters to specify a tag name after the period.
2. The tag name begins with an underscore. Only system tags are allowed to have names starting with underscores.
3. The tag name has a double quotation mark.


1. Remove any periods from the ends of tag names.
2. Remove any underscores from the beginnings of the tag names.
3. Remove any double quotation marks from the tag names.

Note 1:
In server versions prior to 4.280.435.0, the tag indicated as being in error was not necessarily the tag that is Nth in the CSV file. This is because when the server imports the CSV file, it sorts the tags in ascending order before adding them to the tag database. Those prior server versions posted the sorted record number instead of the record number as found in the CSV file. When using one of the prior server versions, users can find the error by sorting the CSV file by tag name or by upgrading to the current server version so that the record number as found in the CSV file is posted in the warning message. Upgrades within the 4.x version series of KEPServerEX are at no charge.

Note 2:
The tag record number given in the message is one less than the line number in the CSV file, because line 1 of the CSV file is a header that isn't counted as a record. If the warning message calls out line N, then look for the error in line N+1.

Related Products