Remote Procedure Call error during install on XP Pro w/SP2

[John Q Public]

Hello,

I have a 3rd-party application that installs fine on Windows XP Home
Edition without SP2. I just installed it on Windows XP Pro w/SP2 where
the installation fails when it tries to execute a Remote Procedure Call
(RPC)--at the end of the installation when it tries to register the
product at the application vendor's web site.

Fortunately, this RPC failure occurs near the end of the installation
procedure so the application is installed and runs fine.

However, since the installation didn't complete normally, certain things
are not working correctly...While the application is listed in the
Control Panel->Add/Remove Programs list, trying to "change/delete" the
program from the Add/Remove Programs List doesn't work right. It is not
possible to change/repair this installation. Also, I'm told when a
update to this application tries to perform an update, the update does
not recognize that the original version of this application is already
installed. The application's manufacturer/developer does not have a fix
for this problem (yet).

I hear that MS Windows XP Pro (or SP2) contains changes to the Remote
Procedure Call--that were not understood by this application's installer.

Is there a workaround or tweak I can do to the Registry or other files
so the system properly recognizes that this application is installed
already--so I can change/repair/update it via the "Add/Remove Programs"
list? Is there a workaround for this RPC change?

Thank you for any help.
--John

 

[Don Taylor]

I have a 3rd-party application that installs fine on Windows XP Home
Edition without SP2. I just installed it on Windows XP Pro w/SP2 where
the installation fails when it tries to execute a Remote Procedure Call
(RPC)--at the end of the installation when it tries to register the
product at the application vendor's web site. ....
The application's manufacturer/developer does not have a fix
for this problem (yet).

I hear that MS Windows XP Pro (or SP2) contains changes to the Remote
Procedure Call--that were not understood by this application's installer.

www.google.com and search for
+sp2 +rpc
will give lots of details about fixing gaping rpc security holes in XP.

Is there a workaround or tweak I can do to the Registry or other files
so the system properly recognizes that this application is installed
already--so I can change/repair/update it via the "Add/Remove Programs"
list? Is there a workaround for this RPC change?

If the manufacturer can't figure out a way to fix the problem yet
then it seems wildly unlikely that some kid on the net will find a
way for you to get around this.

There is one idea that seems to be substantially risky and might
not work, uninstall SP2, install your application, reinstall SP2?
You might ask the vendor if that will work. Even after installation
the app might depend on being able to use the old form of rpc.
Or maybe just uninstall SP2 and use the app till they get it fixed?

I'm still waiting on a vendor who's last instructions were
"For God's sake, DON'T install SP2, we are trying to figure out what to do."
And that pays the bills here, it HAS to be running every morning.