Learn Dynamics 365 Finance and Operations(Axapta)

Error :  Failed to find workflow configuration. This error comes when a configuration is deleted from the workflow, but refrence is still there in the workflowworkitem table so we have to delete it by running a job. Job :- static void deleteJunkWorkflowWorkItems(Args _args) { WorkflowWorkItemTable wrkItemTable,wrkItemTable1; WorkflowConfigurationTable workflowConfTable; while select wrkItemTable where wrkItemTable.UserId == 'XXX(Admin)' { select workflowConfTable where workflowConfTable.ConfigurationId != wrkItemTable.ConfigurationId; info(strfmt('%1,%2,%3',workflowConfTable.TemplateName,wrkItemTable.ConfigurationId,workflowConfTable.dataAreaId)); delete_from wrkItemTable1 where wrkItemTable1.RecId == wrkItemTable.RecId; } } 

HTTP Error 503: Service unavailable Go to the respective application pool in IIS and check whether the service is running or not. If not start the service.  If the service is getting stopped and got the same error when you browse the server.  Check the Identity credentials in advanced settings of the application pool. It may cause due to change of the system credentials.

http://arsalanax.blogspot.com/ 2012/01/ dynamics-ax-technical-consultan t.html

Error  -- at services.msc windows could not start the DAX AOS 5.0$01-xyz_ax on local computer.For more information,review the system event log. If this is a non-microsoft service, contact the service vemdor, and refer to service-specific error code 110. Log at Event viewer  -- Concurrent number of AOS' for this application exceeds the licensed number Resolution -  This is a known issue in Ax, in case of multiple AOS installation, to overcome this issue , First you have to go to Services.msc and there you must first stop the active instance of AOS and then try to start the Other Instance , the second AOS will start in this way, now you can come back to the first AOS and start that also , so both the AOS will get started by following these steps.

There seems to be quite some vagueness when it comes to Ax and AOS clustering. A few statements to (hopefully) clear things up a bit: Single AOS The simplest configuration is an Ax implementation with one single AOS server. Extra AOS servers can be added in scenarios where you want to increase availability or scale up the Ax environment to handle a larger number of users/connections. Several possibilities from that point on: AOS side by side By default multiple AOS's in a single Ax environment will exist side by side. They do know about each others existence, sync their caches, try not to hamper each other too much,  … A user connects to a specific AOS as defined in his client configuration. In case there is more than one AOS defined in the configuration the first available will be used. Adding all available AOS's to one client config file would probably be a smart thing to do. If you only add one node of the cluster to your config file, and this one node is down, y...

INTRODUCTION The standard lookup system in Axapta is based on the use of table field or data type relations. These specify a link between a particular data type, or particular table field, and a corrsponding field in another table containing the base (reference) data. Generally, relations are made on the datatype (EDT) in the AOT, and will then automatically apply to any table field using that EDT. For example, in the standard application, the CustAccount EDT has a relation specified to CustTable.CustAccount. This means that any table field using the CustAccount EDT will be automatically given a lookup icon which allows the user to select from the list of accounts in CustTable. It is possible to further restrict the values which will appear in the lookup by specifying a "Related fixed field" relations on the datatype. In this case, only those values satisfying the relation will be shown in the lookup. See the Dimension datatype for an example of this (each Array Element ...

Very helpful information on indexes http://sumitsaxfactor.wordpress.com/2011/05/05/info-on-indexes/