SS10 - "Label Shapes with ID" Tool Not Working

Hello,

I'm wondering if anyone else has encountered this problem and found a fix on SS10 V 1.03.00 where the Label Shapes with ID tool will not run. Whether I access it from the FDOT Toolbar under Actions > Label Shapes with ID or in the Tasks window under FDOT Plans Development > Quantities I encounter the same error:

I've asked coworkers who are also on SS10 to try the same and they receive the error as well. Looking around the forum, it appears this issue has been present for a while but most of those posts go unanswered. While trying to trouble shoot, we dug into the VBA editor within microstation and pulled the instructions attached to the tool for both SS10 (not working) and SS4 (working). In the attached file, we overlaid the text and the red font is SS10, the green is SS4. It looks like extra ElseIf statements were added to the LabelShapeElements sub and that after that sub, the remainder of the code is the same.

Thank you!

Riley

PDF

  • Riley,

    This is a defect in the Select Series 10 software where an OCX file that was registered during installations of Select Series 4 applications does not get registered during the installation of Select Series 10 applications. We have added this command to the FDOTSS10 installer, but sometimes it apparently does not work even still.

    Try this:

    1. Exit FDOTSS10, and any other forms of Bentley MicroStation product.
    2. See if the following file exists:
      1. C:\Program Files (x86)\Common Files\Bentley Shared\GEOPAK\08.11.09\BentleyControls.ocx
    3. If not, see if you can find that file anywhere and use that path below
    4. If so, open a command prompt As Administrator (in the windows search bar type command, right click on the command prompt app and select “run as administrator”)
    5. Key in the following two commands exactly as shown below (or with the alternate path), spacing matters (do not include “a.” and “b.”):
      1. Regsvr32 /u "C:\Program Files (x86)\Common Files\Bentley Shared\GEOPAK\08.11.09\BentleyControls.ocx"
      2. Regsvr32 "C:\Program Files (x86)\Common Files\Bentley Shared\GEOPAK\08.11.09\BentleyControls.ocx"
    6. Then open FDOTSS10 again and see if you can configure the bar menu, or check LDM to see if the issue is resolved.

     

    Matt Sexton
    CADD Applications Support Coordinator
    Florida Department of Transportation
    Engineering/CADD Systems Office
    850-414-4840
    matt.sexton@dot.state.fl.us

  • Matt,

    It worked for me! Now to try and get everyone to do the same at work.

    Thanks!

    Riley

  • Riley,

    This is a defect in the Select Series 10 software where an OCX file that was registered during installations of Select Series 4 applications does not get registered during the installation of Select Series 10 applications. We have added this command to the FDOTSS10 installer, but sometimes it apparently does not work even still.

    Try this:

    1. Exit FDOTSS10, and any other forms of Bentley MicroStation product.
    2. See if the following file exists:
      1. C:\Program Files (x86)\Common Files\Bentley Shared\GEOPAK\08.11.09\BentleyControls.ocx
    3. If not, see if you can find that file anywhere and use that path below
    4. If so, open a command prompt As Administrator (in the windows search bar type command, right click on the command prompt app and select “run as administrator”)
    5. Key in the following two commands exactly as shown below (or with the alternate path), spacing matters (do not include “a.” and “b.”):
      1. Regsvr32 /u "C:\Program Files (x86)\Common Files\Bentley Shared\GEOPAK\08.11.09\BentleyControls.ocx"
      2. Regsvr32 "C:\Program Files (x86)\Common Files\Bentley Shared\GEOPAK\08.11.09\BentleyControls.ocx"
    6. Then open FDOTSS10 again and see if you can configure the bar menu, or check LDM to see if the issue is resolved.

     

    Matt Sexton
    CADD Applications Support Coordinator
    Florida Department of Transportation
    Engineering/CADD Systems Office
    850-414-4840
    matt.sexton@dot.state.fl.us

  • "Class not registered. Looking for object with CLSID:{C62A69F0-16DC-11CE-9E98-00AA00574A4F}"

    Registering BentleyControls.ocx did not work in our situation. Though it was the same symptom, with the same VBA error, a Microsoft Visual Basic error window also displayed with the above message.

    I'm taking the time with this because the concepts here apply to *any* COM not registered issue.

    Googling the above error message or CLSID (Class ID) points to \windows\system32\fm20.dll not being registered. (Error message when you start Microsoft Dynamics GP: "Errors occurred during load" or when you import a package file that has a user form: Class {C62A69F0-16DC-11CE-9E98-00AA00574A4F} of control frmXXX was not a loaded control class.) But registering that dll per the web page's instructions still doesn't work.

    The reason is that there are *two* versions/copies of fm20.dll in Windows - a 64bit version and a 32bit version. The web page points only to the 64bit version. But SS10 is a 32bit app. Registering the 32bit fm20.dll located in \windows\syswow64\ *did* fix the problem.

    Cause:

    Fm20.dll belongs to Microsoft Forms, part of Microsoft Office. This user's Office was upgraded from the 32bit version to the 64bit just a few days ago. This is likely the cause for the registering to break.

    Understanding:

    COMs (.com, .dll, .ocx) are software subroutine library files. The subroutines standardize common tasks across software applications. The COM file can have any number of differing and separate tasks that can be called from (virtually) any software app. Registering is the process of creating in the system registry database a "directory" of all the available subroutine tasks. It saves the location of the COM file (so it can be loaded into memory on demand by Windows), and the entry point addresses into the COM file for the various subroutine tasks.

    COMs are either 64bit or 32bit versions. In 32bit Windows, dealing with registering issues is much more straight forward. But in 64bit Windows, which virtually everyone is now on, it can be complicated because 64bit Windows strives to be backward compatible with 32bit software. Thus, 64bit system files are all stored in \windows\system32\ while 32bit system files are stored in \windows\syswow64\. These folder names seem contradictory. Under the old 16bit versions of Windows, system files were stored in \windows\system\ (which today is virtually empty). When 32bit Windows came, system files were stored in \windows\system32\. But technical reasons prevented Microsoft from keeping the pattern with a \windows\system64\ directory name. They had to keep the system32 name. So they moved 32bit system files to the SysWOW64 directory and kept the 64bit system files in the System32 directory. WOW stands for Windows-on-Windows and represents the concept of how 32bit software runs in a sense "on top of" 64bit Windows.

    Bottom line: Registering issues need to take into account whether the issue is related to a 64bit app or, as in our case here, a 32bit app, and their respective system folder locations. The safest approach is to always register both COM versions, which the Microsoft instructions above did not take into account.

    Note: Though the regsvr32 utility will tell you that the COM is already registered, Matt's instructions are to unregister the COM first and then re-register it. This is because registerings can get damaged and even confused. Also, it is important to remember that registering a COM may require Admin privileges in order to access system folders and system areas of the registry database. Software should be handling the registration process during installation. The problem of the BentleyControls.ocx not registering correctly is likely the result of not installing the software using Run as Administrator, giving the privileges needed to complete the registerings.

  • We have found that many times, a users PC that was working begins throwing this error. Reregistering the DLL appears to be the needed fix, but we have been unable to find any common cause. We have suspicions that some update from Microsoft is the culprit but have never been able to actually nail it down. 


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996