How to access COM+ Component (windows 2000 server) from Client machine 1

[ArunGupta]

Hello,

I need help in how to access COM+ Component from Client machine (windows-98 - Window application) over the internet.


Let me explain - we are using ActiveX dll in our project. We have windows 2000 server as server and windows 98 as client. We want to register ActiveX dll under COM+ in windows 2000 server and want to use the dll in vb application (Window Application) running at the client place with windows 98. For this we created the dll and added the component using Component Services under Administrators Tools. We created a new application and added the component under it. Then we exported the package and selected ‘Application Proxy - Install on other machines to enable access to this machine’. Package is exported and two files are created one with .msi extension. On client machine we run the exported file (windows installer application (.msi)) and it is installed. Now from the client application (Window Application) when we call this component using CreateObject (‘ClassID’) which lies on remote machine (windows 2000 server - on internet) we get error ‘429 - ActiveX component can't create object’, '424-Object Required' or '462 - The remote server computer does not exist or is unavailable.'.

Can you tell what to do so that the Component will works on windows 2000 server over the Internet.

Waiting for your reply…

Thanks

Arun Kumar Gupta

 

[vishnuprasad]

Use *.TLB/*.VBR files,*.exe with Package and deployment wizard for client side installation.

 

[Guest_imported]

Hi Vishnu,

I am sorry to ask this can u be more specific ..?
How to install this *.TLB/*.VBR. *.EXE files
i am new to com+
your help is really needed

 

[wengyan]

If you developed ActiveX DLL by Visual Basic.Pls make sure remote server files choice is checked in project properties.
After build,you will get a file *.vbr.In client you can use CLIREG32.EXE command to register vbr file.If you developed ActiveX DLL by Visual C++.You can register the tlb file with regsvr32 command,then use dcomcnfg.exe to configure the client setting.

 

[Famika]

There is a bug in Win 2K if you run the Service Pack 2.
Take a look at this article in Microsoft knowledge base
Q289821

Workaround:
Register the DLL locally using regsvr32, then, run the MSI package created by COM+. This should resolve the problem for a while until service pack 3 releases.

Regards