Skip to content
Yesterday I was at a site where they decided to change the service account for the SQL Server services on a set of systems. After changing the service accounts, SQL Server restarted just fine on all machines except one.
I had used the SQL Server Configuration Manager to make the changes (important to not just use the Services applet in Administrative Tools) but I got the typical error telling me that the service wouldn’t start in a timely fashion. The server was running SQL Server 2008 R2 SP2.
Looking in the system event log produced the following errors:
The SQL Server (MSSQLSERVER) service terminated with service-specific error %%-2146885628.
A fatal error occurred when attempting to access the SSL server credential private key. The error code returned from the cryptographic module is 0x8009030d. The internal error state is 10001.
I spent a while looking for info on the last error and found a site where they discussed that it was generated when the service account could not read the machine keys that were stored in the C:ProgramDataMicrosoftCryptoRSAMachineKeys folder. The article then discussed how to add read permissions for the keys one by one.
It suddenly dawned on me that it was probably a problem with the permissions on the folder instead. Checking the permissions on that folder made me realize that the local Administrators account should have the ability to read it. The service account was meant to be a member of the local Administrators account but had not been added to that group on this machine.
Adding the service account to the local Administrators group on the machine (note: not the domain administrators account) fixed the issue and the service started again, until I could get the correct account permissions set in the morning when other staff came back. (In the comments I’ve added a list of what’s actually required).
Hope this helps someone else. (And helps me the next time I see this and have forgotten what it was J)
SQL: SSL and SQL Server 2008 – Service Doesn’t Start – Error Code 26014
After requesting the SSL certificate and getting it in the correct format to import into the server’s Personal Certificate Store using the steps found here, I was finally ready to select the certificate and encrypt the database traffic. As outlined here I selected the correct SSL certificate set the ForceEncryption flag to Yes. After doing such, I went to restart the SQL service as told and was presented with the following error: “Windows could not start the SQL Server (XXXXX) on Local Computer. For more information, review the System Event Log… and refer to service-specific error code 2146885628″
Instead of the System Event Log I went straight to the SQL Error Log (using the default installation the error logs are found in C:Program FilesMicrosoft SQL ServerMSSQL10_50.InstanceName/MSSQL/Log) and found the following information:
2010-09-08 12:35:30.76 Server Unable to load user-specified certificate [Cert Hash(sha1) “XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX”]. The server will not accept a connection. You should verify that the certificate is correctly installed. See “Configuring Certificate for Use by SSL” in Books Online.
2010-09-08 12:35:30.79 Server Error: 17182, Sev erity: 16, State: 1.
2010-09-08 12:35:30.79 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2010-09-08 12:35:30.82 Server Error: 17182, Severity: 16, State: 1.
2010-09-08 12:35:30.82 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
The certificate hash matched that of the certificate I had associated with the instance but it wasn’t loading. By default, SQL Server is run under a non-privileged service account and doing such is good practice as if your database is compromised, the attacker will have limited ability to harm the rest of the data on the server. But, this also raises another problem as when using a custom SSL certificate to encrypt database traffic, the non-privileged service account needs to be able to read both the public and private key of the certificate. Understandably, by default the service account does not have permission to read the private key. Once we give the service account permission to read the private key, the SQL Server will start up without a problem.
Follow the steps below to allow the service account to read the private key of the SSL certificate.
1. First we need to find the name of the service account used by the instance of SQL Server. It will probably be something like ‘SQLServerMSSQLUser$[Computer_Name]$[Instance_Name]‘.
2. One way to do this is to navigate to the installation directory or your SQL Instance. By default SQL Server is installed at C:Program FilesMicrosoft SQL ServerMSSQL10_50.InstanceName.
3. Right click on the MSSQL folder and click Properties.
4. Click the Security tab and write down the user in the Group or user names window that matches the pattern of ‘SQLServerMSSQLUser$[Computer_Name]$[Instance_Name]‘.
5. Now, open the Microsoft Management Console (MMC) by click Start -> Run, entering mmc and pressing Enter.
6. Add the Certificates snap-in by clicking File -> Add/Remove Snap-in… and double clicking the Certificates item (Note: Select computer account and Local computer in the two pages on the wizard that appears.
7. Click Ok.
8. Expand Certificates (Local Computer) -> Personal -> Certificates and find the SSL certificate you imported.
9. Right click on the imported certificate (the one you selected in the SQL Server Configuration Manager) and click All Tasks -> Manage Private Keys…
10. Click the Add… button under the Group or user names list box.
11. Enter the SQL service account name that you copied in step 4 and click OK.
12. By default the service account will be given both Full control and Read permissions but it only needs to be able to Read the private key. Uncheck the Allow Full Control option.
13. Click OK.
14. Close the MMC and restart the SQL service.
If all went well the SQL service should restart without any problems now. To check to see if the selected SSL certificate is actually encrypting the traffic to and from the database, go back to the Log folder in the installation directory of the SQL Instance and open up the ERRORLOG file. You should see somewhere in that file the following line:
1
2010-09-08 13:33:47.88 Server The certificate [Cert Hash(sha1) “XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX”] was successfully loaded for encryption.
Where the certificate hash code matches that of your imported SSL certificate. To verify the has code, go back to the MMC with the Certificates snap-in loaded and your SSL certificate visible. Double click on the certificate and click the Details tab. Scroll to the bottom of the list and select the Thumprint field. The value that appears should match that which is shown in the log file.
If you really want to know if the data is being encrypted, simply run a packet sniffer like Wireshark or Microsoft Network Monitor.
I’m new with development and just wanted to get the Personal Website Sample to work. So far, I’m have am having a terrible time installing SQL Express Edition. I’m not exactly sure what to do next. I have installed, manually uninstalled, and reinstalled many times. Sometimes I get error 29503 & 1067. Other times when I reinstall I get 29503 & -2146885628 . Here’s the info I got so far for my 29503&1067 since that error occurs 95% of time. I believe I got the -2146885628 error when I changed a setting from network to local services.
I feel so confused right now. Any help would be appreciative.
Code Snippet
Machine : DELL1
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
———————————————————————————
Machine : DELL1
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0018_DELL1_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
———————————————————————————
Code Snippet
—- Context ————————————————
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:10:750]: Product: Microsoft SQL Server 2005 — Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Tue Aug 28 01:48:10 2007
Service MSSQL$SQLEXPRESS with parameters ‘-m SqlSetup -Q -qJapanese_CI_AS -T4022 -T3659 -T3610 -T4010’ is being started at Tue Aug 28 01:48:10 2007
Service failed unexpectedly (1067)
Error Code: 0x8007042b (1067)
Windows Error Text: The process terminated unexpectedly.
Source File Name: sqlsetuplibservice.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls::Service::Start
Source Line Number: 301
—- Context ————————————————
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:13:968]: Product: Microsoft SQL Server 2005 — Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
MSI (s) (84:10) [01:48:14:109]: User policy value ‘DisableRollback’ is 0
MSI (s) (84:10) [01:48:14:109]: Machine policy value ‘DisableRollback’ is 0
Action ended 1:48:14: InstallFinalize. Return value 3.
MSI (s) (84:10) [01:48:14:171]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=924585293,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (84:10) [01:48:14:171]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Starting SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ProductInfo(ProductKey={B0F9497C-52B4-4686-8E73-74D866BBDF59},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=Setup,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Stopping SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: CustomActionRollback(Action=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlScript,CustomActionData=100Configuring Microsoft SQL Server81062400lpc:DELL1SQLEXPRESS)
MSI (s) (84:B4) [01:48:14:171]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI571.tmp, Entrypoint: Rollback_sqlScript
Function=Rollback_sqlScript
Doing Action: Rollback_sqlScript
This log does get kind of big, so if you need more information, please feel free to ask
I’m new with development and just wanted to get the Personal Website Sample to work. So far, I’m have am having a terrible time installing SQL Express Edition. I’m not exactly sure what to do next. I have installed, manually uninstalled, and reinstalled many times. Sometimes I get error 29503 & 1067. Other times when I reinstall I get 29503 & -2146885628 . Here’s the info I got so far for my 29503&1067 since that error occurs 95% of time. I believe I got the -2146885628 error when I changed a setting from network to local services.
I feel so confused right now. Any help would be appreciative.
Code Snippet
Machine : DELL1
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
———————————————————————————
Machine : DELL1
Product : Microsoft SQL Server 2005
Product Version : 9.2.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0018_DELL1_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
Error Number : 29503
———————————————————————————
Code Snippet
—- Context ————————————————
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:10:750]: Product: Microsoft SQL Server 2005 — Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Tue Aug 28 01:48:10 2007
Service MSSQL$SQLEXPRESS with parameters ‘-m SqlSetup -Q -qJapanese_CI_AS -T4022 -T3659 -T3610 -T4010’ is being started at Tue Aug 28 01:48:10 2007
Service failed unexpectedly (1067)
Error Code: 0x8007042b (1067)
Windows Error Text: The process terminated unexpectedly.
Source File Name: sqlsetuplibservice.cpp
Compiler Timestamp: Wed Jun 14 16:29:04 2006
Function Name: sqls::Service::Start
Source Line Number: 301
—- Context ————————————————
Setting status of unmanaged components and removing unmanaged resources
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Do_sqlScript
SqlScriptHlpr
Start service MSSQL$SQLEXPRESS
Error Code: 1067
MSI (s) (84!D4) [01:48:13:968]: Product: Microsoft SQL Server 2005 — Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, «How to: View SQL Server 2005 Setup Log Files» and «Starting SQL Server Manually.»
The error is (1067) The process terminated unexpectedly.
.
MSI (s) (84:10) [01:48:14:109]: User policy value ‘DisableRollback’ is 0
MSI (s) (84:10) [01:48:14:109]: Machine policy value ‘DisableRollback’ is 0
Action ended 1:48:14: InstallFinalize. Return value 3.
MSI (s) (84:10) [01:48:14:171]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=924585293,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (84:10) [01:48:14:171]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005)
MSI (s) (84:10) [01:48:14:171]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Starting SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: ProductInfo(ProductKey={B0F9497C-52B4-4686-8E73-74D866BBDF59},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=Setup,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0)
MSI (s) (84:10) [01:48:14:171]: Executing op: ActionStart(Name=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Configuring Microsoft SQL Server,Template=Stopping SQL Service: [1])
MSI (s) (84:10) [01:48:14:171]: Executing op: CustomActionRollback(Action=Rollback_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1345,Source=BinaryData,Target=Rollback_sqlScript,CustomActionData=100Configuring Microsoft SQL Server81062400lpc:DELL1SQLEXPRESS)
MSI (s) (84:B4) [01:48:14:171]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI571.tmp, Entrypoint: Rollback_sqlScript
Function=Rollback_sqlScript
Doing Action: Rollback_sqlScript
This log does get kind of big, so if you need more information, please feel free to ask
DAKTRONICS DOES NOT PROMISE THAT THE CONTENT
PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT
YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED
ON AN «AS-IS» AND «AS-AVAILABLE» BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE
IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT,
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY
AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD
PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT,
REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS
AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL
RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE
REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING
THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE
PARTIES.
The above disclaimer applies to any property damage, equipment
failure, liability, infringement, or personal injury claim arising out of or in
any way related to your use or application of the content, whether such claim is
for breach of contract, tort, negligence or any other cause of action.
Прежде всего, необходимо определение. Что такое Sql server? Системы управления реляционными базами данных позволяют работать с базами данных, хранящимися на сервере.
Такие службы работают по принципу клиент-сервер.
То есть основная база данных храниться на сервере, в то время как пользователь оперирует клиентским приложением, формирующим запросы для работы с её частями.
Содержание:
Работа SQL-служб основывается на структурированном языке запросов (structured query language), откуда, собственно и название.
Особенность подобного языка в том, что он прост в освоении. Даже люди без специальных знаний в области программирования могут легко освоить его.
В свое время именно это обстоятельство обеспечило программному обеспечению с поддержкой SQL лидирующие позиции на рынке.
Где, зачем и кому нужны SQL-серверы?
Сфера применения современных SQL серверов настолько широка, что для ее освещения понадобится отдельный материал.
Кратко можно сформулировать так: работа большинства интернет-ресурсов сложно представима без использования SQL-серверов.
Интересно! Подобным ПО пользуются как частные лица для разработки программ и различных сетевых служб, так и целые корпорации для организации своей деятельности, ведения учета и прочих нужд.
Простота в освоении и неограниченные возможности обеспечили технологиям на основе SQL широкое распространение.
к содержанию ↑
Sql server: яркие представители вида
Наиболее широкое распространение получили три наименования SQL-служб: MS SQL Server, SQLlite и MySQL.
Каждая служба ориентирована для разных потребностей, однако все они в полной мере обладают универсальностью и простотой SQL-серверов.
Рассмотрим подробнее каждого представителя.
Microsoft SQL Server
Мощный промышленный инструмент для работы с базами данных. Используется в основном большими корпорациями.
Частные программисты и небольшие организации предпочитают пользоваться инструментами, распространяемыми по другой модели.
Инструментарий Microsoft sql server позволяет организовать работу множества клиентов с базами данных.
Главное условие – наличие хорошего серверного оборудования.
Использование такого обеспечения не всегда оправдано, порой для решения поставленных целей больше подходят небольшие встраиваемые библиотеки или более простые службы.
MySQL
Не менее мощный, но более узкоспециализированный инструмент для работы с базами данных. Применяется в основном на веб-серверах.
Данная система управления базами данных ориентирована на использование в качестве внешнего сервера, к которому обращаются клиенты и приложения.
Но существуют сборки и для использования в качестве внутреннего сервера.
MySQL распространяется как бесплатно (по лицензии GPL), так и в платных сборках с заказным функционалом.
Первое обстоятельство позволяет СУБД (Система управления базами данных) динамично развиваться.
На основе MySQL выросло множество других СУБД, среди которых MariaDB, Drizzle и Percona DB.
SQLlite
Собственно, это даже не полноценная система управления базами данных, а небольшая библиотека для встраивания в программное обеспечение.
В основе её лежит тот же язык SQL, но предназначается она для использования внутри программы.
Основное применение – различные небольшие онлайн-игры и клиентские сервисы. SQLlite в них позволяет организовывать обращения программы-клиента к серверу.
Пользователь в этом процессе задействован мало.
к содержанию ↑
Наиболее распространенные коды ошибок
- sql server -2146885628
Возникает при неправильном запуске сервера. Для ее предотвращения нужно запускать SQL Server исключительно из SSCM (SQL Server Configuration Manager).
- sql server -2146232060
Ошибка возникает, когда не создана база ACT50. Для ее устранения достаточно создать одну из SQL Server, запустив CreateDB.sql. Вот так выглядит лог ошибки:
- sql server -2068578304
Ошибка возникает при установке SQL Server. Поможет удаление предыдущей версии SQL Server и установка при помощи Milestone installer.
- sql server -t272
Характерная проблема SQL Server 2012.
Возникает из-за того, что метод обработки значений в колонке идентифицирующих значений изменился.
В более ранних версиях каждое значение обрабатывалось отдельно, в SQL server 2012 и более новых версиях подобные значения обрабатываются пакетами.
Пакет значений кэшируется и вызывается по запросу, пока в кэш не будет помещен новый пакет значений.
Перезапуск сервера, оставшиеся в кэше теряются, что приводит к скачку значений после загрузки сервера.
Для устранения значка придется прописать параметр «-t272» в качестве начального. Для этого потребуется:
- Открыть менеджер конфигурации SQL Server Configuration Manager (SSCM);
- В правой части выбрать пункт «SQL Services»;
- В левой части экрана правый клик на «SQL Server (SQLSERVER2012)»;
- В выпадающем меню пункт «Prorties»;
- В окне свойств вкладка «Startup Parameters»;
- В строке ввода напечатать –t272 и нажать «Add»;
- Подтвердить изменения кнопкой «Apply».
Провести проверку поможет оператор языка sql update, позволяющий обновить значение в определенной колонке.
- sql server -2147467259
Ошибка возникает, когда к файлу MDB поступает обращение с неизвестного сервера. Для преодоления проблемы необходимо прописать имя сервера, которому нужен доступ. Синтаксис такой:
- sql -922
Код 922 проблему авторизации DB2. Скорее всего, произошел конфликт имен планов. Текущий план имеет неверное название или вовсе не идентифицирован.
Для устранения ошибки потребуется определить название плана.