MOD2000: Deploying Package with MSCal.ocx Causes Error: "The file ...\$(DllSelfRegisterEx) Could Not Be Registered..."

When you deploy a package created by the Microsoft Office 2000 Developer (MOD) Package and Deployment Wizard, you may receive the following error message and then Setup is not successful.

This problem can occur under the following conditions:

• You are including the Microsoft Calendar Control (MSCal.ocx) in your Run-Time Setup.
• There is a reference to the MSCal.ocx file in your list of library references.

To resolve this problem, obtain Microsoft Office 2000 Service Release 1/1a (SR-1/SR-1a).

To obtain SR-1/SR-1a, click the article number below to view the article in the Microsoft Knowledge Base: Microsoft Access 2000 includes a dependency file for the MSCal.ocx file that does not work correctly with the MOD Package and Deployment Wizard. To temporarily work around this problem, you can fix this file. To do so, follow these steps:

1. In a text editor such as Notepad, open the MSCal.dep file.
2. Remove the letters "Ex" from the Register=$(DLLSelfRegisterEx) line so that it looks as follows:
   Register=$(DLLSelfRegister)
3. Save the MSCal.dep file, and then close Notepad.
4. Re-create the package to include the modified dependency file.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was corrected in Microsoft Office 2000 SR-1/SR-1a.

Steps to Reproduce Problem

1. Open the sample database Northwind.mdb.
2. Start the Package and Deployment Wizard.
3. On the paged named Package and Deployment Wizard - Included Files, click to select the Include Access Runtime check box, and add the MSCal.ocx file. The default location for this file is C:\Program Files\Microsoft Office\Office.
4. Create the rest of the package by accepting all defaults.
5. Deploy the package to a clean computer (a computer that has a newly installed version of Windows, and no other applications).

At the last Setup stage, note that you receive the error message described in the "Symptoms" section of this article.