ASCII error code

[riccardo.crociani]

Hello,

we are facing an error while importing a file by the ascii mangar on WinCC OA 3.15 Patch 005.

the process terminates with the error code -50

In the file WCCOAascii_info.log we get:
...
...
...
DbArchiveInfo (93621): Values for R000035AAND1_1_J_POR_MOUT001_KFIMP01.VALORE_RAW sent.
DbArchiveInfo (93623): Values for R000035AAND1_1_J_POR_MOUT001_KFIMP01.LOGCMD sent.
DbArchiveInfo (93625): Values for R000035AAND1_1_J_POR_MOUT002_KFIMP01.VALORE sent.
DbArchiveInfo (93627): Values for R000035AAND1_1_J_POR_MOUT002_KFIMP01.VALORE_RAW sent.
DbArchiveInfo (93629): Values for R000035AAND1_1_J_POR_MOUT002_KFIMP01.LOGCMD sent.
Waiting for last response from eventmanager...
Scanning of file /home/winccoa/opt/CT2/dplist/CT2-2017_09_29_09_26_27.dpl is finished (-50)
End of Program



In the file WCCOAascii_log.log we get:

WCCOAascii (0), 2017.09.29 09:50:39.277, SYS, INFO, 1, Manager Start, PROJ, CT2, V 3.15 - 3.15 platform Linux x86_64 linked at Jul 25 2017 22:07:38
WCCOAascii (0), 2017.09.29 09:50:39.278, SYS, INFO, 3, Trying to connect to (SYS: 0 Data -num 0 CONN: 1) @ rnesa.local:4797
WCCOAascii (0), 2017.09.29 09:50:39.278, SYS, INFO, 4, Connected to (SYS: 0 Data -num 0 CONN: 1) @ localhost (::1)
WCCOAascii (1), 2017.09.29 09:50:39.391, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAascii (1), 2017.09.29 09:50:39.391, SYS, INFO, 3, Trying to connect to (SYS: 2 Event -num 0 CONN: 1) @ rnesa.local:4898
WCCOAascii (1), 2017.09.29 09:50:39.391, SYS, INFO, 4, Connected to (SYS: 2 Event -num 0 CONN: 1) @ localhost (::1)
WCCOAascii (1), 2017.09.29 09:50:39.392, SYS, INFO, 102, Waiting for user names/passwords
WCCOAascii (1), 2017.09.29 09:50:39.393, SYS, INFO, 103, User names/passwords initialized
WCCOAascii (1), 2017.09.29 09:50:45.343, SYS, INFO, 2, Manager Stop
doAsciiIn returned error code: -50


from the help I can see the error meaning: (-50) DpIdentifier for attribute does not exist.

But how can I detect the datapoint that generates the error?
Does the ascii import process stop immediatly as soon as it reaches the wrong line, or does it complete the import skipping only the wrong line ?

Thanks for the help

Riccardo

[leoknipp]

If you want to find the cause for the error you have to look at the complete log information in the file WCCOAascii_info.log.
The ASCII manager normally gives the information for an error directly at the line where the error occured.

Best Regards
Leopold Knipp
Senior Support Specialist

[riccardo.crociani]

Hi Leopold,

so in my case does the error come from this line (last line of the file WCCOAascii_info.log) ?

DbArchiveInfo (93629): Values for R000035AAND1_1_J_POR_MOUT002_KFIMP01.LOGCMD sent.


What could I check to fix the error ?

Thanks

[leoknipp]

No, the information for the error you see in WCCOAascii_info.log in the last line is only a summary.
The error you should find somewhere in the file. You could search for the keyword "error" maybe you find the entries.

Best Regards
Leopold Knipp
Senior Support Specialist

[riccardo.crociani]

Hi Leopold,
I've found no entry in the logs looking for "error".

The only line with "error" word is that one:
doAsciiIn returned error code: -50

Other ideas?

Thanks,
Riccardo

[Gertjan van Schijndel]

Your error message should look something like this:
DpIdentifier ztesterr for attribute ExampleDP_DpId_01.:_original.._value does not exist!
DpValue (6): Values for ExampleDP_DpId_01. sent.

Where:
'(6)' is a line number
'ExampleDP_DpId_01.' is the datapoint element to be written
'ztesterr' is the datapoint element value

[riccardo.crociani]

Hi Gertjan,

you are right, I've found the exact line by searching for the error string described in the help.


Do you know anything about my second question?

"Does the ascii import process stop immediatly as soon as it reaches the wrong line, or does it complete the import skipping only the wrong line ?"

Thanks.
Riccardo

[Gertjan van Schijndel]

The import process does not stop on errors, but continues to process the remaining part of the file.

Otherwise you the error message would be more or less directly above the last summary line.