Irricad

Hello, Sometimes when I try to save my project, an error occurs that prevents me from saving the file. Is there anything I can do to reverse this or prevent this error from occurring?

I have found if I do an AUDIT - fix any errors and remove unused items the file can usually be saved. I have no idea what causes the error, but have seen it several times.

This message indicates that something is stopping the design from saving.
In our experience this tends to be an open transaction.
We do not know of any causes of this in Link V22 and would need to see the log files to determine what may have caused this.

Note that when the design has open transactions there isn't any way to save the file, AUDIT will not fix this issue. You will need to go back to either the latest .bak file (change the extension to .dwg) or your last successful save.

Send error log files:-
Set your host CAD to create session logs via the LOGFILEON command. This needs to be done prior any problems. This command only needs to be set once.

A. If you are using BricsCAD, and have an installed email program (i.e. not webmail)
1. Action Irricad Options|Send Problem Report.
2. In this particular case, because you can't save, click "No" to the question about sending a copy of the design. In all other cases it is usually helpful if you include the design.
3. An email will be created which contains a zip file of your session log and associated files.
4. Always include a description of the issue and the last actions.
5. The email will be sent directly to the Support and Development team.

B. If you are using AutoCAD, or do not have an installed email program
1. The easiest method is to create a "logs" folder in your IRRICAD Link folder (e.g., C:\Program Files\Irricad\Irricad Link AutoCAD\Logs). This will avoid having to browse to the usual place that AutoCAD and BricsCAD save their session logs. See below for instructions on how to do this (at section C). Note that this is the preferred option because IRRICAD can then control the level of information to be provided.
2. If you have not created a Logs folder then browse to the AutoCAD or BricsCAD Templates location. In the folder one level above Templates you will find your session logs (e.g., C:\Users\[your log in name]\AppData\Local\Autodesk\AutoCAD 2024\R24.3\enu)
4. Attach the log file with the current design name and latest time stamp to an email with an explanantion of the issue. If you do not have the save issue, please also include your design.
5. Send the email to Support@IRRICAD.com.


C. How to create a Logs folder in the IRRICAD Link folder
1. The Host CAD LOGFILEON must be enabled.
2. In the computer's "Search" field enter Regedit. In the list click on "Registry Editor".
3. Go to "Computer\HKEY_CURRENT_USER\Software\AEI Software\Irricad ACAD\AppSettings" for AutoCAD or go to "Computer\HKEY_CURRENT_USER\Software\AEI Software\Irricad BCAD\AppSettings" for BricsCAD.
4. If the “DebugTraceLevel” string exists double-click on it and set the value to 1.
5. If the “DebugTraceLevel” string does not exist you can add the DebugTraceLevel option by right-clicking the right-hand panel and
choosing “New > String Value” 6. Enter DebugTraceLevel as the name. Once created you can set the Value to 1.

The IRRICAD Team

AUDIT will absolutely allow the user to save after running it when this error pops up.

I just got this error:
I then ran AUDIT which fixed/cleared 16 errors. I then saved the file with no problem.

I think there is a bug related to autosave (maybe autosave interupts something?). The popup was triggered right after an autosave.

Hi Nick,

We'd like to understand, if we can, what is causing these errors. I appreciate it's difficult to send us a "bugged" file if you can't save it, but logs (as per Jo's post above) might be illuminating, if this error crops up again.

Even the AUDIT log (from the command line) which tells us what AUDIT fixed might give us some pointers.

If we do have an open transaction in the database (again, see Jo's reply) you can use a special debug command on the command line to show this:

.IRR_DEBUG lo

(the point at the beginning is important!)

This will show any open transactions and the function in which they were opened. Again this gives us a place to start looking for problems.

Thanks,

Dan

I'll see what I can gather. Until this post, I thought it was just me.