SQLPSX Work Item Rss Feed

Edited Unassigned: Get-SqlServer issues [8]

zierde01 — Thu, 02 May 2013 19:51:32 GMT

I'm new to SQLPSX, but in trying to follow an example on someones site:
```
Import-Module sqlmaint
$SQLServer = "localhost"
$SQLDBName = "work"
$SQLQuery = "SELECT * FROM dbo.server"

$database = Get-SqlDatabase $sqlserver $SQLDBName
```

I get the error:
Exception calling "Contains" with "1" argument(s): "Failed to connect to server server='localhost';Trusted_Connection=true;multipleactiveresultsets=false."
At C:\Users\ZierdE1\Documents\WindowsPowerShell\Modules\sqlserver\SQLServer.psm1:164 char:37
+ { if ($server.Databases.Contains <<<< ("$dbname") -and $server.Databases[$dbname].IsAccessible)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException

I've tracked this down to the Get-SqlServer function. The current function performs the following:
$server = new-object ("Microsoft.SqlServer.Management.Smo.Server") $con

I believe the issue is with the $con variable. $ con is set in the Get-SQLConnection function, where it does:
```
$con = new-object ("Microsoft.SqlServer.Management.Common.ServerConnection") $sqlserver
$con.Connect()

```
The code works if I change the Get-SqlServer function code from:
$server = new-object ("Microsoft.SqlServer.Management.Smo.Server") $con

to:

$server = new-object ("Microsoft.SqlServer.Management.Smo.Server") $sqlserver

So if I give it a server name, instead of a Connection.

according to get-host|Select-Object version I am running version 3.6.0.8

I'm including a screen shot of both the failure and success in a simplified query...sorry that it looks distorted.

Created Unassigned: Get-SqlConnection issues [8]

zierde01 — Thu, 02 May 2013 19:50:51 GMT

Edited Issue: Unapproved Verbs Used - should be fixed [7]

tfl — Mon, 25 Feb 2013 10:21:39 GMT

There are two cmdlets/functiosn with unapproved verb names:

Decode-SQLName
Encode-SQLName

To see this, after loading SQLPS, do this from a PowerShell prompt:

Import-Modue SQLPS -Verbose -Force

IMHO, community modules, like this one, really need to follow things like approved verbs and not expect users to have to 'ignore errors'. The commuynity can, and should, do better.

Created Issue: Unapproved Verbs Used - should be fixed [7]

tfl — Mon, 25 Feb 2013 10:16:01 GMT

There are two cmdlets/functiosn with unapproved verb names:

Decode-SQLName
Encode-SQLName

To see this, after loading SQLPS, do this from a PowerShell prompt:

Import-Modue SQLPS -Verbose -Force

Created Issue: SQLPSX error, add-Member : Cannot add a member [6]

cmille19 — Mon, 11 Feb 2013 16:02:09 GMT

See [http://social.technet.microsoft.com/Forums/en/sqlkjmanageability/thread/be63367b-306e-4ab3-a48b-b0bb8be745ee](http://social.technet.microsoft.com/Forums/en/sqlkjmanageability/thread/be63367b-306e-4ab3-a48b-b0bb8be745ee)

Need to add a type file to module in order to avoid add-member issue.

Created Issue: Win7 x64 + SQL2012 rtm load errors for DTS and RMO [5]

ALZDBA — Thu, 06 Dec 2012 09:15:45 GMT

I have this fresh install of Win7 x64 with only a client install ( except the add-in s ) of SQL2012.
(My PowerGUI has been configured to actually use Powershell V3.0)

Now, when I load SQLPSx it generates following errors:

add-type : Could not load file or assembly 'Microsoft.SqlServer.Rmo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The s
ystem cannot find the file specified.
At C:\Users\ADM-B0729\Documents\WindowsPowerShell\Modules\Repl\Repl.psm1:17 char:8
+ catch {add-type -AssemblyName "Microsoft.SqlServer.Rmo"}
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Add-Type], FileNotFoundException
+ FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerShell.Commands.AddTypeCommand

No Oracle found
Loading SQLPSX Module - SQLmaint
Loading SQLPSX Module - SQLServer
Loading SQLPSX Module - Agent
Loading SQLPSX Module - Repl
Loading SQLPSX Module - SSIS
add-type : Cannot add type. The assembly 'Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' could not be found.
At C:\Users\ADM-B0729\Documents\WindowsPowerShell\Modules\SSIS\SSIS.psm1:21 char:5
+ add-type -AssemblyName "Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0, Cu ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Microsoft.SqlSe...9845dcd8080cc91:String) [Add-Type], Exception
+ FullyQualifiedErrorId : ASSEMBLY_NOT_FOUND,Microsoft.PowerShell.Commands.AddTypeCommand

add-type : Cannot add type. One or more required assemblies are missing.
At C:\Users\ADM-B0729\Documents\WindowsPowerShell\Modules\SSIS\SSIS.psm1:21 char:5
+ add-type -AssemblyName "Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0, Cu ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Add-Type], InvalidOperationException
+ FullyQualifiedErrorId : ASSEMBLY_LOAD_ERRORS,Microsoft.PowerShell.Commands.AddTypeCommand

Loading SQLPSX Module - Showmbrs
Loading SQLPSX Module - SQLParser
Loading SQLPSX Module - adolib
Loading SQLPSX Modules is Done!

I altered following SQLPSx components to be able to get the load done without errors:

I've altered the repl.psm1 so it uses the 11.0 types

try {add-type -AssemblyName "Microsoft.SqlServer.ConnectionInfo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" -EA Stop}
catch {add-type -AssemblyName "Microsoft.SqlServer.ConnectionInfo"}
try {add-type -AssemblyName "Microsoft.SqlServer.Rmo, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" -EA Stop}
catch {add-type -AssemblyName "Microsoft.SqlServer.Rmo"}

For the DTS stuff I altered the SSIS.psm1 so it uses:

if ( $Args[0] -eq 2005 )
{
add-type -AssemblyName "Microsoft.SqlServer.ManagedDTS, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"
#add-type -Path "C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll"
}
elseif ( $Args[0] -eq 2008 )
{
add-type -AssemblyName "Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"
#add-type -Path "C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll"
}
else
{
add-type -AssemblyName "Microsoft.SqlServer.ManagedDTS, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"
#add-type -Path "C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll"
}

Now SQLPSx doesn't show errors at load time.

I hope that was all it needed.

Created Issue: Invoke-SqlRestore should kill connections to the database [4]

dholmes — Mon, 12 Nov 2012 16:51:58 GMT

During the execution of Invoke-SqlRestore, it should kill any connections to that database so the restore will finish. A parameter to the function could also be made or just use the exising '-force' parameter.

I added the following lines to SQLServer.psm1 at line 2757 and it accomplished the goal.

switch ($sqlserver.GetType().Name)
{
'String' { $server = Get-SqlServer $sqlserver }
'Server' { $server = $sqlserver }
default { throw 'Invoke-SqlRestore:Param sqlserver must be a String or Server object.' }
}
#new code starts here
if ($force)
{
Write-Verbose "killing all processes for this database $($server.Name) $dbname"
$server.KillAllProcesses($dbname)
}
#new code ends here
Write-Verbose "Invoke-SqlRestore $($server.Name) $dbname"

please consider this for the next release - if there is one.

Created Issue: Property visibilty not found on W7 64-bit & PowerShell V3 in sqlise connect dialog [3]

Bernd_K — Sun, 04 Nov 2012 19:37:29 GMT

In SQLISE when I open the Connect dialog on Windows 7 64-bit with PowerShell V3, I get Property "Visibility" not found. As workaround I did the following modification to Get-ConnectionInfo.ps1:
-On_SelectionChanged {$userName = $window | Get-ChildControl userName
$password = $window | Get-ChildControl Password
if ($userName.Visibility) { ## added
if ($this.SelectedIndex -eq 1)
{
$userName.Visibility = 'Visible'; $password.Visibility = 'Visible'
}
else
{
$userName.Visibility = 'Hidden'; $password.Visibility = 'Hidden'
}
} ## added
}

Commented Issue: Import-Module PerfCounters failes in Windows 8 with SQL Server 2012 [1]

LaertePjunior — Mon, 08 Oct 2012 22:35:26 GMT

Hi guys,

I've created a fresh install of Windows 8 and SQL Server 2012 and tried to install the SQLPSX modules version 2.3.2.1. When PerfCounters module is installed I receive the following error:

At C:\Users\James\Documents\WindowsPowerShell\Modules\PerfCounters\PerfCounters.psm1:96 char:5
+ continue
+ ~~~~~~~~
Control cannot leave a finally block.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : ControlLeavingFinally

import-module : The specified module 'PerfCounters' was not loaded because no valid module file was found in any module directory.
At line:1 char:1
+ import-module PerfCounters
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: (PerfCounters:String) [Import-Module], FileNotFoundException
+ FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

I have a work around on my machine which is to remove the offending try finally block from the Get-ProcessPerfcounter function:

try {
Invoke-Sqlcmd2 -ServerInstance $ServerName -Database $DatabaseName -UserName $UserName -Password $Password -Query $CommandInsertSQL
} finally {
continue
}
leaving the Invoke-Sqlcmd2 intact as shown below:

Invoke-Sqlcmd2 -ServerInstance $ServerName -Database $DatabaseName -UserName $UserName -Password $Password -Query $CommandInsertSQL

I'm then able to import the modules successfully.

If you need any further information please don't hesitate to ask.

Thanks,

James
Comments: Hi James, I got this error and I already solved.It will be in the next version, but if you want you can contact me at laertesqldba@outlook.com and I will send to you a new release to work with Posh 3.0

Created Issue: Overwriting backups breaking transaction log chain [2]

josepmv — Wed, 26 Sep 2012 10:38:02 GMT

I've had an issue with SQLMaint module when with -Action "BKP_LOG" but it could have happened with other backup options. I do a transaction log backup every 15 minutes. When testing the restore plan I got an error because I was breaking the restore chain.
I found that the problem was that the backup made in "pm" was overwritten by the one run in "am" because it happened at the very same time, speaking in minuts and seconds, just with a delay of 12 hours.

I replace all "hh" for "HH" to be 24hours, for example:
Get-Date -Format "yyyy/MM/dd hh:mm:ss" for Get-Date -Format "yyyy/MM/dd HH:mm:ss". I attach the file with the modification that I've done.

Thank you!

Created Issue: Import-Module PerfCounters failes in Windows 8 with SQL Server 2012 [1]

JimmyBoo — Sat, 08 Sep 2012 07:08:58 GMT

Created Issue: Set-SqlObjectPermission problem [22978]

cmille19 — Mon, 02 Jul 2012 21:10:11 GMT

BTW!!!!

($_.Parent.Roles | where {$_.name -eq $name}))

SHOULD BE

($smo.Parent.Roles | where {$_.name -eq $name}))

Created Issue: Set-SqlObjectPermission problem [22977]

cmille19 — Mon, 02 Jul 2012 21:09:54 GMT

in the sqlserver module

definition of function Set-SqlObjectPermission

with on line

"Write-Verbose "Set-SqlObjectPermission $($smo.Name) $permission $name $action""

when i mark it as a comment, starting with #

this function would be fine...

Created Issue: Errors importing SQLMaint and SQLServer [21876]

MikeShepard — Tue, 06 Dec 2011 03:47:11 GMT

SQLServer module shows up in get-module as loaded, though (SQLMaint does not)

PS C:\Users\Mike #[SQL]--- #[Oracle]--- > import-module sqlmaint
Import-Module : Object reference not set to an instance of an object.
At line:1 char:1
+ import-module sqlmaint
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.PowerShell.Commands.ImportModuleCommand

Created Issue: Missing SQLEnum Add-Type [21303]

cmille19 — Fri, 05 Aug 2011 15:35:48 GMT

Need to add this to sqlserver.psm1:

add-type -AssemblyName "Microsoft.SqlServer.SqlEnum, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"

Commented Issue: Invoke-Sql closes connection before executing query [21191]

MikeShepard — Mon, 01 Aug 2011 02:21:07 GMT

When using the Invoke-Sql function in an adhoc manner (i.e. specifying -Server but not providing a connection via the -Connection parameter), the function closes the connection before firing the .ExecuteNonQuery command:

$cmd=new-sqlcommand @PSBoundParameters

#if it was an ad hoc connection, close it
if ($server){
$cmd.connection.close()
}

return $cmd.ExecuteNonQuery()

This causes the function to fail with the following error:

Exception calling "ExecuteNonQuery" with "0" argument(s): "ExecuteNonQuery requires an open and available Connection. The connection's current state is closed."
Comments: ** Comment from web user: MikeShepard **

Sorry about that. This was fixed in "Change Set 59024". We're working on a release (which includes a major reworking of the adolib module).

For what it's worth, if you look at the changeset I mentioned it matches your fix almost exactly (I didn't include the comments with your initials :-))

Thanks for taking the time to post this, though. We appreciate people using the code and looking at how it works.

Mike

Commented Issue: Invoke-Sql closes connection before executing query [21191]

yardbirdsax — Mon, 18 Jul 2011 19:41:29 GMT

Here's a fix for the bug that I tested and it appears to resolve the issue.

Thanks,
Josh

Created Issue: Invoke-Sql closes connection before executing query [21191]

yardbirdsax — Mon, 18 Jul 2011 19:14:05 GMT

Commented Issue: Set-SQLObjectPermission issue [20751]

MikeShepard — Fri, 08 Jul 2011 03:09:19 GMT

I was trying to use Set-SQLObjectPermission from SQLPSX v2.3.2.1 to grant Select on a view to a user, and I got a really weird result.

Command Line:
$view = Get-SQLView -database (get-sqldatabase "dbserver01,1433" db_name) view_myview
set-sqlobjectpermission -smo $view -permission select -name db_name_view_user -action grant -verbose

Result:
VERBOSE: Set-SqlObjectPermission view_myview select db_name_view_user grant

Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
37 4 976 824 14 1476 AEADISRV
396 57 84560 49780 815 104.18 1688 Agent
215 46 18336 19400 207 1500 AgentService
113 14 1664 1620 40 1524 AppleMobileDeviceS...
67 8 1460 1760 76 0.09 2452 atchk
67 8 1436 1540 35 1548 atchksrv
166 10 16416 11088 53 7148 audiodg
1268 44 20264 18216 143 2728 CcmExec
95 9 1280 1388 38 5420 Com4QLBEx
1447 107 82704 74668 460 651.18 3456 communicator
939 47 39288 25864 386 271.75 9408 communicatork9
31 4 872 384 22 1232 conhost
31 4 868 384 22 2932 conhost
64 8 2476 2568 67 7.69 6076 conhost
60 7 2076 4956 57 8.86 7636 conhost
62 7 2436 1844 58 1.22 7960 conhost
. . . <SNIP> . . .
137 11 3476 19300 67 864 winlogon
350 23 5892 4664 84 1224 wlanext
293 18 10296 6484 90 3948 WmiPrvSE
122 12 5472 3656 41 4264 WmiPrvSE
141 13 10504 10296 61 4336 WmiPrvSE
161 11 3996 8024 38 9120 WmiPrvSE
112 10 2408 5908 33 9824 WmiPrvSE

if(($smo.Parent.Users | where {$_.name -eq $name}) -or ($_.Parent.Roles
| where {$_.name -eq $name}))
{
$perm = new-object ('Microsoft.SqlServer.Management.Smo.ObjectPermi
ssionSet')
$perm.$($permission.ToString()) = $true

switch ($action)
{
'Grant' { $smo.Grant($perm,$name) }
'Deny' { $smo.Deny($perm,$name) }
'Revoke' { $smo.Revoke($perm,$name) }
default { throw 'Set-SqlObjectPermission:Param `$action must b
e Grant, Deny or Revoke.' }
}
}
else
{ throw "Role or User $name does not exist in database $($database.Name
)." }

The result set includes the output of Get-Process roughly where the PROCESS keyword appears in the Get-SQLObjectPermissions function, followed by the remainder of the definition of the function. I've never seen a function do this, but I can consistently reproduce it with this function. I have tried this from two different Powershell shells with two different usernames (both with sysadmin permissions) and get the same result.

I'm not convinced that this is a bug, but I'm not convinced it's not, either. Any thoughts are appreciated.

Jamie
Comments: ** Comment from web user: MikeShepard **

Looked again at the pipeline usage, and determined that the write-verbose belongs inside the process block. I have updated the module.

Commented Issue: Set-SQLObjectPermission issue [20751]

MikeShepard — Fri, 08 Jul 2011 02:51:25 GMT

I hadn't seen this before. You're right. The write-verbose definitely belongs inside a begin block for it to make any sense.