Inside Dynamics AX

Another instance of CIL generation is already in progress If AX crashes while doing a full CIL, a record is left behind that does not allow CIL again and gives the Another instance of CIL generation is already in progress. You can delete the record from SysLastValueTable. It has UserID = '-AutoSem' and ElementName = 'Cil Generation'.

Using Export command then no space should exists in your model name but if you have blank space in model name then single quote is required. Example of Exporting model Export-AXModel –Model 'Model1' -File d:\model1.axmodel Example of Importing Model Install-AXModel -File d:\Model1.axmodel -Details Example to delete Model Uninstall-AXModel -Model "USR Model" To execute above command you need to open Microsoft Dynamics AX Management Shell. x

The following error/warning occurred:Setup encountered an error during deployment of the Role Center and Enterprise Portal framework. In SysEPDeployment::clrGenerateProxies... In SysEPDeployment::clrStoreDeleteFolder... Deploying proxies...Complete Deploying All Web Parts...Complete Installing DynamicsAxEnterprisePortal feature... Failed to find the XML file at location '14\Template\Features\DynamicsAxEnterprisePortal\feature.xml' Failed to find the XML file at location '14\Template\Features\DynamicsAxEnterprisePortal\feature.xml' Fixed by following steps: Open regedit and find this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions On SharePoint 2010 environments you can have both 14.0 and 15.0 keys, and the 15.0 key typically has a single "Csom" sybkey. If this is true for your machine rename the 15.0 key to 15.0_newname and try to rerun EP install To avoid any issues revert the key rename after EP ...

If you are getting this message when installing Enterprise Portal in 2012 " Server was unable to process request. ---> Could not retrieve a valid Windows identity. ---> The message could not be dispatched because the service at the endpoint address 'net.pipe://localhost/s4u/022694f3-9fbd-422b-b4b2-312e25dae2a2' is unavailable for the protocol of the address. " it's because of a stopped service in SharePoint. Simply go to  SharePoint Central Administration -> System Settings > Manage services on server  and start the  Claims to Windows Token Service .

During Sales order posting I encountered an issue which was being generated due to below error message: "Cannot create a record in Sales order header - Updating table (SalesParmSubTable). Sales order:*, *. The record already exists." After some analysis and searching this issue I found that this issue sometimes occurs due to database logging enabled on some tables related to Sales Order i.e. SalesParmSubTable, SalesParmSubLine, SalesParmTable,SalesParmUpdate .... Removing these tables from that specific Company Database log setup resolved the issue. Note: For similar issue related to PO I also found a Microsoft fix which may also be helpful in similar scenarios: https://support.microsoft.com/en-us/kb/961909

Static void onHandJob(Args _args) { InventOnhand    inventOnhand;     InventDim       InventDimLocal;     InventSum       InventSumLocal;     ItemID          itemId,ItemIdLocal;     InventDimParm   inventDimParmLocal;     InventBatch     inventBatchLocal; itemid = wmsPickingList_OrderPickTmp.ItemId;     while select InventSumLocal             group by InventSumLocal.ItemId, InventDimLocal.inventBatchId,                      InventDimLocal.wmsLocationId, InventDimLocal.LicensePlateId         where InventSumLocal.Closed == NoYes::No               && InventSumLocal.ClosedQty == NoYes::No               && InventSumLocal.ItemId == itemid    ...

Publishing AX Reports – User or group name not recognized You may encounter an issue with trying to release reports to your AX environment when you move databases between environments. The error you might receive, during the report release, is  Publish_AXReport: The user or group name ‘xxx’ is not  recognized Even though everything is setup correctly in your AX environment, the error is caused by having additional records in the table SysServerSessions. If from SQL you review the data in this table you should notice that you have records that point to old servers/instances. You need to delete all the records that are not relevant to your current environment. Once done you should be able to deploy reports with getting the user or group name error.