Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Automation server can't create Object

17 views
Skip to first unread message

b_jo...@yahoo.com

unread,
Jun 22, 2007, 4:29:48 AM6/22/07
to
Hi,

I'm having issues with an ActiveX control that I developed in C#. I
registered the control with regasm and all went well, except when I'm
calling the control in Javasript (the control is located on the client
and is only going to run on the client - no servers or anything like
that involved).

This is my code (It's just a test project):

var activeX;
activeX = new ActiveXObject("ActiveTest.TestClass");

and the error message I get is either "The specified file cannot be
found" or after I register the activeX dll in the GAC, I now get
"Automation server can't create the object".
I read a bunch of posts that seem to solve to the Automation server
error by setting the Internet Explorer Security to low, however I have
tried this as well, but with no success. I had set all zones to the
lowest possible level and it had no effect on the error. To give you
some more info on the situation:

OS is Vista Ultimate, Browser is Internet Explorer 7 and the
application was developed with .Net 2.0.

My question is, what exactly is the automation server? I read in other
posts that dealt with office automation that Excel or Word were the
automation server in those cases. So am I right when I assume that
Internet Explorer is the automation server in my case?
And of course the main question is, how can I get rid of this error,
since it is a real show stopper!

Thanks,
Steve

b_jo...@yahoo.com

unread,
Jun 22, 2007, 11:06:58 AM6/22/07
to
In case anyone comes across the same issue, I solved it now.
I only used regasm to register the dll, without any options. Since I
had the page that called the dll and the dll itself in two different
folders, and I didn't have the dll registered in the GAC (at least not
my test project), I needed to use the /codebase option with regasm, to
also register the path to the dll.
As soon as that was done, everything worked again.

- Steve

0 new messages