R
Rainy
congratulations.. babies are so much fun!
Rainy
![Smile :) :)](/styles/default/custom/smilies/smile.gif)
Rainy said:You must be a subscriber.. I can't see the solution..
I had a friend send me his msiexec.exe I think that is what it is
called.. too early for me here.. lol and I am going to try and drag it to
the right folder, assuming mine is corrupted.. I might need to rename the
old one first.. but I will see how that goes.. I will try and delete the
MSOcache folder.. this is really a crazy problem you know?Rainy
You must be a subscriber.. I can't see the solution..
I had a friend send me his msiexec.exe I think that is what it is called..
too early for me here.. lol and I am going to try and drag it to the right
folder, assuming mine is corrupted.. I might need to rename the old one
first.. but I will see how that goes.. I will try and delete the MSOcache
folder.. this is really a crazy problem you know?Rainy
Hi.. I bet everyone is tired of my posts, but I think I fixed it.. I went to
control panel, Administrative tools, then Services.. found the installer,
clicked on Properites, and in the startup type I chose disabled.. now when I
click on Spywareblaster, it briefly comes up and goes away by itself..
Well it might not be really fixed, but now it's workable.. thanks everyone
for your help.. of course now I have to remember, when I am installing
anything I have to enable it ...thanks Rainy
Not to be critical Rainy but isn't that exactly what Wes suggestedRainy said:Hi Sharon, this will be my very last post about this thread..I decided
that the problem was not my computer, and it was not the installer, it was
Microsoft Office, so I reinstalled it.
snip<
Actually I looked at the wrong date it was 10/31 not 10/29Rainy said:Hi, Gls858 If you are talking about this post.. I'm sorry but I don't see
it..even now when I am making an effort to read in detail, this is the only
post I see on the 29th from Wes... I have been known to jump over critical
information in the past. and I could be doing that here, and I do apologize
if this is what I have done. I thought in this post he was asking what
happens if you let windows installer do it's thing, and what was the event
that pertained to spywareblaster, which I found. I am just glad to have it
fixed! Rainy
Wesley Vogel said:Some times the Windows Installer launches when an application is corrupt
and
it launches when you start a totally unrelated program.
What happens if you let Windows Installer do it's thing.
[[Troubleshooting
Q. Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand installation?
A. An easy way to determine the cause of an on-demand installation is to
look in the application event log for MsiInstaller log messages of the
form:
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example' failed during request for component
'{00030829-0000-0000-C000-000000000046}'
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example', component '{00030829-0000-0000-C000-000000000046}' failed. The
resource 'C:\Progam Files\example\example.exe' does not exist.
The first message (with event ID 1001) states which component was being
installed. The component listed here is the component named in the
Component_ column of the Shortcut table for the particular shortcut.
The second message (with event ID 1004) indicates which component failed
detection. Improved event logging in Windows Installer 2.0 has updated the
message so that in most cases, the message identifies the actual resource
that resulted in the failed detection. The component with the missing or
damaged keypath is the component that is triggering the reinstallation.
In the example above, the reinstallation is triggered because the resource
'c:\Program Files\example\example.exe' does not exist. You would then need
to find out why the keypath does not exist -in this case, the user deleted
it.]]
Frequently Asked Questions About Windows Installer
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
gls858 said:Actually I looked at the wrong date it was 10/31 not 10/29Rainy said:Hi, Gls858 If you are talking about this post.. I'm sorry but I don't
see it..even now when I am making an effort to read in detail, this is
the only post I see on the 29th from Wes... I have been known to jump
over critical information in the past. and I could be doing that here,
and I do apologize if this is what I have done. I thought in this post
he was asking what happens if you let windows installer do it's thing,
and what was the event that pertained to spywareblaster, which I found.
I am just glad to have it fixed! Rainy
Wesley Vogel said:Some times the Windows Installer launches when an application is corrupt
and
it launches when you start a totally unrelated program.
What happens if you let Windows Installer do it's thing.
[[Troubleshooting
Q. Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand
installation?
A. An easy way to determine the cause of an on-demand installation is to
look in the application event log for MsiInstaller log messages of the
form:
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example' failed during request for component
'{00030829-0000-0000-C000-000000000046}'
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example', component '{00030829-0000-0000-C000-000000000046}' failed.
The
resource 'C:\Progam Files\example\example.exe' does not exist.
The first message (with event ID 1001) states which component was being
installed. The component listed here is the component named in the
Component_ column of the Shortcut table for the particular shortcut.
The second message (with event ID 1004) indicates which component failed
detection. Improved event logging in Windows Installer 2.0 has updated
the
message so that in most cases, the message identifies the actual
resource
that resulted in the failed detection. The component with the missing or
damaged keypath is the component that is triggering the reinstallation.
In the example above, the reinstallation is triggered because the
resource
'c:\Program Files\example\example.exe' does not exist. You would then
need
to find out why the keypath does not exist -in this case, the user
deleted
it.]]
Frequently Asked Questions About Windows Installer
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
Excerpt from post:
Do you have Office 2003?
Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.
Rainy said:Hi Gls858, I did put the cd in the drive, and when I did, the installer
went away.. he did not ask me to reinstall it, I believe he meant for me to
see what happens when I find the file it was asking for.
I followed his instructions..I try really hard to follow all the advice
and instructions that are given to me..and I appreciate all the help.. it is
the only source of help I have when I have a problem on my computer..
perhaps I misunderstood what he was asking me to do.. that's always a
possibility..thanks Rainy
Actually I looked at the wrong date it was 10/31 not 10/29Rainy said:Hi, Gls858 If you are talking about this post.. I'm sorry but I don't
see it..even now when I am making an effort to read in detail, this is
the only post I see on the 29th from Wes... I have been known to jump
over critical information in the past. and I could be doing that here,
and I do apologize if this is what I have done. I thought in this post
he was asking what happens if you let windows installer do it's thing,
and what was the event that pertained to spywareblaster, which I found.
I am just glad to have it fixed! Rainy
Some times the Windows Installer launches when an application is corrupt
and
it launches when you start a totally unrelated program.
What happens if you let Windows Installer do it's thing.
[[Troubleshooting
Q. Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand
installation?
A. An easy way to determine the cause of an on-demand installation is to
look in the application event log for MsiInstaller log messages of the
form:
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example' failed during request for component
'{00030829-0000-0000-C000-000000000046}'
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example', component '{00030829-0000-0000-C000-000000000046}' failed.
The
resource 'C:\Progam Files\example\example.exe' does not exist.
The first message (with event ID 1001) states which component was being
installed. The component listed here is the component named in the
Component_ column of the Shortcut table for the particular shortcut.
The second message (with event ID 1004) indicates which component failed
detection. Improved event logging in Windows Installer 2.0 has updated
the
message so that in most cases, the message identifies the actual
resource
that resulted in the failed detection. The component with the missing or
damaged keypath is the component that is triggering the reinstallation.
In the example above, the reinstallation is triggered because the
resource
'c:\Program Files\example\example.exe' does not exist. You would then
need
to find out why the keypath does not exist -in this case, the user
deleted
it.]]
Frequently Asked Questions About Windows Installer
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
Excerpt from post:
Do you have Office 2003?
Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.
gls858 said:Rainy said:Hi Gls858, I did put the cd in the drive, and when I did, the installer
went away.. he did not ask me to reinstall it, I believe he meant for me
to see what happens when I find the file it was asking for.
I followed his instructions..I try really hard to follow all the
advice and instructions that are given to me..and I appreciate all the
help.. it is the only source of help I have when I have a problem on my
computer.. perhaps I misunderstood what he was asking me to do.. that's
always a possibility..thanks Rainy
Rainy wrote:
Hi, Gls858 If you are talking about this post.. I'm sorry but I don't
see it..even now when I am making an effort to read in detail, this is
the only post I see on the 29th from Wes... I have been known to jump
over critical information in the past. and I could be doing that here,
and I do apologize if this is what I have done. I thought in this post
he was asking what happens if you let windows installer do it's thing,
and what was the event that pertained to spywareblaster, which I found.
I am just glad to have it fixed! Rainy
Some times the Windows Installer launches when an application is
corrupt
and
it launches when you start a totally unrelated program.
What happens if you let Windows Installer do it's thing.
[[Troubleshooting
Q. Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand
installation?
A. An easy way to determine the cause of an on-demand installation is
to
look in the application event log for MsiInstaller log messages of the
form:
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example' failed during request for component
'{00030829-0000-0000-C000-000000000046}'
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example', component '{00030829-0000-0000-C000-000000000046}' failed.
The
resource 'C:\Progam Files\example\example.exe' does not exist.
The first message (with event ID 1001) states which component was being
installed. The component listed here is the component named in the
Component_ column of the Shortcut table for the particular shortcut.
The second message (with event ID 1004) indicates which component
failed
detection. Improved event logging in Windows Installer 2.0 has updated
the
message so that in most cases, the message identifies the actual
resource
that resulted in the failed detection. The component with the missing
or
damaged keypath is the component that is triggering the reinstallation.
In the example above, the reinstallation is triggered because the
resource
'c:\Program Files\example\example.exe' does not exist. You would then
need
to find out why the keypath does not exist -in this case, the user
deleted
it.]]
Frequently Asked Questions About Windows Installer
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
Actually I looked at the wrong date it was 10/31 not 10/29
Excerpt from post:
Do you have Office 2003?
Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.
You right he didn't specifically say re-install. Maybe I was the one
doing the misinterpreting
gls858
gls858 said:Rainy said:Hi Gls858, I did put the cd in the drive, and when I did, the installer
went away.. he did not ask me to reinstall it, I believe he meant for me
to see what happens when I find the file it was asking for.
I followed his instructions..I try really hard to follow all the
advice and instructions that are given to me..and I appreciate all the
help.. it is the only source of help I have when I have a problem on my
computer.. perhaps I misunderstood what he was asking me to do.. that's
always a possibility..thanks Rainy
Rainy wrote:
Hi, Gls858 If you are talking about this post.. I'm sorry but I don't
see it..even now when I am making an effort to read in detail, this is
the only post I see on the 29th from Wes... I have been known to jump
over critical information in the past. and I could be doing that here,
and I do apologize if this is what I have done. I thought in this post
he was asking what happens if you let windows installer do it's thing,
and what was the event that pertained to spywareblaster, which I
found. I am just glad to have it fixed! Rainy
Some times the Windows Installer launches when an application is
corrupt and
it launches when you start a totally unrelated program.
What happens if you let Windows Installer do it's thing.
[[Troubleshooting
Q. Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand
installation?
A. An easy way to determine the cause of an on-demand installation is
to look in the application event log for MsiInstaller log messages of
the form:
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example' failed during request for component
'{00030829-0000-0000-C000-000000000046}'
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}', feature
'Example', component '{00030829-0000-0000-C000-000000000046}' failed.
The
resource 'C:\Progam Files\example\example.exe' does not exist.
The first message (with event ID 1001) states which component was
being installed. The component listed here is the component named in
the Component_ column of the Shortcut table for the particular
shortcut.
The second message (with event ID 1004) indicates which component
failed detection. Improved event logging in Windows Installer 2.0 has
updated the
message so that in most cases, the message identifies the actual
resource
that resulted in the failed detection. The component with the missing
or damaged keypath is the component that is triggering the
reinstallation.
In the example above, the reinstallation is triggered because the
resource
'c:\Program Files\example\example.exe' does not exist. You would then
need
to find out why the keypath does not exist -in this case, the user
deleted
it.]]
Frequently Asked Questions About Windows Installer
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
Actually I looked at the wrong date it was 10/31 not 10/29
Excerpt from post:
Do you have Office 2003?
Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.
You right he didn't specifically say re-install. Maybe I was the one
doing the misinterpreting
gls858
Wesley Vogel said:What happens if you let Windows Installer do it's thing.
What I meant with the above statement was to let Windows Installer install
what it wanted to install. MS Office is famous for on-demand installs
that
create this problem in the first place.
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
Ingls858 said:Rainy said:Hi Gls858, I did put the cd in the drive, and when I did, the installer
went away.. he did not ask me to reinstall it, I believe he meant for me
to see what happens when I find the file it was asking for.
I followed his instructions..I try really hard to follow all the
advice and instructions that are given to me..and I appreciate all the
help.. it is the only source of help I have when I have a problem on my
computer.. perhaps I misunderstood what he was asking me to do.. that's
always a possibility..thanks Rainy
Rainy wrote:
Hi, Gls858 If you are talking about this post.. I'm sorry but I don't
see it..even now when I am making an effort to read in detail, this is
the only post I see on the 29th from Wes... I have been known to jump
over critical information in the past. and I could be doing that here,
and I do apologize if this is what I have done. I thought in this
post
he was asking what happens if you let windows installer do it's thing,
and what was the event that pertained to spywareblaster, which I
found. I am just glad to have it fixed! Rainy
Some times the Windows Installer launches when an application is
corrupt and
it launches when you start a totally unrelated program.
What happens if you let Windows Installer do it's thing.
[[Troubleshooting
Q. Every time I launch my application, Windows Installer performs an
installation. How can I determine the cause of the on-demand
installation?
A. An easy way to determine the cause of an on-demand installation is
to look in the application event log for MsiInstaller log messages of
the form:
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1001
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}',
feature
'Example' failed during request for component
'{00030829-0000-0000-C000-000000000046}'
Event Type: Warning
Event Source: MsiInstaller
Event ID: 1004
Description:
Detection of product '{000C1109-0000-0000-C000-000000000046}',
feature
'Example', component '{00030829-0000-0000-C000-000000000046}' failed.
The
resource 'C:\Progam Files\example\example.exe' does not exist.
The first message (with event ID 1001) states which component was
being installed. The component listed here is the component named in
the Component_ column of the Shortcut table for the particular
shortcut.
The second message (with event ID 1004) indicates which component
failed detection. Improved event logging in Windows Installer 2.0 has
updated the
message so that in most cases, the message identifies the actual
resource
that resulted in the failed detection. The component with the missing
or damaged keypath is the component that is triggering the
reinstallation.
In the example above, the reinstallation is triggered because the
resource
'c:\Program Files\example\example.exe' does not exist. You would then
need
to find out why the keypath does not exist -in this case, the user
deleted
it.]]
Frequently Asked Questions About Windows Installer
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
Actually I looked at the wrong date it was 10/31 not 10/29
Excerpt from post:
Do you have Office 2003?
Stick the CD in the drive the next time Windows Installer asks for
PRO11.MSI.
You right he didn't specifically say re-install. Maybe I was the one
doing the misinterpreting
gls858
I just think there was a mess on my computer
left by a bad uninstall..and until that mess was cleared up by reinstalling
it.. the installer was not going to be happy .
Sharon F said:Why am I left thinking about Abbot and Costello after this thread?
Who's on first?
If Bud Abbott and Lou Costello were alive today, their famous sketch,
"Who's on first?" might have turned out something like this:
Abbott and Costello Buy A Computer
http://www.webenglishteacher.com/text/abbottcostello.txt ;-)