Technology Questions

Go Back   Technology Questions > Software Questions > Operating System Questions > Windows XP

Windows XP Discuss the Microsoft Windows XP Operating System

Reply
 
LinkBack Thread Tools
  #1 (permalink)  
Old 03-07-2007, 02:00 PM
Joye
Newsgroup Contributor
 
Posts: n/a
logfiles created in root directory

I have been getting unwanted log files created in the root directory. In the
last couple of months windows has created 130 log files. I don't know where
they are coming from. I can delete them but it is becoming a pain. It
clutters up the root directory. This is going on at 7 computers we have in
the office.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

 
Old 03-07-2007, 02:00 PM
  #2 (permalink)  
Old 03-07-2007, 05:00 PM
Curt Christianson
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Hi Joye,

If it's a .log file, have you tried opening one up and reading what's logged
there? Log files usually give a clue what application they are logging for.
If you then know the app., then you may find an option from within it to
turn off log files..

--
HTH,
Curt

Windows Support Center
http://aumha.org/

"Joye" <Joye@discussions.microsoft.com> wrote in message
news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
>I have been getting unwanted log files created in the root directory. In
>the
> last couple of months windows has created 130 log files. I don't know
> where
> they are coming from. I can delete them but it is becoming a pain. It
> clutters up the root directory. This is going on at 7 computers we have
> in
> the office.



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #3 (permalink)  
Old 03-08-2007, 05:45 AM
Joye
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Hello,
I have opened them and see no reference to a specific program. It is
creating a folder such as 00b65b48a1bf605c9f and putting a log file in that
directory. This takes time and $ for everyone in the office to go through an
delete the log files. Following is the beginning part of one of the log files:
=== Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
******* Product: c:\00b65b48a1bf605c9f\msxml.msi
******* Action:
******* CommandLine: **********
MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
******* Product: c:\00b65b48a1bf605c9f\msxml.msi
******* Action:
******* CommandLine: **********
MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'DisableUserInstalls'
is 0
MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
MSI (s) (C0:10) [03:00:20:978]: Original package ==>
c:\00b65b48a1bf605c9f\msxml.msi
MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
c:\WINDOWS\Installer\bd028.msi
MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found in
database.
MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from system32
MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch' is 0
MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (C0:10) [03:00:20:978]: Machine policy value
'DisableFlyWeightPatching' is 0
MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found in
database.
MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3 CLIENTPROCESSID=3936
MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
MSI (s) (C0:10) [03:00:20:978]: Product Code passed to Engine.Initialize:
'{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
MSI (s) (C0:10) [03:00:20:978]: Product Code from property table before
transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
MSI (s) (C0:10) [03:00:20:978]: Product Code from property table after
transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
MSI (s) (C0:10) [03:00:20:978]: Product registered: entering maintenance mode
MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
property. Its value is '5'.
MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
ProductToBeRegistered property. Its value is '1'.
MSI (s) (C0:10) [03:00:20:978]: Entering
CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a list.
MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse' is 0
MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownBrowse'
is 1
MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.



"Curt Christianson" wrote:

> Hi Joye,
>
> If it's a .log file, have you tried opening one up and reading what's logged
> there? Log files usually give a clue what application they are logging for.
> If you then know the app., then you may find an option from within it to
> turn off log files..
>
> --
> HTH,
> Curt
>
> Windows Support Center
> http://aumha.org/
>
> "Joye" <Joye@discussions.microsoft.com> wrote in message
> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
> >I have been getting unwanted log files created in the root directory. In
> >the
> > last couple of months windows has created 130 log files. I don't know
> > where
> > they are coming from. I can delete them but it is becoming a pain. It
> > clutters up the root directory. This is going on at 7 computers we have
> > in
> > the office.

>
>
>

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #4 (permalink)  
Old 03-08-2007, 06:15 AM
Curt Christianson
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Hi Joye,

Thise are installer logs. Would you give me the names of a few of the logs?
Not the folders, but the names of a few of the log files insides.


--
HTH,
Curt

Windows Support Center
http://aumha.org/

"Joye" <Joye@discussions.microsoft.com> wrote in message
news:CF7AA9E6-F6AA-432D-8AFA-39098A67749D@microsoft.com...
> Hello,
> I have opened them and see no reference to a specific program. It is
> creating a folder such as 00b65b48a1bf605c9f and putting a log file in
> that
> directory. This takes time and $ for everyone in the office to go through
> an
> delete the log files. Following is the beginning part of one of the log
> files:
> === Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP UNICODE
> 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
> MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
> MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
> MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
> ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> ******* Action:
> ******* CommandLine: **********
> MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic:
> Running
> entire install on the server.
> MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
> MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
> MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled
> priveleges
> before calling Install on Server
> MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable shutdown.
> Counter after increment: 0
> MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
> MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
> MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
> MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
> ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> ******* Action:
> ******* CommandLine: **********
> MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'DisableUserInstalls'
> is 0
> MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
> MSI (s) (C0:10) [03:00:20:978]: Original package ==>
> c:\00b65b48a1bf605c9f\msxml.msi
> MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
> c:\WINDOWS\Installer\bd028.msi
> MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
> entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found
> in
> database.
> MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from
> system32
> MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch' is 0
> MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownPatch'
> is 0
> MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableLUAPatching'
> is 0
> MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> 'DisableFlyWeightPatching' is 0
> MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
> entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found
> in
> database.
> MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
> MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
> CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3
> CLIENTPROCESSID=3936
> MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
> property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
> MSI (s) (C0:10) [03:00:20:978]: Product Code passed to Engine.Initialize:
> '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> MSI (s) (C0:10) [03:00:20:978]: Product Code from property table before
> transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> MSI (s) (C0:10) [03:00:20:978]: Product Code from property table after
> transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> MSI (s) (C0:10) [03:00:20:978]: Product registered: entering maintenance
> mode
> MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
> property. Its value is '5'.
> MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
> ProductToBeRegistered property. Its value is '1'.
> MSI (s) (C0:10) [03:00:20:978]: Entering
> CMsiConfigurationManager::SetLastUsedSource.
> MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a list.
> MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse' is 0
> MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownBrowse'
> is 1
> MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.
>
>
>
> "Curt Christianson" wrote:
>
>> Hi Joye,
>>
>> If it's a .log file, have you tried opening one up and reading what's
>> logged
>> there? Log files usually give a clue what application they are logging
>> for.
>> If you then know the app., then you may find an option from within it to
>> turn off log files..
>>
>> --
>> HTH,
>> Curt
>>
>> Windows Support Center
>> http://aumha.org/
>>
>> "Joye" <Joye@discussions.microsoft.com> wrote in message
>> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
>> >I have been getting unwanted log files created in the root directory.
>> >In
>> >the
>> > last couple of months windows has created 130 log files. I don't know
>> > where
>> > they are coming from. I can delete them but it is becoming a pain. It
>> > clutters up the root directory. This is going on at 7 computers we
>> > have
>> > in
>> > the office.

>>
>>
>>



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #5 (permalink)  
Old 03-08-2007, 07:15 AM
Joye
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Curt,
I am glad you asked that. I did not realize that the files are all the same
name under diferent directory names. The file name is
msxml4-KB927978-enu.log.

"Curt Christianson" wrote:

> Hi Joye,
>
> Thise are installer logs. Would you give me the names of a few of the logs?
> Not the folders, but the names of a few of the log files insides.
>
>
> --
> HTH,
> Curt
>
> Windows Support Center
> http://aumha.org/
>
> "Joye" <Joye@discussions.microsoft.com> wrote in message
> news:CF7AA9E6-F6AA-432D-8AFA-39098A67749D@microsoft.com...
> > Hello,
> > I have opened them and see no reference to a specific program. It is
> > creating a folder such as 00b65b48a1bf605c9f and putting a log file in
> > that
> > directory. This takes time and $ for everyone in the office to go through
> > an
> > delete the log files. Following is the beginning part of one of the log
> > files:
> > === Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP UNICODE
> > 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
> > MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
> > MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
> > MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
> > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> > ******* Action:
> > ******* CommandLine: **********
> > MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic:
> > Running
> > entire install on the server.
> > MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
> > MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
> > MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled
> > priveleges
> > before calling Install on Server
> > MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable shutdown.
> > Counter after increment: 0
> > MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
> > MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
> > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
> > MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
> > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> > ******* Action:
> > ******* CommandLine: **********
> > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'DisableUserInstalls'
> > is 0
> > MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
> > MSI (s) (C0:10) [03:00:20:978]: Original package ==>
> > c:\00b65b48a1bf605c9f\msxml.msi
> > MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
> > c:\WINDOWS\Installer\bd028.msi
> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
> > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found
> > in
> > database.
> > MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from
> > system32
> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch' is 0
> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownPatch'
> > is 0
> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableLUAPatching'
> > is 0
> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> > 'DisableFlyWeightPatching' is 0
> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
> > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found
> > in
> > database.
> > MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
> > MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
> > CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3
> > CLIENTPROCESSID=3936
> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
> > property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
> > MSI (s) (C0:10) [03:00:20:978]: Product Code passed to Engine.Initialize:
> > '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table before
> > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table after
> > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> > MSI (s) (C0:10) [03:00:20:978]: Product registered: entering maintenance
> > mode
> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
> > property. Its value is '5'.
> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
> > ProductToBeRegistered property. Its value is '1'.
> > MSI (s) (C0:10) [03:00:20:978]: Entering
> > CMsiConfigurationManager::SetLastUsedSource.
> > MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a list.
> > MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is 'nmu'
> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse' is 0
> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownBrowse'
> > is 1
> > MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.
> >
> >
> >
> > "Curt Christianson" wrote:
> >
> >> Hi Joye,
> >>
> >> If it's a .log file, have you tried opening one up and reading what's
> >> logged
> >> there? Log files usually give a clue what application they are logging
> >> for.
> >> If you then know the app., then you may find an option from within it to
> >> turn off log files..
> >>
> >> --
> >> HTH,
> >> Curt
> >>
> >> Windows Support Center
> >> http://aumha.org/
> >>
> >> "Joye" <Joye@discussions.microsoft.com> wrote in message
> >> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
> >> >I have been getting unwanted log files created in the root directory.
> >> >In
> >> >the
> >> > last couple of months windows has created 130 log files. I don't know
> >> > where
> >> > they are coming from. I can delete them but it is becoming a pain. It
> >> > clutters up the root directory. This is going on at 7 computers we
> >> > have
> >> > in
> >> > the office.
> >>
> >>
> >>

>
>
>

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #6 (permalink)  
Old 03-08-2007, 08:00 AM
Curt Christianson
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Hi Joye,

Now we're getting somewhere. These are the log files for a Critical Windows
Update, KB927078, which keeps trying to install, and apparently fails. This
advice on that subject from MS-MVP Mow Green:
<quote>
Did you download KB927978 manually, save it, and then attempt to install
it ?
http://www.microsoft.com/downloads/d...d=24B7D141-6CD...
If not suggest you attempt that. When you do, ***make sure*** that the
system is RESTARTED PRIOR to attempting to install it.
If 3 options are presented, Modify/Repair/Remove, choose Remove.
If you are prompted to, restart the system.
If not, run msxml4-KB927978-enu.exe once more and it *should* install.
If yes, then restart and then run msxml4-KB927978-enu.exe

MowGreen [MVP 2003-2007]
<end quote>



Go to the link Mow referenced, and download that file to your desktop so you
can locate it easily, then proceed with the rest of his instructions *to the
letter*.

After you've done that, go to Add/Remove Programs in Control Panel, make
sure that the box at the top for "Show Updates" is checked. Look for "MSXML
4.0 SP2 (KB927978) in the list. It's probably located somewhere in the
middle rather than with the rest of the Windows uodates. It should be there.
I would re-boot the computer one last time, then go to all those log files
and delete them. If the update (KB937978) has installed correctly (which it
should be), you shouldn't get any more of those files.


--
HTH,
Curt

Windows Support Center
http://aumha.org/

"Joye" <Joye@discussions.microsoft.com> wrote in message
news:EF4AEAFD-FF7E-4FBD-89B7-609C3EDD6EAB@microsoft.com...
> Curt,
> I am glad you asked that. I did not realize that the files are all the
> same
> name under diferent directory names. The file name is
> msxml4-KB927978-enu.log.
>
> "Curt Christianson" wrote:
>
>> Hi Joye,
>>
>> Thise are installer logs. Would you give me the names of a few of the
>> logs?
>> Not the folders, but the names of a few of the log files insides.
>>
>>
>> --
>> HTH,
>> Curt
>>
>> Windows Support Center
>> http://aumha.org/
>>
>> "Joye" <Joye@discussions.microsoft.com> wrote in message
>> news:CF7AA9E6-F6AA-432D-8AFA-39098A67749D@microsoft.com...
>> > Hello,
>> > I have opened them and see no reference to a specific program. It is
>> > creating a folder such as 00b65b48a1bf605c9f and putting a log file in
>> > that
>> > directory. This takes time and $ for everyone in the office to go
>> > through
>> > an
>> > delete the log files. Following is the beginning part of one of the log
>> > files:
>> > === Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP
>> > UNICODE
>> > 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
>> > MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
>> > MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
>> > MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
>> > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
>> > ******* Action:
>> > ******* CommandLine: **********
>> > MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic:
>> > Running
>> > entire install on the server.
>> > MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
>> > MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
>> > MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled
>> > priveleges
>> > before calling Install on Server
>> > MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable
>> > shutdown.
>> > Counter after increment: 0
>> > MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
>> > MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
>> > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
>> > MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
>> > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
>> > ******* Action:
>> > ******* CommandLine: **********
>> > MSI (s) (C0:10) [03:00:20:962]: Machine policy value
>> > 'DisableUserInstalls'
>> > is 0
>> > MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
>> > MSI (s) (C0:10) [03:00:20:978]: Original package ==>
>> > c:\00b65b48a1bf605c9f\msxml.msi
>> > MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
>> > c:\WINDOWS\Installer\bd028.msi
>> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat
>> > database
>> > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
>> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode
>> > found
>> > in
>> > database.
>> > MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from
>> > system32
>> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch' is
>> > 0
>> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > 'AllowLockdownPatch'
>> > is 0
>> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > 'DisableLUAPatching'
>> > is 0
>> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > 'DisableFlyWeightPatching' is 0
>> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat
>> > database
>> > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
>> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode
>> > found
>> > in
>> > database.
>> > MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
>> > MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
>> > CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3
>> > CLIENTPROCESSID=3936
>> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
>> > property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
>> > MSI (s) (C0:10) [03:00:20:978]: Product Code passed to
>> > Engine.Initialize:
>> > '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
>> > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table before
>> > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
>> > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table after
>> > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
>> > MSI (s) (C0:10) [03:00:20:978]: Product registered: entering
>> > maintenance
>> > mode
>> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
>> > property. Its value is '5'.
>> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
>> > ProductToBeRegistered property. Its value is '1'.
>> > MSI (s) (C0:10) [03:00:20:978]: Entering
>> > CMsiConfigurationManager::SetLastUsedSource.
>> > MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a
>> > list.
>> > MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is
>> > 'nmu'
>> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse' is
>> > 0
>> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > 'AllowLockdownBrowse'
>> > is 1
>> > MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.
>> >
>> >
>> >
>> > "Curt Christianson" wrote:
>> >
>> >> Hi Joye,
>> >>
>> >> If it's a .log file, have you tried opening one up and reading what's
>> >> logged
>> >> there? Log files usually give a clue what application they are
>> >> logging
>> >> for.
>> >> If you then know the app., then you may find an option from within it
>> >> to
>> >> turn off log files..
>> >>
>> >> --
>> >> HTH,
>> >> Curt
>> >>
>> >> Windows Support Center
>> >> http://aumha.org/
>> >>
>> >> "Joye" <Joye@discussions.microsoft.com> wrote in message
>> >> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
>> >> >I have been getting unwanted log files created in the root directory.
>> >> >In
>> >> >the
>> >> > last couple of months windows has created 130 log files. I don't
>> >> > know
>> >> > where
>> >> > they are coming from. I can delete them but it is becoming a pain.
>> >> > It
>> >> > clutters up the root directory. This is going on at 7 computers we
>> >> > have
>> >> > in
>> >> > the office.
>> >>
>> >>
>> >>

>>
>>
>>



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #7 (permalink)  
Old 03-08-2007, 10:45 AM
Joye
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Curt,

Thank you so much. You are a lifesaver. I will see if this works!

Joye

"Curt Christianson" wrote:

> Hi Joye,
>
> Now we're getting somewhere. These are the log files for a Critical Windows
> Update, KB927078, which keeps trying to install, and apparently fails. This
> advice on that subject from MS-MVP Mow Green:
> <quote>
> Did you download KB927978 manually, save it, and then attempt to install
> it ?
> http://www.microsoft.com/downloads/d...d=24B7D141-6CD...
> If not suggest you attempt that. When you do, ***make sure*** that the
> system is RESTARTED PRIOR to attempting to install it.
> If 3 options are presented, Modify/Repair/Remove, choose Remove.
> If you are prompted to, restart the system.
> If not, run msxml4-KB927978-enu.exe once more and it *should* install.
> If yes, then restart and then run msxml4-KB927978-enu.exe
>
> MowGreen [MVP 2003-2007]
> <end quote>
>
>
>
> Go to the link Mow referenced, and download that file to your desktop so you
> can locate it easily, then proceed with the rest of his instructions *to the
> letter*.
>
> After you've done that, go to Add/Remove Programs in Control Panel, make
> sure that the box at the top for "Show Updates" is checked. Look for "MSXML
> 4.0 SP2 (KB927978) in the list. It's probably located somewhere in the
> middle rather than with the rest of the Windows uodates. It should be there.
> I would re-boot the computer one last time, then go to all those log files
> and delete them. If the update (KB937978) has installed correctly (which it
> should be), you shouldn't get any more of those files.
>
>
> --
> HTH,
> Curt
>
> Windows Support Center
> http://aumha.org/
>
> "Joye" <Joye@discussions.microsoft.com> wrote in message
> news:EF4AEAFD-FF7E-4FBD-89B7-609C3EDD6EAB@microsoft.com...
> > Curt,
> > I am glad you asked that. I did not realize that the files are all the
> > same
> > name under diferent directory names. The file name is
> > msxml4-KB927978-enu.log.
> >
> > "Curt Christianson" wrote:
> >
> >> Hi Joye,
> >>
> >> Thise are installer logs. Would you give me the names of a few of the
> >> logs?
> >> Not the folders, but the names of a few of the log files insides.
> >>
> >>
> >> --
> >> HTH,
> >> Curt
> >>
> >> Windows Support Center
> >> http://aumha.org/
> >>
> >> "Joye" <Joye@discussions.microsoft.com> wrote in message
> >> news:CF7AA9E6-F6AA-432D-8AFA-39098A67749D@microsoft.com...
> >> > Hello,
> >> > I have opened them and see no reference to a specific program. It is
> >> > creating a folder such as 00b65b48a1bf605c9f and putting a log file in
> >> > that
> >> > directory. This takes time and $ for everyone in the office to go
> >> > through
> >> > an
> >> > delete the log files. Following is the beginning part of one of the log
> >> > files:
> >> > === Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP
> >> > UNICODE
> >> > 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
> >> > MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
> >> > MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
> >> > MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
> >> > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> >> > ******* Action:
> >> > ******* CommandLine: **********
> >> > MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic:
> >> > Running
> >> > entire install on the server.
> >> > MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
> >> > MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
> >> > MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled
> >> > priveleges
> >> > before calling Install on Server
> >> > MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable
> >> > shutdown.
> >> > Counter after increment: 0
> >> > MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
> >> > MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
> >> > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
> >> > MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
> >> > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> >> > ******* Action:
> >> > ******* CommandLine: **********
> >> > MSI (s) (C0:10) [03:00:20:962]: Machine policy value
> >> > 'DisableUserInstalls'
> >> > is 0
> >> > MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
> >> > MSI (s) (C0:10) [03:00:20:978]: Original package ==>
> >> > c:\00b65b48a1bf605c9f\msxml.msi
> >> > MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
> >> > c:\WINDOWS\Installer\bd028.msi
> >> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat
> >> > database
> >> > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> >> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode
> >> > found
> >> > in
> >> > database.
> >> > MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from
> >> > system32
> >> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch' is
> >> > 0
> >> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> >> > 'AllowLockdownPatch'
> >> > is 0
> >> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> >> > 'DisableLUAPatching'
> >> > is 0
> >> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> >> > 'DisableFlyWeightPatching' is 0
> >> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat
> >> > database
> >> > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> >> > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode
> >> > found
> >> > in
> >> > database.
> >> > MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
> >> > MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
> >> > CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3
> >> > CLIENTPROCESSID=3936
> >> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
> >> > property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
> >> > MSI (s) (C0:10) [03:00:20:978]: Product Code passed to
> >> > Engine.Initialize:
> >> > '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> >> > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table before
> >> > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> >> > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table after
> >> > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> >> > MSI (s) (C0:10) [03:00:20:978]: Product registered: entering
> >> > maintenance
> >> > mode
> >> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
> >> > property. Its value is '5'.
> >> > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
> >> > ProductToBeRegistered property. Its value is '1'.
> >> > MSI (s) (C0:10) [03:00:20:978]: Entering
> >> > CMsiConfigurationManager::SetLastUsedSource.
> >> > MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a
> >> > list.
> >> > MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is
> >> > 'nmu'
> >> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse' is
> >> > 0
> >> > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> >> > 'AllowLockdownBrowse'
> >> > is 1
> >> > MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.
> >> >
> >> >
> >> >
> >> > "Curt Christianson" wrote:
> >> >
> >> >> Hi Joye,
> >> >>
> >> >> If it's a .log file, have you tried opening one up and reading what's
> >> >> logged
> >> >> there? Log files usually give a clue what application they are
> >> >> logging
> >> >> for.
> >> >> If you then know the app., then you may find an option from within it
> >> >> to
> >> >> turn off log files..
> >> >>
> >> >> --
> >> >> HTH,
> >> >> Curt
> >> >>
> >> >> Windows Support Center
> >> >> http://aumha.org/
> >> >>
> >> >> "Joye" <Joye@discussions.microsoft.com> wrote in message
> >> >> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
> >> >> >I have been getting unwanted log files created in the root directory.
> >> >> >In
> >> >> >the
> >> >> > last couple of months windows has created 130 log files. I don't
> >> >> > know
> >> >> > where
> >> >> > they are coming from. I can delete them but it is becoming a pain.
> >> >> > It
> >> >> > clutters up the root directory. This is going on at 7 computers we
> >> >> > have
> >> >> > in
> >> >> > the office.
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>

>
>
>

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #8 (permalink)  
Old 03-08-2007, 12:45 PM
Joye
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Curt,
I also checked the other computers in the office. They all have the same
file name as mine above which is msxml4-KB927978-enu.log.

"Joye" wrote:

> Curt,
> I am glad you asked that. I did not realize that the files are all the same
> name under diferent directory names. The file name is
> msxml4-KB927978-enu.log.
>
> "Curt Christianson" wrote:
>
> > Hi Joye,
> >
> > Thise are installer logs. Would you give me the names of a few of the logs?
> > Not the folders, but the names of a few of the log files insides.
> >
> >
> > --
> > HTH,
> > Curt
> >
> > Windows Support Center
> > http://aumha.org/
> >
> > "Joye" <Joye@discussions.microsoft.com> wrote in message
> > news:CF7AA9E6-F6AA-432D-8AFA-39098A67749D@microsoft.com...
> > > Hello,
> > > I have opened them and see no reference to a specific program. It is
> > > creating a folder such as 00b65b48a1bf605c9f and putting a log file in
> > > that
> > > directory. This takes time and $ for everyone in the office to go through
> > > an
> > > delete the log files. Following is the beginning part of one of the log
> > > files:
> > > === Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP UNICODE
> > > 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
> > > MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
> > > MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
> > > MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
> > > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> > > ******* Action:
> > > ******* CommandLine: **********
> > > MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic:
> > > Running
> > > entire install on the server.
> > > MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
> > > MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
> > > MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled
> > > priveleges
> > > before calling Install on Server
> > > MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable shutdown.
> > > Counter after increment: 0
> > > MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
> > > MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
> > > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
> > > MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
> > > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
> > > ******* Action:
> > > ******* CommandLine: **********
> > > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'DisableUserInstalls'
> > > is 0
> > > MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
> > > MSI (s) (C0:10) [03:00:20:978]: Original package ==>
> > > c:\00b65b48a1bf605c9f\msxml.msi
> > > MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
> > > c:\WINDOWS\Installer\bd028.msi
> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
> > > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found
> > > in
> > > database.
> > > MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from
> > > system32
> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch' is 0
> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownPatch'
> > > is 0
> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableLUAPatching'
> > > is 0
> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
> > > 'DisableFlyWeightPatching' is 0
> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat database
> > > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode found
> > > in
> > > database.
> > > MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
> > > MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
> > > CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3
> > > CLIENTPROCESSID=3936
> > > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
> > > property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
> > > MSI (s) (C0:10) [03:00:20:978]: Product Code passed to Engine.Initialize:
> > > '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> > > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table before
> > > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> > > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table after
> > > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
> > > MSI (s) (C0:10) [03:00:20:978]: Product registered: entering maintenance
> > > mode
> > > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
> > > property. Its value is '5'.
> > > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
> > > ProductToBeRegistered property. Its value is '1'.
> > > MSI (s) (C0:10) [03:00:20:978]: Entering
> > > CMsiConfigurationManager::SetLastUsedSource.
> > > MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a list.
> > > MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is 'nmu'
> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse' is 0
> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'AllowLockdownBrowse'
> > > is 1
> > > MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.
> > >
> > >
> > >
> > > "Curt Christianson" wrote:
> > >
> > >> Hi Joye,
> > >>
> > >> If it's a .log file, have you tried opening one up and reading what's
> > >> logged
> > >> there? Log files usually give a clue what application they are logging
> > >> for.
> > >> If you then know the app., then you may find an option from within it to
> > >> turn off log files..
> > >>
> > >> --
> > >> HTH,
> > >> Curt
> > >>
> > >> Windows Support Center
> > >> http://aumha.org/
> > >>
> > >> "Joye" <Joye@discussions.microsoft.com> wrote in message
> > >> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
> > >> >I have been getting unwanted log files created in the root directory.
> > >> >In
> > >> >the
> > >> > last couple of months windows has created 130 log files. I don't know
> > >> > where
> > >> > they are coming from. I can delete them but it is becoming a pain. It
> > >> > clutters up the root directory. This is going on at 7 computers we
> > >> > have
> > >> > in
> > >> > the office.
> > >>
> > >>
> > >>

> >
> >
> >

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

  #9 (permalink)  
Old 03-08-2007, 01:00 PM
Curt Christianson
Newsgroup Contributor
 
Posts: n/a
Re: logfiles created in root directory

Are they all creating more instances as time goes on too?

--
HTH,
Curt

Windows Support Center
http://aumha.org/

"Joye" <Joye@discussions.microsoft.com> wrote in message
news:0B6E9456-6710-454D-8A48-DDFE53B1DD61@microsoft.com...
> Curt,
> I also checked the other computers in the office. They all have the same
> file name as mine above which is msxml4-KB927978-enu.log.
>
> "Joye" wrote:
>
>> Curt,
>> I am glad you asked that. I did not realize that the files are all the
>> same
>> name under diferent directory names. The file name is
>> msxml4-KB927978-enu.log.
>>
>> "Curt Christianson" wrote:
>>
>> > Hi Joye,
>> >
>> > Thise are installer logs. Would you give me the names of a few of the
>> > logs?
>> > Not the folders, but the names of a few of the log files insides.
>> >
>> >
>> > --
>> > HTH,
>> > Curt
>> >
>> > Windows Support Center
>> > http://aumha.org/
>> >
>> > "Joye" <Joye@discussions.microsoft.com> wrote in message
>> > news:CF7AA9E6-F6AA-432D-8AFA-39098A67749D@microsoft.com...
>> > > Hello,
>> > > I have opened them and see no reference to a specific program. It is
>> > > creating a folder such as 00b65b48a1bf605c9f and putting a log file
>> > > in
>> > > that
>> > > directory. This takes time and $ for everyone in the office to go
>> > > through
>> > > an
>> > > delete the log files. Following is the beginning part of one of the
>> > > log
>> > > files:
>> > > === Verbose logging started: 12/18/2006 3:00:20 Build type: SHIP
>> > > UNICODE
>> > > 3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===
>> > > MSI (c) (60:08) [03:00:20:868]: Resetting cached policy values
>> > > MSI (c) (60:08) [03:00:20:868]: Machine policy value 'Debug' is 0
>> > > MSI (c) (60:08) [03:00:20:868]: ******* RunEngine:
>> > > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
>> > > ******* Action:
>> > > ******* CommandLine: **********
>> > > MSI (c) (60:08) [03:00:20:868]: Client-side and UI is none or basic:
>> > > Running
>> > > entire install on the server.
>> > > MSI (c) (60:08) [03:00:20:868]: Grabbed execution mutex.
>> > > MSI (c) (60:08) [03:00:20:946]: Cloaking enabled.
>> > > MSI (c) (60:08) [03:00:20:946]: Attempting to enable all disabled
>> > > priveleges
>> > > before calling Install on Server
>> > > MSI (c) (60:08) [03:00:20:962]: Incrementing counter to disable
>> > > shutdown.
>> > > Counter after increment: 0
>> > > MSI (s) (C0:58) [03:00:20:962]: Grabbed execution mutex.
>> > > MSI (s) (C0:10) [03:00:20:962]: Resetting cached policy values
>> > > MSI (s) (C0:10) [03:00:20:962]: Machine policy value 'Debug' is 0
>> > > MSI (s) (C0:10) [03:00:20:962]: ******* RunEngine:
>> > > ******* Product: c:\00b65b48a1bf605c9f\msxml.msi
>> > > ******* Action:
>> > > ******* CommandLine: **********
>> > > MSI (s) (C0:10) [03:00:20:962]: Machine policy value
>> > > 'DisableUserInstalls'
>> > > is 0
>> > > MSI (s) (C0:10) [03:00:20:978]: End dialog not enabled
>> > > MSI (s) (C0:10) [03:00:20:978]: Original package ==>
>> > > c:\00b65b48a1bf605c9f\msxml.msi
>> > > MSI (s) (C0:10) [03:00:20:978]: Package we're running from ==>
>> > > c:\WINDOWS\Installer\bd028.msi
>> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat
>> > > database
>> > > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
>> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode
>> > > found
>> > > in
>> > > database.
>> > > MSI (s) (C0:10) [03:00:20:978]: MSCOREE not loaded loading copy from
>> > > system32
>> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisablePatch'
>> > > is 0
>> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > > 'AllowLockdownPatch'
>> > > is 0
>> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > > 'DisableLUAPatching'
>> > > is 0
>> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > > 'DisableFlyWeightPatching' is 0
>> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: looking for appcompat
>> > > database
>> > > entry with ProductCode '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'.
>> > > MSI (s) (C0:10) [03:00:20:978]: APPCOMPAT: no matching ProductCode
>> > > found
>> > > in
>> > > database.
>> > > MSI (s) (C0:10) [03:00:20:978]: Transforms are not secure.
>> > > MSI (s) (C0:10) [03:00:20:978]: Command Line: REBOOT=ReallySuppress
>> > > CURRENTDIRECTORY=c:\00b65b48a1bf605c9f CLIENTUILEVEL=3
>> > > CLIENTPROCESSID=3936
>> > > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding PackageCode
>> > > property. Its value is '{2B27DCD9-53FA-4885-B6CD-698623819F4C}'.
>> > > MSI (s) (C0:10) [03:00:20:978]: Product Code passed to
>> > > Engine.Initialize:
>> > > '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
>> > > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table
>> > > before
>> > > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
>> > > MSI (s) (C0:10) [03:00:20:978]: Product Code from property table
>> > > after
>> > > transforms: '{37477865-A3F1-4772-AD43-AAFC6BCFF99F}'
>> > > MSI (s) (C0:10) [03:00:20:978]: Product registered: entering
>> > > maintenance
>> > > mode
>> > > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding ProductState
>> > > property. Its value is '5'.
>> > > MSI (s) (C0:10) [03:00:20:978]: PROPERTY CHANGE: Adding
>> > > ProductToBeRegistered property. Its value is '1'.
>> > > MSI (s) (C0:10) [03:00:20:978]: Entering
>> > > CMsiConfigurationManager::SetLastUsedSource.
>> > > MSI (s) (C0:10) [03:00:20:978]: Specifed source is not already in a
>> > > list.
>> > > MSI (s) (C0:10) [03:00:20:978]: User policy value 'SearchOrder' is
>> > > 'nmu'
>> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value 'DisableBrowse'
>> > > is 0
>> > > MSI (s) (C0:10) [03:00:20:978]: Machine policy value
>> > > 'AllowLockdownBrowse'
>> > > is 1
>> > > MSI (s) (C0:10) [03:00:20:978]: Adding new sources is allowed.
>> > >
>> > >
>> > >
>> > > "Curt Christianson" wrote:
>> > >
>> > >> Hi Joye,
>> > >>
>> > >> If it's a .log file, have you tried opening one up and reading
>> > >> what's
>> > >> logged
>> > >> there? Log files usually give a clue what application they are
>> > >> logging
>> > >> for.
>> > >> If you then know the app., then you may find an option from within
>> > >> it to
>> > >> turn off log files..
>> > >>
>> > >> --
>> > >> HTH,
>> > >> Curt
>> > >>
>> > >> Windows Support Center
>> > >> http://aumha.org/
>> > >>
>> > >> "Joye" <Joye@discussions.microsoft.com> wrote in message
>> > >> news:051E4114-33B5-4DAE-979A-FE616D54B0C8@microsoft.com...
>> > >> >I have been getting unwanted log files created in the root
>> > >> >directory.
>> > >> >In
>> > >> >the
>> > >> > last couple of months windows has created 130 log files. I don't
>> > >> > know
>> > >> > where
>> > >> > they are coming from. I can delete them but it is becoming a pain.
>> > >> > It
>> > >> > clutters up the root directory. This is going on at 7 computers
>> > >> > we
>> > >> > have
>> > >> > in
>> > >> > the office.
>> > >>
>> > >>
>> > >>
>> >
>> >
>> >



Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote

Reply

Bookmarks

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Initializeing Root Directory Tree MWP Windows XP 3 03-13-2008 01:50 PM
Two huge files in root directory Bobbi Windows XP 5 12-01-2007 01:20 AM
How do I get all entries in root-directory? (FAT32) keandi Windows XP 3 11-30-2007 05:50 AM
*.sqm files in root directory Steve T Windows Vista 4 09-08-2007 05:20 PM
Strange files in my root directory LJ Windows XP 3 03-29-2007 06:30 AM


New To Technology Questions? Do You Need Help with Your Computer or Device? Do You Need Help with this site?

All times are GMT -8. The time now is 09:49 PM.


2003 - 2009 All Rights Reserved. Technology Questions

Search Engine Friendly URLs by vBSEO 3.3.0