AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 10.05.2010, 21:05   #1  
Blog bot is offline
Blog bot
Участник
 
25,643 / 848 (80) +++++++
Регистрация: 28.10.2006
emeadaxsupport: Event 117 Changed language setting to us_english
Источник: http://blogs.msdn.com/emeadaxsupport...s-english.aspx
==============

I came across another instance of a reasonably common issue today, which is that many instances of these errors appear in the event log, but apparently nothing is wrong with the system (i.e. no other symptoms/problems are apparent):



110 Object Server 01: Dialog issued for client-less session 1: Cannot edit a record

in LastValue

(SysLastValue). User ID: , AdminUserSetup.

The SQL database has issued an error.



117 Object Server 01: The database reported (session 1 (-AOS-)): [Microsoft][ODBC

SQL Server

Driver][SQL Server]Changed language setting to us_english.. The SQL statement was:

"UPDATE

SYSLASTVALUE SET VALUE=?,RECVERSION=? WHERE (((((((USERID=?) AND (RECORDTYPE=?))

AND (ELEMENTNAME=?)) AND (DESIGNNAME=?)) AND (ISKERNEL=?)) AND (COMPANY=?)) AND

(RECVERSION=?))"



These messages do not appear constantly, but actually sporadically, and always in pairs, of 110 and 117.



I found that these messages are nothing to worry about - the detailed explanation on what is going on here is below:



An update conflict occurs when updating a table with a blob type field, like SysLastValue table. The kernel uses ODBC function SQLParamData to put data into a blob field, in case of an update conflict the code continues to try to update the blob field and SQLParamData returns SQL_NO_DATA (because the recVersion in the where predicate has changed due to the update conflict).



The AX kernel misinterprets this return value, thinking that SQL server has raised an error, and so raises the two messages in the event log - message 110 indicates the update failed, message 117 is the last message raised from SQL server, which is actually just a standard information message that is normally not shown, as there is no actually no error from SQL, it is only a difference in interpretation from the AX kernel.







Источник: http://blogs.msdn.com/emeadaxsupport...s-english.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
CRM DE LA CREME! Some more useful javascripts for MS CRM Blog bot Dynamics CRM: Blogs 0 04.05.2010 11:05
AX 2009 Technical Journal: Event ID 110 and 117 (annoying database error) Blog bot DAX Blogs 0 08.03.2010 16:05
emeadaxsupport: Group policy setting "System Objects: Default owner for objects created by members of the administrators group" is missing on Windows Server 2008 Blog bot DAX Blogs 2 28.08.2009 02:14
Microsoft Dynamics CRM Team Blog: ASP.NET 2.0.50727.0 Warning Event ID: 1309 due to Request time out Blog bot Dynamics CRM: Blogs 0 21.11.2008 02:08
Microsoft Dynamics CRM Team Blog: CRM Accelerators – Part III – Event Management Accelerator Blog bot Dynamics CRM: Blogs 0 20.08.2008 01:05

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 04:15.