Skip to Content
author's profile photo Former Member
Former Member

MSA ConnTrans issue

Hi all,

I have a problem with the ConnTrans tool on MSA repository.

The Send and Receive functions are completed without errors but when the Import action starts ,t ConnTrans gives error.

It seems the ConnTrans is not able to import the first entry from CRM itself and the technical team is saying that an entry is getting locked repeatedly when they analyzed the SQL server 'Locks\Process ID' and that is preventing the queue flow. How can I find what is stuck ?

Pls help.

Regards,

Emily.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2009 at 01:36 PM

    Hi Emily,

    Since the Send and recieve works properly, and Import is failing from the beginning,

    I would like you to check the following :

    1. Make sure that comm.station is installed properly and also you maintain the destination(CRM Server) that you want to connect to the Comm.station.

    2. In the Mobile Client, Go to QmtCOnfg.exe from Bin.Net and Select the destination (CRM Server) where you want to send and recieve data and test the connection.

    3. In the Client Console, Make sure that you have generated the Tables and BDocs from the Destination(CRM Server) that you configured in the Mobile Client.

    For example, If you have configured the Q5C server in the Comm.station, then generate the tables and BDocs from the same Q5C server from the Client Console.

    4.Run the Contrans.

    For furthur analysis, Please check the TLTrace.dat file available in the %Temp% folder from the Run Command.(TLTrace should be set to 1 in the registry)

    Note : If all the above information are configured correctly and still contrans fails, then there might be some inconsistencies in the BDocs

    and Table Structures.

    Hence generate the tables and BDocs again from the Client Console and Run the Contrans. It will work..

    Have a good day!!

    Best Regards,

    Vignesh Ravikumar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2009 at 03:02 PM

    Hi Emily,

    The TL_Trace.dat file will be present inside ,

    HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\MW\TL - Check the location from the TL_TRACE_DIR key. Go to that location and check the TLTrace.dat file after running the contrans.

    And also make sure that you the TL_Trace to 1 from the same regsitry seting(HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\MW\TL )

    Thanks and Regards,

    Vignesh Ravikumar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 07, 2009 at 10:14 AM

    Hi ,

    I believe the MetaData(Client Console) and TransactionData(Contrans) are pointing to the same CRM Server. If yes, Then Ideally, the Import Phase should work fine.

    If not, then make sure that they are in sink.

    Otherwise, MsgTransferService.dll, NewQmtConfg.dll might be corrupt.

    The Dll's will be present in the system where Comm.Station is installed.

    Best Regards,

    Vignesh Ravikumar

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Emily,

      In CRM MSA 4.0, you might need the laptop connected to the network even when you are not sending/receiving in Conntrans but only importing.

      The error you have posted occurs exactly when the CRM server is contacted fro verifying the structures that have been received at the Mobile client. So we have to check 2 things now:

      1) Check if the laptop is still connected to the network.

      2) Check properties of site assigned to the laptop:

      If you are using XML mode of transfer, check whether you have set the properties correctly:

      a) at the CRM server transaction SMOEAC.

      b) in Mobile client registry HKLM\SOFTWARE\SAP\MSA\MW\TL\UNICODE_ENABLED.

      For XML transfer UNICODE_ENABLED should be 1 and for RFC mode of transfer UNICODE_ENABLED = 0.

      Thank you

      Best Regards

      Jothi

  • author's profile photo Former Member
    Former Member
    Posted on Jul 13, 2009 at 04:25 PM

    Hi,

    We have got the same issue with Contranns when importing the data. So, it sends and receives perfectly but was not able to import. Could you please reply to my message based on the following questions.

    1. Is there any kind of Color do you see when you do a contranns saying that it failed for some BDOC(Such as yellow color which says failed for some BDoc and some kind of red color which says network connectivity).

    2. As far as I understood that you have no problems with contranns and you have a problem only with importing data(where your queue is filled with bigger attachements).

    a) So , can you open your client console and Goto "Actions -> Data Transfer, then click on the Queue manager".Check if there exists any data on Inbound Queue.If there is any data it says processed ='NO' for that following messages which mean that data is received but it says in your local table where you can see the unprocessed messages.

    you can see the unprocessed messages in the table "MW_U_QIN_50" . If it exists you need to apply the following note which solves this kind of issue.

    b) If this could be the case could you please look at the following note . Note 1330433 - ConnTrans OutOfMemoryException during data import phase. Just run the registry file which is contained in the "NO_INTEROP.zip".

    c) Extract the same attachements and test to see it solves the issue.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      thanks for your reply.

      our problem with ConnTrans is only for a particlar kind of bdoc like 'ppr_obj_write'.

      when trying to import these kind of bdocs its giving error in TL Trace file- 'QBlockers found'

      I am not able to find any errors in smw01 for this bdoc.

      Regards,

      Emily.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.