Jira (PUP-9370) Could not evaluate: ADSI connection error: failed to parse display name

22 views
Skip to first unread message

Paul H (JIRA)

unread,
Dec 19, 2018, 4:41:04 PM12/19/18
to puppe...@googlegroups.com
Paul H created an issue
 
Puppet / Bug PUP-9370
Could not evaluate: ADSI connection error: failed to parse display name
Issue Type: Bug Bug
Assignee: Unassigned
Created: 2018/12/19 1:40 PM
Priority: Minor Minor
Reporter: Paul H

Pertinent information: 
-OS: Windows Server 2016 Standard
-Puppet version 5.5.6
-Hardware: VMWare VM with 2 cores, 4gb of ram

-Summary: When trying to create a local user on a host and associate them to the local administrator group, a "failed to parse display name of moniker" error appears

-Code: 

 

    user { 'Windows':
 
      ensure     => 'present',
 
      name       => 'windows_eng',
 
      password   => '$REDACTED',
 
      groups     => 'Administrators',
 
      forcelocal => true,
 
      comment    => 'Windows Engineer Administrator Account'
 
    }

-Output:

 

 

puppet apply .\asdf.pp
 
Warning: Setting configtimeout is deprecated.
 
 (location: C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/settings.rb:1169:in `issue_deprecation_warning')
 
Notice: Compiled catalog for $HOST in environment production in 0.02 seconds
 
Error: /Stage[main]/Main/User[Windows]: Could not evaluate: ADSI connection error: failed to parse display name of moniker `WinNT://./windows_eng,user'
 
 HRESULT error code:0x800708ad
 
 The user name could not be found.
 
Wrapped exception:
 
failed to parse display name of moniker `WinNT://./windows_eng,user'
 
 HRESULT error code:0x800708ad
 
 The user name could not be found.
 
Notice: Applied catalog in 0.19 seconds

This also appears on agent runs, and I've included the relevant excerpt from "puppet agent -t --trace --debug --verbose" below: 

Error: /User[Windows_Engineer_account]: Could not evaluate: ADSI connection error: failed to parse display name of moniker `WinNT://./windows_eng,user'
 
 HRESULT error code:0x800708ad
 
 The user name could not be found.
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:19:in `rescue in connect'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:15:in `connect'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:184:in `native_user'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:202:in `[]'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/provider/user/windows_adsi.rb:104:in `comment'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/property.rb:470:in `retrieve'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:507:in `block in retrieve'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:501:in `each'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:501:in `inject'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:501:in `retrieve'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type.rb:1098:in `retrieve_resource'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:302:in `from_resource'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:257:in `apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:277:in `eval_resource'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:181:in `call'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:181:in `block (2 levels) in evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:515:in `block in thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:514:in `thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:181:in `block in evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:121:in `traverse'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:171:in `evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:239:in `block (2 levels) in apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:515:in `block in thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:514:in `thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:238:in `block in apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/log.rb:156:in `with_destination'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/report.rb:146:in `as_logging_destination'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:237:in `apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:186:in `block (2 levels) in apply_catalog'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:515:in `block in thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:514:in `thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:185:in `block in apply_catalog'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:232:in `block in benchmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:231:in `benchmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:184:in `apply_catalog'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:369:in `run_internal'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:237:in `block in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet.rb:260:in `override'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:211:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:59:in `block (5 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/timeout.rb:76:in `timeout'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:58:in `block (4 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent/locker.rb:21:in `lock'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:52:in `block (3 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:130:in `with_client'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:49:in `block (2 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:87:in `run_in_fork'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:48:in `block in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:46:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application/agent.rb:372:in `onetime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application/agent.rb:350:in `run_command'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:663:in `exit_on_fail'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/command_line.rb:136:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'
 
C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:4:in `<main>'
 
Wrapped exception:
 
failed to parse display name of moniker `WinNT://./windows_eng,user'
 
 HRESULT error code:0x800708ad
 
 The user name could not be found.
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:17:in `connect'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:17:in `connect'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:184:in `native_user'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/windows/adsi.rb:202:in `[]'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/provider/user/windows_adsi.rb:104:in `comment'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/property.rb:470:in `retrieve'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:507:in `block in retrieve'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:501:in `each'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:501:in `inject'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type/user.rb:501:in `retrieve'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/type.rb:1098:in `retrieve_resource'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:302:in `from_resource'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:20:in `evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:257:in `apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:277:in `eval_resource'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:181:in `call'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:181:in `block (2 levels) in evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:515:in `block in thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:514:in `thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:181:in `block in evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:121:in `traverse'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction.rb:171:in `evaluate'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:239:in `block (2 levels) in apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:515:in `block in thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:514:in `thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:238:in `block in apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/log.rb:156:in `with_destination'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/transaction/report.rb:146:in `as_logging_destination'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:237:in `apply'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:186:in `block (2 levels) in apply_catalog'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:515:in `block in thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:514:in `thinmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:185:in `block in apply_catalog'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:232:in `block in benchmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:231:in `benchmark'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:184:in `apply_catalog'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:369:in `run_internal'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:237:in `block in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet.rb:260:in `override'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/configurer.rb:211:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:59:in `block (5 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/timeout.rb:76:in `timeout'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:58:in `block (4 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent/locker.rb:21:in `lock'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:52:in `block (3 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:130:in `with_client'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:49:in `block (2 levels) in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:87:in `run_in_fork'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:48:in `block in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/agent.rb:46:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application/agent.rb:372:in `onetime'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application/agent.rb:350:in `run_command'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util.rb:663:in `exit_on_fail'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/command_line.rb:136:in `run'
 
C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute'
 
C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:4:in `<main>'

-What's strange about this issue is that when slightly modifying the name, puppet processes the code without issue: 

 

    user { 'Windows':
 
      ensure     => 'present',
 
      name       => 'windows_eeng',
 
      password   => '$REDACTED',
 
      groups     => 'Administrators',
 
      forcelocal => true,
 
      comment    => 'Windows Engineer Administrator Account'
 
    }

-Result: 

puppet apply .\asdf.pp
 
Warning: Setting configtimeout is deprecated.
 
   (location: C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/settings.rb:1169:in `issue_deprecation_warning')
 
Notice: Compiled catalog for $HOST in environment production in 0.02 seconds
 
Notice: /Stage[main]/Main/User[Windows]/ensure: created
 
Notice: Applied catalog in 0.25 seconds

Please excuse the "configtimeout" setting.

I'm speculating that this might be due to "windows_eng" being a domain account, however I'm able to add the user via computer management without issue. Would anyone be able to provide insight on possible causes of this behavior? If any additional information is needed I'll be happy to assist! 

 

 
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Paul H (JIRA)

unread,
Dec 19, 2018, 4:42:03 PM12/19/18
to puppe...@googlegroups.com
Paul H updated an issue
Change By: Paul H
Pertinent information: 
-OS: Windows Server 2016 Standard
-Puppet version 5.5.6
-Hardware: VMWare VM with 2 cores, 4gb of ram

-Summary: When trying to create a local user on a host and associate them to the local administrator group, a "failed to parse display name of moniker" error appears

-Code: 
 
{code:java}
    user { 'Windows':
      ensure     => 'present',
      name       => 'windows_eng',
      password   => '$REDACTED',
      groups     => 'Administrators',
      forcelocal => true,
      comment    => 'Windows Engineer Administrator Account'
    }
{code}
-Output:

 

 
 {code:java}
puppet apply .\asdf.pp
Warning: Setting configtimeout is deprecated.
(location: C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/settings.rb:1169:in `issue_deprecation_warning')
Notice: Compiled catalog for $HOST in environment production in 0.02 seconds
Error: /Stage[main]/Main/User[Windows]: Could not evaluate: ADSI connection error: failed to parse display name of moniker `WinNT://./windows_eng,user'
HRESULT error code:0x800708ad
The user name could not be found.
Wrapped exception:
failed to parse display name of moniker `WinNT://./windows_eng,user'
HRESULT error code:0x800708ad
The user name could not be found.
Notice: Applied catalog in 0.19 seconds
{code}

This also appears on agent runs, and I've included the relevant excerpt from "puppet agent -t --trace --debug --verbose" below: 
{code:java}
C:/Program Files/Puppet Labs/Puppet/puppet/bin/puppet:4:in `<main>'{code}

-What's strange about this issue is that when slightly modifying the name, puppet processes the code without issue: 

 
 {code:java}
    user { 'Windows':
      ensure     => 'present',
      name       => 'windows_eeng',
      password   => '$REDACTED',
      groups     => 'Administrators',
      forcelocal => true,
      comment    => 'Windows Engineer Administrator Account'
    }
{code}
-Result: 
{code:java}
puppet apply .\asdf.pp
Warning: Setting configtimeout is deprecated.
   (location: C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/vendor_ruby/puppet/settings.rb:1169:in `issue_deprecation_warning')
Notice: Compiled catalog for $HOST in environment production in 0.02 seconds
Notice: /Stage[main]/Main/User[Windows]/ensure: created
Notice: Applied catalog in 0.25 seconds
{code}

Please excuse the "configtimeout" setting.

I'm speculating that this might be due to "windows_eng" being a domain account, however I'm able to add the user via computer management without issue. Would anyone be able to provide insight on possible causes of this behavior? If any additional information is needed I'll be happy to assist! 

 

Glenn Sarti (JIRA)

unread,
Dec 19, 2018, 7:42:02 PM12/19/18
to puppe...@googlegroups.com
Glenn Sarti commented on Bug PUP-9370
 
Re: Could not evaluate: ADSI connection error: failed to parse display name

Paul H Have you tried prefixing the name with the domain name? e.g. 'DOMAIN\windows_eng'

Otherwise ADSI Doesn't know in which domain the user exists e.g. multi forest or local.

Glenn Sarti (JIRA)

unread,
Dec 19, 2018, 7:42:03 PM12/19/18
to puppe...@googlegroups.com
Glenn Sarti commented on Bug PUP-9370

Also you can use SIDs

Paul H (JIRA)

unread,
Dec 19, 2018, 9:11:02 PM12/19/18
to puppe...@googlegroups.com
Paul H commented on Bug PUP-9370

Hi Glenn Sarti! 

Test 1: 

    user { "Windows":
 
      ensure     => 'present',
 
      name       => "BUILTIN\\windows_eng",
 
      password   => 'REDACTED',
 
      groups     => "BUILTIN\\Administrators",
 
      forcelocal => true,
 
      comment    => 'Windows Engineer Administrator Account'
 
    }


Error: Puppet is not able to create/delete domain users with the user resource. Wrapped exception: (in OLE method `SetInfo': ) OLE error code:8007089A in Active Directory The specified username is invalid. HRESULT error code:0x80020009 Exception occurred. Error: /Stage[main]/Main/User[Windows]/ensure: change from 'absent' to 'present' failed: Puppet is not able to create/delete domain users with the user resource. Notice: Applied catalog in 0.20 seconds

Test 2: 

    user { "Windows":
 
      ensure     => 'present',
 
      name       => ".\\windows_eng",
 
      password   => 'REDACTED',
 
      groups     => ".\\Administrators",
 
      forcelocal => true,
 
      comment    => 'Windows Engineer Administrator Account'
 
    }


Error: Puppet is not able to create/delete domain users with the user resource. Wrapped exception: (in OLE method `SetInfo': ) OLE error code:8007089A in Active Directory The specified username is invalid. HRESULT error code:0x80020009 Exception occurred. Error: /Stage[main]/Main/User[Windows]/ensure: change from 'absent' to 'present' failed: Puppet is not able to create/delete domain users with the user resource. Notice: Applied catalog in 0.20 seconds

Test 3:   

 

    user { "Windows":
 
      ensure     => 'present',
 
      name       => "${::hostname}\\windows_eng",
 
      password   => 'REDACTED',
 
      groups     => "Administrators",
 
      forcelocal => true,
 
      comment    => 'Windows Engineer Administrator Account'
 
    }
 

Error: Puppet is not able to create/delete domain users with the user resource.
 
Wrapped exception:
 
(in OLE method `SetInfo': )
 
    OLE error code:8007089A in Active Directory
 
      The specified username is invalid.    HRESULT error code:0x80020009
 
      Exception occurred.
 
Error: /Stage[main]/Main/User[Windows]/ensure: change from 'absent' to 'present' failed: Puppet is not able to create/delete domain users with the user resource.
 
Notice: Applied catalog in 0.20 seconds

I apologize for the lack of clarity, however I'm looking to add a local user which happens to have the same name as a domain user. I'm also unsure about using SIDs, as this local account doesn't exist on some hosts yet.

 

 

Glenn Sarti (JIRA)

unread,
Dec 19, 2018, 9:15:07 PM12/19/18
to puppe...@googlegroups.com
Glenn Sarti commented on Bug PUP-9370

Ahh Ok...so you want to CREATE a new user, AND assign to Admins Group, but the username just happens to be the same as a domain account too.

Paul H (JIRA)

unread,
Dec 19, 2018, 9:29:02 PM12/19/18
to puppe...@googlegroups.com
Paul H commented on Bug PUP-9370

Hi Glenn! 

That's correct. What's odd is that changing the name to an account that doesn't already exist on the domain creates the local account normally. I'm also able to add the local account without issue via computer management and I've confirmed that other usernames that have a domain account display the same behavior.

Branan Riley (JIRA)

unread,
Jan 2, 2019, 6:51:02 PM1/2/19
to puppe...@googlegroups.com
Branan Riley updated an issue
 
Change By: Branan Riley
Team: Platform OS

Branan Riley (JIRA)

unread,
Jan 2, 2019, 6:52:02 PM1/2/19
to puppe...@googlegroups.com
Branan Riley updated an issue
Change By: Branan Riley
Labels: customer type_and_provider user windows

Aaron Gilbert (Jira)

unread,
Jun 11, 2020, 11:17:03 AM6/11/20
to puppe...@googlegroups.com
Aaron Gilbert commented on Bug PUP-9370
 
Re: Could not evaluate: ADSI connection error: failed to parse display name

I ran into the same issue in my environment. I didn't even realize I had an account in Active Directory that had the same name as the local accounts I've been using until I attempted to manage that account on a new system with Puppet. 

That aside, I see the same error as stated by Paul:

ADSI connection error: failed to parse display name of moniker `WinNT://./srvradmin,user'

HRESULT error code:0x800708ad
The user name could not be found.
Wrapped exception:
failed to parse display name of moniker `WinNT://./srvradmin,user'

HRESULT error code:0x800708ad
The user name could not be found.
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Aaron Gilbert (Jira)

unread,
Jun 11, 2020, 11:17:04 AM6/11/20
to puppe...@googlegroups.com
Aaron Gilbert updated an issue
 
Change By: Aaron Gilbert
Comment:
I ran into the same issue in my environment. I didn't even realize I had an account in Active Directory that had the same name as the local accounts I've been using until I attempted to manage that account on a new system with Puppet. 

That aside, I see the same error as stated by Paul:
|ADSI connection error: failed to parse display name of moniker `WinNT://./srvradmin,user'
HRESULT error code:0x800708ad
The user name could not be found.
Wrapped exception:
failed to parse display name of moniker `WinNT://./srvradmin,user'
HRESULT error code:0x800708ad
The user name could not be found.|

Aaron Gilbert (Jira)

unread,
Jun 11, 2020, 11:17:04 AM6/11/20
to puppe...@googlegroups.com
Aaron Gilbert commented on Bug PUP-9370

I ran into the same issue in my environment. I didn't even realize I had an account in Active Directory that had the same name as the local accounts I've been using until I attempted to manage that account on a new system with Puppet. 

That aside, I see the same error as stated by Paul:

ADSI connection error: failed to parse display name of moniker `WinNT://./srvradmin,user'
HRESULT error code:0x800708ad
The user name could not be found.
Wrapped exception:
failed to parse display name of moniker `WinNT://./srvradmin,user'
HRESULT error code:0x800708ad
The user name could not be found.
Add Comment Add Comment
 

Nick Howell (Jira)

unread,
Jun 26, 2020, 9:28:03 AM6/26/20
to puppe...@googlegroups.com
Nick Howell commented on Bug PUP-9370

Another +1 on this. I see the same error that Paul and Aaron mention.

 

Interestingly, if I manually create the local user via Computer Management, Puppet is then able to manage it as expected.

Bogdan Irimie (Jira)

unread,
Nov 5, 2020, 3:51:05 AM11/5/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
 
Change By: Bogdan Irimie
Sprint:

Bogdan Irimie (Jira)

unread,
Nov 5, 2020, 3:52:04 AM11/5/20
to puppe...@googlegroups.com
Bogdan Irimie updated an issue
Change By: Bogdan Irimie
Sprint: ready for triage

Ciprian Badescu (Jira)

unread,
Oct 21, 2021, 8:06:04 AM10/21/21
to puppe...@googlegroups.com
Ciprian Badescu commented on Bug PUP-9370
 
Re: Could not evaluate: ADSI connection error: failed to parse display name

Paul H, we recently did some changes in this area, is the error still seen with the latest puppet versions(6.25.0/7.12.0)?

 
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo

Ciprian Badescu (Jira)

unread,
Oct 29, 2021, 5:12:03 AM10/29/21
to puppe...@googlegroups.com
Ciprian Badescu updated an issue
 
Change By: Ciprian Badescu
Sprint: ready for triage
Reply all
Reply to author
Forward
0 new messages