I have been pretty lucky when it came to inView mail installs so far. However, my luck just ran out. I tried to install View Mail on 3 freshly imaged Windows 2000 machines with only Office 2000 on them. They are Pentium 133 MHz with 64 MB of RAM (they are real slow with W2K).<br><br>I get the following error messages on all 3 machines:<br><br>1st error popup window:<br><br>UpdateRegistryFromResourceFailed<br>OK<br><br>2nd error popup window:<br><br>RegisterServer Failed<br>OK<br><br>Then I get a "Telephone Record & Playback Error" window:<br><br>Unable to create the client connector. The file AVTrapConnectionHolderSvr.exe is either missing from the system directory, an incorrect version, or corrupt. A full installation may solve the problem.<br>OK<br><br>I tried to uninstall (using Add/remove programs) View Mail & then re-install it but this did not get rid of the error messages.<br><br>I can ping the unity server using the DNS name.<br><br>Thanks,<br><br>Kimberly<br><br><br>
Unity version 18.104.22.168 (with soft prompts) VMO version 22.214.171.124 I installed the VMO client from original Unity 126.96.36.199 CD & from the network. During the install I was logged in as a domain admin with rights to log on locally & install device drivers. The computers are hybrids our company builds but all 3 machines do NOT all have the same hardware.
They were all running W2K SP 2 They did not all have the same sound cards
1st New discovery: one of the PCs had working sound & could actually listen to the voice message if choose the sound card option. But Phone option did not work.
Final Discovery: although all the other PCs have the older 188.8.131.52 VMO version, I tried the Viewmail version 184.108.40.206 that I downloaded off the Internet. I can now play voice messages over the phone. The PCs seemed to need the .135 version of VMO while all other PCs have the old version. Why??
I would guess that the version of all new VMO installations should match the version of Unity, but I installed VMO 220.127.116.11 last week on two PCs (Unity version 18.104.22.168) without any problems!?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.