December 4, 2017 at 7:15 am
This is a Win 10 desktop and I've installed the sqlserver module via install-module sqlserver -force. I can import it into a Powershell session and navigate the SQLSERVER: drive but SSMS 17.3 doesn't see the module. Is there something else I need to do.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 7:51 am
[/qu
Not really sure what you mean. You could get to the SQLSERVER drive so something loaded.
When you start Powershell from SSMS and then execute Get-module what is returned?
Sue
December 4, 2017 at 8:14 am
In previous versions of SSMS, right clicking on any item in Object Explorer and Start Powershell would take you to the location in SQLSERVER: in a Powershell session. This isn't working in 17 or at my installation. .
The complete message is:
No SQL Server cmdlets found on this computer.
Get the 'SqlServer' module at https>//powershellgallery.com/packages/SqlServer
Start Powershell without the SQL Server cmdlets?
The SqlServer module is loaded correctly but it seems SSMS 17 can't see it. I know that the Sqlserver module has been segregated from SSMS and is a separate install. The Web page in Powershell Gallery indicates that SSMS 17 should be able to access the module.
Get-Module sqlserver -listavailable returns:
C:\Program Files\WindowsPowerShell\Modules.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 9:07 am
Perhaps silly question, but have you rebooted?
I tried today from 17.3 and got the message that my cmdlets were too old (v20), and updated. SSMS then found them easily, but I wonder if the install didn't work for you with pathing somehow. Did you install the cmdlet before SSMS?
I have found that SSMS is sometimes slightly flaky with the 2015VS shell (v16/17). I've had to repair it a few times. Maybe retry the module install with the allowclobber parameter?
December 4, 2017 at 9:11 am
Did you install the cmdlet before SSMS?
Yes but when I ran into this issue, I installed again with -force. Is -allowclobber more effective.
I also rebooted.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 10:51 am
MG-148046 - Monday, December 4, 2017 8:14 AMIn previous versions of SSMS, right clicking on any item in Object Explorer and Start Powershell would take you to the location in SQLSERVER: in a Powershell session. This isn't working in 17 or at my installation. .
The complete message is:
No SQL Server cmdlets found on this computer.
Get the 'SqlServer' module at https>//powershellgallery.com/packages/SqlServerStart Powershell without the SQL Server cmdlets?
The SqlServer module is loaded correctly but it seems SSMS 17 can't see it. I know that the Sqlserver module has been segregated from SSMS and is a separate install. The Web page in Powershell Gallery indicates that SSMS 17 should be able to access the module.Get-Module sqlserver -listavailable returns:
C:\Program Files\WindowsPowerShell\Modules.
When you go to C:\Program Files\WindowsPowerShell\Modules, are there a couple of sqlps files in that directory? And do you have a SQLServer directory?
In Powershell, try updating everything with: update-module
Sue
December 4, 2017 at 11:23 am
When you go to C:\Program Files\WindowsPowerShell\Modules, are there a couple of sqlps files in that directory? And do you have a SQLServer directory?
In Powershell, try updating everything with: update-module
No sqlps files in the Modules folder. I have a Sqlserver folde rand in it are sub folders for the last 2 releases - 21.0.17178 &21.0.17199.
I did the update-module sqlserver as an admin after checking the folder, restarted SSMS and there is no change in SSMS 17.
My manners are a bit rusty. I hadn't thanked you for responding. I appreciate the help. Thanks
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 11:29 am
I was thinking context. Allowclobber should reinstall for all users, which hopefully sets pathing and other items for you.
December 4, 2017 at 12:00 pm
I tried AllowClobber and no difference in behavior. I am thinking I need to uninstall SSMS 17 and reinstall. It is possible that it didn't install correctly.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 12:29 pm
I uninstalled, reinstall and still no change
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 12:56 pm
I noticed that when I Start Powershell in SSMS 16.x it executes sqltoolsps.exe in the C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn which also contains SQLToolsPS.exe.config but there are no corresponding files in C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn. Can someone check your folders to see if these 2 files are in the ...\140\Binn folder?
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 1:12 pm
SQLtoolsps or just SQLPS?
December 4, 2017 at 1:19 pm
I don't have SQLPS or SQLToolsPS in my 140 folder so both.
MG
"There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
Tony Hoare
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
December 4, 2017 at 1:24 pm
I just have SQLPS.exe (and config)
Viewing 15 posts - 1 through 15 (of 28 total)
You must be logged in to reply to this topic. Login to reply