Users of client computers may receive an "An error has occurred in the script on this page" error message for certain Webparts in Business Portal

In Business Portal, users of client computers may receive the following error message for certain Webparts:
An error has occurred in the script on this page.
Additional detail in the error message indicates the following:

Object doesn't support this property or method.
URL: http//servername/BusinessPortal/UI/ResultViewer/Scripts/


The CHListFactory Object is a Microsoft ActiveX control that is installed on each computer when users access certain parts of Business Portal for the first time after installation. Under typical conditions, the CHListFactory Object is installed correctly on the computer if the user is a member of the Administrators local group.


To resolve this issue, you must manually install the CHListFactory Object. To do this, you must be an administrator.
  1. On the server that is running Microsoft Internet Information Services (IIS), extract the following two files from the file:
    • MbfWebBehaviors.dll
    • Msvcr71.dll

    Note By default, the following is the path for the .cab file:
    C:\Program Files\Microsoft Business Solutions\Business Portal\ui\ResultViewer\Scripts\
  2. Log on to the client computer as a local administrator.

  3. In Windows Explorer, create a new folder on the client computer. The path for the new folder may be similar to the following:
    C:\Program Files\Microsoft Business Solutions\Business Portal
  4. Give any non-administrator users who will use Business Portal on this computer NTFS read access to the folder that you created. For example, a non-administrator user may be a user who is a member of only the Users group.
  5. Copy the two files that you extracted in step 1 to the new folder.
  6. Register the MbfWebBehaviors.dll file by issuing the following command at a command prompt that is rooted in the folder that you created in step 3:
    regsvr32 MbfWebBehaviors.dll

More Information

This issue cannot be reproduced under typical circumstances. The issue seems to be an environmental issue at the operating system level. The issue may involve registry permissions.


For more information about how to register .dll files, click the following article number to view the article in the Microsoft Knowledge Base:

844592 How to register a .dll file