DIAdem

cancel
Showing results for 
Search instead for 
Did you mean: 

"Cannot load the file *.ATF with the loader 'ATFX'".

Solved!
Go to solution

Hello,

Every 10 or so ATF files, I get the following error:

CannotLoadATFError190204.png

 

The error message is not so informative.  Since I can't open the file, I have no idea what hangup is.  Any ideas on how to solve this one?  The data is not something I can post publicly, but may be able to share on an individual basis.

 

Thanks in advance.

 

 

 

 

0 Kudos
Message 1 of 7
(3,373 Views)

It is very hard to find errors in ATF classic (*.atf).

I would strongly suggest to switch to ATF XML (*.atfx) which has less issues in the structure itself. (XML parser ist more common)

 

The following script can be used to create a logfile

C:\temp\read_atf_log.txt.readerlog

that contains the interptreted data till the first fatal error.

 

Option Explicit

dim fileToCheck : fileToCheck = "C:\temp\notworking.ATF"
dim logfilePath : logfilePath = "C:\temp\read_atf_log.txt" ' will create a file read_atf_log.txt.readerlog

dim param : param = "<filename readonly=""yes"">" & replace(fileToCheck, "&", "&amp;") & "</filename><logfile>" & logfilePath & "</logfile>"
dim store : set store = navigator.ConnectDataStoreByParameter("ATFX", param)

' hopefully C:\temp\read_atf_log.txt.readerlog can be used to determine the issue
0 Kudos
Message 2 of 7
(3,324 Views)

Thanks for posting this.  I ran the ATF loading script and generated the log file, but as mentioned it's still not clear what's going on and I don't have a way to modify the existing ATF file anyway.  I have tried to load ATFx files from the same lab in the past without success, so I will try to get an example of one of those that I can share.

0 Kudos
Message 3 of 7
(3,308 Views)

Can you post the last lines of

C:\temp\read_atf_log.txt.readerlog

Normally they show if end is reached or they may point to the issue.

0 Kudos
Message 4 of 7
(3,302 Views)

Hi Andreas,

Below is the last 35 lines of the report.  Let me know if you'd like me to post more or share the log file with you.

 

 

INSTELEM Quantity
Id = 18190;
iName = "T_FAC_CLT_OUT";
iDescription = "Facility Tower Water Out Temperature";
iNormcode = 9217;
rUnit = 17;
iDataType = 3;
iSize = 0;
iMainNr = 8;
iBlockNr = 24;
iBlockCnt = 0;
iSubblNr = 0;
iWgNr = 0;
iWgInd = 0;
iSystemName = "v_T_FAC_CLT_OUT";
iDefaultMqName = "T_FAC_CLT_OUT";
iCustom1 = UNDEFINED;
iCustom2 = UNDEFINED;
iCustom3 = UNDEFINED;
iCustom4 = UNDEFINED;
iCustom5 = UNDEFINED;
iLastUpdateUser = "PO Import";
iUpdatedBy = "A";
iLastUpdate = "20181009163704";
QuantityGroup = 5;
QuantityGroup*** Wrong Attribute ***
ENDINSTELEM;

INSTELEM Quantity
Id = 18450;
iName = "C_i60_u";
iDescription = "
Error found on ATF-File.
Status=1

 

 

Thanks,

Chris

0 Kudos
Message 5 of 7
(3,297 Views)
Solution
Accepted by topic author Chris_P_SD

I would assume that this 

Id = 18450; 
iName = "C_i60_u"; 
iDescription = "

I assume that the parser  stopped because of an invalid character in the description of the quantity.

Be aware that ATF is not capable to store unicode characters.

 

Maybe you can ask to switch the process to ATFX which does solve those issues.

Message 6 of 7
(3,294 Views)

Opening the offending *.ATF file in Notepad++ and replacing the "µ" characters with "mu" did allow this ATF file to load in DIAdem.  Strangely, the µ existed in other *.ATF files in the past that did load successfully:

 

190204_A µ character loaded.PNG

 

 

We will evaluate migrating to *.ATFX files in the future.

 

Thank you to Andreas and company for support with this.

Chris

Message 7 of 7
(3,260 Views)