P-job channel transactions

(0) Share

Report

Posted on by echo

595

Hi,

Some of the transactions are being missed by the p-job and i can't calculate the statements because there is a difference in transaction count between the shift count and actual transactions in retailtransactiontable

how can i replicate those transactions to hq.? And any reasons su this might happen? I am on ax 2012 r3 cu8.

-echo

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (1)

Verified answer

Denis Macchinetti 16,444 on at

Like (0)

Report

Hi Echo

On LCS I found a Solution about R3 that can help you.

The solution id is 3211092

Below an extract.

Hope this help you.

Transactions are not pulling to store HQ

MITIGATION

How does Async Client know what records to upload during a P job?

In the channel database the following table is checked for each table:

SELECT ISNULL(MAX(FilterMax), 0) FROM crt.TABLEREPLICATIONLOG WHERE TABLENAME='ax.RETAILTRANSACTIONSALESTRANS' AND FILTERFIELDNAME = 'REPLICATIONCOUNTERFROMORIGIN'

This check is done with all the tables that is sent to the HQ.

So one thing you could do is to force the Channel Database into thinking that the records haven’t been uploaded to Async Server. If that table was cleared out it would “reset” the channel database and it would re-upload all records into a new RPF file. This should be OK since any duplicate transactions would be ignored by AX.

Follow this steps:

1. Stop the AsyncClient in the StoreDB machine

2. Make a backup of the Channel Database

3. Delete records from table crt.TABLEREPLICATIONLOG

4. Start the Async Client

5. Run the P-job

Was this reply helpful? Yes No
R_V on at

Like (0)

Report

Hi Denis,

I am also facing the same issue. So I decided to go with the solution provided by you. but after performing the steps, I am unable to see any entries in TableReplicationLog. Can you please tell me what would be the root cause of entries not getting generated in TableReplicationLog table.

Regards,

RV

Was this reply helpful? Yes No
Suggested answer

Vino9667 364 on at

Like (0)

Report

Dear Denis,

Your solution worked for me thank you soo much and you saved my time.

One more suggestion in your steps, please change step no. 3 as Delete records from crt.TABLEREPLICATIONLOG

instead of Delete the delete because some times it will create confusion.

Once again thank you soo much...

Was this reply helpful? Yes No
Denis Macchinetti 16,444 on at

Like (0)

Report

Done!

Thanks for your suggestion.

Was this reply helpful? Yes No
Mark_Edel 160 on at

Like (0)

Report

Hi Dennis,

I also encountered the same issue and tried your suggestion sadly it does not solve our issue. The status in the upload sessions is still "started" even though we already uncheck 'ReRun' field at session table in AsyncServer DB. Still the P-Jobs does not applied.

Regards,

Mark

Was this reply helpful? Yes No
hatem.bouhdida 5 on at

Like (0)

Report

After deleting the table crt.tablereplicationlog and starting the Async service. The table is still empty.

Any idea?

Thank you.

Was this reply helpful? Yes No
Vino9667 364 on at

Like (0)

Report
Hello hatem

Delete record from crt.tablereplicationlog table in store db

Check the Async Retail channel connectivity from store

If the connectivity is ok then restart the service once

Run the P-job

It will work, else please check your event viewer and give more details about your error.

Was this reply helpful? Yes No
R_V on at

Like (0)

Report

Hi Mark,

I am also facing same issue, data packets are in started status and not getting applied. When I manually changed status to "Uploaded" and then trying to run P job, I am getting below error. Can you please let me know how did you solved this.

Error occurred in this data upload worker. Last error message: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Dynamics.Retail.StoreConnect.Request.SCRequestPackingException: Cannot unpack data file: RetailTransactionSalesTransT_83b4afbc-766c-4956-855c-bba6b6e7794f.xml ---> Microsoft.Dynamics.Retail.StoreConnect.Request.SCRequestPackingException: Cannot unpack data file: RetailTransactionSalesTransT_83b4afbc-766c-4956-855c-bba6b6e7794f.xml; file is corrupted

at Microsoft.Dynamics.Retail.StoreConnect.Request.SCTargetRequestHeaderPacking.Unpack(Stream stream, String workingDirectoryPath, Byte[]& requestHeaderBytes, String& requestHeaderTypeFullName)

--- End of inner exception stack trace ---

at Microsoft.Dynamics.Retail.StoreConnect.Request.SCTargetRequestHeaderPacking.Unpack(Stream stream, String workingDirectoryPath, Byte[]& requestHeaderBytes, String& requestHeaderTypeFullName)

at Microsoft.Dynamics.Retail.SynchLibrary.Metadata.UploadSession.UnpackDataFile(String dataFilePath, String workingDirectoryPath)

--- End of inner exception stack trace ---

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at Microsoft.Dynamics.AX.ManagedInterop.ClrBridgeImpl.InvokeClrStaticMethod(ClrBridgeImpl* , Char* pszClassName, Char* pszMethodName, Char* assemblyName, Int32 argsLength, ObjectWrapper** arguments, Boolean* argsAreByRef, Boolean* isException)

Was this reply helpful? Yes No
hatem.bouhdida 5 on at

Like (0)

Report

Never seen this. Can you explain more?

Was this reply helpful? Yes No