Unable to run DSC resource in Production

Welcome Forums DSC (Desired State Configuration) Unable to run DSC resource in Production

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

 
Participant
1 year, 11 months ago.

  • Author
    Posts
  • #59536

    Participant
    Points: 0
    Rank: Member

    Hi All

    We are using DSC to configure the sharepoint machines and we have various resources built. Currently we are facing an issues in production which we are not able to replicate in other server.

    The error is as belows

    The term 'Write-Verbose' is not recognized as the name of a cmdlet, function, script file, or operable program. Check t
    he spelling of the name, or if a path was included, verify that the path is correct and try again.
    + CategoryInfo : InvalidOperation: (:) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName

    We have multiple resources using write-verbose statement.The first resource does not have issue with the write-verbose statement but the second resources in the configuration errors out with the above message

    Kindly let us know hoe to troubleshoot the same

    Thanks

  • #59538

    Keymaster
    Points: 1,638
    Helping HandTeam Member
    Rank: Community Hero

    That's odd, given that verbosity is part of the core. I'd almost suspect a problem with PSMOdulePath environment variable. Can you check that? Is this one affected machine, or several affected?

    • #59622

      Participant
      Points: 0
      Rank: Member

      Hi

      Write-verbose is part of the module "Microsoft.PowerShell.Utility" . we were thinking of replicated the issue in our environemnt
      can we delete this module from the machine and check if we get the same error

      Thanks

The topic ‘Unable to run DSC resource in Production’ is closed to new replies.