Powershell как закрыть excel

I am initiating a macro in a workbook from powershell (to automate a process). The below in powershell opens the excel workbook and runs the macro without visualizing the process.

The issue is even though I do not see the macro running, the new instance of excel generated from the macro is still open.

# start Excel
$excel = New-Object -comobject Excel.Application

#open file
$FilePath = 'C:fileBook1.xlsm'
$workbook = $excel.Workbooks.Open($FilePath)


#access the Application object and run a macro
$app = $excel.Application
$app.Run("macro")


#close excel
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($excel)
Start-Sleep 1
'Excel processes: {0}' -f @(Get-Process excel -ea 0).Count
Remove-Variable $excel

exit $LASTEXITCODE

The excel file still comes up as a process in task manager and is taking up memory space.

How do I have powershell completely close the instance of the excel application that opens through the macro?

Any help greatly appreciated!

1
2
3
4
5
6
7
8
9
10

$object=new-object -comobject V82.ComConnector
try
{
    $connection=$object.connect("Srvr=srv;Ref=ut;Usr=user;Pwd=123")
}
catch
{
    sleep -Seconds 5
    $connection=$object.connect("Srvr=srv;Ref=ut;Usr=user;Pwd=123")
}

1

[System.Runtime.Interopservices.Marshal]::ReleaseComObject($connection)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

$object=new-object -comobject V82.ComConnector
try
{
    $connection=$object.connect("Srvr=srv;Ref=ut;Usr=user;Pwd=123")
}
catch
{
    sleep -Seconds 5
    $connection=$object.connect("Srvr=srv;Ref=ut;Usr=user;Pwd=123"
}
$zapros=[System.__comObject].InvokeMember("NewObject",[System.reflection.bindingFlags]::invokemethod,$null,$connection,"Запрос")                  
[system.__comObject].InvokeMember("Text",[System.reflection.bindingFlags]::setproperty,$null,$zapros,$zapros_1)
[system.__comObject].InvokeMember("УстановитьПараметр",[System.reflection.bindingFlags]::invokemethod,$null,$zapros,("Дата",$curDate))
[system.__comObject].InvokeMember("УстановитьПараметр",[System.reflection.bindingFlags]::invokemethod,$null,$zapros,("Дата2",$nextDate))
$res=[system.__comObject].invokeMember("Выполнить",[System.reflection.bindingFlags]::invokemethod,$null,$zapros,$null)
$vigruzka=[system.__comObject].invokeMember("Выгрузить",[System.reflection.bindingFlags]::invokemethod,$null,$res,$null)

1
2
3
4
5
6
7

[System.Runtime.Interopservices.Marshal]::ReleaseComObject($vigruzka)
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($EVOTORvigruzka)
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($zapros) 
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($res)
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($EVOTORzapros)   
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($EVOTORres)              
[System.Runtime.Interopservices.Marshal]::ReleaseComObject($connection)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

PS C:Usersbafomet> $vigruzka
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject
System.__ComObject

1
2
3
4

foreach($element in $vigruzka)
{
 
}

0

Powershell работа с Excel на примере служб windows

Для работы с Excel в среде powershell нужно использовать COM объект.

При выполнении данного командлета произойдет запуск приложения Excel в скрытом состоянии, т.е. у нас будет висеть процесс Excel, но при этом самого приложения как такового мы не увидем. Для того чтобы увидеть работу приложения нужно обратиться к его свойству Visible и установить его в TRUE т.к. по умолчанию стоит FALSE

Далее после того как приложение открылось нужно создать книгу воспользовавшись свойством Workbooks и методом Add().

После создания книги нужно выбрать лист с которым будем работать в данной книге. Для этого воспользуемся свойством Worksheet и методом Item()передав ему номер листа с которым будем работать.

Зададим имя нашему листу для этого используем свойство Name и присвоим ему значение нового имени листа.

Так как Excel это таблица и мы работаем с ее ячейками то используем свойство Cells и метод Item() для указания с какими ячейками данного листа мы будем работать. Отсчет начинается с 1.

В данном примере мы устанавливаем названия наших колонок которые в дальнейшем будем заполнять. Первый аргумент это номер строки с которой работаем, второй аргумент это ячейка в таблице. Перед тем как перебирать массив с данными и записывать все в таблицу нам нужна вспомогательная переменная которая будет ссылаться на начальную строку в таблице с дальнейшим увеличением в цикле для перехода на новую строку.

После того как книга заполнена нужными данными ее необходимо сохранить. Для этого используем метод Saveas() и передаем ему путь и имя файла для сохранения.

После этого закрываем саму книгу воспользовавшить методом Close().

После того как закрыли книгу можно завершать работу приложения Excel использую метод Quit(). Тем самым освободив память в системе.

У данного способа есть существенный недостаток это очень медленная работа экспорта данных в таблицу Excel, но за то можно создавать красивые отформатированные таблицы для конечного пользователя. Здесь представлен полный скрипт, который получает список всех служб на вашем компьютере и записывает их в ячейки таблицы Excel.

Источник

Excel, save and close after run

how can I save the below script after it has run?

6 Answers 6

This worked for me :

To properly and completely close Excel, you also need to release COM references. In my own testing have found removing the variable for Excel also ensures no remaining references exist which will keep Excel.exe open (like if you are debugging in the ISE).

Without performing the above, if you look in Task Manager, you may see Excel still running. in some cases, many copies.

This has to do with how the COM object is wrapped in a “runtime callable wrapper».

Here is the skeleton code that should be used:

Got it working! — Special thanks to @Matt

Complete script that is working:

As mentioned in MSDN documentation here, the ReleaseComObject call only decrements the reference counter of that COM object by 1. If your scripts has multiple references of the same COM object, It will not release the object.

The documentation recommends using FinalReleaseComObject method to completely release the COM object and close the Excel process once in for all.

Just be sure to call this method only when you are done with the COM reference, as not doing so may lead to bugs which are hard to debug.

Источник

Closing open instances of excel

Is there a line of code I can add to a script to close all open instances of Excel?

The open instances of Excel is preventing my folder cleanup scripts to execute fully.

Fix it Fast: 6 ways LogicMonitor helps you reduce MTTR

This should take you in the right direction. =]

CloseExcel
SUB CloseExcel()
on error resume next
set xl =getobject(,»Excel.Application»)
xl.activeworkbook.saved = true
xl.Quit
set xl = nothing
call CloseExcel
End Sub

This closes all open Excel Workbooks. Hope it helps!

• check 1337 Best Answers
• thumb_up 3072 Helpful Votes

or just like so

Can you please add comments to the code you provided so I can better understand how it works. I’d appreciate it highly

• check 1337 Best Answers
• thumb_up 3072 Helpful Votes

Can you please add comments to the code you provided so I can better understand how it works. I’d appreciate it highly

Nice! Thx Neally!!

The problem with jspr’s link and Neally’s script is that they’re just going to kill any instance of Excel. If there are any open, unsaved workbooks, you’re going to lose all the work since the last save for each workbook. (I believe the default autosave period for Excel is ten minutes, so it may not be that much of a problem, but you’re going to have to deal with recovered files when you reopen Excel.)

I haven’t tried TheEggOnTop’s script, but it appears to be the correct way to go. The only issue I see with it is it’s not PowerShell, it’s either VBScript or VBA. Most VB scripts can be translated into PowerShell though (emphasis on «most»).

• check 1337 Best Answers
• thumb_up 3072 Helpful Votes

The problem with jspr’s link and Neally’s script is that they’re just going to kill any instance of Excel. If there are any open, unsaved workbooks, you’re going to lose all the work since the last save for each workbook. (I believe the default autosave period for Excel is ten minutes, so it may not be that much of a problem, but you’re going to have to deal with recovered files when you reopen Excel.)

I haven’t tried TheEggOnTop’s script, but it appears to be the correct way to go. The only issue I see with it is it’s not PowerShell, it’s either VBScript or VBA. Most VB scripts can be translated into PowerShell though (emphasis on «most»).

I’m sure you can mess around with com objects or try the ‘importExcel’ module.

OP didn’t give too much info or follow up though. so ..

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

Uh-Oh! An end user (and his laptop) fell off an oil rig

Hi, y’all — Chad here. With all the hustle and bustle of life on Spiceworks, you may not know anything about me. That’s hard for me to imagine, because in my head, I’ve built up quite the fantasy world where I’m good-looking, popular, and well-liked. I me.

How do you manage budget for laptop replacement batteries?

Hi, I have three questions:1. An HP article said laptop battery lifespan is about 2-4 years. I wasn’t able to see other data sources. Does it match what you observe in practice? Our PC replacement cycle is about 4-5 years, so I am planning all batteries w.

Snap! — Counterfeit Drives, Disposable Satellite, AI Hands Fixed, Automated CEO

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: March 20, 1909: Edmund Berkeley, founder of the Association of Computing Machinery, is born (Read more HERE.) Bonus Flashback: March 20, 1959: Task force formed to pl.

Nerd Journey # 209 — Meetings with the Chief with Anudeep Parhar (2/2)

Last week we shared the first part of Anudep Parhar’s progression from developer to technology executive (link to the episode is here if you missed it).In part 2 of the story, we hear about a moment of ignition Opens a new window that gave Anudeep the mot.

Источник

Powershell как закрыть excel

Вопрос

the correct way to avoid Excel zombies is to release all ComObjects in the powershell environment / script by invoking:

on each posh variable holding a reference to a COM object, and to do so in «reverse» order (suitably defined).

«Correct» means specifically «leaves no invisible lurking Excel apps behind».

The recipe works for me when I invoke my scripts as (say):

But when I invoke the script as:

and then list posh variables:

posh throws an error when it encounters the first variable that (previously) held a ComObject reference:

I tried rv’ing the posh variables, but when I do so prior to the ReleaseComObject, I no longer have a handle to the Com Object; alternatively when I rv the posh variable after ReleaseComObject, posh throws the same error as above.

How to release both the Com Object and the posh variable in the base posh environment (ie . ./script) while avoiding Excel zombies?

Code excerpts below:

TIA for the help.

FWIW, I’m running Win7 and Office 2010 in a Workstation 8 VM.

Ответы

Keep variables in array wwhen you build them,

$xl=New-Object -Com Excel.Application
$vars_to_remove+=’xl’
. use var
. release objects
# now remove vars
$vars_to_remove | | %