Powershell problem for noobie

Question

0.00/5 (No votes)

See more:

I downloaded the script below to help me uninstall a problematic SQL Server install, when I try and run it in the PS editor I receive an error

HTML

The term 'Select–String' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that 
the path is correct and try again.
At line:1 char:40

msiinv.exe I downloaded from a link on the same site. Here is the script, I've never used PS before and Google didn't find much of help

HTML

$a = msiinv.exe -s | Select–String "SQL Server" -Context 1,1;
$a = $a -replace "Product code:	","msiexec /x """
$a = $a -replace ">", "rem"
$a = $a -replace "\t", ""
$a = $a -replace "}","}"""
$a | Out-File c:\BatFiles\remove.bat -encoding ascii

What I have tried:

All of the above and lots of swearing

Posted 4-May-16 2:33am

pkfox

Updated 31-May-20 13:51pm

Add a Solution

Comments

Patrice T 4-May-16 9:33am

Ask the author of that script!

3 solutions

Solution 3

Try this, it worked for me:
$a = d:\temp\msiinv.exe -s | Select-String "SQL Server" -Context 0,1
$a = $a -replace "Product code: ","msiexec /x """;
$a = $a -replace ">", "rem";
$a = $a -replace "\t", "";
$a = $a -replace "}","}""";
$a | Out-File d:\temp\remove.bat -encoding ascii;

Posted 31-May-20 13:52pm

Member 10348502

Comments

CHill60 1-Jun-20 4:33am

You are still using Select-String so the error would still occur for the OP - they did not have .NET 4.5 installed.
It's also good to explain what you changed from the original code and why - how does changing the Context help for example

Solution 2

For those with the same issue.

Even with the error message, the remove.bat file is generated.
Open it and replace manually (I used notepad++ to replace the file):

P.E, my file was writing the lines like this:

rem Microsoft SQL Server System CLR Types
  Product code:{C3F6F200-6D7B-4879-B9EE-700C0CE1FCDA}"

On my case I had to replace the Product code: to msiexec /x "
In order to have the code formatted correctly, like this:

rem Microsoft SQL Server System CLR Types
  msiexec /x "{C3F6F200-6D7B-4879-B9EE-700C0CE1FCDA}"

Now that you formatted everything, just run as admin and it should work well.

Posted 29-Apr-20 1:39am

Member 14817027

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2016-05-04T03:54:00

Solution 1

Select-String didn't show up in PowerShell until version 3.0. You're probably running an earlier version of PowerShell.

Update the version of PowerShell on the machine and you should be good to go.

Posted 4-May-16 3:54am

Dave Kreskowiak

Comments

pkfox 4-May-16 10:09am

Ok thanks I'll try updating it

pkfox 4-May-16 10:20am

Hi Dave, I updated to version 4 and still the same error :-(

Dave Kreskowiak 4-May-16 10:41am

Very odd. What comes back if you type $PSVersionTable.PSVersion
at the PowerShell command prompt?

pkfox 4-May-16 10:48am

PS C:\Users\pjk> $PSVersionTable.PSVersion

Major Minor Build Revision
----- ----- ----- --------
4 0 -1 -1

Dave Kreskowiak 4-May-16 10:52am

In that case, I have no idea what's wrong. I would try uninstalling PowerShell and reinstalling it from the 4.0.

pkfox 4-May-16 11:52am

I was thinking that thanks

pkfox 5-May-16 7:49am

Hi Dave, just to update you - the problem was twofold, the first was I didn't have dotnet 4.5 framework installed which is a must for Powershell 4 and the second was a copy paste problem ( I've had this before copying code from the web ) I discovered if I typed and executed the code line by line in the bottom pane of the ps editor it worked , so I then simply typed the whole thing into a script and Bingo - I'm now obsessed with Powershell - thank you for pointing me in the right direction.

Dave Kreskowiak 5-May-16 7:56am

Cool. I have all versions of .NET installed so it didn't even occur to me that could be the problem.

Răzvan Muntea 30-Jul-18 3:37am

.\msiinv.exe -s | Select-String "SQL Server" -Context 0,1 did work as a single command but none of the abouve solutions to generate the .bat worked for me. I have powershell 5

I removed the components manually

milapm 20-Feb-21 14:40pm

Hey man, I have also tried writing the code manually and now I am getting the error 1605(), which simply relates to the file being already uninstalled. I have SQL server 2016 and some of the components are installed twice in different directories. I also have .net4.8 and powershell v5.1. Please help.

milapm 20-Feb-21 14:42pm

Writing the code manually didn't work for me.

Powershell problem for noobie

3 solutions

Solution 1

Solution 3

Solution 2

Add your solution here

Preview 0

Powershell problem for noobie

3 solutions

Solution 1

Solution 3

Solution 2

Add your solution here

Preview 0

Existing Members

...or Join us