<div>
Help me again to understand your problem. 
You have bunch of files in a folder. 
Each file is of type .txt 
Each file contain some number (45653) in the LAST line. 
You want this Last line to be read from each file and copied to an another file.
</div>

<div>
$files = Get-ChildItem &quot;O:\Private\WLP_SSIS\Files\Load\Visit_In\&quot;*.txt -Recurse | 
 
ForEach-Object -process $Name 
{ 
&nbsp; &nbsp; (Get-Content $file )[-1] | Out-File c:\test\Visit_In_Counts.txt -Append 
} 
 
Would this work to cut down memory usage? &nbsp;But will it take longer?
</div>

<div>
Yeah, thats due to file size i believe 
whats the .txt file size that we are trying to read here? max/min size
</div>

<div>
File sizes 1 - 703166 KB 
File sizes 2 - 906 KB 
Files sizes 3 - 321637 KB
</div>

<div>
The script ran but do not write to the file??
</div>

<div>
I tried reading 6 text files of size 52MB approx. 
but couldn't find much different in the time it takes run. 

<pre><code class="code-1 nolinks" id="code-20-41439943-1">Set-Location -Path O:\Private\WLP_SSIS\Files\Load\Visit_In
$Files = Get-ChildItem -Path .\ | where{$_.Extension -eq &quot;.txt&quot;}
foreach($File in $Files){
 Get-Content -Path $File.FullName -ReadCount 1 | select -Last 1 | Out-File -FilePath c:\test\Visit_In_Counts.txt -Append
}
</code></pre>
</div>

<div>
If you have PS 3.0+, you can use the -Tail parameter of Get-Content to speed things up. 

<pre><code class="code-1 nolinks" id="code-20-41440530-1">$files = Get-ChildItem &quot;O:\Private\WLP_SSIS\Files\Load\Visit_In\&quot;*.txt
foreach ($file in $files)
{
 Get-Content $file -Tail 1 | Out-File c:\test\Visit_In_Counts.txt -Append
}
</code></pre>
Unless you have a lot of files in the folder, you probably won't see any difference using the foreach statement vs. ForEach-Object cmdlet. 

<pre><code class="code-1 nolinks" id="code-20-41440530-2">Get-ChildItem &quot;O:\Private\WLP_SSIS\Files\Load\Visit_In\&quot;*.txt | ForEach-Object { Get-Content $_ -Tail 1 } | Out-File c:\test\Visit_In_Counts.txt -Append
</code></pre>
</div>

<div>
Just to be clear, most of the comments here haven't directly answered your question about the error you're encountering. &nbsp;However, I think all of the options shown will result in less memory usage, thereby avoiding the error. 
 
Here's a link for changing the limit on how much memory PS can use. 
<a href="http://blogs.technet.com/b/heyscriptingguy/archive/2013/07/30/learn-how-to-configure-powershell-memory.aspx" rel="ugc">http://blogs.technet.com/b/heyscriptingguy/archive/2013/07/30/learn-how-to-configure-powershell-memory.aspx</a> 
 
The biggest source of memory usage in your script comes from this 
(Get-Content $file )[-1] 
With the parentheses, the entire file will be loaded in memory before the last item is selected and output. &nbsp;If you use the following, again the entire file is read, but each line is sent to the pipeline as it's read (and each one is discarded until the last one), resulting in negligible memory usage. 
get-content $file.fullname | Select-Object -last 1 
However, because it still has to read in the entire file, large files will slow down execution. &nbsp;One thing that will help the speed of execution for both the previous commands is setting the -ReadCount parameter to 0 for Get-Content. 
The option I showed has the advantage of both speed and reduced memory usage because of the -Tail parameter for Get-Content (again, only available in PS 3.0 and newer). &nbsp;The larger the files that you have to read in, the greater improvement you will see from using this. &nbsp;If you only have PS 2.0, you would have to use .Net classes directly to do the same thing, though I've seen a script someone put together to do this. 
 
The next optimization (for speed) comes from how you handle writing to your output file. &nbsp;As David mentioned, repeatedly opening, writing to, and closing the file is a slow process. &nbsp;The more times you do it, the more you're likely to be able to see the effects of this, which is why I mentioned this was dependent on having a lot of files. &nbsp;There are different ways to avoid this, my second example is one, David's &quot;version 2&quot; is another (and I can think of a third).
</div>

<div>
using -tail 1 is actually the fastest 

<pre><code class="code-10 nolinks" id="code-20-41441932-1">remove-item c:\test\count*.txt -ErrorAction SilentlyContinue
$timer= measure-command {
$files = Get-ChildItem -Path G:\Documents\WindowsPowershell\modules\ -Filter *.ps1 -Recurse
foreach ($file in $files)
 { 
 get-content $file.fullname | Select-Object -last 1 | out-file c:\test\counts.txt -Append
 }
}
Write-Host ('Version 1 found: {0} Files and took: {1:N2} seconds' -f $files.Count,$timer.TotalSeconds)
$timer2 = measure-command {
$myobject = @()
$files2 = Get-ChildItem -Path G:\Documents\WindowsPowershell\Modules\ -Recurse -Filter *.ps1
foreach ($file in $files2){ 
 $myobject += (get-content $file.fullname | select-object -last 1 )
 }
$myobject | out-file C:\test\counts2.txt
}
Write-Host ('Version 2 found: {0} Files and took: {1:N2} seconds' -f $files2.Count,$timer2.TotalSeconds)

$timer= measure-command {
$files = Get-ChildItem -Path G:\Documents\WindowsPowershell\modules\ -Filter *.ps1 -Recurse
foreach ($file in $files)
 { 
 get-content $file.fullname -Tail 1 | out-file c:\test\counts3.txt -Append
 }
}
Write-Host ('Version 3 found: {0} Files and took: {1:N2} seconds' -f $files.Count,$timer.TotalSeconds)
$timer2 = measure-command {
$myobject = @()
$files2 = Get-ChildItem -Path G:\Documents\WindowsPowershell\Modules\ -Recurse -Filter *.ps1
foreach ($file in $files2){ 
 $myobject += (get-content $file.fullname -Tail 1 )
 }
$myobject | out-file C:\test\counts4.txt
}
Write-Host ('Version 4 found: {0} Files and took: {1:N2} seconds' -f $files2.Count,$timer2.TotalSeconds)


$file1 = get-content C:\test\counts.txt
$file2 = get-content C:\test\counts2.txt
$test =(compare-object -ReferenceObject $file1 -DifferenceObject $file2 -PassThru)
if ($test -eq $null){Write-Output (&quot;counts.txt compared to counts2.txt:No Difference'&quot;)}
else {write-output('Differences Found')}

$file1 = get-content C:\test\counts.txt
$file2 = get-content C:\test\counts3.txt
$test =(compare-object -ReferenceObject $file1 -DifferenceObject $file2 )
if ($test -eq $null){Write-Output (&quot;counts.txt compared to counts3.txt:No Difference'&quot;)}
else {write-output('Differences Found')}
$file1 = get-content C:\test\counts.txt
$file2 = get-content C:\test\counts4.txt
$test =(compare-object -ReferenceObject $file1 -DifferenceObject $file2 -PassThru) 
if ($test -eq $null){Write-Output (&quot;counts.txt compared to counts4.txt:No Difference'&quot;)}
else {write-output('Differences Found')}
</code></pre>
 
Version 1 found: 746 Files and took: 13.74 seconds 
Version 2 found: 746 Files and took: 9.87 seconds 
Version 3 found: 746 Files and took: 4.56 seconds 
Version 4 found: 746 Files and took: 0.76 seconds 
counts.txt compared to counts2.txt:No Difference' 
counts.txt compared to counts3.txt:No Difference' 
counts.txt compared to counts4.txt:No Difference'
</div>

<div>
Unfortunately I do not have 3.0
</div>

<div>
Well, the options have been laid out. 
If you don't want to or can't upgrade your PowerShell version, then use one of the other methods shown, or try out this Tail-Content script. &nbsp;<a href="https://rkeithhill.wordpress.com/2009/01/28/tail-content-%E2%80%93-better-performance-for-grabbing-last-lines-from-large-ascii-log-files/" rel="ugc">https://rkeithhill.wordpress.com/2009/01/28/tail-content-%E2%80%93-better-performance-for-grabbing-last-lines-from-large-ascii-log-files/</a>
</div>

<div>
<div class="content wysiwyg-content">
I am running this powershell script from my PC and it keeps running out of shared memory and locking up my computer. &nbsp;I am hoping that there may be a better way. &nbsp;This script pulls the last line of my files that contain the row counts. &nbsp;Some of these files have millions of rows. 
 
This is my first powershell script and are very new to it. 
 
cd &quot;O:\Private\WLP_SSIS\Files\Load\Visit_In&quot; 
 
$files = Get-ChildItem &quot;O:\Private\WLP_SSIS\Files\Load\Visit_In\&quot;*.txt 
 
foreach ($file in $files) 
{ 
&nbsp; &nbsp; (Get-Content $file )[-1] | Out-File c:\test\Visit_In_Counts.txt -Append 
}
</div>
</div>

I am running this powershell script from my PC and it keeps running out of shared memory and locking up my computer.  I am hoping that there may be a better way.  This script pulls the last line of my files that contain the row counts.  Some of these files have millions of rows.

This is my first powershell script and are very new to it.

cd "O:\Private\WLP_SSIS\Files\Load\Visit_In"

$files = Get-ChildItem "O:\Private\WLP_SSIS\Files\Load\Visit_In\"*.txt

foreach ($file in $files)
{
    (Get-Content $file )[-1] | Out-File c:\test\Visit_In_Counts.txt -Append
}

Powershell script &quot;Out of Shared Memory&quot; error

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

A scripting language is a programming language that supports scripts, programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator. Scripting languages are often interpreted (rather than compiled). Primitives are usually the elementary tasks or API calls, and the language allows them to be combined into more complex programs. Environments that can be automated through scripting include software applications, web pages within a web browser, the shells of operating systems (OS), embedded systems, as well as numerous games. A scripting language can be viewed as a domain-specific language for a particular environment; in the case of scripting an application, this is also known as an extension language.

Scripting Languages

Programming includes both the specifics of the language you’re using, like Visual Basic, .NET, Java and others, but also the best practices in user experience and interfaces and the management of projects, version control and development. Other programming topics are related to web and cloud development and system and hardware programming.

Powershell script &quot;Out of Shared Memory&quot; error

Powershell script "Out of Shared Memory" error