When the following error occurs during data import via DAT/DEF then the following could help:
Cannot execute the required database operation. The SQL database has issued an error.
An error occured during data import
First of all this message does not tell where the error came from. So I checked the error log of the SQL Server and found this message:
Object Server 03: The database reported (session 3 ()): [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'DBO.[AX2012_model]
.[dbo].SECURITYROLE'.. The SQL statement was: "UPDATE "DBO"."T073473B435914AF595C2B7075BD5D7D6" SET "CONFLICTS" = 1, "NEWRECID" = "DBO".SYSOLD2NEWRECID.IDREF FROM "DBO"."[AX2012_model].[dbo].SECURITYROLE","DBO".SYSOLD2NEWRECID WHERE "DBO"."T073473B435914AF595C2B7075BD5D7D6"."CONFLICTS" = 0 AND "DBO"."T073473B435914AF595C2B7075BD5D7D6".RECID = "DBO".SYSOLD2NEWRECID.ID AND "DBO"."[AX2012_model].[dbo].SECURITYROLE".RECID = "DBO".SYSOLD2NEWRECID.IDREF AND "DBO".SYSOLD2NEWRECID.TABLEREF = 65491 AND "DBO".SYSOLD2NEWRECID.SOURCEGUID = '{F20E9748-9070-4138-8546-38B382154E08}' AND "DBO".SYSOLD2NEWRECID.TARGETVIRTUALCOMPANY = '""' AND "DBO".SYSOLD2NEWRECID.PARTITION = 5637144576"
This message indicates that there is a problem with the table SecurityRole. So I tried to find out why the system want's to import records from this table even though it was not included in the tablegroup. After exporting into a comma seperated file i could find records with this table in the exported DAT File. Searching for the RecID of these records I found a refernce from the DirExternalRole table.
After removing this Table from the tableGroup I exported the data again and nowthe import is not throwing this error anymore :)
TECHNICAL TOPICS: MICROSOFT DYNAMICS AX & DYNAMICS 365 FOR FINANCE AND OPERATIONS - ENTERPRISE EDITION
07 June 2013
29 May 2013
AX 2012 Shortcut to view details
If you want to view details in AX 2012 the standard way is using the mouse -> Right click -> click on view details. But you can get there evan faster and without using the mouse.
The ShortCut to open the context menu is SHIFT + F10 or the ContextMenu Key between ALT GR and STRG. Clicking this followed by the key V will open the View details.
SHIFT + F10 -> V
or
This also works with other letters. If you use F for example then you need to press enter if you want to Filter by Field or use the down arrow and press enter.
06 May 2013
Get a list of users in a Windows Active Directory group
Because I always forget this short and important command I post it here. It is the shortest command line prompt to get a list of users in an AD Group:
net group /domain
net group /domain
07 March 2013
Microsoft Product Lifecycle - Mainstream and extended support end dates
| Products Released | Lifecycle Start Date | Mainstream Support End Date | Extended Support End Date | Service Pack Support End Date | |
| Dynamics AX 2009 | 8/14/2008 | 10/8/2013 | 10/9/2018 | 1/11/2011 | |
| Dynamics AX 2009 Service Pack 1 | 11/3/2008 | Support ends 24 months after the next service pack releases or at the end of the product's support lifecycle, whichever comes first | |||
| Dynamics AX 2012 | 9/25/2011 | 10/11/2016 | 10/12/2021 | ||
| Dynamics AX 2012 R2 | 2/19/2013 | 10/11/2016 | 10/12/2021 | ||
20 February 2013
Microsoft SQL Server build numbers
Here is a wonderful list of all the build numbers from the SQL Server versions:
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
29 January 2013
Default number sequence list - AX 2012
Here is an Excel spreadsheet providing all the default number sequence configurations in Dynamics AX 2012 as it is set up through the configuration wizard:
Dynamics AX 2012 - Default number sequence list
Dynamics AX 2012 - Default number sequence list
31 August 2012
Best Practise Error: different origin value on a new object
I just got thie Best Pracitse Error on a newly created table in Dynamics AX 2012:
The element has an origin value that is different from the origin value in a previous version of Microsoft Dynamics AX.
Checks that the element had the same origin value in earlier versions of Microsoft Dynamics AX. The origin value is the beginning value of the element. This check was added due to the changes regarding installation specific IDs.
BPErrorObjectOriginMismatch @SYS335100
I was confused about this message, cause it doesn't make any sence for new objects. After a restart of the AOS the error is gone.
The element has an origin value that is different from the origin value in a previous version of Microsoft Dynamics AX.
Checks that the element had the same origin value in earlier versions of Microsoft Dynamics AX. The origin value is the beginning value of the element. This check was added due to the changes regarding installation specific IDs.
BPErrorObjectOriginMismatch @SYS335100
I was confused about this message, cause it doesn't make any sence for new objects. After a restart of the AOS the error is gone.
Subscribe to:
Posts (Atom)


