Type Conflict in File - TestStand 3.0

Hi,
I am having a "Type Conflict in file" error in TestStand 3.0. We have a system in production that used to have 8 instruments; the GPIB addresses of these instruments are station globals defined in TestStand. Ever since this system was created, no new instrument was added and all the sequence files created had the same station globals; however recently I added a new LCR and therefore I added a new station global.
During Development I did not see the problem since I had to manually change the station globals in order for my software to work; however now that I released it, I changed the Station Globals for the system and therefore I am affecting all the old sequence files.
This is happening with TestStand 3.0 which is a very old version. When running the old sequence files manually a dialog box pops up asking if I want to use the currently loaded type or to use the type from the sequence. By selecting either-or the problem goes away and the sequence is now able to run normally. I am wondering if there is a way to do this programmatically or if there is any configuration that I can set so that It chooses one of these two options by default.
I read that TestStand 4.1 has an option inside the Station Options->Preferences that I believe fixes this kind of problem. Please let me know if there is something I can do in TestStand 3.0
Thanks in advance
Attachments:
TESTSTAND_FILE_CONFLICT.JPG ‏39 KB

Hi,
I think that you can avoid this conflict in TestStand 3 :
- Define a newer version number of your type (if the version was 1.0.0.0, set the new version to 1.1.0.0) : Type Properties --> Version.
- In the version tab, set the option "Use the definition that has the highest version number".
Now the type in your StationGlobals should be newer than the type in the sequence files.
When you load a sequence file, TestStand will update automatically the type in your sequence file (if you open the file in the sequence editor, TestStand indicates that the file should be saved, because it was modified to update the type).
Hope this will work for you.
Bruno

Similar Messages

Type conflict error when using TS_EngineGetSeqFile

I was trying to use function TS_EngineGetSeqFile to load a sequence file build in TestStand 4.0, and I got a OLE error showing me that I have a type conflict with "CommonResults". Does anyone know how to solve this problem??

Hi huizhong,
The type conflict dialog you are seeing is evidence that the copy of CommonResults (an NI-Installed type) in the sequence file has the same version but different settings than the currently loaded CommonResults type definition. CommonResults
is stored in almost all of the built in TestStand type palettes which
automatically get loaded when you open TestStand. Because of this, it
becomes a part of the global type usage list in the Engine. If you
didn't make any changes to CommonResults yourself, it is likely you have inherited a type virus from somewhere and I suggest you take measures to correct the problem.
A
type virus can spread when you tell TestStand to resolve a type
conflict by using the version from the file you are currently opening
(as opposed to the currently loaded type in the global type usage
list). Once the "new" type is copied over to the type palettes, it will
then get loaded every time TestStand runs. At this point, if you open
up more files that use this same type and choose to use the currently
loaded type when the type conflict dialog shows, TestStand will copy
the "new" version into the file - thus the spread or viral like
behavior.
In order to correct the problem, you can either:
Manually open each and every infected file and replace the invalid type with the valid type or...
Use the Type Differ tool that I wrote to inspect each file pair and merge the conflict automatically
I
realize that using the Type Differ at this point is still "manual" in
the sense that you must open each file pair and merge the conflict, but
hopefully in your case there aren't that many affected files. To that
end, I am working on a Batch version of the Type Differ that can diff
and merge entire directory structures automatically. Let me know if you
are interested in using such a tool and I will post a link when
development has reached a beta version.
Regards,

TestStand 4.0 reportgen_html.seq Type Conflict

We have converted from TestStand 3.5 to TestStand 4.0. We had created a custom reportgen_html.seq in TestStand 3.5 which we copied over to the TestStand 4.0\Components\User\Models\TestStandModels directory and updated using the Update Sequence Files utility (which is nice by the way). Everything works fine until we try enabling on the fly report generation. Then we get the following error when we run any sequence using single pass:
Details:
Type 'NI_BatchTestSocket' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the file with the type conflict in the Sequence Editor and resave it.
The sequence file 'C:\Program Files\National Instruments\TestStand 4.0\Components\User\Models\TestStandModels\reportgen_html.seq' could not be loaded.
Error Code:
-17329; Invalid type - conflicts with an existing type.
Location:
Step 'Process Step Result' of sequence 'SequenceFilePostResultListEntry' in 'SequentialModel.Seq
If we open the \User copy of reportgen_html.seq prior to running a sequence, the error does not occur. If we view the sequence file types for the \User copy of reportgen_html.seq, the Usage column shows reportgen_html.seq twice, which is a surprise and an indication that the \NI copy of reportgen_html.seq is involved. If we rename the \NI copy of reportgen_html.seq and restart TestStand, we can run without errors without having to open the \User copy first.
We had thought that if a copy of reportgen_html.seq was in \User, then the \NI copy would not be loaded or used at all, but it looks like TestStand is trying to load both the \NI and the \User sequences. Is that how it is supposed to work? If so, it seems like we have to modify files under \NI to avoid the error. It is our understanding that we really don't want to change anything under \NI so that future versions of TestStand won't stomp the changes.
Hans

Hi Hans,
It looks like you are having two problems. The first appears to be a type conflict. You can resolve this by opening the file in TestStand and saving it. The update utility will update the files to the 4.0 format, but it won't necessarily fix any custom types.
The second problem you are experiencing is because TestStand is still loading the reportgen_html.seq file from the NI directory. I would assume that you are still loading one of our process models from the NI directory. The process models have a relative path so they will find the reportgen_html.seq file in the NI side first. Renaming that file fixes your problem because the file is not found in the local directory (which I would assume is your first search directory) but is instead found in the User directory. If you copy everything from the NI directory to the User directory and use the user files, then everything should be taken care of for you.
Matt M.
NI

Type conflict where type not found in sequence file

Hi,
from a central master sequence, I am starting several sequences from other sequence files in new executions. These sequences have individual types as input and output parameters, the types being defined within these sequence files.
The master sequence only knows the names (as strings) of these types and when I do a "Find/Replace in files" in the master sequence file looking for those types, they are not found.
However when I change one of the types in its respective sequence file while I have the master sequence file open, the master sequence file is shown with an asterisk and later I get a type conflict if the settings is to "Never allow automatic type conflict resolution". This is fairly awkward since the master sequence file is supposed to be password protected and no-one should have to touch it in a project.
What can cause this behavior?
Apparently, usage of these types spread around through all sequence files although they do not have any need for using the types from other files.
Is it possible that it makes a difference whether the type was first defined in a type palette file or directly in a sequence file?
Best regards,
Peter

Peter,
using the data type as parameter in another sequence file will include the type definition in the calling sequence file, therefore changing it. I am not sure why the Find/Replace tool does not display it, but it shows up in the types palette of the file.
When the data type is changed, it will result in a type conflict....
So when trying to reproduce the issue with TS 2010, i receive an dialog for resolving type conflict when setting to never do an automatic resolve...
Nevertheless, the calling sequence must be updated for sure if a used type is changed.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

File datalog type conflict???

Bonjour, j'ai quelques soucis sur Labview dont je n'arrive pas a résoudre!!!
J'ai réaliser un vi qui permet de lire des données dans un fichier .rdt. Par contre, j'ai le code d'erreur 71 "File datalog type conflict" qui s'affiche et je ne sais pas comment faire!!
Est ce que vous pouvez m'aidez svp??
Cordialement.
Murat.
Attachments:
Lecture donnÃ©es RÃ©sultats.vi ‏20 KB

Bonjour,
Il semblerait que ce soit un problème d'extension de fichier. Veuillez vérifier votre fichier.
PS: éviter de poster la même question à différents endroits. Merci.
http://forums.ni.com/ni/board/message?board.id=170&message.id=250333
Cordialement.

What does LabVIEW mean by "Error 71: File Datalog Type Conflict"

What does LabVIEW mean by "Error 71: File Datalog Type Conflict" (Hex code:47)
Thank you.

Please provide us further information on when you are getting the error and what the functionality of the VI is. That would help us to troubleshoot your issue.
Is the error caused by a similar situation as the one descibed in this KnowledgeBase?
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions

Type conflict in OI

Hello,
I have several sequence files that make use of sequences in one common sequence file. There are two container types defined in that common sequence file (not, unfortunately, in a type INI file, I inherited it that way).
When I try to start the master sequence, that starts all others, from an Operator Interface (this is the full-featured MFC example coming with TestStand 4.1), then I get a type conflict for both these types and the recommendation to open the conflicting files in the sequence editor and resave them.
The sequence editor does not show any type conflicts. Resaving the files does not remove the error in the Operator Interface.
Any suggestions? (this is all TestStand 4.1).
Best regards
Peter

Peter,
i take it that both types are defined in the same (*.seq) file. The dialog tells that there are more than one file involved in the conflict. Is that correct?
Is it possible, that the UI loads an older version of the sequence file by default as well?
What is the general setup in the UI when the conflict occurs?
Maybe you can attach some screenshots of the dialog in order to clear things a bit up.
thanks,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Type conflict in deployment

We are ttrying to port a sequence from teststand-3.1 to teststand-2013. We are using old models from teststand-3.1 . Running the sequence in the teststand development environment seems to work fine. But when starting the OI from the deployment it complains about a type conflict in SequentialModel.seq ( which is shipped in the Teststand Public directory) . I hoped that shipping the type palette directory in Teststand Public would solve that problem , but it does not. Now it complains about a type confict with ini files in Teststand Public.
Whats the right way to solve such a type conflict ?

In the deployment utilties System Source tab. I have enabled the check box Deploy file " from TestStand User Directory". That should include all needed files, shouldn't it ?
And it also slould include lots of files that aren't needed for the deployment like .prj, .c, .h, .cws files which are only needed for rebuilding from source. Or all flavors of OIs ( with source code) where you only need one ( without source code) .
What specifically puzzles me , that in the first try the teststand user TypesPalettes directory on the development system was empty and the deployment complained about a type conflict with CommonResults in sequentialmodel.seq. And after filling that directory with a copy of the ini files from the development systems teststand installation directory it now complains about a conflict in one these files when deploying ( Error message : Type 'CommonResults' in NI_Flowcontrol.ini ( C:\Users\Public\Documents\National Instrumemts\Teststand 2013\Components\TypePalettes\Ni_Flowcontrol.ini) is different from the currently loaded Type CommonResults). So I may have damaged the development system with modified files ( i.e NI_Flowcontrol.ini ) in the installation directory. But why does this conflict happen on the deployed system ? Shouldn't the contents of the deployed user directory overide anything what is deployed in the teststand installation directory ?
And what's the right fix on the development system ? A repair installation ?

AutomationParameter Type Conflict

Hi Guys,
I have been trying to use a custom station model with a sequence file however whenever I open it I get a AutomationParameter Type Conflict Error Code: -17329 Source: TSAPI as shown in the picture attached. I can normally solve other type conflicts by just making sure the 2 Types are the same in both sequences however in this case I can't really see where the types are to even compare them. Any help would be appreciated
Regards
Kewal
Solved!
Go to Solution.
Attachments:
error.JPG ‏31 KB

Kewal -
You may want to use the Type Differ tool that is included in the TestStand Toolkit - Large Application Development that is available on ni.com/labs. This tool can be very helpful in merging the types in a number of different files to the same definition as the types defined in a master file that you specify.
Hope this helps.
Manooch H.
National Instruments

Type differ not finding type conflict

Hi,
I just tried out the batch type differ. I loaded in all the step type files in the MASTER files stage of the wizard, and then selected the sequence file directory (including sub-directories). The batch type differ did not find any type conflicts, however I KNOW that the sequence file has a conflict because TestStand tells me so when I try to open it. I reduced the files to the two files in question, and tried various combinations of the locked state etc, but to no avail.
I just tried the single file Type Differ tool, and it actually found the conflcts!
Any hints as to why the batch type differ did not pick up the conflicts?
Regards
CF
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au

Hi Manooch,
Sorry for the long delay in replying.
We are using TestStand 4.2.
The files have changes since I wrote this post, and it would take a bit of effort to determine which files I actually found the issue with! Apologies for this, there was a lot going on at the time.
Thanks
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au

Personal Profile service for Brazil - Type Conflict for infotype 0002

Hello All,
We are enabling personal profile service for Brazil. And we did all the required configuration for that.
When I access the personal info service I can see the overview page with personal data. But when I click on display link, I get the error message saying -
Type conflict with ASSIGN in program CL_HRPA_UI_CONVERT_0002_BR
Is there any configuration missing?
Thanks,
Bhushan

Short text
    Type conflict with ASSIGN in program "CL_HRPA_UI_CONVERT_0002_BR====CP".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_HRPA_UI_CONVERT_0002_BR====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    You attempted to assign a field to a typed field symbol,
    but the field does not have the required type.
How to correct the error
    Adapt the type of the field symbol to the type of the field or use an
    untyped field symbol or use the "CASTING" addition.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "ASSIGN_TYPE_CONFLICT" " "
    "CL_HRPA_UI_CONVERT_0002_BR====CP" or "CL_HRPA_UI_CONVERT_0002_BR====CM003"
    "IF_HRPA_UI_CONVERT_STANDARD~OUTPUT_CONVERSION"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
Line SourceCde
    6   DATA: attributes           TYPE hrpad_field_attribute_tab.
    7   DATA: l_object_key         TYPE hcm_object_key.
    8   DATA: l_subrc              TYPE sysubrc.
    9
   10   FIELD-SYMBOLS <r0002_br>   TYPE hcmt_bsp_pa_br_r0002.
   11   FIELD-SYMBOLS <p0002_br>   TYPE p0002.
   12   FIELD-SYMBOLS <p0625>      TYPE p0625.
   13
   14   is_ok = if_hrpa_ui_convert_standard~true.
   15   ASSIGN screen_structure    TO <r0002_br>.
   16   l_object_key = <r0002_br>-object_key.
   17   MOVE-CORRESPONDING pnnnn TO super_screen_ref.
   18
   19   CALL METHOD super->if_hrpa_ui_convert_standard~output_conversion
   20     EXPORTING
   21       screen_structure_name = a_super_screen_structure_main
   22       pnnnn                 = pnnnn
   23       message_handler       = message_handler
   24       field_metadatas       = field_metadatas
   25     IMPORTING
   26       screen_structure      = super_screen_ref
   27       is_ok                 = is_ok
   28       field_attributes      = field_attributes.
   29
   30   MOVE-CORRESPONDING super_screen_ref TO screen_structure.
   31
   32   CASE a_super_screen_structure_main.
   33     WHEN 'HCMT_BSP_PA_XX_R0002'.
   34       ASSIGN pnnnn                  TO <p0002_br>.
   35       ASSIGN screen_structure       TO <r0002_br>.
>>>>>       ASSIGN pnnnn2                 TO <p0625>.
   37       MOVE-CORRESPONDING <p0002_br> TO <r0002_br>.
   38       MOVE-CORRESPONDING <p0625>    TO <r0002_br>.

Share the customed data types between sequence files

Is there any way to share the customed data type , ex. containter, between the sequence files?
I created some containters, ex, datatype1 in the File1.seq. The other
file File2.seq calls a subsequence which pass the datatype1 as
parameter. But now I have to copy the datatype1in the custom data type
section in the File2.seq. I didn't find the way in the teststand , when
I want to insert a container which is from another file.
The disdavantage of this way is , if the data type is changed, you have to change the data type in both files.
Thanks
Sundog

You can add the data type to the station globals. Then they would be updated for each sequence that uses them.
Open the stations globals and change the view to Global Types. Add your type there.
Message Edited by paulmw on 01-10-2007 01:01 PM
* I noticed that I can't find the type when tring to create a local varable using the above steps, so it looks like this won't exactly work.
Message Edited by paulmw on 01-10-2007 01:06 PM

Compare query ZY/SD Functional area ZREP:Type conflict for field MARC-DISPO

Hi,
Iam in 3.1i system, trying to load fUser group SD and Query ZY for the Functional area ZREP from text file.
Iam getting error log as : Compare query ZY/SD functional area ZREP : TYPE conflict for field MARC-DISPO
Could anybody please provide the solution.
Thanks, Krishna
Edited by: Krishnama Raju Samunuri on Jun 20, 2008 8:37 PM

Hi DST
This is a great effort and gesture. thank you on behalf of all the newbies.
PJ

CTE : ERRO MONITOR ( Type conflict in program /XNFE/SAPLGROUPING )

Ola Sap Experts, preciso de uma mão de vcs.
Estou em um ambiente de um cliente onde o monitor de outbound de CTe, quando se tenta acessar o detalhe da CTe ou qualquer outra ação é gerado o erro "Type conflict in program /XNFE/SAPLGROUPING. (termination; RABAX_STATE)" é gerado um dump na ST22.
O cliente nao tem qualquer customizacao desse monitor usa de maneira standart e se encontra no sp 16 do SLL-NFe rodando em base de um PI 7.31 dual stack.
Alguem já passou ou esta passando por isso ?

Prezados,
Alguém conseguiu resolver o DUMP?
Estamos enfrentando o mesmo problema no projeto, mas o erro só ocorre quando testamos um cenário com IPI Return.
Alguma dica?
Obrigada,
Tatiana Augusto

Saving cluster of different data types to a file

Hi,
I use LV 8.6 SDK. I need to save clusters of different data types to a file on a disk, row by row.
To be specific: I have a program that performs various investigations on a signal collected by DAQmx. Each time the quality of the signal is not in a specified boundaries, i get an indication. It is a cluster of time stamp, string, dbl, and Boolean. The program is supposed to run for few weeks in a row so there can be a lot of these indications. I expect to have around 200 000 rows a week (Altogether, divided into several groups).
I thought about TDMS but I am not able to save such a cluster. And I would like to save it as tdms cause i could divide the data to different groups. I also thought about data base but that would be the first time i use db and I really do not have time to learn that now.
I know it is possible to change some of the data types to others, ex Boolean to 0-1, but i need a string and a time stamp there.
Can someone advise me which data format should I use? Which one is the best one in this situation?
Thanks in advance
handre

If you do not need to access data from another application (other than Labview) you can just save it as a binary file.
It is the best choice (for me).
I made an example with one cluster. You can replace that with an array of clusters, of that data type.
Attachments:
Example_VI_BD.png ‏2 KB

Type Conflict in File - TestStand 3.0

Similar Messages

Maybe you are looking for