Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
We are using Intralink 3.4 M070 with Wildfire 4.0 M210 and are seeing an odd error.
While working with certain assemblies we have had users running into situations where ProI would either crash, take hours to check in a simple assembly, or return the error:
"ProINTRALINK has detected an internal error..... Attempt to get object with NULL_DBID"
Until recently, we were unable to isolate the error or circumstances that cause the error. We thought that the error might have been coming from a "poison pill" part or subassembly. To eliminate the parts I created a brand new assembly and assembled in the suspect pieces of hardware models. After multiple attempts, I found that there was not a "poison pill" but seemed to be a quantity of parts that was the issue. I created a new plain rectangular flat part, new bolt, new washer, and new nut models. The plain part has a pattern of holes though it. Whenthe bolt, washer, and nut are added to the assembly (with or without reference patterning) and the total number of parts equals 200 ProI returns the above message. If I delete any one item from the assembly bringing the total number of parts to 199 it checks in without issue. Add one more part fails to check in again.
Also, we exported the assembly from the workspace and then imported it into a new fresh workspace of a different user. Initially the assembly with more than 200 components checks in. However, if any of the components is redefined or replaced the assembly check in fails with the Null_DBID error.
Has anyone else seen this sort of error or hit a max component ceiling with ProI?
Matt Seibert