Skip to content

Fail to Copy Elliott to Local Path & Create Desktop Icon

← Systems Manager
Release Date: 09/12/2024
Version: 8.5 & Up

Q - One user is running Elliott 8.5 right now. I tried to upgrade this workstation to Elliott 8.6. So I navigated to the <ElliottRoot>\Bin86 folder and execute EL860.EXE.  I received the following message:
System.Management.ManagementException: Invalid class at
System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
  at  System.Management.ManagementObject.Initialize(Boolean getObject)
  at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName)
  at System.Management.ManagementBaseObject.get_item(String propertyName)
  at EL860.MappedDriveResolver.ResolverToRootUNC(String path) in C:\Users\cls\Source\Repos\EL860\EL860\MappedDriveResolver.cs:line 238 
  at  EL860.MappedDriveResolver.ResolverToUNC(String path) in ....

See sample screen below:


We tried a few things and it did not help:
  1. While this machine is already on Elliott 8.5, we tried to run <ElliottRoot>\Bin85\EL850.EXE. We got a similar message.
  2. We logged into a different Windows user, including Administrator, to run EL860.EXE.  We still got the same error.  
This machine is running on Windows 10 and is the only machine in our organization that fails to run EL860.EXE.  What do we do?

A -  The message implies the failure takes place when EL860.EXE tries to resolve the UNC path and a  Windows systems level component (class) is missing.  Since this machine is already running on Elliott 8.5 from a local path, that implies when you used EL850.EXE to create the local desktop icon in the past, it was working at that time.  So it is reasonable to conclude that there's certain updates made to this workstation to cause this error.

It will be difficult to figure out why it fails.  Updating to Windows 11 may help (edit: we were told that this machine does not meet the minimum requirement to upgrade to Windows 11).  One easy way is to manually create the local Bin86 folder by copying from the network path.  Here are the instructions:
  1. Navigate to the existing local path of your Elliott 8.5 icon. This would be something like: C:\Users\userid\AppData\Local\Netcellent\M\Elliott7\Bin85\EL850CC.EXE
  2. Create the Bin86 folder like C:\Users\userid\AppData\Local\Netcellent\M\Elliott7\Bin86.
  3. Copy from your network path all files in Bin86 folder: M:\Elliott7\Bin86 for everything except do not copy the subfolders to  C:\Users\userid\AppData\Local\Netcellent\M\Elliott7\Bin86.
  4. Right click on  C:\Users\userid\AppData\Local\Netcellent\M\Elliott7\Bin86\EL860CC.EXE to create a desktop icon.
Rename your EL860CC.EXE desktop icon to "Elliott 8.6."  Now run Elliott 8.6 to see if it works.

If You Encounter this Problem on the Server

Note, when you use EL860.EXE to create a desktop icon, it performs the following three tasks:
  1. Create the network path Bin86 folder to the local path.
  2. Create the desktop icon and menu.
  3. Create DEP (Data Execution Prevention) registry entry.
Since #3 above is only applicable to the Windows server, you only need to perform task 1 & 2 that are included in the instructions above.  If this issue is on a server environment, you can perform task 3 with the instructions in the following KB article: https://support.elliott.com/knowledgebase/articles/531028-manage-data-execution-prevention-dep-by-editing



EMK

Feedback and Knowledge Base

(thinking…)