Cant load program as Admin

[Guest]

Have a customer loading our program on Windows XP Home, SP2 laptop. The
program is a reporting application for Chiropractors. When the Windows
Installer
starts we get the following message: "Windows Installer: The System
Administrator
has set Policies that prevent this installation." Here are the pertinent
facts:

1) Doctor has two laptops that share a printer and a DSL connection through
a hub.
2) He is logged in as the administrator on the machine. (was the only
account on the pc.)
3) We created a second profile set to admin, same message.
4) I turned of Norton Anti Virus and disabled the network connection (no luck)
5) I went to the Registry and checked the user control was full for the
following keys
a) HKEY_LOCAL_MACHINE\Software\Install Shield
b) HKEY_LOCAL_MACHINE\Software\microsoft\windows\current version\installer
c) HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\windows\installer

6) And the HKEY_Current_User control as well all were set to full control.

I am really at my wits end on this one. The other laptop, same operating
system
and odvious settings the same installed the program no problem. Does anyone
have anything that can help me with this one. I would really be very
gratefull. I do not like loosing to a stupid computer.....Thanks.

 

[Mark L. Ferguson]

Error Message: The System Administrator Has Set Policies to Prevent This
Installation: http://support.microsoft.com/default.aspx?scid=kb;en-us;322963

 

[Guest]

This is not a Norton Anti-Virus Software program. It is a database program.
Any other suggestions that I may be missing?

Error Message: The System Administrator Has Set Policies to Prevent This
Installation: http://support.microsoft.com/default.aspx?scid=kb;en-us;322963

 

[Mark L. Ferguson]

No, I'm pretty sure the same solution is going to be called for, however. (A
re-write of the app.)

This is not a Norton Anti-Virus Software program. It is a database
program.
Any other suggestions that I may be missing?

 

[Guest]

I am not so sure, as I have installed this on many XP SP 2 machines including
his second laptop in his office without this error ever occuring. I am
wondering if there
is a policy setting somewhere that I am missing.