locked
Powershell scripts failing with error There is not enough space on the disk RRS feed

  • Question

  • Hi All

    I have a scenario where all my scripts are failing on my Orchestrator Windows 2016 server " There is not enough space on the disk".

    What could be the issue. I also could see in the Operations manager log that even SCOM scripts are failing with the same error.


    Justin


    • Edited by JS2206 Tuesday, December 4, 2018 10:02 AM
    Tuesday, December 4, 2018 10:02 AM

Answers

  • Definetly jrv. its clearly not a script issue. But a simple trim function fails when tried to run.

    I have raised a Microsoft case and awaiting their response. Meanwhile wanted to understand if any of you have faced such issues.

    Thanks for your response.


    Justin

    • Marked as answer by JS2206 Wednesday, December 5, 2018 5:22 AM
    Wednesday, December 5, 2018 5:22 AM
  • Hi All

    The issue has been resolved after contacting Microsoft. It seems that the Powershell transcripts were enabled and the sharepoint to which it was getting written were getting full.

    The logging has been disabled and now the issue has been resolved.


    Justin

    • Marked as answer by JS2206 Monday, January 28, 2019 6:29 AM
    Monday, January 28, 2019 6:29 AM

All replies

  • Sounds like your script is taking all the drive space.

    If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. (99,108,97,121,109,97,110,50,64,110,121,99,97,112,46,114,114,46,99,111,109|%{[char]$_})-join''

    Tuesday, December 4, 2018 12:58 PM
  • You have to fix the reported problem.  It is not a scripting issue. 


    \_(ツ)_/

    Tuesday, December 4, 2018 1:00 PM
  • Hi

    The physical disks are fine. They have enough free space. I just wanted to understand what could i check to see which is causing this error.


    Justin

    Tuesday, December 4, 2018 1:56 PM
  • You have to come up with more information.  What line in the script is causing the error.  What is the complete error message.

    We cannot troubleshoot your systems for you.


    \_(ツ)_/

    Tuesday, December 4, 2018 2:00 PM
  • Definetly jrv. its clearly not a script issue. But a simple trim function fails when tried to run.

    I have raised a Microsoft case and awaiting their response. Meanwhile wanted to understand if any of you have faced such issues.

    Thanks for your response.


    Justin

    • Marked as answer by JS2206 Wednesday, December 5, 2018 5:22 AM
    Wednesday, December 5, 2018 5:22 AM
  • Definetly jrv. its clearly not a script issue. But a simple trim function fails when tried to run.

    I have raised a Microsoft case and awaiting their response. Meanwhile wanted to understand if any of you have faced such issues.

    Thanks for your response.


    Justin

    How is that the answer to the question?

    Live long and prosper!

    (79,108,97,102|%{[char]$_})-join''

    Wednesday, December 5, 2018 7:24 AM
  • Maybe your code is trying to save some information (csv output, whatever) to disk and the account doesn´t  have permissions to write.  

    You can try to turn off UAC. 

    Wednesday, December 5, 2018 8:30 AM
  • we have the exact same issue. Is it possible you share the resolution or the case please?
    Monday, December 17, 2018 3:43 PM
  • Please do not "hijack" other poeples threads. If you have q question create an own thread and place a link to this one if needed.

    Thanks


    Live long and prosper!

    (79,108,97,102|%{[char]$_})-join''

    Monday, December 17, 2018 3:47 PM
  • Hi All

    The issue has been resolved after contacting Microsoft. It seems that the Powershell transcripts were enabled and the sharepoint to which it was getting written were getting full.

    The logging has been disabled and now the issue has been resolved.


    Justin

    • Marked as answer by JS2206 Monday, January 28, 2019 6:29 AM
    Monday, January 28, 2019 6:29 AM