Код ошибки 851a0043

  • Remove From My Forums

  • Вопрос

  • I’ve installed SQL Server 2014 on a new Windows 7 computer. I am trying to apply the SQLServer2014-KB3158271-x64.exe update which is the «3158271 Cumulative update package 14 (CU14) for SQL Server 2014.» I am getting the error shown in the issue
    title: «The User Data directory in the registry is not valid … Error code: 0x851A0043.» I’ve check the registry setting for DefaultData and it has the correct path: E:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA. The path
    exists, and has the database files. I’ve done this successfully before. The only difference this time is that E: is a network drive.

    Help sorting this out would be greatly appreciated.

    • Изменено

      1 декабря 2019 г. 4:49

Ответы

  • Uri Dimant: version: SQL Server 2014 Express. Build number is confusing. The Studio Help says 12.0.2569.0 which is the build of the CU that supposedly didn’t take, but the version on the server instance name is 12.0.2000, which is the base installed version.

    What you see in SQL Server Management Studio is the version of SSMS, and not the version of SQL Server. Those two are not the same. (And these days SSMS is a separate download. I would recommend that you get SSMS 17.9.1 from this

    link. Later versions are not good for Windows 10.)

    As to locations, I have some more confusion. Right-clicking on the server instance > Properties > Database Settings shows Data, Log and Backup as E:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA, which is what I want. However,
    running

    SELECT name, physical_name AS current_file_location FROM sys.master_files

    Shows C:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA for everything. Huh?

    The SELECT command shows you the location for current databases. The registry setting is default setting for new databases.

    Erland Sommarskog: A fairly old post, https://www.brentozar.com/archive/2012/01/sql-server-databases-on-network-shares-nas/, indicates that network drives can store database files. That’s one reason I’m trying to set this up.The main reason is that I’ve
    found system administrators often set up their database servers as a virtual machine for the ability to quickly restore systems in the event of problems.

    Yes, VMs are very powerful. They are more powerful if you have everything on the disks that are created inside the VM, since this permits you to move the VM to different host.

    Yes, it is possible that it is supported to have things on network drives these days, but mapped drives may still not be the best thing, since the drive-mapping is in the user space and the mapping may not exist for SQL Server which runs under a separate
    account. It would be better to use a UNC path \servershareetc.

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

    • Помечено в качестве ответа
      jmarkfoley
      19 декабря 2019 г. 20:29

  • Installing software on a network drive does not sound like the best of ideas. If the network drive disappears, the software cannot work anymore. So leave the instance root with the default. Then you can later try to create the database on that network drive
    (that is the drive of the VM host).

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

    • Помечено в качестве ответа
      jmarkfoley
      19 декабря 2019 г. 20:30

Источник
  • Remove From My Forums

  • Question

  • I’ve installed SQL Server 2014 on a new Windows 7 computer. I am trying to apply the SQLServer2014-KB3158271-x64.exe update which is the «3158271 Cumulative update package 14 (CU14) for SQL Server 2014.» I am getting the error shown in the issue
    title: «The User Data directory in the registry is not valid … Error code: 0x851A0043.» I’ve check the registry setting for DefaultData and it has the correct path: E:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA. The path
    exists, and has the database files. I’ve done this successfully before. The only difference this time is that E: is a network drive.

    Help sorting this out would be greatly appreciated.

    • Edited by

      Sunday, December 1, 2019 4:49 AM

Answers

  • Uri Dimant: version: SQL Server 2014 Express. Build number is confusing. The Studio Help says 12.0.2569.0 which is the build of the CU that supposedly didn’t take, but the version on the server instance name is 12.0.2000, which is the base installed version.

    What you see in SQL Server Management Studio is the version of SSMS, and not the version of SQL Server. Those two are not the same. (And these days SSMS is a separate download. I would recommend that you get SSMS 17.9.1 from this

    link. Later versions are not good for Windows 10.)

    As to locations, I have some more confusion. Right-clicking on the server instance > Properties > Database Settings shows Data, Log and Backup as E:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA, which is what I want. However,
    running

    SELECT name, physical_name AS current_file_location FROM sys.master_files

    Shows C:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA for everything. Huh?

    The SELECT command shows you the location for current databases. The registry setting is default setting for new databases.

    Erland Sommarskog: A fairly old post, https://www.brentozar.com/archive/2012/01/sql-server-databases-on-network-shares-nas/, indicates that network drives can store database files. That’s one reason I’m trying to set this up.The main reason is that I’ve
    found system administrators often set up their database servers as a virtual machine for the ability to quickly restore systems in the event of problems.

    Yes, VMs are very powerful. They are more powerful if you have everything on the disks that are created inside the VM, since this permits you to move the VM to different host.

    Yes, it is possible that it is supported to have things on network drives these days, but mapped drives may still not be the best thing, since the drive-mapping is in the user space and the mapping may not exist for SQL Server which runs under a separate
    account. It would be better to use a UNC path \servershareetc.

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

    • Marked as answer by
      jmarkfoley
      Thursday, December 19, 2019 8:29 PM

  • Installing software on a network drive does not sound like the best of ideas. If the network drive disappears, the software cannot work anymore. So leave the instance root with the default. Then you can later try to create the database on that network drive
    (that is the drive of the VM host).

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

    • Marked as answer by
      jmarkfoley
      Thursday, December 19, 2019 8:30 PM

Источник
  • Remove From My Forums

  • Question

  • I’ve installed SQL Server 2014 on a new Windows 7 computer. I am trying to apply the SQLServer2014-KB3158271-x64.exe update which is the «3158271 Cumulative update package 14 (CU14) for SQL Server 2014.» I am getting the error shown in the issue
    title: «The User Data directory in the registry is not valid … Error code: 0x851A0043.» I’ve check the registry setting for DefaultData and it has the correct path: E:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA. The path
    exists, and has the database files. I’ve done this successfully before. The only difference this time is that E: is a network drive.

    Help sorting this out would be greatly appreciated.

    • Edited by

      Sunday, December 1, 2019 4:49 AM

Answers

  • Uri Dimant: version: SQL Server 2014 Express. Build number is confusing. The Studio Help says 12.0.2569.0 which is the build of the CU that supposedly didn’t take, but the version on the server instance name is 12.0.2000, which is the base installed version.

    What you see in SQL Server Management Studio is the version of SSMS, and not the version of SQL Server. Those two are not the same. (And these days SSMS is a separate download. I would recommend that you get SSMS 17.9.1 from this

    link. Later versions are not good for Windows 10.)

    As to locations, I have some more confusion. Right-clicking on the server instance > Properties > Database Settings shows Data, Log and Backup as E:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA, which is what I want. However,
    running

    SELECT name, physical_name AS current_file_location FROM sys.master_files

    Shows C:Program FilesMicrosoft SQL ServerMSSQL12.MEMBERSLINKMSSQLDATA for everything. Huh?

    The SELECT command shows you the location for current databases. The registry setting is default setting for new databases.

    Erland Sommarskog: A fairly old post, https://www.brentozar.com/archive/2012/01/sql-server-databases-on-network-shares-nas/, indicates that network drives can store database files. That’s one reason I’m trying to set this up.The main reason is that I’ve
    found system administrators often set up their database servers as a virtual machine for the ability to quickly restore systems in the event of problems.

    Yes, VMs are very powerful. They are more powerful if you have everything on the disks that are created inside the VM, since this permits you to move the VM to different host.

    Yes, it is possible that it is supported to have things on network drives these days, but mapped drives may still not be the best thing, since the drive-mapping is in the user space and the mapping may not exist for SQL Server which runs under a separate
    account. It would be better to use a UNC path \servershareetc.

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

    • Marked as answer by
      jmarkfoley
      Thursday, December 19, 2019 8:29 PM

  • Installing software on a network drive does not sound like the best of ideas. If the network drive disappears, the software cannot work anymore. So leave the instance root with the default. Then you can later try to create the database on that network drive
    (that is the drive of the VM host).

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

    • Marked as answer by
      jmarkfoley
      Thursday, December 19, 2019 8:30 PM

Источник

Иногда при установке очередного CU или SP на MS SQL Server возникает ошибка установки и установить обновления не получается.
Подробный текст ошибки:

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  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:                SQL Server Database Engine Services Instance Features
  Component error code:          0x851A0044
  Error description:             The User Log directory in the registry is not valid. Verify DefaultLog key under the instance hive points to a valid directory.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.6024.0&EvtType=0xD8FB5EBA%400x97A656BB%401306%4068&EvtType=0xD8FB5EBA%400x97A656BB%401306%4068 

Причина данной ошибки : путь для файлов логов или данных по умолчанию указан несуществующий. Возможно старый диск поменяли или путь ошибочно указали.

Решение:

Указать актуальный путь для файлов баз данных ,либо через MS SQL Management Studio Server Properties -> Database Settings , либо через команды:

USE [master]

GO

EXEC xp_instance_regwrite N’HKEY_LOCAL_MACHINE’, N’SoftwareMicrosoftMSSQLServerMSSQLServer’, N’BackupDirectory’, REG_SZ, N’E:Backup_01′

GO

EXEC xp_instance_regwrite N’HKEY_LOCAL_MACHINE’, N’SoftwareMicrosoftMSSQLServerMSSQLServer’, N’DefaultData’, REG_SZ, N’E:Data_01data’

GO

EXEC xp_instance_regwrite N’HKEY_LOCAL_MACHINE’, N’SoftwareMicrosoftMSSQLServerMSSQLServer’, N’DefaultLog’, REG_SZ, N’E:Logs_01log’

GO

. и после этого запустить снова установку обновления MS SQL Server.

Источник

Symptom

•　Error message occurred during SQL Server patch update.

•　Error details:

    Error installing SQL Server Database Engine Services Instance Features

    The User Data directory in the registry is not valid. Verify DefaultData key under the instance hive points to a valid directory.

    Error code: 0x851A0043

Read more…

Environment

•　SAP Systems based on SAP NetWeaver

•　Microsoft SQL Server 2005 and higher

Product

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

Keywords

0x851A0043,DefaultData key,cumulative patch,User Data directory , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , BC-DB-MSS-UPG , SQL Server Upgrades in SAP NetWeaver Products , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login
required).

Search for additional results

Visit SAP Support Portal’s SAP Notes and KBA Search.

Источник

Понравилась статья? Поделить с друзьями:

Не пропустите эти материалы по теме:

  • Яндекс еда ошибка привязки карты
  • Код ошибки 8504
  • Код ошибки 846
  • Код ошибки 830 шевроле нива
  • Код ошибки 830 приора

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии