'DBX CAS 4' Error message

[Anonymous]

I have a huge volume of classes and functions in libraries that i have
developed over the years to automate a lot of things i want to do with
AutoCAD - smart pointers, "apply" functions that iterate model space and
perform some function on every entity, etc. If i'm calling these functions
from an ARX, i have no problem.

However, i'm working with RealDWG now - so i thought i might just recompile
these libraries as DBX instead of the original ARX. They don't use anything
"AcEd", nor do they use anything relating to documents - mostly just AcDb
related things. Everything compiles fine, but trying to access more than
one drawing, or trying to create a model space iterator will result in the
"DBX CAS 4" error message (as the documentation specifies it will).

So my question is this - what is it about the DBX that causes this? What is
the *right* way to make libraries like this to be used via RealDWG? I'd
like to use the same libraries for both RealDWG as well as my ARX apps.
Should i just compile them as dlls, and manually refer to all the LIB files
i need?

Interestingly enough, i've found that these same DBX files will NOT throw
the "DBX CAS 4" if they are simply implicitly linked - provided that i don't
do an acrxLoadModule( ). The only time this ever gave me problems was when
i was creating objects in the DBX that were passed back to the caller.
Doing that will cause AutoCAD to lock up when you go to close it - which
makes sense....

Thanks,
Rich

[Anonymous]

Rich:

> So my question is this - what is it about the DBX that causes this?

Obviously the way you're using your libraries causes ObjectDBX to think
the calls are not coming from your licensed application. I don't have any
experience with RealDWG, but I would expect the SDK documentation to spell
out Autodesk's requirements for how your code is allowed to call into the
ObjectDBX DLLs. 🙂
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[Anonymous]

Thanks for the response Owen. I know that the RealDWG provides a special
OBJ that you need to link to in order to avoid that error. If it were just
the host app that required it (which is what the documentation seems to
indicate), i would be satisfied. But any library i try to make that creates
an iterator will throw the error. Which means i have to compile different
versions of my libraries for ACAD and RealDWG - i was really hoping to avoid
that.

I'll post back if i find any other relevant info...

-Rich



"Owen Wengerd" wrote in message
news:4999434@discussion.autodesk.com...
Rich:

> So my question is this - what is it about the DBX that causes this?

Obviously the way you're using your libraries causes ObjectDBX to think
the calls are not coming from your licensed application. I don't have any
experience with RealDWG, but I would expect the SDK documentation to spell
out Autodesk's requirements for how your code is allowed to call into the
ObjectDBX DLLs. 🙂
--
Owen Wengerd
President, ManuSoft ==> http://www.manusoft.com
VP Americas, CADLock, Inc. ==> http://www.cadlock.com

[henrik.vallgren]

I've seen this in AutoCAD LT. Are you trying to open something or locking a document?

[Anonymous]

No, RealDWG has nothing relating to documents, since it has no UI
whatsoever. It's a security error (built in on purpose, i assume) that
happens when you try to access multiple databases simultaneously, or if you
try to create a model space iterator (might be any kind of BTR iterator, i
didn't test out anything else). I knew exactly what was causing the error -
just didn't know how to circumvent it without linking to the special
security object that comes with RealDWG. Mostly because i was being a baby,
and i didn't want to have separate compiles for AutoCAD and RealDWG. But it
seems that you MUST link to the OBJ that they give you with RealDWG, or you
will get that error.

As i had specified previously, you can get the same error in AutoCAD if you
have a DBX that attempts to create an iterator or tries to open another
drawing. However, that problem can be circumvented by just implicitly
linking to the DBX, and skipping the acrxLoadModule( ). That's fine, as
long as you aren't creating things in the DBX that must be passed back to
the ARX - in that case you must use acrxLoadModule( ), or AutoCAD will lock
up while trying to unload your app. So if you have custom objects, the DBX
must be loaded using acrxLoadModule( ).

-Rich


wrote in message news:5005362@discussion.autodesk.com...
I've seen this in AutoCAD LT. Are you trying to open something or locking a
document?

[jas-pdx]

DBX CAS 4 Fatal Error

After installing and running ACAD 2007 for several months, I started to get the “DBX CAS 4 Fatal Error” msg when trying to open or load a solid model. The DLLs would load and when the process reached the Modeler DLLS, the err msg was displayed. At that point I had no option but to cancel and/or send Autodesk a trouble msg. They suggested that I install SP2. I did so and no change.

I then uninstalled acad and reinstalled it. The problem went away for the next 2-3 weeks. Now, I’m getting the “DBX CAS 4 Fatal Error” without running acad even after a cold boot and running nothing else. Acad 2007 runs fine (it seems) otherwise.

Any ideas on what is going on?
Thanks,
jas-pdx

[Rudedog]

We have started getting the same message on 2006 AutoCAD machines, which are not running anything at all.

Anyone else seeing this?

[ljordan316]

After installing and using AutoCAD Lt 2007, Autodesk Design Review, and Autodesk DWF Reviewer for over a year I am suddenly getting the DBX CAS4 error even when I am not using the products. Very annoying!

Is there a fix?

Larry

[afik]

I also get the same error message on my AC2008.
Any solutions?