If you get that kind of error, in most cases that means the automation, which should be registered with that given GUID in your system is missing or misconfigured. In both cases the system does not know the common name of the system. That’s why you get that cryptic message.
Search the web (e.g. google.com, microsoft.com) to get more information about the automation. The given GUID is unique worldwide! So you’ll get the name for the automation quite easy. The variable name, where the automation is used, is also a hint for the name, also comments in the code.
Then search for the file on the server using windows explorer, where the nav service is installed and where you want to run the nav object (report, table, codeunit, …), if that automation file (dll) is physically installed.
- If you do not find it, then it’s missing. download it from the vendor or install the missing software, which includes that automation.
- If you find the file, then it was not registered correctly. In that case you need to run the registry tool regsrv32. First uninstall, then re-install the automation:
Regsvr32 [/u] [/n] [/i[:cmdline]] <full path to dllname>
for more details and troubleshooting follow this.
Typical GUIDs according that issue:
- 000208D5-0000-0000-C000-000000000046: Microsoft.Office.Interop.Excel
- 248DD896-BB45-11CF-9ABC-0080C7E7B78D: Winsock Control 6.0
- DB07BCE5-B131-11D3-9219-00002430F8E2: CFront Plus
- F5078F18-C551-11D3-89B9-0000F81FE221: MS XML 4.0 (or 6.0)
If you can’t find the GUID on the web, then it is probably a custom automation developed by yourself or a vendor years ago.