DSC Errors

Viewing 1 reply thread
  • Author
    Posts
    • #48991
      Participant
      Topics: 4
      Replies: 15
      Points: 18
      Rank: Member

      I goofed earlier today – and sent a DSC COnfiguration to the wrong node. A simple typo. But now I get errors I can not resolve.

      Here's the first part of my configuratino document

      Configuration  IISSRV2
      {
        Import-DscResource -ModuleName xWebAdministration
        Import-DscResource -ModuleName PSDesiredStateConfiguration
        Node SRV2
          {
              Windowsfeature IISSrv2
                  { Ensure =  'Present' 
                    Name   =  'Web-Server'
                    Source =  'wim:d:\sources\install.wim:4'
                  }
                  
                  Windowsfeature IISSrvtools
                  { Ensure    ='Present' 
                    Name      = 'Web-Mgmt-Tools'
                    Source    = 'wim:d:\sources\install.wim:4'
                    DependsOn = "[WindowsFeature]IISSrv2"
                  } 
                  
                  Windowsfeature Scripttools
                  { Ensure    = 'Present' 
                    Name      = 'Web-Scripting-Tools'
                    Source    = 'wim:d:\sources\install.wim:4'
                    DependsOn = "[WindowsFeature]IISSrv2"
                  }

      Nothing special (and there's more but I've cut that for this post).

      I initially ran this, incorrectly against DC1, then changed the config document to point to SRV2. NOW< now matter what I do, I get errors, like this: VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, "methodName' = SendConfigurationApply,'className' = MS
      FT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
      VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, "methodName' = SendConfigurationApply,'className' = MS
      FT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
      VERBOSE: An LCM method call arrived from computer SRV1 with user sid S-1-5-21-1987174662-1902880718-1430139159-500.
      VERBOSE: [DC1]: LCM: [ Start Set ]
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      VERBOSE: An LCM method call arrived from computer SRV1 with user sid S-1-5-21-1987174662-1902880718-1430139159-500.
      VERBOSE: [SRV2]: LCM: [ Start Set ]
      VERBOSE: [SRV2]: LCM: [ Start Resource ] [[WindowsFeature]IISSrv2]
      VERBOSE: [SRV2]: LCM: [ Start Test ] [[WindowsFeature]IISSrv2]
      VERBOSE: [SRV2]: [[WindowsFeature]IISSrv2] The operation 'Get-WindowsFeature' started: Web-Server
      VERBOSE: [SRV2]: [[WindowsFeature]IISSrv2] The operation 'Get-WindowsFeature' succeeded: Web-Server
      VERBOSE: [SRV2]: LCM: [ End Test ] [[WindowsFeature]IISSrv2] in 0.6900 seconds.
      VERBOSE: [SRV2]: LCM: [ Skip Set ] [[WindowsFeature]IISSrv2]
      VERBOSE: [SRV2]: LCM: [ End Resource ] [[WindowsFeature]IISSrv2]
      VERBOSE: [SRV2]: LCM: [ Start Resource ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [SRV2]: LCM: [ Start Test ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [SRV2]: [[WindowsFeature]IISSrvtools] The operation 'Get-WindowsFeature' started: Web-Mgmt-T
      ools
      VERBOSE: [SRV2]: [[WindowsFeature]IISSrvtools] The operation 'Get-WindowsFeature' succeeded: Web-Mgmt
      -Tools
      VERBOSE: [SRV2]: LCM: [ End Test ] [[WindowsFeature]IISSrvtools] in 0.3130 seconds.
      VERBOSE: [SRV2]: LCM: [ Skip Set ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [SRV2]: LCM: [ End Resource ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [SRV2]: LCM: [ Start Resource ] [[WindowsFeature]Scripttools]
      VERBOSE: [SRV2]: LCM: [ Start Test ] [[WindowsFeature]Scripttools]
      VERBOSE: [SRV2]: [[WindowsFeature]Scripttools] The operation 'Get-WindowsFeature' started: Web-Script
      ing-Tools
      VERBOSE: [SRV2]: [[WindowsFeature]Scripttools] The operation 'Get-WindowsFeature' succeeded: Web-Scri
      pting-Tools
      VERBOSE: [SRV2]: LCM: [ End Test ] [[WindowsFeature]Scripttools] in 0.2420 seconds.
      VERBOSE: [SRV2]: LCM: [ Skip Set ] [[WindowsFeature]Scripttools]
      VERBOSE: [SRV2]: LCM: [ End Resource ] [[WindowsFeature]Scripttools]
      VERBOSE: [SRV2]: LCM: [ Start Resource ] [[File]IISFIles]
      VERBOSE: [SRV2]: LCM: [ Start Test ] [[File]IISFIles]
      VERBOSE: [SRV2]: [[File]IISFIles] The network name cannot be found.
      VERBOSE: [SRV2]: [[File]IISFIles] The related file/directory is: \\dc1\psmcapp.
      VERBOSE: [SRV2]: [[File]IISFIles] Building file list from cache.
      VERBOSE: [SRV2]: LCM: [ End Test ] [[File]IISFIles] in 0.0310 seconds.
      VERBOSE: [SRV2]: LCM: [ Start Set ] [[File]IISFIles]
      VERBOSE: [SRV2]: [[File]IISFIles] The network name cannot be found.
      VERBOSE: [SRV2]: [[File]IISFIles] The related file/directory is: \\dc1\psmcapp.
      VERBOSE: [SRV2]: [[File]IISFIles] Building file list from cache.
      VERBOSE: [SRV2]: [[File]IISFIles] Copying file \\dc1\psmcapp\Index.htm to c:\inetpub\wwwroot\ReskitAp
      p\Index.htm.
      VERBOSE: [SRV2]: [[File]IISFIles] Copying file \\dc1\psmcapp\Page2.htm to c:\inetpub\wwwroot\ReskitAp
      p\Page2.htm.
      VERBOSE: [SRV2]: LCM: [ End Set ] [[File]IISFIles] in 0.0160 seconds.
      VERBOSE: [SRV2]: LCM: [ End Resource ] [[File]IISFIles]
      VERBOSE: [SRV2]: LCM: [ Start Resource ] [[xWebAppPool]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ Start Test ] [[xWebAppPool]ReskitApp]
      VERBOSE: [SRV2]: [[xWebAppPool]ReskitApp] Application pool "RKAppPool" was found.
      VERBOSE: [SRV2]: [[xWebAppPool]ReskitApp] The target resource is already in the desired state. No act
      ion is required.
      VERBOSE: [SRV2]: LCM: [ End Test ] [[xWebAppPool]ReskitApp] in 0.3900 seconds.
      VERBOSE: [SRV2]: LCM: [ Skip Set ] [[xWebAppPool]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ End Resource ] [[xWebAppPool]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ Start Resource ] [[xWebApplication]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ Start Test ] [[xWebApplication]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ End Test ] [[xWebApplication]ReskitApp] in 0.1720 seconds.
      VERBOSE: [SRV2]: LCM: [ Skip Set ] [[xWebApplication]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ End Resource ] [[xWebApplication]ReskitApp]
      VERBOSE: [SRV2]: LCM: [ End Set ]
      VERBOSE: [SRV2]: LCM: [ End Set ] in 2.5890 seconds.
      VERBOSE: Operation 'Invoke CimMethod' complete.
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      VERBOSE: [DC1]: LCM: [ Start Resource ] [[WindowsFeature]IISSrv2]
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      VERBOSE: [DC1]: LCM: [ Start Test ] [[WindowsFeature]IISSrv2]
      VERBOSE: [DC1]: [[WindowsFeature]IISSrv2] The operation 'Get-WindowsFeature' started: Web-Server
      VERBOSE: [DC1]: [[WindowsFeature]IISSrv2] The operation 'Get-WindowsFeature' succeeded: Web-Server
      VERBOSE: [DC1]: LCM: [ End Test ] [[WindowsFeature]IISSrv2] in 0.9000 seconds.
      VERBOSE: [DC1]: LCM: [ Skip Set ] [[WindowsFeature]IISSrv2]
      VERBOSE: [DC1]: LCM: [ End Resource ] [[WindowsFeature]IISSrv2]
      VERBOSE: [DC1]: LCM: [ Start Resource ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      VERBOSE: [DC1]: LCM: [ Start Test ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [DC1]: [[WindowsFeature]IISSrvtools] The operation 'Get-WindowsFeature' started: Web-Mgmt-To
      ols
      VERBOSE: [DC1]: [[WindowsFeature]IISSrvtools] The operation 'Get-WindowsFeature' succeeded: Web-Mgmt-
      Tools
      VERBOSE: [DC1]: LCM: [ End Test ] [[WindowsFeature]IISSrvtools] in 0.3690 seconds.
      VERBOSE: [DC1]: LCM: [ Skip Set ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [DC1]: LCM: [ End Resource ] [[WindowsFeature]IISSrvtools]
      VERBOSE: [DC1]: LCM: [ Start Resource ] [[WindowsFeature]Scripttools]
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      VERBOSE: [DC1]: LCM: [ Start Test ] [[WindowsFeature]Scripttools]
      VERBOSE: [DC1]: [[WindowsFeature]Scripttools] The operation 'Get-WindowsFeature' started: Web-Scripti
      ng-Tools
      VERBOSE: [DC1]: [[WindowsFeature]Scripttools] The operation 'Get-WindowsFeature' succeeded: Web-Scrip
      ting-Tools
      VERBOSE: [DC1]: LCM: [ End Test ] [[WindowsFeature]Scripttools] in 0.3750 seconds.
      VERBOSE: [DC1]: LCM: [ Skip Set ] [[WindowsFeature]Scripttools]
      VERBOSE: [DC1]: LCM: [ End Resource ] [[WindowsFeature]Scripttools]
      VERBOSE: [DC1]: LCM: [ Start Resource ] [[File]IISFIles]
      VERBOSE: [DC1]: LCM: [ Start Test ] [[File]IISFIles]
      VERBOSE: [DC1]: [[File]IISFIles] The system cannot find the file specified.
      VERBOSE: [DC1]: [[File]IISFIles] The related file/directory is: c:\inetpub\wwwroot\ReskitApp.
      VERBOSE: [DC1]: [[File]IISFIles] The network name cannot be found.
      VERBOSE: [DC1]: [[File]IISFIles] The related file/directory is: \\dc1\reskitapp.
      VERBOSE: [DC1]: [[File]IISFIles] The path cannot point to the root directory or to the root of a net
      share.
      VERBOSE: [DC1]: [[File]IISFIles] The related file/directory is: \\dc1\reskitapp.
      VERBOSE: [DC1]: [[File]IISFIles] SourcePath must be specified if you want to configure the destinatio
      n directory recursively. Make sure that SourcePath is a directory and that it is accessible.
      SourcePath must be specified if you want to configure the destination directory recursively. Make sure that SourcePath is a
      directory and that it is accessible.
      + CategoryInfo : InvalidArgument: (:) [], CimException
      + FullyQualifiedErrorId : MI RESULT 4
      + PSComputerName : dc1

      VERBOSE: [DC1]: LCM: [ End Set ]
      VERBOSE: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      WARNING: [DC1]: [] LCM state is changed by non-DSC operations. If you wish to change the state of LCM
      , please use Remove-DscConfigurationDocument cmdlet.
      The SendConfigurationApply function did not succeed.
      + CategoryInfo : InvalidArgument: (root/Microsoft/...gurationManager:String) [], CimException
      + FullyQualifiedErrorId : MI RESULT 4
      + PSComputerName : dc1

      As you can see – loads of issues on DC1, but I've tried everything: remove-dscconfiguration documents, deleting every relevant MOF file I can see in \windows\system32\configuration.

      CLues?

      I really do not want to have to rebuild the systems just to get rid of these errors!

    • #49014
      Participant
      Topics: 4
      Replies: 15
      Points: 18
      Rank: Member

      I figured it out.

      I had left the older MOF files in the directory I ran the Start-DSCConfiguration from. 🙁

      An easy solution once you work out just what the heck is going on!

      I wish there was some better output form the cmdlet – possibly saying 'we are applying x.mof'...

Viewing 1 reply thread
  • The topic ‘DSC Errors’ is closed to new replies.