Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SqlSetup: Trouble installing the feature RS_SHPWFE #13

Open
andrstor opened this issue Oct 29, 2015 · 7 comments
Open

SqlSetup: Trouble installing the feature RS_SHPWFE #13

andrstor opened this issue Oct 29, 2015 · 7 comments
Labels
enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community.

Comments

@andrstor
Copy link

When i try running xSqlServerSetup with the feature RS_SHPWFE (Reporting
Services Add-in for SharePoint Products) the dsc-configuration throws "Set-Tar
getResouce failed" even though the feature actually gets installed.

It looks like the Test-TargetResource can't handle this feature and will always consider it not installed even though it actually is.

The result of this is that the Set-TargetResource always triggers and always fails, while the setup is actually OK.

@olljanat
Copy link

olljanat commented Nov 7, 2015

Looks hat "Get-TargetResource" cmdlet is implemented the way that it only supports these features:

  • SQLENGINE
  • AS
  • IS
  • SSMS
  • ADV_SSMS

You can use any combination of these features but these must be on that order.
Example:

  • "SQLENGINE,ADV_SSMS"
  • "AS,SSMS"

Other way test will fail and DSC will always try reinstall SQL.

Issue #3 is also connected to this one.

Right solution probably would be create "Get-TargetResource" function which supports all SQL features and these should be handled stored to sorted array which would fix all these issues.

Biggest issue is that detetion method is probably needed to implement for each feature differently.

Another option would be use discovery tool from installation media using command:discovery too
\setup.exe /ACTION=RUNDISCOVERY /QUIET
That stores HTML report of features to C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log

@abouman
Copy link

abouman commented Jan 11, 2016

I am experiencing the same issue while trying to add the following features:
BIDS, CONN, BC (Business Intelligence Design Studio, Client Tools Connectivity, Backwards Compatibility).
I receive the following error, even though the features get installed, same as reported above:
"PowerShell DSC resource MSFT_xSQLServerSetup failed to execute Set-TargetResource functionality with error message: Set-TargetResouce failed"

I am running WMF5.0 on Windows Server 2012R2

Is there a plan to enhance the Set-TargetResource to support the additional features of SQL Server? Is there a suggested work-around?

I am currently using DSC to install SQL Server 2012, Enterprise Edition.

Another issue: In the xSQLServer module, the "Paths" location for database files, log files, TempDB files, and Backup files are included (SQLUserDBDir, SQLUserDBLogDir, SQLTempDBDir, etc), however they are not included for Full Text Data. In my installs, I typically place my Full Text files on a separate drive for performance. I am not able to do this with the module as currently written.
Is there a plan to correct this?

Thank you kindly in advance!
Angela Bouman

@rolflobker
Copy link

Also; looks like it is also failing on SSMS;

I only selected SQLEngine, SSMS as features to install.

The Get-TargetResource function contains;

$Products = Get-WmiObject -Class Win32_Product
switch($SQLVersion)
{
    "10"
    {
        $IdentifyingNumber = "{72AB7E6F-BC24-481E-8C45-1AB5B3DD795D}"
    }
    "11"
    {
        $IdentifyingNumber = "{A7037EB2-F953-4B12-B843-195F4D988DA1}"
    }
    "12"
    {
        $IdentifyingNumber = "{75A54138-3B98-4705-92E4-F619825B121F}"
    }
}

But it seems the SSMS feature for SQL 2014 Express is:

IdentifyingNumber : {839EF29A-3055-43DC-ADCE-8E84893798D5}
Name : SQL Server 2014 Management Studio
Vendor : Microsoft Corporation
Version : 12.1.4100.1
Caption : SQL Server 2014 Management Studio

@rolflobker
Copy link

Also, the install state for the features fails if they are not CAPITALIZED in the configuration;

This works: Features = "SQLENGINE,SSMS"
This fails : Features = "SQLEngine,SSMS"

@abouman
Copy link

abouman commented Jan 28, 2016

Update: For the issue of no support for the following features:
BC, CONN, BIDS and REPLICATION, I have taken the xSQLServerSetup module and created a cSQLServerSetup custom module that allows for the support of these additional features.
Angela Bouman

@rodtobias
Copy link

Hi @abouman,
What did you do to get the BC, CONN, and BIDS working for the xSQLServerSetup module? I understand you created a cSQLServerSetup custom module that allows for the support of these additional features. Is it possible if I see this code as well? Do you have it posted anywhere? Thanks in advance.

@kwirkykat kwirkykat added the enhancement The issue is an enhancement request. label Aug 2, 2016
@kwirkykat kwirkykat added the help wanted The issue is up for grabs for anyone in the community. label Aug 19, 2016
@johlju
Copy link
Member

johlju commented Nov 16, 2016

xSQLServerSetup does not currently support RS_SHP or RS_SHPWFE shared features.
We should make sure to add these. They should also support the 'FilesOnly' support option.

@johlju johlju changed the title Trouble installing the feature RS_SHPWFE SqlSetup: Trouble installing the feature RS_SHPWFE Dec 22, 2017
@SteveL-MSFT SteveL-MSFT added this to Help Wanted in powershell/dscresources May 14, 2019
@SteveL-MSFT SteveL-MSFT removed this from Help Wanted in powershell/dscresources Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request. help wanted The issue is up for grabs for anyone in the community.
Projects
None yet
Development

No branches or pull requests

7 participants