Powershell error when adding filepathPowershell - How to find who is a local administrator on the servers in...

Increase performance creating Mandelbrot set in python

Return the Closest Prime Number

Why, precisely, is argon used in neutrino experiments?

Why Were Madagascar and New Zealand Discovered So Late?

What is paid subscription needed for in Mortal Kombat 11?

How easy is it to start Magic from scratch?

Is HostGator storing my password in plaintext?

How do we know the LHC results are robust?

How did Arya survive the stabbing?

System.debug(JSON.Serialize(o)) Not longer shows full string

Arithmetic mean geometric mean inequality unclear

Was Spock the First Vulcan in Starfleet?

How to Reset Passwords on Multiple Websites Easily?

How do I go from 300 unfinished/half written blog posts, to published posts?

Class Action - which options I have?

Is it appropriate to ask a job candidate if we can record their interview?

Valid Badminton Score?

Escape a backup date in a file name

Why escape if the_content isnt?

Pre-amplifier input protection

Is exact Kanji stroke length important?

Go Pregnant or Go Home

What can we do to stop prior company from asking us questions?

Is there a korbon needed for conversion?



Powershell error when adding filepath


Powershell - How to find who is a local administrator on the servers in Active DirectoryHow to read cell data in excel and output to command promptget-adcomputer error: “Invalid Enumeration Context” when running powershell scriptPowershell querying Sharepoint listCan you use SQLite 64 bit odbc from powershellPowershell script to insert SQL Statement with a apostrophe errorpowershell script to create exchange reportCopying files from local server to remote server using powershellPowershell execution policy within SQL ServerExchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works LocallyGet local User group members - Powershell













0















The script looks like this:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt
}
}


If I remove this part after New-Object...



 | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


...the script works perfect. When adding the above mentioned line I get this error for all the servers / members it finds:




Exception calling "Invoke" with "2" argument(s): "The network path was
not found. " At C:scriptsmyscript.ps1:5 char:62
+ ([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke <<<< ('Members') |
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException











share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • remove the "Format-Table" part from the pipeline. That is only used for viewing in the console and will screw up stuff that comes after it.

    – August
    Jan 22 '13 at 12:15











  • @August: A format- before an out- often makes sense (write the file in a specific format).

    – Richard
    Jan 22 '13 at 13:10
















0















The script looks like this:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt
}
}


If I remove this part after New-Object...



 | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


...the script works perfect. When adding the above mentioned line I get this error for all the servers / members it finds:




Exception calling "Invoke" with "2" argument(s): "The network path was
not found. " At C:scriptsmyscript.ps1:5 char:62
+ ([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke <<<< ('Members') |
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException











share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • remove the "Format-Table" part from the pipeline. That is only used for viewing in the console and will screw up stuff that comes after it.

    – August
    Jan 22 '13 at 12:15











  • @August: A format- before an out- often makes sense (write the file in a specific format).

    – Richard
    Jan 22 '13 at 13:10














0












0








0








The script looks like this:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt
}
}


If I remove this part after New-Object...



 | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


...the script works perfect. When adding the above mentioned line I get this error for all the servers / members it finds:




Exception calling "Invoke" with "2" argument(s): "The network path was
not found. " At C:scriptsmyscript.ps1:5 char:62
+ ([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke <<<< ('Members') |
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException











share|improve this question
















The script looks like this:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt
}
}


If I remove this part after New-Object...



 | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


...the script works perfect. When adding the above mentioned line I get this error for all the servers / members it finds:




Exception calling "Invoke" with "2" argument(s): "The network path was
not found. " At C:scriptsmyscript.ps1:5 char:62
+ ([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke <<<< ('Members') |
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException








windows-server-2008-r2 scripting powershell






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 22 '13 at 12:18









August

3,0741117




3,0741117










asked Jan 22 '13 at 10:18









SabeltigerSabeltiger

112




112





bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • remove the "Format-Table" part from the pipeline. That is only used for viewing in the console and will screw up stuff that comes after it.

    – August
    Jan 22 '13 at 12:15











  • @August: A format- before an out- often makes sense (write the file in a specific format).

    – Richard
    Jan 22 '13 at 13:10



















  • remove the "Format-Table" part from the pipeline. That is only used for viewing in the console and will screw up stuff that comes after it.

    – August
    Jan 22 '13 at 12:15











  • @August: A format- before an out- often makes sense (write the file in a specific format).

    – Richard
    Jan 22 '13 at 13:10

















remove the "Format-Table" part from the pipeline. That is only used for viewing in the console and will screw up stuff that comes after it.

– August
Jan 22 '13 at 12:15





remove the "Format-Table" part from the pipeline. That is only used for viewing in the console and will screw up stuff that comes after it.

– August
Jan 22 '13 at 12:15













@August: A format- before an out- often makes sense (write the file in a specific format).

– Richard
Jan 22 '13 at 13:10





@August: A format- before an out- often makes sense (write the file in a specific format).

– Richard
Jan 22 '13 at 13:10










1 Answer
1






active

oldest

votes


















0














One fix: the format and out need to follow the pipeline of the outer Foreach-Object:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user}
}
} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


Second: the error is coming from the ADSI Invoke call, probably unable to resolve the machine name.






share|improve this answer
























  • I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

    – Sabeltiger
    Jan 22 '13 at 14:37











  • I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

    – Richard
    Jan 22 '13 at 16:14











  • And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

    – Sabeltiger
    Jan 23 '13 at 8:51











  • @Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

    – Richard
    Jan 23 '13 at 9:13













  • You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

    – Sabeltiger
    Jan 23 '13 at 10:49











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f471326%2fpowershell-error-when-adding-filepath%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














One fix: the format and out need to follow the pipeline of the outer Foreach-Object:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user}
}
} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


Second: the error is coming from the ADSI Invoke call, probably unable to resolve the machine name.






share|improve this answer
























  • I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

    – Sabeltiger
    Jan 22 '13 at 14:37











  • I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

    – Richard
    Jan 22 '13 at 16:14











  • And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

    – Sabeltiger
    Jan 23 '13 at 8:51











  • @Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

    – Richard
    Jan 23 '13 at 9:13













  • You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

    – Sabeltiger
    Jan 23 '13 at 10:49
















0














One fix: the format and out need to follow the pipeline of the outer Foreach-Object:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user}
}
} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


Second: the error is coming from the ADSI Invoke call, probably unable to resolve the machine name.






share|improve this answer
























  • I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

    – Sabeltiger
    Jan 22 '13 at 14:37











  • I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

    – Richard
    Jan 22 '13 at 16:14











  • And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

    – Sabeltiger
    Jan 23 '13 at 8:51











  • @Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

    – Richard
    Jan 23 '13 at 9:13













  • You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

    – Sabeltiger
    Jan 23 '13 at 10:49














0












0








0







One fix: the format and out need to follow the pipeline of the outer Foreach-Object:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user}
}
} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


Second: the error is coming from the ADSI Invoke call, probably unable to resolve the machine name.






share|improve this answer













One fix: the format and out need to follow the pipeline of the outer Foreach-Object:



$searchOU='ou=Servers,dc=mydomain,dc=NET'
Get-ADComputer -filter * -SearchBase $searchOU |
Foreach-Object {
$server = $_.Name
([ADSI]"WinNT://$($_.Name)/Administrators").psbase.invoke('Members') |
ForEach-Object {
$user = $_.GetType().InvokeMember('Name', 'GetProperty', $null, $_, $null)

New-Object 'PSObject' -property @{'Server'=$server; 'Admin'=$user}
}
} | Format-Table -AutoSize Server, Name | Out-File C:Scriptsservers.txt


Second: the error is coming from the ADSI Invoke call, probably unable to resolve the machine name.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 22 '13 at 13:09









RichardRichard

5,01911719




5,01911719













  • I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

    – Sabeltiger
    Jan 22 '13 at 14:37











  • I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

    – Richard
    Jan 22 '13 at 16:14











  • And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

    – Sabeltiger
    Jan 23 '13 at 8:51











  • @Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

    – Richard
    Jan 23 '13 at 9:13













  • You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

    – Sabeltiger
    Jan 23 '13 at 10:49



















  • I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

    – Sabeltiger
    Jan 22 '13 at 14:37











  • I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

    – Richard
    Jan 22 '13 at 16:14











  • And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

    – Sabeltiger
    Jan 23 '13 at 8:51











  • @Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

    – Richard
    Jan 23 '13 at 9:13













  • You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

    – Sabeltiger
    Jan 23 '13 at 10:49

















I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

– Sabeltiger
Jan 22 '13 at 14:37





I hate to say it, but adding the Out-file line as in the above script does not work for me or PowerShell. when adding the Out-File path it writes the error already posted, which is my problem when adding the Out-file path.

– Sabeltiger
Jan 22 '13 at 14:37













I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

– Richard
Jan 22 '13 at 16:14





I suggest lots of Write-Debug and setting $DebugPreference to Continue to check things like the path passed to ADSI. (I think outputing to the host is likely hiding the error: scrolling off the top: using AutoSize means all the data needs to be read first so any errors will be before any output.)

– Richard
Jan 22 '13 at 16:14













And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

– Sabeltiger
Jan 23 '13 at 8:51





And how exactly will the Write-Debug and DebugPreference be added to the script? I guess that $DebugPreference is a variable that you put something in, perhaps the ADSI path itself?

– Sabeltiger
Jan 23 '13 at 8:51













@Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

– Richard
Jan 23 '13 at 9:13







@Sabeltiger eg. Write-Debug "This is the path: $thePath" in the script to show the values of things and state. See get-help about_preference_variables.

– Richard
Jan 23 '13 at 9:13















You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

– Sabeltiger
Jan 23 '13 at 10:49





You mentioned that errors would be shown before any output because of the Autosize. Does that mean that it trie to contact the server and if not successful then it will write the error output first and the server it tried to reach, beneath the error output? like this: Server-path not available and next line "Server 31" or will Server 31 be on the line above the error log in PowerShell?

– Sabeltiger
Jan 23 '13 at 10:49


















draft saved

draft discarded




















































Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f471326%2fpowershell-error-when-adding-filepath%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

As a Security Precaution, the user account has been locked The Next CEO of Stack OverflowMS...

Список ссавців Італії Природоохоронні статуси | Список |...

Українські прізвища Зміст Історичні відомості |...