Class not registered on local machine

[Silas]

Hi all,

We have developed a COM+ component that uses MSXML3 to get shipping quotes
via the internet.

Now, we have this component installed on Win2K in COM+, and have tested the
client MSI on Win95 and Win2K clients. It works great. Next, we installed
the MSI onto our web server, which is running NT4, so that ASP could use it.
When any asp scripts (or even test exe's) on the web server try to
instantiate the component, we get "Class not registered on local machine".
We have verified the presence and functionality of MSXML3 on both the COM+
box and the web server, so we are somewhat confused here.

There is also a serious lack of info about this error both in the newsgroups
and on the web at large.

We have tried numerous ways to debug this, including going as far as
completely rebuilding and re-exporting the COM+ package, all to no avail.
Any ideas?

Thanks,
Silas

[Joe \Nuke Me Xemu\ Foster]

"Silas" <smarner@noemail.com> wrote in message <news:3cb1b1d1@10.1.10.29>...

> We have developed a COM+ component that uses MSXML3 to get shipping quotes
> via the internet.
>
> Now, we have this component installed on Win2K in COM+, and have tested the
> client MSI on Win95 and Win2K clients. It works great. Next, we installed
> the MSI onto our web server, which is running NT4, so that ASP could use it.
> When any asp scripts (or even test exe's) on the web server try to
> instantiate the component, we get "Class not registered on local machine".
> We have verified the presence and functionality of MSXML3 on both the COM+
> box and the web server, so we are somewhat confused here.
>
> There is also a serious lack of info about this error both in the newsgroups
> and on the web at large.
>
> We have tried numerous ways to debug this, including going as far as
> completely rebuilding and re-exporting the COM+ package, all to no avail.
> Any ideas?

A COM+ "proxy" does need to be registered on the web host, so that it
can intercept attempts to instantiate the component and forward them
to the COM+ server. Or is this what the COM+ tools mean by "exporting"?
Sometimes I think Humpty Dumpty is Microsoft's chief tech-writer:

"'When I use a word,' Humpty Dumpty said, in a rather scornful tone,
'it means just what I choose it to mean, neither more nor less.'"
-- Lewis Carrol, _Through the Looking Glass_

--
Joe Foster <mailto:jlfoster%40znet.com> On the cans? <http://www.xenu.net/>
WARNING: I cannot be held responsible for the above They're coming to
because my cats have apparently learned to type. take me away, ha ha!

[Paul Clement]

On Mon, 8 Apr 2002 11:26:58 -0400, "Silas" <smarner@noemail.com> wrote:

¤ Hi all,
¤
¤ We have developed a COM+ component that uses MSXML3 to get shipping quotes
¤ via the internet.
¤
¤ Now, we have this component installed on Win2K in COM+, and have tested the
¤ client MSI on Win95 and Win2K clients. It works great. Next, we installed
¤ the MSI onto our web server, which is running NT4, so that ASP could use it.
¤ When any asp scripts (or even test exe's) on the web server try to
¤ instantiate the component, we get "Class not registered on local machine".
¤ We have verified the presence and functionality of MSXML3 on both the COM+
¤ box and the web server, so we are somewhat confused here.
¤
¤ There is also a serious lack of info about this error both in the newsgroups
¤ and on the web at large.
¤
¤ We have tried numerous ways to debug this, including going as far as
¤ completely rebuilding and re-exporting the COM+ package, all to no avail.
¤ Any ideas?
¤
¤ Thanks,
¤ Silas

I think you need to identify all of the COM components you are using. For example, if ADO is being
used, make certain that you have the appropriate version of MDAC installed on the server.

In addition, if you use the server parameter in the CreateObject function make certain that you are
specifying the correct server name.


Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)

[MarkN]

It might be cheaper and quicker to install W2k on your webserver(since you
know W2K clients work). Me is guessing it has something to do with NT/MTS
and W2K/COM+ incompatabilities.


"Silas" <smarner@noemail.com> wrote:
>Hi all,
>
>We have developed a COM+ component that uses MSXML3 to get shipping quotes
>via the internet.
>
>Now, we have this component installed on Win2K in COM+, and have tested
the
>client MSI on Win95 and Win2K clients. It works great. Next, we installed
>the MSI onto our web server, which is running NT4, so that ASP could use
it.
>When any asp scripts (or even test exe's) on the web server try to
>instantiate the component, we get "Class not registered on local machine".
>We have verified the presence and functionality of MSXML3 on both the COM+
>box and the web server, so we are somewhat confused here.
>
>There is also a serious lack of info about this error both in the newsgroups
>and on the web at large.
>
>We have tried numerous ways to debug this, including going as far as
>completely rebuilding and re-exporting the COM+ package, all to no avail.
>Any ideas?
>
>Thanks,
>Silas
>