TrueImageCmd.exe appears to mount but no drive is present.

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 1

Hello,

I am having difficulty mounting a backup image to a logical drive using TrueImageCmd.exe.

Executing a command via cmd such as:

TrueImageCmd.exe /explore /partition:1-1 /letter:Z /password:aBcD3f /filename:"\\192.168.1.150\share\1234567890\VolBackup\20120114 20.55.08\volBackup1.tib"

 - where the partition is known to exist, the drive letter is guaranteed to be free, the password is correct, and the file path points to a valid TIB file - will produce the output:

Assigning logical drives letters.

Operation succeeded.

However, the assigned drive will not appear in any drive list and executing the command:

TrueImageCmd.exe /unplug /letter:all

yields the output:

Cannot unplug a logical drive created for exploring the image archive.

Other methods of mounting a backup image to a logical drive (such as with Kaseya Backup local UI) fail in a similar manner. Using the exact same command from another computer with access to the UNC path works flawlessly and the mounted drive can be explore and unplugged just fine. Unfortunately, this workaround does not help us with what we need to do. We would still like to be able to mount a backup to a logical drive on the machine for which the backup was made.

Out of about 80 machines which have this command ran daily, six of them reliably experience this issue. The other machines execute the command and mount the drive successfully. The six machines in question don't seem to have much in common. Their operating systems range from Windows Vista and Windows 7 to Windows Server 2003 and Windows Server 2008. Most have version 10.0-18058 of the Acronis client installed, though one still has version 9.7-8218.

Any help or direction you could provide would be appreciated.

Thanks,
Brandon

lun 23/01/2012 - 19:19
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 1

An update:

I found an issue in the Acronis Knowledge Base that pretty much matches my problem exactly.

I wrote a PowerShell script to check whether the TimounterMonitor.exe process is running before attempting to mount an image. If the process was not running I have it automatically run the associated executable file based on whether the machine is 32- or 64-bit.

Unfortunately, this doesn't seem to fix the problem and even though I can manually verify that TimounterMonitor.exe is running, no drives are ever mounted.

I'm going to try this on a few other machines with the same problem and attempt to look for another explanation.

mer 08/02/2012 - 22:21
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Contributions: 27
Commentaires: 1940

Even if missing TimounterMonitor is the cause, it may be unable to detect the mounted image immediately after start, and may need some delay to initialize before it starts to work properly. The default advice - to contact support?

jeu 09/02/2012 - 04:32