Solution
This issue can be seen due to a missing entry in the Windows Registry for the object library that is presenting the reported behavior, or that the application that provides the type library has a different bitness than the LabVIEW version you are using.
Make sure the application you are trying to control, such as Microsoft Outlook, has the same bitness of the LabVIEW version being used.
A possible workaround is to manually create an entry for the type library in the registry, following these steps:
WARNING: Inappropriate changes to the Windows Registry can cause unexpected behavior in the Operating System. To safeguard against such an event, you should backup your existing Registry by selecting File>>Export after launching the Registry Editor and before making any changes.
1. In the Windows search bar, type
regedit and press <Enter> to open the Registry Editor.
2. Navigate to
Computer\HKEY_CLASSES_ROOT\TypeLib.
3. Using <Ctrl-F>, search for the type library object. You should see something similar to the following:
- Notice that when you expand the keys as shown above, there is a key called "win64", but not one called "win32".
4. Create a new key and copy the contents in the existing key to the newly created one. The content of the key is the path to the type library file.
- To create the new key, you can right-click the key named "0" select New>>Key, and name it "win32".
- You can copy the contents from the "win64" key by opening it then right-click its entry, select Modify and copy the text in the Value data parameter. Click on Cancel to close the window.
- To paste the value, go to the newly created key and right-click its entry to Modify it and paste the value in the Value data parameter, the result should look similar to the image above.
5. Close all LabVIEW windows.
6. After launching LabVIEW again, the properties or methods appear correctly.