PowerShell transcription logging error

Welcome Forums General PowerShell Q&A PowerShell transcription logging error

This topic contains 2 replies, has 2 voices, and was last updated by

Jon
 
Participant
6 months ago.

  • Author
    Posts
  • #102326
    Jon

    Participant
    Points: 35
    Rank: Member

    I was trying to establish a remote session to a couple servers at my DR site and noticed I was getting this error message:

    "Processing data from remote server SERVERA failed...could not find a part of path \\serverB\PSLogs..."

    So off to Google and I find these articles, which makes sense. But from reading these articles all my servers should be getting that error message, however it's only two over there that I can find are having this error message and none of the servers at my primary datacenter are having the problem. I've combed through the event logs on both of the servers having the error and can't find any error, even in the powershell log. I can browse the file share from the server, running effective access as the machine shows it has write permissons. Any suggestions on where to go?

    https://rcmtech.wordpress.com/2017/04/06/powershell-transcription-to-a-file-share-breaks-everything-and-how-to-fix-it/

    https://social.technet.microsoft.com/Forums/windows/en-US/531820d5-e611-41ff-8059-8c14ab1feda5/quotcould-not-find-a-part-of-the-pathquot-after-enabling-powershell-transcription?forum=winserverpowershell

  • #102329

    Participant
    Points: 305
    Helping Hand
    Rank: Contributor

    What context are you running the script in? If it was running as SYSTEM, its possible you may need to allow ANONYMOUS access to the file share or Domain Computers. This seems like it would be more a Windows issue than Powershell. Does it always fail on the same servers?

  • #102334
    Jon

    Participant
    Points: 35
    Rank: Member

    Not even running a script, just trying to open up a interactive session to the server doing enter-pssession. I have the NTFS/Shre permissions set to authenticated users, and this works for all of my machines.

The topic ‘PowerShell transcription logging error’ is closed to new replies.