Will do, but thats odd.
that snippet is from the one that worked, not the one that failed.
I'm trying to write the converted file to Destination Path -> \COKROSERVE\CoKroPool\TV Series, my server.
The conversion and writing to the server from the first log had failed. That was from HTPC8 writing to \COKROSERVE.
This was mcebuddy.log (the first one I posted), and the file "F:\Recorded TV\Nashville_WABCDT_2013_11_13_22_37_08.wtv" is the same as referred to as "\Htpc8\f htpc video\Recorded TV\Nashville_WABCDT_2013_11_13_22_37_08.wtv" in the mcebuddy2.log file.
I copied the file to the 2nd machine's desktop to try again:
C:\Users\Corey\Desktop\Nashville_WABCDT_2013_11_13_22_37_08.wtv
I thought I had manually cancelled the task that was reading the file off of HTPC8 machine, but it looks like I cancelled the local task off the desktop?
My confusion, I guess, is that I thought that the problem was that the instance of MCEBuddy running on HTPC8 wasn't able to connect to the server.
From the first log, mcebuddy.log
2013-11-13T22:48:31 MCEBuddy.Engine.QueueManager --> Attempting to connect to network share \COKROSERVE\CoKroPool\TV Series
--> Unable to connect to network location \COKROSERVE\CoKroPool\TV Series
Domain name:
Username:mcebuddy
Password:*****
Return code is 67
The network name cannot be found
But from the 2nd log:
2013-11-14T08:48:12 MCEBuddy.Engine.QueueManager --> Attempting to connect to network share \Htpc8\f htpc video\Recorded TV\MCEBuddyArchive
--> Unable to connect to network location \Htpc8\f htpc video\Recorded TV\MCEBuddyArchive
Domain name:
Username:
Password:
Return code is 1219
So the first log is the problem where HTPC8 can't connect to the server, but the 2nd log seems to show that the 2nd machine can't connect to the first, where the recordings are being made.
Guess I'm just confused.
that snippet is from the one that worked, not the one that failed.
I'm trying to write the converted file to Destination Path -> \COKROSERVE\CoKroPool\TV Series, my server.
The conversion and writing to the server from the first log had failed. That was from HTPC8 writing to \COKROSERVE.
This was mcebuddy.log (the first one I posted), and the file "F:\Recorded TV\Nashville_WABCDT_2013_11_13_22_37_08.wtv" is the same as referred to as "\Htpc8\f htpc video\Recorded TV\Nashville_WABCDT_2013_11_13_22_37_08.wtv" in the mcebuddy2.log file.
I copied the file to the 2nd machine's desktop to try again:
C:\Users\Corey\Desktop\Nashville_WABCDT_2013_11_13_22_37_08.wtv
I thought I had manually cancelled the task that was reading the file off of HTPC8 machine, but it looks like I cancelled the local task off the desktop?
My confusion, I guess, is that I thought that the problem was that the instance of MCEBuddy running on HTPC8 wasn't able to connect to the server.
From the first log, mcebuddy.log
2013-11-13T22:48:31 MCEBuddy.Engine.QueueManager --> Attempting to connect to network share \COKROSERVE\CoKroPool\TV Series
--> Unable to connect to network location \COKROSERVE\CoKroPool\TV Series
Domain name:
Username:mcebuddy
Password:*****
Return code is 67
The network name cannot be found
But from the 2nd log:
2013-11-14T08:48:12 MCEBuddy.Engine.QueueManager --> Attempting to connect to network share \Htpc8\f htpc video\Recorded TV\MCEBuddyArchive
--> Unable to connect to network location \Htpc8\f htpc video\Recorded TV\MCEBuddyArchive
Domain name:
Username:
Password:
Return code is 1219
So the first log is the problem where HTPC8 can't connect to the server, but the 2nd log seems to show that the 2nd machine can't connect to the first, where the recordings are being made.
Guess I'm just confused.