Second project in relationship does not exist

[PineCone]

We have a main assembly checked into our library that is at Version 45. This assembly contains two other sub-assemblies and five individual parts. The two sub-assemblies contained in the main assembly are versions 35 and 43. These sub-assemblies have now been modified to versions 38 and 46. We need to update the main assembly to reflect these changes and we cannot.
Both of the sub assemblies can be checked out of the library in their latest version and they can both be referenced from the library at any priveous version with no appearent problems. The main assembly will not check out and it is also no longer possible to reference any of the old versions.
When you go into get from library and select the main assembly and then select check out, reference or copy, the system clears the highlight from the assembly name and reverts to no items pending. When you go into Manage libraries and select the main assembly and then select update in library, you get this error message.
“The second project in the relationship does not exist an invalid ID was specified”
Can anyone please tell me how we have created this problem and even more important, how can we fix it?

Many thanks

 

[nibola]

Hello, you can try a couple of things:

Do you have your projects configured?
When you go to the manage libraries, have you checked the related items of your assemblies? anything strange there?
Have you tryed to update it from the main server? (all the ID memebers are specified there)
In the manage libraries, when you select "Parent item" and "Project" in the menu, does it show the correct location of your assemblies?

 

[PineCone]

Thanks for the reply

I have managed libraries and checked related items of every assembly and sub assembly and drawing of this assembly. Most of it looks strange (to me lol). The only relations that say invalid were "due to new item version" and those that said it should be "invalid due to new item version".

The project is not configured.
All Assemblies and models appeared in correct location under partnt item and project.

While I cannot check out or update the main assembly, I actually now believe that the problem is in one of the sub assemblies and not in the main assembly. One of the Sub assemblies can be checked out but it has a problem. It was at V 38. I check it out, made a change and checked it in. Ideas showed in the list region, "check in uccessfull", and also showed V 39 in the bin. But Manage libraries only showed V38.

Obviously, I thought, there is a problem with this latest version of that assembly. So as my logic went, I deleated the V39 from my bin, I then deleated the V38 from my Library. I checked out the old version V37 from the library thinking (always gets me in trouble)I could then update this one and be off and running with only minor rework. I guess there was a hole in this logic.

I now have an assembly at V37 that I can check out but not check back in. Check it in and the Ideas list region, says "check in successfull", and also shows V 38 in the bin. but then go to manage libraries and it shows only V37. I also now have a sub-assembly V12 within this assembly V37 that shows the following relation
"<- Parent of, Invalid due to new Item Version, Assembly name, V37"
There is no longer any V38


I'm not sure what to do

Thanks for any help that anyone can give
PineCone

 

[nibola]

Ok, I don´t know if I can help you...

I don't undersand how can you check v39 in succesfully and not be updated in the manage library. Take care where you look if v39 has been checked in. You have to go to the proper project and library, show all and take a look at your assembly directly. If you go to the main assembly (v45) in the manage library, you open it and you look to the version of the subassembly, there you will have v38 instead of 39 because still have to be updated.

Anyway, if you are blocked and you can not work, what you can do is a copy of v37, you change the name, you check that you can check it in (and then you will have v1 of a new assembly). Then you go to your main assembly (v45) you delete v38 from there, you put your new v1 and you check the main assembly as v46. It is not by far the best way to do it, but if you are in a hurry...

Anyway, watch out copies, they are very dangerous to work with... have you make any copy already?? because sometimes they are the starting point of many problems. If you make the copy, make sure you change the name, because you can have two different assemblies with the same name in different projects, and that can lead to a missunderstanding of information...

 

[PineCone]

Copy is not much help because I cannot copy the top level assembly and the drawings related to them. I can only copy the sub-assembly. I am not so sure now that the promlem is within the assembly, perhaps it is in the project.

Here is the latest that I can tell you

I can make a new part and check it into into any library within this project.
I can get a part out of a catalog and check it another project but not this one.
Any other new part can be checked into any library within this project except those parts from a catalog.

Get a catalog part out of the catalog, check it into any library from this project and Ideas says in the list region "Check in Successfull" The Version column will change to "1" but the Stat column does not change to "CK" Then look into Manage Libraries and the file is not there.

I can check out a part from the project, even if that part was from a catalog, make a change to it, and check it back in without issues. There are however some models within this project that when you check them out, make a change, check them in, Ideas says in the list region "Check in Successfull" The Version column will change to the next version number and the Stat column continues to say "CK" but when you then look into Manage Libraries, the latest version number has not changed. The Version number in the model file will be one version ahead of the library version.

So now what do you think?

 

[nibola]

Hello,
Well, I don't really know what else you can do. Maybe you should check if the projects are configured or not. If they are, this could be the reason why you cannot check parts in and out. Maybe somebody else in your company has been configuring them and you don't know.

To know if a project is configured or not you have to:
1.- open a new model file and, in the first screen where you choose the project and the name of the model file click on "find" in the projects.
2.-In the upper right part of the new screen click on "modify"
3.-Click on your project (only 1 click).
4.-Click on configured. If the project is not configured a warning screen will appear saying "configuring projects is permanent. Configured projects can not be unconfigured".Click cancel
If the project is configured an screen will say "Project is already configured".
Whatever wach out with this screen, you can delete many things from here.

Also look carefully in which projects you check things in and out. Is not possible checking in succesfully and not having a new version