2014-12-01 53 views
10

我最近安裝了Visual Studio 2013.幾周後,我發現成千上萬的MSI * .LOG文件已經在我的C:\ Windows \ Temp目錄 - 幾乎30Gb的價值。每個文件實際上是相同的,大約是3.1Mb。它似乎一遍又一遍地安裝了相同的東西。我可以刪除所有文件,但他們幾乎立即開始重新出現。我已經放置了以下其中一個文件的片段。我是新發布在StackOverflow上,所以我不確定是否需要放置更多的文件或全部文件或什麼。我在互聯網上發現了2篇關於VS2013的問題,所以我已經完成了修復過程以及卸載/重新安裝VS2013。我注意到在卸載VS2013之後,沒有更多的文件被創建,但是在我重新安裝VS2013之後,它們又開始出現了。Visual Studio 2013在C: Windows Temp目錄中創建了太多的日誌文件

我在VS2013安裝過程中沒有收到任何錯誤。我能夠創建新的解決方案/項目,似乎所有東西都可以編譯/構建,所以我不知道該怎麼解決問題。

有沒有人看過這個問題?有沒有解決問題的解決方案?我正在尋找的不僅僅是「每晚清理文件」!

=== Verbose logging started: 12/1/2014 12:29:41 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorsvw.exe === 
MSI (c) (9C:18) [12:29:41:414]: Resetting cached policy values 
MSI (c) (9C:18) [12:29:41:414]: Machine policy value 'Debug' is 0 
MSI (c) (9C:18) [12:29:41:414]: ******* RunEngine: 
     ******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA} 
     ******* Action: 
     ******* CommandLine: ********** 
MSI (c) (9C:18) [12:29:41:414]: Client-side and UI is none or basic: Running entire install on the server. 
MSI (c) (9C:18) [12:29:41:414]: Grabbed execution mutex. 
MSI (c) (9C:18) [12:29:41:414]: Cloaking enabled. 
MSI (c) (9C:18) [12:29:41:414]: Attempting to enable all disabled privileges before calling Install on Server 
MSI (c) (9C:18) [12:29:41:430]: Incrementing counter to disable shutdown. Counter after increment: 0 
MSI (s) (84:94) [12:29:41:430]: Running installation inside multi-package transaction {9C593464-7F2F-37B3-89F8-7E894E3B09EA} 
MSI (s) (84:94) [12:29:41:430]: Grabbed execution mutex. 
MSI (s) (84:DC) [12:29:41:430]: Resetting cached policy values 
MSI (s) (84:DC) [12:29:41:430]: Machine policy value 'Debug' is 0 
MSI (s) (84:DC) [12:29:41:430]: ******* RunEngine: 
     ******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA} 
     ******* Action: 
     ******* CommandLine: ********** 
MSI (s) (84:DC) [12:29:41:430]: Machine policy value 'DisableUserInstalls' is 0 
MSI (s) (84:DC) [12:29:41:445]: SRSetRestorePoint skipped for this transaction. 
MSI (s) (84:DC) [12:29:41:445]: End dialog not enabled 
MSI (s) (84:DC) [12:29:41:445]: Original package ==> C:\Windows\Installer\4c8872.msi 
MSI (s) (84:DC) [12:29:41:445]: Package we're running from ==> C:\Windows\Installer\4c8872.msi 
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: Uninstall Flags override found. 
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: Uninstall VersionNT override found. 
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: Uninstall ServicePackLevel override found. 
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: looking for appcompat database entry with ProductCode '{9C593464-7F2F-37B3-89F8-7E894E3B09EA}'. 
MSI (s) (84:DC) [12:29:41:461]: APPCOMPAT: no matching ProductCode found in database. 
MSI (s) (84:DC) [12:29:41:461]: MSCOREE not loaded loading copy from system32 
MSI (s) (84:DC) [12:29:41:461]: Opening existing patch 'C:\Windows\Installer\3007d0.msp'. 
MSI (s) (84:DC) [12:29:41:461]: Opening existing patch 'C:\Windows\Installer\2fe190.msp'. 
MSI (s) (84:DC) [12:29:41:461]: Opening existing patch 'C:\Windows\Installer\20c3cd.msp'. 
MSI (s) (84:DC) [12:29:41:477]: Opening existing patch 'C:\Windows\Installer\20c3cc.msp'. 
MSI (s) (84:DC) [12:29:41:477]: SequencePatches starts. Product code: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}, Product version: 12.0.21005, Upgrade code: {015856DA-C69D-3EE0-85EC-270367A147A1}, Product language 1033 
MSI (s) (84:DC) [12:29:41:477]: SequencePatches returns success. 
MSI (s) (84:DC) [12:29:41:477]: Final Patch Application Order: 
MSI (s) (84:DC) [12:29:41:477]: {BFB5154E-888D-4D0E-B377-018AF8B74968} - 
MSI (s) (84:DC) [12:29:41:477]: {C823005E-3448-3126-A3E5-9B568096F87A} - 
MSI (s) (84:DC) [12:29:41:477]: {1B46DFCA-9504-4ACD-AB79-FBC3C899784E} - 
MSI (s) (84:DC) [12:29:41:477]: {1F654618-A065-3008-9415-576BB5F0E42D} - 
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'DisablePatch' is 0 
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'AllowLockdownPatch' is 0 
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'DisableLUAPatching' is 0 
MSI (s) (84:DC) [12:29:41:477]: Machine policy value 'DisableFlyWeightPatching' is 0 
MSI (s) (84:DC) [12:29:41:477]: Looking for patch transform: RTM.1 
DEBUG: Error 2746: Transform RTM.1 invalid for package C:\Windows\Installer\4c8872.msi. Expected product {7781AFF2-D0BE-364B-B18A-D7DBEF8B712D}, found product {9C593464-7F2F-37B3-89F8-7E894E3B09EA}. 
MSI (s) (84:DC) [12:29:41:477]: Skipping validation for patch transform #RTM.1. Will not apply because previous transform was invalid 
MSI (s) (84:DC) [12:29:41:477]: Looking for patch transform: RTM.2 
1: 2746 2: RTM.1 3: C:\Windows\Installer\4c8872.msi 4: {7781AFF2-D0BE-364B-B18A-D7DBEF8B712D} 5: {9C593464-7F2F-37B3-89F8-7E894E3B09EA} 

謝謝!

+0

相關:http://superuser.com/questions/736253/too-many-log-files-being-created-in-temp-folder – test 2014-12-01 19:43:46

+1

是的,這是我找到的2篇文章之一,它表明它是一個問題與VS2013。但是,在嘗試修復VS2013(以及卸載/重新安裝)後,我仍然看到正在創建的.log文件。 – 2014-12-01 20:31:21

+0

同一個!填補我的自由空間!通常我甚至不使用我的本地VS 2013(我通過RDP使用遠程主機工作)。即使我沒有啓動它,VS 2013也會填滿我的日誌! o_O – 2015-02-11 18:01:25

回答

3

從Visual Studio安裝程序運行修復後,問題似乎得到解決。我失去了一些演出,但沒有更多的每日fillup。

+1

嗯,我認爲在發佈我的問題之前我已經完成了修復過程,但是我繼續嘗試再次嘗試Csaba Toth的成功,它確實解決了我的問題。感謝大家的幫助! – 2015-02-23 18:26:23

+0

我希望能夠確定根本原因,但作爲一名開發人員,我有很多版本的Visual Studios,其他IDE,SDK和其他相關的東西安裝,所以很難指出罪魁禍首。不過這在幾個月前就開始了。也許在我安裝VS 2013社區版之後?還是VS Update 4? – 2015-02-24 23:44:46

1

在我的情況下,安裝Update 2013 for VS 2013 Community Edition後開始出現問題。修復不能解決問題。

但是,我在Heath Stewart's MSDN Blog上找到了this post,這對我有幫助。

+0

http://blogs.msdn.com/b/heaths/archive/2015/04/20/visual-studio-2013-continuously-repairs-producing-many-small-log-files.aspx – 2015-08-01 11:54:49

相關問題