Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tinear]

Hi,
Hope all is well with everyone.
Last evening I downloaded MC16beta and purchased the license for it. Everything works fine but I keep getting a "Debug.log" showing up on my desktop when I shut MC down.
Shouldn't that file be held in the program folder?
What do I need to do to put it in its proper place
Don't know why it keeps finding my desktop!
Thanks for any help!
Cheers,
Fred

[Alex B]

I did a search: http://www.google.com/search?q=%22debug.log%22+desktop

"Google Talk Plugin" seems to be a common cause. Perhaps MC's built-in browser somehow interacts with it. Do you have Google Talk installed? What is your exact MC version? Is it 16.0.39 or older?

[tinear]

Thanks for your quick reply!
As far as I know I've never installed the "Google Talk PlugIn" on my computer.
I forgot to mention that I've got the latest MC16, 16.0.39 installed.
Thanks again,
Fred

[Matt]

I'm not familiar with Debug.log, so I don't think it was created by an internal Media Center component.

What's in the log?  Maybe it'll have clues.

[tinear]

It's an absolutely empty notepad log.
Guess I'll have to delve into it a little more. I thought that it was connected to MC16 since it didn't show up until I installed the latest MC.
Go figga'!
 

[Alex B]

Actually, I suspect the new Chromium engine. A search found it on my both machines that have MC16 installed. In my case the debug.log files are not on Desktop.

XP:

C:\Documents and Settings\[my username]\debug.log
Created: February 23, 2011, 11:14:26
Modified: February 24, 2011, 11:57:26
The contents:

Code: [Select]

[0223/113613:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113614:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113614:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113615:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113615:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113616:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113616:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113617:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113617:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113617:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113618:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113618:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113619:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113620:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0223/113655:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113717:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113719:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113725:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113727:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113732:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113734:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0223/113811:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED
[0224/115703:ERROR:backend_impl.cc(1091)] Critical error found -8
[0224/115704:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0224/115704:ERROR:tcp_client_socket_win.cc(423)] connect failed: 10061
[0224/115704:WARNING:storage_block-inl.h(119)] Failed data load.
[0224/115725:WARNING:tcp_client_socket_win.cc(98)] Unknown error 10004 mapped to net::ERR_FAILED

Windows 7, 32-bit:

C:\Windows\System32\Debug.log
Modifed: February 24, 2011  (if I recall correctly)
I'll post the other details when I am on that machine...

... EDIT, February 28

C:\Windows\System32\Debug.log
Created: February 24, 2011, 13:00:00
Modified: February 24, 2011, 13:22:17
The contents:

Code: [Select]

[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132215:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
[0224/132216:WARNING:backend_impl.cc(1779)] Destroying invalid entry.
Apparently the files have remained unchanged since February 24.

[tinear]

Hello again,
I've uninstalled and re-installed MC16 and that seems to have solved the problem.
Much obliged for all the responses!
Fred 

[Supersnake]

I'm not familiar with Debug.log, so I don't think it was created by an internal Media Center component.

What's in the log?  Maybe it'll have clues.

Reproducible Examples:  
1.  Go to the Playing Now window.
2.  From the menu at the top of the window select: Player > Play Last.fm Radio > [enter a search item of your choice]
3.  Wait for your target to load and start playing.
4.  While the music is playing press the "Next (hold to fast forward)" icon (screenshot).
5.  Let the "Next" item load and play; the item that you played before will be listed in the playlist - it may have a horizontal  line running through it (screenshot).
6. Attempt to replay that, or any other previously played Last.fm item.
7. Media Center will generate:
(a) an Information window reading "Media Center encountered errors while trying to play the last several files. Please make sure that the path to your media library points to the right location." (screenshot)
(b) a Debug.log with no data in it [mine appeared on my desktop] (screenshot)
8. While Media Center is still running attempt to delete the Debug.log and Windows will inform you that
"The action can't be completed because the file is open in Media Center" (screenshot)

Reproducible events aren't restricted to the example above.  You can also generate an MC event that will create what was described in (Item 7a) and (Item 7b) by deleting one of your playlist/album/tracks.  Then, look and see if the deleted track is still listed in the playlist; if it is still listed (i.e. before auto-import refreshes the playlist), attempt to play it and you will generate the (7a) (7b).

I've uninstalled and re-installed MC16 and that seems to have solved the problem.
Fred  

Thanks for the idea.  I found that it was not necessary to uninstall MC16 - all I did was reinstall MC16.
To see if the fix would be sustaining I forced another couple of events like I described above, the (Item 7a) notification window appeared but a Debug.log did not appear on my desktop.   Also, after reinstalling MC16, the strange horizontal lines (Item 5) that would run through previously played Last.fm items did not appear again.

[Supersnake]

Debug.log files have reappeared again on my desktop after going to Tools > Links > Manage Links > Action and changing one of the links to open in an external browser.

Now I can't stop MC from creating desktop debug.log files despite:
(a) resetting all links to default
(b) closing and reopening MC
(c) reinstalling MC 16 again

Actually, I suspect the new Chromium engine. A search found it on my both machines that have MC16 installed. In my case the debug.log files are not on Desktop.

Alex, do you think that it is the Chromium engine also causing the generation of the debug.log when we tweak something in the Manage Links area?

[JimH]

Wait a few days ...  If it's our problem, we'll fix it.

[BryanC]

I'm getting the debug.log too...

[Beamer]

Just in case this helps:

Seems that Media Center 16.0.39 is generating a debug.log file in every directory that it plays a file from.  The empty file cannot be deleted until Media Center is closed.

[tinear]

Hello again,
Anything new on the debug.log showing up on the desktop problem?
I'm still experiencing it even though, as I wrote earlier, I've uninstalled and reinstalled MC16.
Cheers,
Fred