RPC is a Service and it may be that the Service needs to be started before InstallShield will work.
Try that. Goto Start > Run, type in services.msc and click OK. In the Services console that appears scroll down until you see Remote Procedure Call and see if the Status column shows it as Started. If not, double click the entry and in the dialog box click the Start button. Also for good measure, change the Startup type: to Automatic.
You may have to reboot the computer, but I wouldn't think so.
If that doesn't do it, have a look at this link;
It is a list of all discussions about InstallShield. It's a long list, so you may need to read ll the entries, but you may find something useful there.
Is there some way to repair installshield without using scannow? Last time I tried that, my whole
system went wack. If it matters, I have a Windows XP, sp3. I also have the Net
framework 3.5. It took weeks to get
things back to an almost normal state. Unfortunately, it seems the only thing
that didn't get restored was my installshield. My computer won't launch DCOM,
complains about not locating RPC, comes up with error 1053. I've checked and
double checked for viruses, malware, etc. Apparently my system is clean. It just
won't behave. I have the latest files for it, but something seems to be
missing. Any idea what I could do short of a complete re install of the system?
Everything else works fine, but I cannot install anything that needs the Installshield
wizard, other self installer or self contained.exe files seem OK. Help??