Hey @ThatTechGuy,
This message displays when ctx.Unc.NetUseWithCredentials() fails and the last error is not 1219 in this section of the code in Toems-ServiceCore/EntityServices/ServiceRemoteAccess.cs
var basePath = Path.Combine(ectx.Settings.GetSettingValue(SettingStrings.StoragePath), "software_uploads", "99999999-9999-9999-9999-999999999999");
if (uncService.NetUseWithCredentials() || uncService.LastError == 1219)
{
try
{
var installer = Path.Combine(basePath, "Remotely_Installer.exe");
var x64 = Path.Combine(basePath, "Remotely-Win10-x64.zip");
var x86 = Path.Combine(basePath, "Remotely-Win10-x86.zip");
//no need to check if exists, exception will catch when looking for size
var hasSize = new FileInfo(installer).Length > 0;
if (!hasSize)
return new DtoActionResult() { ErrorMessage = "Remotely_Installer.exe Is Missing From Storage Path" };
hasSize = new FileInfo(x64).Length > 0;
if (!hasSize)
return new DtoActionResult() { ErrorMessage = "Remotely x64 File Is Missing From Storage Path" };
hasSize = new FileInfo(x86).Length > 0;
if (!hasSize)
return new DtoActionResult() { ErrorMessage = "Remotely x86 File Is Missing From Storage Path" };
}
catch
{
return new DtoActionResult() { ErrorMessage = "Remote Access Files Have Not Been Copied To The Storage Path" };
}
}
else
{
return new DtoActionResult() { ErrorMessage = "Could Not Determine If Remote Access Installer Files Are Available" };
}
return new DtoActionResult() { Success = true };
So your specific error does not mean one of the files is definitely missing. It means TOEM could not connect/authenticate to the storage path well enough to check whether the files are present. If it can connect but the files are missing or zero bytes, you’d get one of the more specific messages like:
Remotely_Installer.exe Is Missing From Storage Path
If I were you, I would start with the TOEM application log, look for storage connection errors and based on the error code (if present) diagnose from there.
