Topic: ActiveX Server returned an error

[Anonymous]

Hi,
As anyone of the many genius's out there explain the following:

Command: kitoX-dimtools-scale
Select dimension :; error: ActiveX Server returned an error: Error loading type
library/DLL

This not the only code that produces the same error, I suspect that some component was not loaded when Autocad was installed.
I'm running A2002 by the way. I'm sure that th solution is very simple.
Derek

[Mark]

Just for the heck of it try typing in this before you run the command.
(vl-load-com)

[dellboy]

Just for the heck of it try typing in this before you run the command.
(vl-load-com)

Mike,
Tried that but with no success.
Derek

[Mark]

I would try contacting the author of the software. He can probably fix it, or tell you how real quick.
vg_AT_kitox.com

[dellboy]

Mike,
I've already contacted him and he's as lost as me.
The puzzle is it only happens to some of the routines, the others work fine. The same problem occurs in say Express Tools, one or two commands don't work the rest do, snd of ccourse Sods Law says thet the one you want to use won't.
Derek

[daron]

Well, first of all lisp is having trouble loading a typelibrary and a certain dll file. Do you have the source code or is it all compiled? If you have it, can you post it, so we could at least have some idea of what types are being called? If it is only calling the ActiveX model, there might be a problem with your installation. Try repairing the acad install through add/remove programs.

[Keith™]

The VLisp extensions require the loading of the type libraries for VBA. If you do not have the VBA option installed, you will not be able to use VLisp unless you specifically extract the type library to the support path.
Another reason could be that there are too many support paths listed in the support search folder, and those required to operate AutoCAD cannot exceed the maximum string length for a registry entry, otherwise the operating system will truncate the entry.
I have seen that where the files were indeed installed, but because the user added so many paths to the support search AutoCAD could not find critical files. It is a limitation with the registry and should not be viewed as an AutoCAD bug.

See this link for more detail.

[Craig]

 Mike???  

[daron]

I think he means Mark.

[Craig]

Oh, I know. It's the holidays and I'm in a festive *drunk* mood. I was just having fun with Derek. You know how it is when you're at a party or a gathering and you  introduce yourself to someone and they continue to call you the wrong name the entire party. I find it really funny.      

hmmmm...not that I've ever done that  

[dellboy]

Happy New Year everyone.
Well I've got the code, if only I could send it someone. How do I send it, can't find a way to attach the file.
One interesting avenue is the support file refs, I do have one or two, I will look at reducing them.

Derek

[Keith™]

Derek, you can upload the code in the lilly pond. To do this go here and create a "dellboy" folder, then upload the file to your folder, then we can all get to it to help you diagnose the problem.

[SMadsen]

If you have the source code, and assuming it is AutoLISP code, there is perhaps a quicker way to get to know more about the error.
If you are not familiar with the VLIDE then don't worry. Just follow the steps below. If you don't have the source code and/or it is not AutoLISP code, then disregard the following.

1. Type VLIDE at the command line. This will bring up the Visual LISP editor.
2. Go to the Debug menu and see if the item "Break On Error" is checked. If not, select it to check it.
3. Leave the Visual LISP editor open and switch to AutoCAD.
4. Call the offending command.
5. On error, switch to the VLIDE editor.
6. In the editor, go to the Debug menu and choose "Last Break Source", or hit Ctrl-F9. This should bring up the code and locate the error within the code.
7. If no. 6 succeeded, copy the offending code to the forum and we'll take a look at it.
8. If no go at no. 6, we'll need more to go with.

[dellboy]

I've looked round and can't find the Lily Pond. How do I get there from the forums.
Derek

[Keith™]

Click on the link in my previous post or click here

[dellboy]

Mark,
Found it thank you, I've uploaded the files(apart from thebmps). Is there of getting to the Lily pond without using your link
Derek

[daron]

You could take note of the address when you're in there and bookmark it.

[Keith™]

Ok I have sucessfully executed the commands with no adverse effects. I would suspect you do not have all of the VBA type libraries installed. Since the code is a compiled VLX we cannot look at it to determine the reason it won't work, we can only speculate. Since some Express tools also don't work, I think that if you reinstalled the VBA components it should fix the problem. What you need to realize is that the module likely uses ActiveX VisualLisp commands that require the VBA Type libraries. If you are missing a specific one, then the commands that require that library will not work.

[deegeecees]

This is going to be a hit/miss for my suggestion.

Try going to Tools>Macro>Visual Basic Editor and see if there is a reference to the application you are having the problem with i.e. (in VBAIDE) Tools>References, scroll down until you see something that has the same name, or make sure that AutoCAD type library is loaded.

Like I said, hit or miss...

[daron]

So, you are both saying that even though it's a lisp (vlx) file, you can set the references in vba and retrieve them in lisp?

[deegeecees]

I guess thats what I'm saying. It's either that or you need to load the DLL externally. I used to know how to do that. Let me investigate more into this as I have ample free time.

[Keith™]

What I am saying is that the ActiveX components in lisp aka VisualLisp uses the exact same type libraries as VBA, so if you don't have all of the AutoCAD VBA type libraries VisualLisp will not function properly.

[daron]

I think that's what I wanted to hear. Cool!