Why New does not work on one machine?

Ed · Joined: 28 Feb 2008 Posts: 2

We have a home grown out of process automation server written in C++.
When I use the following lines it works

Dim objSvr as Object
Set objSvr = CreateObject ("ProgID")

Following also works on several machine we tired except one

Dim objSvr as ClassName
Set objSvr = New ClassName

On that machine we get a error like "ActiveX component cannot create
object" or something very similar. We used the same installation to
install the server and the VB client on every machine.

Any idea what can be wrong.

Thanks in Advance

Archived from group: microsoft>public>vb>general>discussion

MikeD · Joined: 04 Oct 2007 Posts: 3348

"Ed" wrote in message $47c611a5$1860b4f9$15697@KNOLOGY.NET...
> We have a home grown out of process automation server written in C++. When
> I use the following lines it works
>
> Dim objSvr as Object
> Set objSvr = CreateObject ("ProgID")
>
> Following also works on several machine we tired except one
>
> Dim objSvr as ClassName
> Set objSvr = New ClassName
>
> On that machine we get a error like "ActiveX component cannot create
> object" or something very similar. We used the same installation to
> install the server and the VB client on every machine.
>
> Any idea what can be wrong.
>

You need to provide more information (OS, service packs, etc.), but the
underlying, probable reason is that the component is not registered. Why it
didn't get registered on this PC during installation is another matter.
Perhaps it wasn't installed under an account that was a member of the
Administrators group.

--
Mike
Microsoft MVP Visual Basic

Ed · Joined: 28 Feb 2008 Posts: 2

MikeD wrote:
> "Ed" wrote in message
> $47c611a5$1860b4f9$15697@KNOLOGY.NET...
>> We have a home grown out of process automation server written in C++. When
>> I use the following lines it works
>>
>> Dim objSvr as Object
>> Set objSvr = CreateObject ("ProgID")
>>
>> Following also works on several machine we tired except one
>>
>> Dim objSvr as ClassName
>> Set objSvr = New ClassName
>>
>> On that machine we get a error like "ActiveX component cannot create
>> object" or something very similar. We used the same installation to
>> install the server and the VB client on every machine.
>>
>> Any idea what can be wrong.
>>
>
>
> You need to provide more information (OS, service packs, etc.), but the
> underlying, probable reason is that the component is not registered. Why it
> didn't get registered on this PC during installation is another matter.
> Perhaps it wasn't installed under an account that was a member of the
> Administrators group.
>
Thanks for the reply.

OS is XP Pro and VB SP6.

I think the registration is correct. CreateObject on the same object
works correctly. Is there any specific registry needed by New but not by
CreateObject?