I'm getting an Error 429 : ActiveX component can't create object when trying
to run a program that ran perfectly fine on Windows XP. It was created in VB6
but does not run on my version of Vista Business. Anyone have any ideas as to
why this may not work. We are desperate...it is a buisiness application that
our customers cannot run!

"Brad" <Brad@discussions.microsoft.com> wrote in message
news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...[color=blue]
> I'm getting an Error 429 : ActiveX component can't create object when
> trying
> to run a program that ran perfectly fine on Windows XP. It was created in
> VB6
> but does not run on my version of Vista Business. Anyone have any ideas as
> to
> why this may not work. We are desperate...it is a buisiness application
> that
> our customers cannot run![/color]

The particular activex object may not be registered on your system, so you
may need to install it.

Otherwise try running the program elevated.

--
Jon

Brad Hi,

We also have a complex VB6 financial app which, when we installed on Vista
32 - runs with no problems.

Are you using the Microsoft Best Practices - for instance, if the app tries
to write anything to Program Files on the target computer where the user is
not an ADMIN, you can get funny messages. Perhaps the DLL is not registered
properly..

Perhaps the DLL should be in Program Files\Common Files\Company
Name\DLLName.dll and not %System32%.

Perhaps you should have a VISTA machine with VB6 installed as your test
developement environment. See if the error happens there within the
development environment.

WE use VMWare very successfully for this kind of problem. You can install a
Vista VM under XP but, I am not sure if the environment is really identical
to a real time Vista installation.

Consider also testing the APP on Vista 64 bit. This is the future so get
used to it.

Garry


"Brad" <Brad@discussions.microsoft.com> wrote in message
news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...[color=blue]
> I'm getting an Error 429 : ActiveX component can't create object when
> trying
> to run a program that ran perfectly fine on Windows XP. It was created in
> VB6
> but does not run on my version of Vista Business. Anyone have any ideas as
> to
> why this may not work. We are desperate...it is a buisiness application
> that
> our customers cannot run![/color]

"Garry" <garrygrolman******.com> wrote in message
news:eDDWYqYZHHA.4616@TK2MSFTNGP03.phx.gbl...
[color=blue]
> Are you using the Microsoft Best Practices - for instance, if the app
> tries to write anything to Program Files on the target computer where the
> user is not an ADMIN, you can get funny messages. Perhaps the DLL is not
> registered properly..[/color]

Or, even worse, the app is trying to write to HKEY_LOCAL_MACHINE - that is
*very* tricky with Vista, and actively discouraged by Microsoft...
[color=blue]
> WE use VMWare very successfully for this kind of problem. You can install
> a Vista VM under XP but, I am not sure if the environment is really
> identical to a real time Vista installation.[/color]

I use VirtualPC for the same thing - it's certainly close enough to the real
thing for testing purposes...
[color=blue]
> Consider also testing the APP on Vista 64 bit. This is the future so get
> used to it.[/color]

Absolutely!

Garry,
We tried to regsvr32 the file: documark_bsl.dll under the c:\Program
Files\Midmark\Documark directory.

We are getting an error though when completing the previously stated
procedure.

The module "documark_bsl.dll" was loaded but the call to DllRegisterServer
failed with error code 0x80004005.

For more information about this problem, search online using the error code
as a search item.

"Garry" wrote:
[color=blue]
> Brad Hi,
>
> We also have a complex VB6 financial app which, when we installed on Vista
> 32 - runs with no problems.
>
> Are you using the Microsoft Best Practices - for instance, if the app tries
> to write anything to Program Files on the target computer where the user is
> not an ADMIN, you can get funny messages. Perhaps the DLL is not registered
> properly..
>
> Perhaps the DLL should be in Program Files\Common Files\Company
> Name\DLLName.dll and not %System32%.
>
> Perhaps you should have a VISTA machine with VB6 installed as your test
> developement environment. See if the error happens there within the
> development environment.
>
> WE use VMWare very successfully for this kind of problem. You can install a
> Vista VM under XP but, I am not sure if the environment is really identical
> to a real time Vista installation.
>
> Consider also testing the APP on Vista 64 bit. This is the future so get
> used to it.
>
> Garry
>
>
> "Brad" <Brad@discussions.microsoft.com> wrote in message
> news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...[color=green]
> > I'm getting an Error 429 : ActiveX component can't create object when
> > trying
> > to run a program that ran perfectly fine on Windows XP. It was created in
> > VB6
> > but does not run on my version of Vista Business. Anyone have any ideas as
> > to
> > why this may not work. We are desperate...it is a buisiness application
> > that
> > our customers cannot run![/color]
>
>
>[/color]

Brad,

Try registering the component from an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting [url]http://www.winhelponline.com[/url]


"Brad" <Brad@discussions.microsoft.com> wrote in message news:B9654E07-EB35-4CA9-AFD4-80FE5D686AE3@microsoft.com...
Garry,
We tried to regsvr32 the file: documark_bsl.dll under the c:\Program
Files\Midmark\Documark directory.

We are getting an error though when completing the previously stated
procedure.

The module "documark_bsl.dll" was loaded but the call to DllRegisterServer
failed with error code 0x80004005.

For more information about this problem, search online using the error code
as a search item.

"Garry" wrote:
[color=blue]
> Brad Hi,
>
> We also have a complex VB6 financial app which, when we installed on Vista
> 32 - runs with no problems.
>
> Are you using the Microsoft Best Practices - for instance, if the app tries
> to write anything to Program Files on the target computer where the user is
> not an ADMIN, you can get funny messages. Perhaps the DLL is not registered
> properly..
>
> Perhaps the DLL should be in Program Files\Common Files\Company
> Name\DLLName.dll and not %System32%.
>
> Perhaps you should have a VISTA machine with VB6 installed as your test
> developement environment. See if the error happens there within the
> development environment.
>
> WE use VMWare very successfully for this kind of problem. You can install a
> Vista VM under XP but, I am not sure if the environment is really identical
> to a real time Vista installation.
>
> Consider also testing the APP on Vista 64 bit. This is the future so get
> used to it.
>
> Garry
>
>
> "Brad" <Brad@discussions.microsoft.com> wrote in message
> news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...[color=green]
> > I'm getting an Error 429 : ActiveX component can't create object when
> > trying
> > to run a program that ran perfectly fine on Windows XP. It was created in
> > VB6
> > but does not run on my version of Vista Business. Anyone have any ideas as
> > to
> > why this may not work. We are desperate...it is a buisiness application
> > that
> > our customers cannot run! [/color]
>
>
>[/color]

Ramesh,

We did run a regsvr32 in the elevated Command Prompt window, but we still
recieve an error 429 - ActiveX component can't create object when we start
the application. Just wondering if you have any suggestions on what to do at
this point. Thanks.

Brad


"Ramesh, MS-MVP" wrote:
[color=blue]
> Brad,
>
> Try registering the component from an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
>
> --
> Regards,
>
> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
> Windows® Troubleshooting [url]http://www.winhelponline.com[/url]
>
>
> "Brad" <Brad@discussions.microsoft.com> wrote in message news:B9654E07-EB35-4CA9-AFD4-80FE5D686AE3@microsoft.com...
> Garry,
> We tried to regsvr32 the file: documark_bsl.dll under the c:\Program
> Files\Midmark\Documark directory.
>
> We are getting an error though when completing the previously stated
> procedure.
>
> The module "documark_bsl.dll" was loaded but the call to DllRegisterServer
> failed with error code 0x80004005.
>
> For more information about this problem, search online using the error code
> as a search item.
>
> "Garry" wrote:
>[color=green]
> > Brad Hi,
> >
> > We also have a complex VB6 financial app which, when we installed on Vista
> > 32 - runs with no problems.
> >
> > Are you using the Microsoft Best Practices - for instance, if the app tries
> > to write anything to Program Files on the target computer where the user is
> > not an ADMIN, you can get funny messages. Perhaps the DLL is not registered
> > properly..
> >
> > Perhaps the DLL should be in Program Files\Common Files\Company
> > Name\DLLName.dll and not %System32%.
> >
> > Perhaps you should have a VISTA machine with VB6 installed as your test
> > developement environment. See if the error happens there within the
> > development environment.
> >
> > WE use VMWare very successfully for this kind of problem. You can install a
> > Vista VM under XP but, I am not sure if the environment is really identical
> > to a real time Vista installation.
> >
> > Consider also testing the APP on Vista 64 bit. This is the future so get
> > used to it.
> >
> > Garry
> >
> >
> > "Brad" <Brad@discussions.microsoft.com> wrote in message
> > news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...[color=darkred]
> > > I'm getting an Error 429 : ActiveX component can't create object when
> > > trying
> > > to run a program that ran perfectly fine on Windows XP. It was created in
> > > VB6
> > > but does not run on my version of Vista Business. Anyone have any ideas as
> > > to
> > > why this may not work. We are desperate...it is a buisiness application
> > > that
> > > our customers cannot run![/color]
> >
> >
> >[/color]
>[/color]

Brad,

Did you get any errors when registering the module? It appears that the registration was not successful. Check if the ProgID that you're initializing in your program is listed in the registry.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting [url]http://www.winhelponline.com[/url]


"Brad" <Brad@discussions.microsoft.com> wrote in message news:D8304832-3BAD-4943-80DF-5E1E88CBE881@microsoft.com...
Ramesh,

We did run a regsvr32 in the elevated Command Prompt window, but we still
recieve an error 429 - ActiveX component can't create object when we start
the application. Just wondering if you have any suggestions on what to do at
this point. Thanks.

Brad


"Ramesh, MS-MVP" wrote:
[color=blue]
> Brad,
>
> Try registering the component from an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
>
> --
> Regards,
>
> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
> Windows® Troubleshooting [url]http://www.winhelponline.com[/url]
>
>
> "Brad" <Brad@discussions.microsoft.com> wrote in message news:B9654E07-EB35-4CA9-AFD4-80FE5D686AE3@microsoft.com...
> Garry,
> We tried to regsvr32 the file: documark_bsl.dll under the c:\Program
> Files\Midmark\Documark directory.
>
> We are getting an error though when completing the previously stated
> procedure.
>
> The module "documark_bsl.dll" was loaded but the call to DllRegisterServer
> failed with error code 0x80004005.
>
> For more information about this problem, search online using the error code
> as a search item.
>
> "Garry" wrote:
> [color=green]
> > Brad Hi,
> >
> > We also have a complex VB6 financial app which, when we installed on Vista
> > 32 - runs with no problems.
> >
> > Are you using the Microsoft Best Practices - for instance, if the app tries
> > to write anything to Program Files on the target computer where the user is
> > not an ADMIN, you can get funny messages. Perhaps the DLL is not registered
> > properly..
> >
> > Perhaps the DLL should be in Program Files\Common Files\Company
> > Name\DLLName.dll and not %System32%.
> >
> > Perhaps you should have a VISTA machine with VB6 installed as your test
> > developement environment. See if the error happens there within the
> > development environment.
> >
> > WE use VMWare very successfully for this kind of problem. You can install a
> > Vista VM under XP but, I am not sure if the environment is really identical
> > to a real time Vista installation.
> >
> > Consider also testing the APP on Vista 64 bit. This is the future so get
> > used to it.
> >
> > Garry
> >
> >
> > "Brad" <Brad@discussions.microsoft.com> wrote in message
> > news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...[color=darkred]
> > > I'm getting an Error 429 : ActiveX component can't create object when
> > > trying
> > > to run a program that ran perfectly fine on Windows XP. It was created in
> > > VB6
> > > but does not run on my version of Vista Business. Anyone have any ideas as
> > > to
> > > why this may not work. We are desperate...it is a buisiness application
> > > that
> > > our customers cannot run! [/color]
> >
> >
> >[/color]
>[/color]

Also sure that you're registering the correct dll ie make sure that that is
definitely the component that is causing the error. It may be another.

Go back to the source code, if you have it, and look for statements
containing 'CreateObject'. Then find the file associated with the ProgID eg
via the registry.

--
Jon


"Brad" <Brad@discussions.microsoft.com> wrote in message
news:D8304832-3BAD-4943-80DF-5E1E88CBE881@microsoft.com...[color=blue]
> Ramesh,
>
> We did run a regsvr32 in the elevated Command Prompt window, but we still
> recieve an error 429 - ActiveX component can't create object when we start
> the application. Just wondering if you have any suggestions on what to do
> at
> this point. Thanks.
>
> Brad
>
>
> "Ramesh, MS-MVP" wrote:
>[color=green]
>> Brad,
>>
>> Try registering the component from an elevated Command Prompt window.
>> Click Start, click All Programs, click Accessories, right-click Command
>> Prompt, and then click Run as administrator.
>>
>> --
>> Regards,
>>
>> Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
>> Windows® Troubleshooting [url]http://www.winhelponline.com[/url]
>>
>>
>> "Brad" <Brad@discussions.microsoft.com> wrote in message
>> news:B9654E07-EB35-4CA9-AFD4-80FE5D686AE3@microsoft.com...
>> Garry,
>> We tried to regsvr32 the file: documark_bsl.dll under the
>> c:\Program
>> Files\Midmark\Documark directory.
>>
>> We are getting an error though when completing the previously stated
>> procedure.
>>
>> The module "documark_bsl.dll" was loaded but the call to
>> DllRegisterServer
>> failed with error code 0x80004005.
>>
>> For more information about this problem, search online using the error
>> code
>> as a search item.
>>
>> "Garry" wrote:
>>[color=darkred]
>> > Brad Hi,
>> >
>> > We also have a complex VB6 financial app which, when we installed on
>> > Vista
>> > 32 - runs with no problems.
>> >
>> > Are you using the Microsoft Best Practices - for instance, if the app
>> > tries
>> > to write anything to Program Files on the target computer where the
>> > user is
>> > not an ADMIN, you can get funny messages. Perhaps the DLL is not
>> > registered
>> > properly..
>> >
>> > Perhaps the DLL should be in Program Files\Common Files\Company
>> > Name\DLLName.dll and not %System32%.
>> >
>> > Perhaps you should have a VISTA machine with VB6 installed as your test
>> > developement environment. See if the error happens there within the
>> > development environment.
>> >
>> > WE use VMWare very successfully for this kind of problem. You can
>> > install a
>> > Vista VM under XP but, I am not sure if the environment is really
>> > identical
>> > to a real time Vista installation.
>> >
>> > Consider also testing the APP on Vista 64 bit. This is the future so
>> > get
>> > used to it.
>> >
>> > Garry
>> >
>> >
>> > "Brad" <Brad@discussions.microsoft.com> wrote in message
>> > news:B6D962C0-AC1B-49E0-8E42-FD79F19B8266@microsoft.com...
>> > > I'm getting an Error 429 : ActiveX component can't create object when
>> > > trying
>> > > to run a program that ran perfectly fine on Windows XP. It was
>> > > created in
>> > > VB6
>> > > but does not run on my version of Vista Business. Anyone have any
>> > > ideas as
>> > > to
>> > > why this may not work. We are desperate...it is a buisiness
>> > > application
>> > > that
>> > > our customers cannot run!
>> >
>> >
>> >[/color]
>>[/color][/color]

The answer is supposedly here:
[url]http://support.microsoft.com/kb/247979[/url]
I haven't tried it.
There is a scripting issue, and on this link above there is a patch
that you can download and install.
Let us know how it works out.

Thanks,
John


--
jshenry1963
------------------------------------------------------------------------
jshenry1963's Profile: [url]http://forums.techarena.in/member.php?userid=23467[/url]
View this thread: [url]http://forums.techarena.in/showthread.php?t=704469[/url]

[url]http://forums.techarena.in[/url]

I'm facing the same problem.... have you finally found a solution????


--
mia6224
------------------------------------------------------------------------
mia6224's Profile: [url]http://forums.techarena.in/members/135737.htm[/url]
View this thread: [url]http://forums.techarena.in/vista-help/704469.htm[/url]

[url]http://forums.techarena.in[/url]