Axapta 4.0 SP2 Event ID 117 & 110

[Ken Wincel]

We've recently moved from Axapta 3.0 to Axapta 4.0 SP2, which was a
successful migration. The only odd behavior we're seeing is Event ID's 110
and 117 which occur all the time. We have 5 AOS servers, and everyone of them
see the following errors, which are always together and always the same;
----------
Event Type: Error
Event Source: Dynamics Server 01
Event Category: None
Event ID: 117
Date: 2/22/2008
Time: 8:46:37 AM
User: N/A
Computer: AOS1
Description:
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=?))"

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------
Event Type: Error
Event Source: Dynamics Server 01
Event Category: None
Event ID: 110
Date: 2/22/2008
Time: 8:46:37 AM
User: N/A
Computer: AOS1
Description:
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.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--------------
Being the largest deployment of Dynamics, we've had some strong MS suport.
However, their only response to these events is that they are related to a
network problem. Though we've been sniffing the network, monitoring latency
across all sites, and complete server performance profiling. And we see no
indication of a network issue anywhere. And reading through the event, it
really doesn't sound like a network related\triggered event.

Has anyone else seen, resolved, or know anything about these events?
--
Ken Wincel
Sr. Enterprise Architect

[Guillaume]

Hi,

1-
i've met plenty of these messages errors after big infrastruture problems
(lost network or SQL server down). After the network crash for example,
there was AX client not connected to AOS but still alive, and users
disconnected but still having processus between the AOS and the SQL server...
I receive these messages errors until i kill all the clients still alive,
then stop all the AOS, and then restart the SQL Server to be certain to have
no more communication between AOS and SQL server.

2- Another idea : one of our customer never met these error message for the
first six months, and finally these messages haved appeared for some times
"without no apparent reason". It's occured when we add new type of users with
new AX security profiles, so may be there is something with insufficient
rights given to Ax user, just an idea.

[Hasselblad@discussions.microsoft.com Henrik Hasselblad]

Hi all,
I have the same error all the time.....
with six AOS servers. Have you any news?

// Henrik

[CJMorganT110]

We as well receive the same set of errors. Though they are not all the time,
they appear in clumps (i.e. 1:40 a.m. this morning (9.16.08) and again at
8:30 a.m. today). SQL server is fine as far as I can tell and mostly happens
on one of our 6 object servers. One thing I read pointed to Orphan users but
our database doesn't have that issue with the account that connects in from
tha server. Let us know if you find out anything.

C.J.

[Henrik]

Hi Guys...
Any new on this problem, I have escalated this with Microsoft but still no
solution in place.

Br
Henrik

[M Matin]

We have the same issue in our client site and looking for a resolution.
I saw the following comment but not sure if it fixes the issue.
"If connection pooling is enabled, these messages may not reappear during a
page refresh until the length of time specified by the CPTimeout value passes
and the connection is removed from the connection pool. If a page is
subsequently refreshed, the connection messages may reappear since the
connection has to be re-established."

[Jacky]

Dear Ken,

Do you have more findings or a solution?
We also have this issue and our system is AX3+SP3+KR3 and SQL2005SP2.

Thanks
Best Regards
Jacky

[Bello@discussions.microsoft.com Israel Bello]

Can you tell me if you are running AX clients through a Citrix farm?

[Back2AX]

I think this is a weakness (not a bug) in the way the AOS kernels treats
errors raised from the ODBC layer. A simple filter in the error handling is
missing (should ignore the corresponding ODBC native error). From my
understanding this is pure information returned by the ODBC layer after
successfully connecting to the database telling the language used by the SQL
Server login. See
http://ax2009tech.blogspot.com/2010/03/annoying-database-error.html for
further details.