What does this mean. I used to receive this message in Aecosim constantly and made everything either super slow or crash. It has now started appearing in Microstation when attempting to place a parametric cell from a library.
Message center tells me nothing more than the aforemantioned - *Maximum dependency callback iterations exceeded* - Is anybody aware of what this means or how to ascertain what the problem actually is?
Duncan Gammie said:Maximum dependency callback iterations exceeded
Many objects in MicroStation are dependent on another object. For example, an associated label is dependent on its host element.
MicroStation has a dependency engine to manage dependencies. Under normal circumstances that engine is invisible to us users. However, sometimes things go wrong and the engine makes a noise that we can hear.
If a circular dependency is inadvertently created then the dependency engine may get stuck in a loop while attempting to resolve those dependencies. The message you see is the result of a recursive computation that has been halted by some monitoring agent.
Duncan Gammie said:Is anybody aware of what this means or how to ascertain what the problem actually is?
This is an indication of MicroStation internals going wrong. If your problem with parametric cell placement is reproducible, then file a Service Request (SR) with your evidence. Support won't be able to do anything except allocate an SR number. It needs to go to the developers.
Regards, Jon Summers LA Solutions
Thanks for that Jon, I have filed several service requests over the years and nobody has been able to explain that to me. The issue I currently have is not consistent. This particular occurrence is to do with placing a particular version of a parametric cell in a blank file. however placing the same cell in a different workset does not have the same issue. I have experienced the same error with other procedures also. It's just unclear. If there is an engine that manages these things, then surely there must be a way to tell me what the issue is or at least give some sort of indication. I normally attempt to resolve issues myself in the first instance before reverting to SR's. Just having another go at a long standing issue for me.
Hi Duncan, please let us have the file and some more details on how to reproduce and on the environment when the cell works, we'll look into this. Jon's explanation is correct, it means there is some sort of circular dependencies and the constraint solver goes in a loop. We are looking into return more precise indication on specific failures, where possible.
Product Manager, MicroStation
Bentley Systems intl