selected model does not match the missing one

[calacc]

Good morning, everyone!

during the regeneration of an axieme containing more sub-assiemi I noticed with surprise the lack of regeneration of one of them. this never happened, especially after I properly configured my search.pro file. . .
by clicking on info-feature tells me that the component model is missing. trying to manually recover the missing component (which should not serve as the search.pro...) gives me an error message as in the title "selected model does not match the missing one". This is very strange because I am sure I have never renamed anything and opening the general of the failed sub-assieme individually opens it to me and regenerates it well with all variants, so it seems that there is a conflict of identity. . .

Has anyone ever happened that? Can you give me any suggestions about this?
Thank you.

 

[calacc]

right, solved now the hippo!!! :wink:

Now I'll tell you what happened. . .
in my search.pro file there were 3 consecutive paths that schematize my premontages: level1; level2; level3; in this order.
the axieme I tried to open was in level4, so first it regenerated levels 1, then 2, then 3.
Well, I found out that in level 1 there was a file together with the same name as the corresponding level2 that gave me the initial error. . I go to open it and it was a blank file, probably ended up there by mistake with a copy and paste or that I know.
So the system what he did, he tried to open the sub-assieme file of the level1 (empty), at the 2 it was not going because according to him he had already found it. That's why when I forced the component search to level 2, he said, "Selected model doesn't match the missing one." .
I went to open that fake file, I did delete all versions and voilà, as by magic everything regenerates!

Fuck you, a whole afternoon lost for this shit, but now I don't think about it anymore!

 

[taz83]

Let me ask you a question.
I use proe wf5 but I can't find the search.pro file while the search_path file is where it should be, can you tell me where it should be? ! ?
I changed pc and I already had problems of various kind, so maybe it went deleted(? ! ).
Thank you.

 

[nicksoft]

Let me ask you a question.
I use proe wf5 but I can't find the search.pro file while the search_path file is where it should be, can you tell me where it should be? ! ?
I changed pc and I already had problems of various kind, so maybe it went deleted(? ! ).
Thank you.

search.pro can be in any folder, its location is defined by the config variable "search_path_file", see if you have that parameter in your various config and which folder points;
Have you already done a search.pro on all records?

 

[taz83]

Thanks nicksoft.
I have already done a search on all the pc and all the server, there is no search.pro, but the search_path_file variable does not refer to the search.pro but to a .txt file (search_path.txt). .
so it should be right, the references take them from the list in .txt? ! !

 

[calacc]

But that's how it works? because I believe that the file containing text strings should be called just search.pro...
to the maximum according to me just rename it and set the variable search_path_file correctly to search.pro

 

[nicksoft]

Yes, it is fine even if it refers to search_path.txt, which must contain folders where to search for objects

 

[taz83]

as nicksoft says, in fact it works.
As for commercial details there are no problems, I have "fixed" folders on the server with references in the search_path, but the big problem that I have the division for customers before for projects (have different numbering codes) and some have large assemblies divided in turn into subassies (which for convenience are separated into subfolders) and insert them all would be a suicide...

 

[nicksoft]

as nicksoft says, in fact it works.
As for commercial details there are no problems, I have "fixed" folders on the server with references in the search_path, but the big problem that I have the division for customers before for projects (have different numbering codes) and some have large assemblies divided in turn into subassies (which for convenience are separated into subfolders) and insert them all would be a suicide...

There is a command that can help you
if you have the folder, for example,
c:\clients so divided :

c:\client\clientea\progetto1\. . .
c:\client\clientea\progetto2\. . .
c:\clienteb\progetto1\. . .
etc.

you can do, from a command prompt,

dir c:\clients /ad /b /s > c:\search.pro

and writes all the folders, recursively, in search.pro

risk becoming a huge search.pro, resulting in increased loading times, but can do to your case

 

[taz83]

Um...
It could be my case, but I still ask you something, being a command ("batch"?!) I have to start it every time I add the folders, right?!?
I'm sorry if the question turns out stupid!

 

[nicksoft]

Yes, if the folder structure changes, you have to relaunch the command that overwrites the previous search.pro.
you can make a .bat start that as first line creates search.pro and as second start create