Saturday, December 29, 2012
AX Mobile Blog ( Adroid and Windows Phone )
Mobile Apps for Dynamics AX
Microsoft Dynamics AX 2012 White Paper: Configure Microsoft Dynamics AX Connector for Mobile Applications
Kurt Hatlevik – Dynamics Ax Blog
10-Minute App - Windows Phone 7 App
10-minute App Series Conclusion
ERP2mobile
AX2012 Windows 8 App Developer Starter Kit
Developing Secure Mobile Apps for Dynamics AX 2012 - Connector
Windows 8 Apps for Dynamics AX
Monday, December 24, 2012
Friday, December 7, 2012
Wednesday, December 5, 2012
AX 2012 - AOS Crash Kernel Hotfix
Hi All
Below the last Kernel Hotfix about AOS Crash ( KB Article Number : 2787191 ) :
http://hotfixv4.microsoft.com/Microsoft%20Dynamics%20AX%202012/nosp/KB2787191/6.0.1108.3086/free/455982_intl_i386_zip.exe
Finally, here a complete list of all Kernel Hotfix about AOS Crash issue :
Client crash when selecting record in form's derived table's referencegroup fieldyesdir
Below the last Kernel Hotfix about AOS Crash ( KB Article Number : 2787191 ) :
http://hotfixv4.microsoft.com/Microsoft%20Dynamics%20AX%202012/nosp/KB2787191/6.0.1108.3086/free/455982_intl_i386_zip.exe
Finally, here a complete list of all Kernel Hotfix about AOS Crash issue :
Client crash when selecting record in form's derived table's referencegroup fieldyesdir
2724568 6.0.1108.1260
System
crash when posting intercompany invoice
2726353 6.0.1108.1331
Client
crash when removing multiple users from a security role
2728524 6.0.1108.1339
Generate
Incremental CIL causes AOS to crash if CIL code is executed at the same time
2729087 6.0.1108.1363
AOS
crash on development environment using 8 GB and 16 total
2730676 6.0.1108.1399
Client
crash when performing impact analysis against CU-3
2730777 6.0.1108.1413
Adding
an EDT with the reference table property set, Crash the AX Client when on
"Confirm adding relation" dialog "yes" is cliccked
2738534 6.0.1108.1682
AOS
crash stack overflow relating to SqlConnectBase::setContext() with multiple SQL
statement trace enabled
2739574 6.0.1108.1707
Client
crashes in the query lookup
2745617 6.0.1108.1894
Request
for port of AX6 bug 301574 to the 6.0/6.1 branch - AOS crashing in
Ax32Serv!interpret::xal_asg_sym_opr
2748615 6.0.1108.1932
Client
crash when system parameters is set to en for the default language and trying
to enter workflow language instructions
2748479 6.0.1108.1956
AX is
crashing while opening edit payment praposal form from Payment journal[ALL ON]
2758284 6.0.1108.2216
AOS
crash during compilation after installing CU3
2764075 6.0.1108.2360
[Revert
of 316400] Client crashes when hovering over method resolve of class SysWorkFlowHierarchyProvider
2768644 6.0.1108.2506
AOS
crash when trying to covert Blank string to ENUM using a custom webservice in
AIF
2778096 6.0.1108.2753
AX
client crash when form personalization with moving button from actionpane to
page
2780317 6.0.1108.2844
RFH:
DAXSE_314175 (Inactive plan versions are never cleaned up in case of AOS crash)
failing whilie clearing all pending orders if AOS crashed
2779941 6.0.1108.2860
AX
client crashes exporting to Excel
2785905 6.0.1108.3031
Running
aximpactanalysis.exe in KB Article Number (s) : 2765336 crashes.
2786562 6.0.1108.3068
Enjoy !
Friday, November 30, 2012
AX 2012 - SQL Server Collation
There is a
difference in collation setting between SQL Server default collation setting
used for system databases (Master, Model, Msdb, TempDB) and the Microsoft
Dynamics AX database . Latin1_General_CI_AS_KS_WS v.s.
Latin1_General_CI_AS
Database Name
|
Collation name
|
AX2012PROD
|
Latin1_General_CI_AS
|
master
|
SQL_Latin1_General_CP1_CI_AS
|
model
|
SQL_Latin1_General_CP1_CI_AS
|
msdb
|
SQL_Latin1_General_CP1_CI_AS
|
tempdb
|
SQL_Latin1_General_CP1_CI_AS
|
It is recommended that the collations of user-defined databases match
the collation of master or model. Otherwise, collation conflicts can occur that might prevent code from
executing. For example, when a stored procedure joins one table to a temporary
table, SQL Server might end the batch and return a collation conflict error if
the collations of the user-defined database and the model database are
different. This occurs because temporary tables are created in TempDB, which
bases its collation on that of model.
If you
experience collation conflict errors, consider one of the following solutions:
· Export the data from the user
database and import it into new tables that have the same collation as the
master and model databases.
· Rebuild the system databases to use
a collation that matches the user database collation. For more information
about how to rebuild the system databases, see Rebuilding System Databases (http://technet.microsoft.com/en-us/library/dd207003.aspx).
More
information can be found here:
http://technet.microsoft.com/en-us/library/bb402915.aspx
Windows Collation Name (Transact-SQL)
Here you can find a good post that explain the difference between collation Latin1_General_CI_AS (United Kingdom) respect SQL_Latin1_General_CP1_CI_AS (United States).
It’s better to use Latin1_General_CI_AS collation because is a Windows collation and the rules around sorting unicode and non-unicode data are the same.
Difference between collation SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS
Windows Collation Name (Transact-SQL)
Here you can find a good post that explain the difference between collation Latin1_General_CI_AS (United Kingdom) respect SQL_Latin1_General_CP1_CI_AS (United States).
It’s better to use Latin1_General_CI_AS collation because is a Windows collation and the rules around sorting unicode and non-unicode data are the same.
Difference between collation SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS
Subscribe to:
Posts (Atom)