Microsoft KB Archive/231393

= BUG: Using DCOM with an Active Document =

Article ID: 231393

Article Last Modified on 5/22/2003

-

APPLIES TO


 * Microsoft Visual Basic 6.0 Learning Edition
 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition

-



This article was previously published under Q231393



SYMPTOMS
When you navigate to an Active Document that uses Distributed Component Object Model (DCOM), you may receive the following message:

Internet Explorer is opening file of unknown type: .VBD from...

This happens when CliReg32.exe is included in the CAB instead of being downloaded from the Microsoft Web site or installed as a separate CAB from the local server.



CAUSE
When the user packages a DCOM Active Document by using the Visual Basic Package and Deployment Wizard (PDW), the user can include CliReg32.exe in the current CAB. However, this option does not work correctly.



RESOLUTION
To work around the problem, download CliReg32.exe from the Microsoft Web site. Alternatively, you can download Msracli.cab from the Microsoft Web site and refer to in from your local Web server.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
If you look in the code download error log file, you should see the following error:

Code Download Error: (hr = 80070057) The parameter is incorrect.

To view this file, follow these steps:  In Microsoft Internet Explorer 4.0, click Internet Options on the View menu. Or, in Internet Explorer 5, click Internet Options on the Tools menu. On the General tab, click Settings. Click View Files.  Click the Name column header to sort the files. You should see at least one file named something like this: ?CodeDownloadErrorLog!name={0000000-0000-0000-0000-000000000000} where the zeroes contain the class ID of your Active Document. </li> Close the dialog boxes that you opened in steps 2 and 3.</li> Drag the error log into Internet Explorer.</li></ol>

Note CliReg32.exe could be packaged in its own CAB but not in the same one as the .vbr or .tlb files. Note that the PDW assumes the .inf file name is Msracli.inf when you choose a local CAB. To avoid changing each .inf file that is generated for any DCOM project, name the .inf in your CLIREG CAB Msracli.inf.

<div class="references_section">