Forum Discussion

JYMSSQL's avatar
JYMSSQL
Copper Contributor
Apr 12, 2020

SQL Server Features Setup Failed

Hi,

 

I'm trying to install SQL Server 2019 Evaluation version and I got some errors especially when the setup try to configure IS Master and IS Worker .

 

I tried the installation many times . Each time I uninstall SQL Server componenet , delete all keys in registery , folders .

 

In the beginning , I got errors in almost whole features and after searching in the internet , I disabled antiviruses and this time only IS Master / IS Worker failed.

 

Please see attached screen shot.

 

Can anyone help please?

 

Thank you in advance,

 

Best regards

  • mcdasa's avatar
    mcdasa
    Brass Contributor
    can we.. transalate french into english?
    it seems that error message related to service….
    • JYMSSQL's avatar
      JYMSSQL
      Copper Contributor

      Hi mcdasa 

       

      Yes for sure . Please see below the translation of the part of error message in french:

       

      The service did not respond quickly enough to the launch or control request

       

      It's Strange when I change the default account service NT SERVICE / ISScaleOutMaster150 by a Système account the both of services run but can't connect to SSIDB catalog.

       

      I think the setup of the Scale Out that failed generete this kind of issues. what do you think about that.

       

      Thank you in advance,

       

      Best ragards

      • mcdasa's avatar
        mcdasa
        Brass Contributor
        https://docs.microsoft.com/en-us/sql/machine-learning/known-issues-for-sql-server-machine-learning-services?view=sql-server-ver15

        in the document above;
        For example, this error might occur if you install the database engine by using the release version, apply a patch to upgrade the database engine, and then add the R Services feature by using the release version.

        To avoid this problem, use a utility such as File Manager to compare the versions of Launchpad.exe with version of SQL binaries, such as sqldk.dll.

        All components should have the same version number. If you upgrade one component, be sure to apply the same upgrade to all other installed components.

        ——
        documents said that different version of components cause similiar problem but i don't think you installed different version of components.

        did you also mean that you change the service account from default to built-in account and it has succeed to run but cannot connect to ssidb catalog?

        I'm not sure what ssidb catalog is, is it SSISDB catalog? You can connect to sql server by windows os admin in single mode(net start mssqlserver /m)

        my apology of no useful answer.

Resources