Advertisements

Archive

Archive for the ‘Others’ Category

SSMS Installation Error – This version of SSMS cannot be installed because a xyz version of SSMS 17.0 was detected

September 23, 2017 Leave a comment

 
So, today I tried to install SSMS 17.3 version, and got following error:

This version of ssms cannot be installed because a release candidate version of ssms 17.0 was detected.


 
This is because if you had installed SSMS previously and uninstalled it and because of some files were not cleaned up properly, you will get this kind of message while installing SSMS separately.

 
–> The solution is to remove the previously installed SSMS related files from the respective version folder:

Go to following folder and remove all folders and files: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\
 

Now try installing SSMS again and you won’t get any error !!!


Advertisements
Categories: SQL Server Tags: ,

DACPAC – Could not deploy package, the database platform service with type Sql130DatabaseSchemaProvider is not valid


 
So, today while deploying a DACPAC file by using SqlPackage.exe utility I faced an error:

*** Could not deploy package
Internal error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql130DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.

For few minutes I was wondering why this error was coming, but when I saw the version number in above error message it became clear. The version number 130 highlighted above belongs to SQL Server 2016, and the database where I need to deploy DACPAC was SQL Server 2012. So, its clear that the DACPAC was built in Visual Studio with SQL Server 2016 setting.

So I went back to Visual Studio – Project Settings and changed the version to SQL Server 2012, and re-build the Project, and got the correct DACPAC file.


Categories: Uncategorized

Powershell error – Import-Module : File AzureRM.psm1 cannot be loaded because running scripts is disabled on this system


 
After installing the AzureRM module, I tried to import it, but it gave me an error:

Import-Module : File C:\Program Files\WindowsPowerShell\Modules\AzureRM\4.0.2\AzureRM.psm1 cannot
be loaded because running scripts is disabled on this system. For more information, see
about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ Import-Module AzureRM
+ ~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [Import-Module], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.PowerShell.Commands.ImportModuleComman
d

This error means that the AzureRM module downloaded from internet must be signed by a trusted publisher before they can be run.
 

–> Now to fix it you need to change the execution policy by this simple command:

PS c:\> Set-ExecutionPolicy RemoteSigned

If you are on PowerShell Window then it will throw a popup to confirm to change the Execution policy, you can choose “Yes”:

Now try running again the import command, it will run:

PS c:\> Import-Module AzureRM


Powershell error – The term ‘Login-AzureRmAccount’ is not recognized as the name of a cmdlet, function, script file, or operable program


 
If you are new to PowerShell like me then you would have encountered this ans similar errors.

Recently while executing one PowerShell script to connect to Azure Resource Manager I faced following error:

XyzPSScript.ps1 : The term ‘Login-AzureRmAccount’ 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.
+ CategoryInfo : ObjectNotFound: (Login-AzureRmAccount:String) [XyzPSScript.ps1], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,XyzPSScript.ps1

This error means that you do not have Azure PowerShell module installed on your system or server.
 

–> So, let’s see how to install the dependent modules.
 

1. Connect to PowerShell from command prompt (CMD) in Admin mode:

c:\> powershell.exe

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

 

2. Check the version of PowerShell:

PS c:\> $PSVersionTable.PSVersion

Major Minor Build Revision
—– —– —– ——–
5 1 14409 1005

 

3. Run the below command to check if you have PowerShellGet installed on your system:

PS c:\> Get-Module PowerShellGet -list | Select-Object Name,Version,Path

Name Version Path
—- ——- —-
PowerShellGet 1.0.0.1 C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PowerShellGet.psd1

 

4. Now we can easily install the Azure PowerShell from the PowerShell Gallery by runnign following command:

PS C:\> Install-Module AzureRM

NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘2.8.5.201’ or newer to interact
with NuGet-based repositories. The NuGet provider must be available in
‘C:\Program Files\PackageManagement\ProviderAssemblies’ or
‘C:\Users\essensed\AppData\Local\PackageManagement\ProviderAssemblies’. You can
also install the NuGet provider by running ‘Install-PackageProvider -Name
NuGet -MinimumVersion 2.8.5.201 -Force’. Do you want PowerShellGet to install
and import the NuGet provider now?
[Y] Yes [N] No [S] Suspend [?] Help (default is “Y”): Y

Untrusted repository
You are installing the modules from an untrusted repository. If you trust this
repository, change its InstallationPolicy value by running the Set-PSRepository
cmdlet. Are you sure you want to install the modules from ‘PSGallery’?
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is “N”):Y

On every prompt type ‘Y’ to proceed ahead.

While Installing the module you will see this screen:

5. Finally you just need to import the AzureRM module:

PS C:\> Import-Module AzureRM

This import command will not give any output, and you may proceed with the PS prompt.


Error – The following feature couldn’t be installed – .NET Framework 3.5


 
I got error this message on a pop window while running a new application after installing it on my Windows Server 2012 Azure VM.


 

This feature can be installed from the “Windows Server Manager”, you will see its icon on the task bar besides the Start button, as shown below. Or you can directly type “servermanager” on CMD or Run prompt.

Click on the “Add Roles and Features”


 

A new window will open up “Add Roles and Features Wizard”, click Next.
On “Installation Type”, click Next again.
On “Server Selection”, select the current/default server and click Next.
On “Server Roles” click Next.
Now on Features select the “.NET Framework 3.5 Features” option, an click Next.
On Confirmation page you will see “Specify an alternate source path” link, click on that link, and a new window opens up, as shown below:


 

Here on the highlighted text box you need to specify the “side-by-side (SxS) folder” path of the OS installation media. So, if you have an ISO file you can mount it or if you have a dump of the setup, provide the path form the respective location. Finally click on Install button.
 

If you are on an Azure Windows VM, you will not have access to the ISO or installation media. In this case you can simply run a Windows Update from Control Panel–> System and Security –> Windows Update.


Categories: MS.net, Windows