Windows Installer Error When Joined to a Windows 2000 Domain

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I apologise if this is the wrong group.

I have several Compaq Evo D500 with Windows XP Profesional XP SP 2 which are
joined to a Windows 2000 SBS server. All systems are unable to load any new
programs - when trying you receive the following error message "Windows
Installer cannot be accessed" - Event Log Event ID 1015 "Failed to connect
to server. Error: 0x80070005"

When I join one of these systems to a Windows 2003 domain controller on a
seperate domain the problem is resolved.

I have tried the following kb article to no avail
http://support.microsoft.com/kb/909444/en-us

I have also run through all of the kb articles on Windows Insaller Errors.

Please help!!
 
Ryan said:
I apologise if this is the wrong group.

It's probably not an AD issue but we generally do our
best to help in any case -- and if we cannot help to direct
you to another group which more likely has the correct set
of expertise....
I have several Compaq Evo D500 with Windows XP Profesional XP SP 2 which
are
joined to a Windows 2000 SBS server. All systems are unable to load any
new
programs

"Any"? What methods have you tried? Have you used the
Windows Installer (program) to just click on an MSI file and
load software that way?

Or is this strictly for doing something like "Automatic Updates"
(with an internal SUS server) or perhaps doing Software Settings
in a GPO?

If it is the latter then likely the issue is access to the FILE server
which holds the software.

Generally this is likely to be either an AUTHENTICATION or a
PERMISSION problem.

Most authentication problems are really DNS issues so use both
DCDiag (on the DC) and NetDiag on the client to test.

Notice that DNS clients (INCLUDING DCs) must all use STRICTLY
the internal DNS server set capable of resolving ALL of the names
from the domain where they live.

If you use an 'external' DNS (or other DNS) which cannot resolve
the names of their DC(s) then they will fail to authenticate.
...- when trying you receive the following error message "Windows
Installer cannot be accessed" - Event Log Event ID 1015 "Failed to
connect
to server. Error: 0x80070005"

When I join one of these systems to a Windows 2003 domain controller on a
seperate domain the problem is resolved.

This would jibe with perhaps the clients using the 'wrong'
DNS server OR with the other DC not being properly registered
with the DNS server that they are (correctly) using (or both.)
I have tried the following kb article to no avail
http://support.microsoft.com/kb/909444/en-us

I have also run through all of the kb articles on Windows Insaller Errors.

Windows Installer is both a service (for GPO deployments) and
a program for manual installations.

If the "program" is broken for local, manual installs then likely
you have a damaged installer and a REPAIR install might help.

My understanding is that you likely have one of the network/domain
issues but you said "any software" so maybe I am incorrect about
your actual problem(s).
 
Hi

Thanks for your speedy response - this problem occurs when I try to install
from a cd locally on the system simply running the setup.exe or if the
installation files are copied locally. I am not trying to use a group policy
to install it is just simply running a local install. I believe it may be
something to do with the default domain policy which has not been changed.

Thanks

Ryan

Herb Martin said:
Ryan said:
I apologise if this is the wrong group.

It's probably not an AD issue but we generally do our
best to help in any case -- and if we cannot help to direct
you to another group which more likely has the correct set
of expertise....
I have several Compaq Evo D500 with Windows XP Profesional XP SP 2 which
are
joined to a Windows 2000 SBS server. All systems are unable to load any
new
programs

"Any"? What methods have you tried? Have you used the
Windows Installer (program) to just click on an MSI file and
load software that way?

Or is this strictly for doing something like "Automatic Updates"
(with an internal SUS server) or perhaps doing Software Settings
in a GPO?

If it is the latter then likely the issue is access to the FILE server
which holds the software.

Generally this is likely to be either an AUTHENTICATION or a
PERMISSION problem.

Most authentication problems are really DNS issues so use both
DCDiag (on the DC) and NetDiag on the client to test.

Notice that DNS clients (INCLUDING DCs) must all use STRICTLY
the internal DNS server set capable of resolving ALL of the names
from the domain where they live.

If you use an 'external' DNS (or other DNS) which cannot resolve
the names of their DC(s) then they will fail to authenticate.
...- when trying you receive the following error message "Windows
Installer cannot be accessed" - Event Log Event ID 1015 "Failed to
connect
to server. Error: 0x80070005"

When I join one of these systems to a Windows 2003 domain controller on a
seperate domain the problem is resolved.

This would jibe with perhaps the clients using the 'wrong'
DNS server OR with the other DC not being properly registered
with the DNS server that they are (correctly) using (or both.)
I have tried the following kb article to no avail
http://support.microsoft.com/kb/909444/en-us

I have also run through all of the kb articles on Windows Insaller Errors.

Windows Installer is both a service (for GPO deployments) and
a program for manual installations.

If the "program" is broken for local, manual installs then likely
you have a damaged installer and a REPAIR install might help.

My understanding is that you likely have one of the network/domain
issues but you said "any software" so maybe I am incorrect about
your actual problem(s).

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Please help!!
 
This happens on any program I try to install ie Mcafee Virus Scan 8, Office
2003, Acrobat Reader etc

Ryan said:
Hi

Thanks for your speedy response - this problem occurs when I try to install
from a cd locally on the system simply running the setup.exe or if the
installation files are copied locally. I am not trying to use a group policy
to install it is just simply running a local install. I believe it may be
something to do with the default domain policy which has not been changed.

Thanks

Ryan

Herb Martin said:
Ryan said:
I apologise if this is the wrong group.

It's probably not an AD issue but we generally do our
best to help in any case -- and if we cannot help to direct
you to another group which more likely has the correct set
of expertise....
I have several Compaq Evo D500 with Windows XP Profesional XP SP 2 which
are
joined to a Windows 2000 SBS server. All systems are unable to load any
new
programs

"Any"? What methods have you tried? Have you used the
Windows Installer (program) to just click on an MSI file and
load software that way?

Or is this strictly for doing something like "Automatic Updates"
(with an internal SUS server) or perhaps doing Software Settings
in a GPO?

If it is the latter then likely the issue is access to the FILE server
which holds the software.

Generally this is likely to be either an AUTHENTICATION or a
PERMISSION problem.

Most authentication problems are really DNS issues so use both
DCDiag (on the DC) and NetDiag on the client to test.

Notice that DNS clients (INCLUDING DCs) must all use STRICTLY
the internal DNS server set capable of resolving ALL of the names
from the domain where they live.

If you use an 'external' DNS (or other DNS) which cannot resolve
the names of their DC(s) then they will fail to authenticate.
...- when trying you receive the following error message "Windows
Installer cannot be accessed" - Event Log Event ID 1015 "Failed to
connect
to server. Error: 0x80070005"

When I join one of these systems to a Windows 2003 domain controller on a
seperate domain the problem is resolved.

This would jibe with perhaps the clients using the 'wrong'
DNS server OR with the other DC not being properly registered
with the DNS server that they are (correctly) using (or both.)
I have tried the following kb article to no avail
http://support.microsoft.com/kb/909444/en-us

I have also run through all of the kb articles on Windows Insaller Errors.

Windows Installer is both a service (for GPO deployments) and
a program for manual installations.

If the "program" is broken for local, manual installs then likely
you have a damaged installer and a REPAIR install might help.

My understanding is that you likely have one of the network/domain
issues but you said "any software" so maybe I am incorrect about
your actual problem(s).

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

Please help!!
 
Hello Ryan

Did you check if the windows installer service is in manual mode (default).
if it's in Disable mode change to manual, and then check if you have aby
group policy that places Windows installer in disabled mode.

Try to logon LOCALLY not on the DOMAIN on the machine and run the .msi to
see if it runs. Next check the firewall definitions on WXP SP2.


See if it helped.
Regards.

--
Systems Administrator
MCSA + Exchange


Ryan said:
This happens on any program I try to install ie Mcafee Virus Scan 8,
Office
2003, Acrobat Reader etc

Ryan said:
Hi

Thanks for your speedy response - this problem occurs when I try to
install
from a cd locally on the system simply running the setup.exe or if the
installation files are copied locally. I am not trying to use a group
policy
to install it is just simply running a local install. I believe it may
be
something to do with the default domain policy which has not been
changed.

Thanks

Ryan

Herb Martin said:
I apologise if this is the wrong group.

It's probably not an AD issue but we generally do our
best to help in any case -- and if we cannot help to direct
you to another group which more likely has the correct set
of expertise....

I have several Compaq Evo D500 with Windows XP Profesional XP SP 2
which
are
joined to a Windows 2000 SBS server. All systems are unable to load
any
new
programs

"Any"? What methods have you tried? Have you used the
Windows Installer (program) to just click on an MSI file and
load software that way?

Or is this strictly for doing something like "Automatic Updates"
(with an internal SUS server) or perhaps doing Software Settings
in a GPO?

If it is the latter then likely the issue is access to the FILE server
which holds the software.

Generally this is likely to be either an AUTHENTICATION or a
PERMISSION problem.

Most authentication problems are really DNS issues so use both
DCDiag (on the DC) and NetDiag on the client to test.

Notice that DNS clients (INCLUDING DCs) must all use STRICTLY
the internal DNS server set capable of resolving ALL of the names
from the domain where they live.

If you use an 'external' DNS (or other DNS) which cannot resolve
the names of their DC(s) then they will fail to authenticate.

...- when trying you receive the following error message "Windows
Installer cannot be accessed" - Event Log Event ID 1015 "Failed to
connect
to server. Error: 0x80070005"

When I join one of these systems to a Windows 2003 domain controller
on a
seperate domain the problem is resolved.

This would jibe with perhaps the clients using the 'wrong'
DNS server OR with the other DC not being properly registered
with the DNS server that they are (correctly) using (or both.)

I have tried the following kb article to no avail
http://support.microsoft.com/kb/909444/en-us

I have also run through all of the kb articles on Windows Insaller
Errors.

Windows Installer is both a service (for GPO deployments) and
a program for manual installations.

If the "program" is broken for local, manual installs then likely
you have a damaged installer and a REPAIR install might help.

My understanding is that you likely have one of the network/domain
issues but you said "any software" so maybe I am incorrect about
your actual problem(s).

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]


Please help!!
 
Back
Top