Skip to main content

Posts

Management Reporter Exception -The security timestamp is invalid with Ax 2012

Error Description Getting below error on opening Management reporter . This error logged in event-viewer. System.ServiceModel.Security.MessageSecurityException: The security timestamp is invalid because its creation time ('2015-10-01T10:50:06.777Z') is in the future. Current time is '2015-10-01T10:43:51.967Z' and allowed clock skew is '00:05:00'. Server stack trace:     at System.ServiceModel.Security.SecurityTimestamp.ValidateFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)    at System.ServiceModel.Security.SecurityTimestamp.ValidateRangeAndFreshness(TimeSpan timeToLive, TimeSpan allowedClockSkew)    at System.ServiceModel.Security.ReceiveSecurityHeader.ReadTimestamp(XmlDictionaryReader reader)    at System.ServiceModel.Security.ReceiveSecurityHeader.ExecuteFullPass(XmlDictionaryReader reader)    at System.ServiceModel.Security.ReceiveSecurityHeader.Process(TimeSpan timeout, ChannelBinding channelBinding, Exte...

Relation between HcmPosition , HcmWorker and DirPartyTable in ax 2012

Relation between HcmPosition , HcmWorker and DirPartyTable in ax 2012  1.DirPartyTable is equivalnt to Dir Person and PersonId is present in HcmWorker Table and for worker Position there is HcmPositionWorkerAssingment table in which u will find the HcmWorker id n HcmPosition id. 2.there is no direct relation b/w HcmPosition and HcmWorker where the relation is made through HcmPositionWorkerAssignment as #Xainu said i.e HcmPositionWorkerAssignment .worker = HcmWorker.RecId, and for HcmWorker and DirPartyTable - RecId of DirPartyTable is nothing but person field in HcmWorker 3.For hcmworker and hxm position: hcmworker has relation with hcmpositionworkerassignment and hcmpositionworkerassignment has relation with hcmposition and hcmposition has with hcmposition detail. For dirpartytable abd hcmworker: dirpartytable has relation with dirperson and dirperson has relation with hcmworker.

Posting Error in AR Module in Ax 2012 for customer Payment

Following Error on Posting .. Solution: This is because the Method Of Payment is PDC in your case and when making customer payments using PDC, click the Postdated checks tab on the customer payment journal tab and enter the PDC details there. In the Maturity date field, enter the future date when the postdated check is due for payment and that will solve your issue.

Error code 110-Concurrent number of AOS for this application Exceeds the licensed number in axapta service

Problem: If you are facing Error code 110-"Concurrent number of AOS for this application Exceeds the licensed number" in axapta service  starting then you can apply below solution. Solution: You can go to sql server where you database attached. select the database open query editor then find the record from table dbo.sysserversessions  where status is active. You need to update that status to inactive it means set the value to zero. like this. update dbo.sysserversessions set status = 0 where status = 1 I hope your problem will be resolve by this.

Error on Purchase order posting in Ax 2012

 If You are getting following error on  Purchase order posting in Ax 2012 Error Description Cannot execute a data definition language command on accounting distribution (AccountingDistributionTmpJournalize). Amount in transaction currency: 0,00. The SQL database has issued an error.  Object Server 01:   [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name  'tempdb.DBO.t100007_093C403F6242343F93ED4D1F8739A'. Error Message  INSERT INTO tempdb."DBO".t100007_093323236220423232323 (TRANSACTIONCURRENCYAMOUNT,ACCOUNTINGDISTRIBUTION,RECVERSION,PARTITION) SELECT T1.TRANSACTIONCURRENCYAMOUNT,T1.RECID,1,5637144576 FROM ACCOUNTINGDISTRIBUTION T1 WHERE ((T1.PARTITION=5637144576) AND ((T1.REFERENCEROLE=3) AND (T1.SOURCEDOCUMENTLINE<>563343466))) AND EXISTS (SELECT 'x' FROM ACCOUNTINGDISTRIBUTION T2 WHERE ((T2.PARTITION=5637144576) AND (((T2.SOURCEDOCUMENTLINE=5637251266) AND (T2.MONETARYAMOUNT=1)) AND (T2.RECID=T1.REFERENCEDISTRIB...

Resolved:SQL error after CU7 update to AX2012 R3 on Execution of query

Following SQL error throwing  after CU7 update to AX2012 R3 on Execution of query. Error: SQL error description: [Microsoft][SQL Server Native Client 11.0][SQL Server]String or binary data would be truncated. SQL statement: UPDATE T1 SET ACTNAME=((T2.DISPLAYVALUE+?)+T4.NAME),NONLEDGERACCOUNTNAME=T4.NAME,RECVERSION=? FROM tempdb."DBO".t12143_065EB03A5044473883A01845DF64A84A T1 CROSS JOIN DIMENSIONATTRIBUTEVALUECOMBINATION T2 CROSS JOIN VENDTABLE T3 CROSS JOIN DIRPARTYTABLE T4 WHERE ((T1.PARTITION=?) AND (T1.ACCOUNTTYPE=?)) AND ((T2.PARTITION=?) AND (T2.RECID=T1.LEDGERDIMENSION)) AND (((T3.PARTITION=?) AND (T3.DATAAREAID=?)) AND (T3.ACCOUNTNUM=T2.DISPLAYVALUE)) AND ((T4.PARTITION=?) AND (T4.RECID=T3.PARTY)) Solution: Find then Actname column in table which are currently used for query then increase then length of column as required or change Extended datatype which have more size then current. For example -Change EDT from Name to DirPartyName for particular column ....