exception while saving the activeDocument on V2026 and after migration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
I have switched our application (which uses the Inventor and the inventor api) to inventor2026. Then I have processed a migration... the call to the save() function (activeDocument.save) triggers now a n exception. I have tried to call the save2() function instead... then we land in Bug Report formular.
As I have refined the saves at different stages (one save after each component processing), I saw that this problem is triggered on 5 components among 20. This leads me to the first impression that the problem is due to an incompatibility in data.
I am posting the visual basic code where the problem surges. And can optionally supply more code...
PS : is there anywhere any Inventor api reference guide for developpers ?
PS : the faulty save is at line 345 in TürDesigner.vb
To come tot he point were the problem surges, you have to do the following sequence
(pay attention : in order to actually trigger the problem, you have to uncomment the line _appInv.activeDocuemnt.save() at line 345)
- Start autodesk inventor professional 2026
- In the start home page select TürDesigner.iam (double click)
- It will load this
- Then in „ilogic“ panel (near Modell panel) (upward links), right click on TürDesigner
- Select „execute the rule“ or „Regel ausführen
- In the file browser, choose the file at the bottom (cadTest.csv)
- In the new window, select „ausführen“ (execute)
The modules where the cause might be are the following :
- FlügelRahmen
- TürRahmen
- Beschläge
- Pfostenkonstruktion
- Verbreiterungsprofile
(I have tested everyone in isolation)
Addition to the former investigations :
In der Folge von letzten Untersuchungen ist bestätigt dass die Probleme am speichern von Modelen entstehen durch der Benützung von folgenden Primitiven :
- Parameter()
- Replace()
In den folgenden Modulen :
- FlügelRahmen
- TürRahmen
- Beschläge
- Pfostenkonstruktion
- Verbreiterungsprofile
- GanzGlasFüllung
(das Problem verbreitet sich durch ein Struktur Mismatch von Daten bis auf dem Speichern…)