none
errors perhaps R, perhaps Python on install RRS feed

  • Question

  • Hi I installed developer 2017 and got these errors in the rsetup.log

    2019-06-02T20:06:15 ERROR C:\Users\myfirstnamelastinitial\AppData\Local\Temp\tmp3CEF.tmp: Unable to save temp file [The operation has timed out.]

    2019-06-02T20:06:15 INFO Exiting with code 851502

    and I see these errors in  what appears to be a summary log...

    Setup completed with required actions for features.

    Troubleshooting information for those features:
      Next step for sql_inst_mpy:    Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Next step for sql_shared_mpy:  Use the following information to resolve the error, uninstall this feature, and then run the setup process again.

    Feature:                       Python
      Status:                        Failed
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
      Component error code:          0x80131500
      Error description:             Python Install failed. Check /logfile "C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190602_144939\RSetup.log" for details.
      Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0x40E21AA9%400xC68B78F0&EvtType=0x40E21AA9%400xC68B78F0

    does anybody know why this happens and if its really as simple as uninstalling and reinstalling just the python feature?

    Sunday, June 2, 2019 9:31 PM

Answers

  • Hi db042190,

     

    The worst situation: You need to uninstall the  whole SQL Server and try to reinstall the SQL Server by admin account.

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Marked as answer by db042190 Friday, June 21, 2019 6:45 PM
    Thursday, June 20, 2019 6:41 AM
  • Yes, you can install a new instance, but keep in mind use admin account to install it

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Marked as answer by db042190 Friday, June 21, 2019 6:46 PM
    Friday, June 21, 2019 1:48 AM

All replies

  • Hi db042190,

     

    >>2019-06-02T20:06:15 ERROR C:\Users\myfirstnamelastinitial\AppData\Local\Temp\tmp3CEF.tmp: Unable to save temp file [The operation has timed out.]

     

    This problem occurs at the process of installing R Service. You can try to unselect R Service when installing SQL Server and then install R Service with offline installation package. Please refer to this document: https://docs.microsoft.com/en-us/sql/advanced-analytics/install/sql-ml-component-install-without-internet-access?view=sql-server-2017

     

    Hope this could help you .

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Monday, June 3, 2019 1:27 AM
  • thx is there a way to determine if they actually got installed?  some of the tools stuff installed in spite of errors so maybe that occurred here too. 

    I know sql server 2017 got installed in spite of the error.  so i'd rather just deal with an incremental type update instead of (as your link suggests) dealing with the original install media too. 

    I see what looks like 4 items  related to python in my w10 app list (idle (python 3.7 64 bit), python 3.7 module docs, python 3.7 manuals and python 3.7.  

    and I thought I saw an R server somewhere but don't recall where.

    Monday, June 3, 2019 3:06 PM
  • I made a python app without changing anything so maybe the errors didn't really stop python from adding.  or maybe this isn't really a valid way of testing whether python got installed with sql server 2017, perhaps its just a way of seeing whether it was added into vs?


    Monday, June 3, 2019 7:44 PM
  • What may not work is running Python script from SQL Server with sp_execute_external_script.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Monday, June 3, 2019 9:55 PM
  • thx, i'll give that a whirl and post results back here.
    Tuesday, June 4, 2019 3:05 PM
  • from what I read and ran I would have expected something different than what what you see below.  Going to look up this error.

    Tuesday, June 4, 2019 4:06 PM
  • ok, this worked after cycling the engine service.  so either the error msgs were bogus on sql install or my vs actions accomplished the same thing as installing with sql? 

    I'll look to see if R can be reached.  If that's even a thing.


    • Edited by db042190 Tuesday, June 4, 2019 4:25 PM clarity
    Tuesday, June 4, 2019 4:24 PM
  • not so good for R (which I dont recall having a vs extension).

    Tuesday, June 4, 2019 4:51 PM
  • I see these items but am suspicious of the date modified next to the R app.  The pc was only purchased a couple of weeks ago.  when I run R as admin I see a flash and nothing.  i'm surprised not to see my instance name in these folder names.   and very curious what pbi means.  I see my db in a data folder at C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\MSSQL\DATA.   From Dedmond's post and link, it sounds like there is no way to add these things to an existing instance.  That you have to download the cab files and try a reinstall.  Are you kidding? 


    • Edited by db042190 Tuesday, June 4, 2019 6:27 PM more info
    Tuesday, June 4, 2019 5:18 PM
  • this guy is suggesting R stuff can be removed from add/remove programs (apps and features in settings) before attempting a repair.  Is that true?

    https://mostafaelmasry.com/2012/02/08/how-to-remove-instance-or-feature-from-sql-server/ 

    • Edited by db042190 Tuesday, June 4, 2019 6:43 PM forgot link
    Tuesday, June 4, 2019 6:43 PM
  • a repair showed red on python and r.  green on everything else.

    I didn't think to snag the repair details so I may try a repair again. 

    but now with a warning I reach r as shown below.  and I still reach python with no warning.  the file mod dates on the r app at C:\Program Files\Microsoft SQL Server\140\R_SERVER\bin and also in the x64 folder beneath that still show march.  

    is it possible that a repair would use the cab files (if I download them to the correct place)  referenced by dedmond's link and fix the problem?  

     

    Tuesday, June 4, 2019 8:18 PM
  • rerunning repair, even before reds and greens show, I am directed to a log file where this error shows...

    2019-06-04T20:27:07 ERROR Error renaming source directory: Access to the path 'C:\Program Files\Microsoft SQL Server\140\R_SERVER\' is denied.
    2019-06-04T20:27:07 INFO Exiting with code 5

    waiting for repair to finish before looking to see if I can still connect etc.

    Tuesday, June 4, 2019 8:34 PM
  • these are what are probably summary errors from the re run of repair, it talks about removing features

    but nobody knows how to do that. 

    Feature:                       Python
      Status:                        Failed
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component error code:          0x84B40002
      Error description:             The SQL Server feature 'sql_inst_mpy' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
      Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.2014.14&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
      Feature:                       R
      Status:                        Failed
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                R
      Component error code:          0x80131500
      Error description:             R Repair failed. Check /logfile "C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190604_161952\RSetup.log" for details.
      Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.2014.14&EvtType=0x2C9553C5%400xC68B78F0&EvtType=0x2C9553C5%400xC68B78F0
    Feature:                       R
      Status:                        Failed
      Reason for failure:            An error occurred during the setup process of the feature.
      Next Step:                     Use the following information to resolve the error, and then try the setup process again.
      Component name:                R
      Component error code:          0x80131500
      Error description:             R Repair failed. Check /logfile "C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190604_161952\RSetup.log" for details.
      Error help link:               https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.2014.14&EvtType=0x2FEC6C05%400xC68B78F0&EvtType=0x2FEC6C05%400xC68B78F0

    Tuesday, June 4, 2019 8:57 PM
  • Hi db042190,

     

    Would you please show more details in C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190604_161952\RSetup.log?

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, June 7, 2019 3:28 AM
  • sure, that file is 18 meg.  what are some easy options for sharing it with you?
    Friday, June 7, 2019 6:43 PM
  • Hi db042190,

     

    Would you please show us the part with the error message?

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Tuesday, June 11, 2019 9:47 AM
  • 2019-06-04T20:27:07 INFO Command invoked: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\SQL2017\x64\RSetup.exe /install /component SRO /version 3.3.3.1400 /language 1033 /destdir C:\Program Files\Microsoft SQL Server\140\R_SERVER /logfile C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20190604_161952\RSetup.log
    2019-06-04T20:27:07 INFO RSetup.exe version: 9.2.0.56
    2019-06-04T20:27:07 INFO Reading registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\130\Bootstrap\Setup\R_SERV_CACHE
    2019-06-04T20:27:07 INFO Registry value:
    2019-06-04T20:27:07 INFO Reading registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\130\Bootstrap\BootstrapDir
    2019-06-04T20:27:07 INFO Registry value:
    2019-06-04T20:27:07 INFO Using default cache directory: C:\Users\stant\AppData\Local\Temp\
    2019-06-04T20:27:07 INFO Backing up source directory: C:\Program Files\Microsoft SQL Server\140\R_SERVER\ => C:\Program Files\Microsoft SQL Server\140\R_SERVER_a1908c8f-16ae-4eb6-ae3a-95f814c229d9
    2019-06-04T20:27:07 ERROR Error renaming source directory: Access to the path 'C:\Program Files\Microsoft SQL Server\140\R_SERVER\' is denied.
    2019-06-04T20:27:07 INFO Exiting with code 5


    • Edited by db042190 Tuesday, June 11, 2019 1:08 PM more complete
    Tuesday, June 11, 2019 1:06 PM
  • Hi db042190,

     

    Sorry for late response.

     

    >>ERROR Error renaming source directory: Access to the path 'C:\Program Files\Microsoft SQL Server\140\R_SERVER\' is denied.

     

    Is there a registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\36832937063F44041B69EA54696C5005 on your machine? Can you remove that registry key (and all its children) and retry? Make a backup before modifying the registry.

     

    Hope this could help you .

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Thursday, June 13, 2019 9:30 AM
  • thx, make a backup of what?  the registry?
    Thursday, June 13, 2019 12:45 PM
  • the best I can tell there is no such registry key.  I both eyeballed it and did a "find" on 36832937063F44041B69EA54696C5005 in regedit.
    Thursday, June 13, 2019 2:02 PM
  • Would you please tell me if you install it by admin account?

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    Friday, June 14, 2019 10:07 AM
  • I probably didn't run the original install as admin.  But I just now ran the repair as admin and got this instead way at the bottom of the rsetup log.  The repair popup reported that R repair failed and led me to c:\program files\...20190614_093741\rsetup.log which this came from...notice there is no path access denial in this one...

    2019-06-14T14:13:00 INFO Extracting C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\o16n\RServe\bin\x64\Rserv.cfg
    2019-06-14T14:13:00 INFO Extracting C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\o16n\RServe\R\dummy
    2019-06-14T14:13:00 INFO Extracting C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\o16n\RServe\RScripts\source.R
    2019-06-14T14:13:00 INFO Running command: C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\\library\RevoScaleR\rxLibs\x64\registerRext.exe /uninstall /sqlbinnpath:"C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\\..\MSSQL\Binn" /userpoolsize:0 /instance:"MYCOMPANY"
    2019-06-14T14:13:03 WARN C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\\library\RevoScaleR\rxLibs\x64\registerRext.exe: Command returned exit code -1
    2019-06-14T14:13:03 INFO Running command: C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\\library\RevoScaleR\rxLibs\x64\registerRext.exe /install /sqlbinnpath:"C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\\..\MSSQL\Binn" /userpoolsize:0 /instance:"MYCOMPANY"
    2019-06-14T14:13:03 WARN C:\Program Files\Microsoft SQL Server\MSSQL14.PBI\R_SERVICES\\library\RevoScaleR\rxLibs\x64\registerRext.exe: Command returned exit code 0
    2019-06-14T14:13:03 INFO Exiting with code 5


    • Edited by db042190 Friday, June 14, 2019 3:28 PM reposted file content as repair wasnt done yet
    Friday, June 14, 2019 3:01 PM
  • Hi db042190,

     

    The worst situation: You need to uninstall the  whole SQL Server and try to reinstall the SQL Server by admin account.

     

    Best regards,

    Dedmon Dai


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Marked as answer by db042190 Friday, June 21, 2019 6:45 PM
    Thursday, June 20, 2019 6:41 AM
  • or perhaps install a new instance? using same installation media at C:\program files x(86)\SQLServer2017Media\Developer_ENU ?
    • Edited by db042190 Thursday, June 20, 2019 7:48 PM more info required
    • Marked as answer by db042190 Friday, June 21, 2019 6:45 PM
    • Unmarked as answer by db042190 Friday, June 21, 2019 6:46 PM
    Thursday, June 20, 2019 7:26 PM
  • Yes, you can install a new instance, but keep in mind use admin account to install it

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com

    • Marked as answer by db042190 Friday, June 21, 2019 6:46 PM
    Friday, June 21, 2019 1:48 AM
  • that seems to have worked, thx Dedmon. 

    R and Python showed green on install.  And as before I can reach both from sql/ssms.

    Friday, June 21, 2019 6:36 PM