cancel
Showing results for 
Search instead for 
Did you mean: 

Contrans SEND problem.

Former Member
0 Kudos

Hi All,

We are using CRM 7.0 MOBILE V5

The client MSA worked well into the 7 july.

Now, the CONTRANS work fine with recieve but Indicate a connection problem with sending issue.

Some one faced the same problem?

Thank you for your help.

regards,

Accepted Solutions (0)

Answers (1)

Answers (1)

rohit_sharma2
Active Contributor
0 Kudos

Hello Ahmed,

Do you mean to say that conntrans works fine when you select only the "receive" checkbox in the Conntrans GUI and throws an error when "send" is also selected?

Maybe you can check TransferService.log(corresponds to SEND phase) kept at %temp% folder to know the cause if this issue.

Thanks,

Rohit

Former Member
0 Kudos

Thank you for your quick response.

where do we activate the SEND and RECIEVE queues? (It could be the origin of the problem)

Where is the %temp% folder?

Otherwise, I think they are both activated from the CRM central.

The contrans work, the SEnd is in orange and recieve is blue (ok)

regards,

Former Member
0 Kudos

In the transfer service (advanced setting) of the conntrans.

SEND and recieve are activated

rohit_sharma2
Active Contributor
0 Kudos

Just type %temp% in RUN command window. And search for TransferService.log

If you can't locate this file inside %temp%, it'll be located inthe folder path specified in the registry key :

HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\MW\TL | string value TL_TRACE_DIR

Former Member
0 Kudos

Thank you.

There is the log :

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

192 298 Thu Oct 21 15:42:43 2010 ! *** Service started

192 298 ! *** Trace level '2'

192 298 ! *** Output file 'C:/DOCUME1/CHATAI1/LOCALS~1/TEMP/TRANSFERSERVICE.LOG'

192 298 ! TransferService internal version 5000 generated Jul 16 2009 at 23:52:58

NewTransferService running on STRES_0052 (192.168. 0. 12) with Windows NT, Vers. 5.1 (Build 2600)

Service Pack 3

192 298 ! Entering GetName

192 298 ! Leaving GetName

192 298 ! Entering AdviseEvents

192 298 ! Leaving AdviseEvents

192 298 ! Entering InitTransactionLayer

192 298 ! *** ATTENTION *** Error popups explicitly switched off by caller -

errors recognized in transferservice only reported in this log file

192 298 ! Transfer mode: Transfer time optimization attempt 20000 msecs, but minimum message transfer rate 20

192 298 ! User is: 'INNOTHERA\CHATAINGM'

192 298 Thu Oct 21 15:42:44 2010 ! Find DB id without dbinfo object (local method invoked)

192 298 ! Leaving InitTransactionLayer after successfull initialization (922 msecs)

192 298 Thu Oct 21 15:42:45 2010 ! Entering PreConnect

192 298 ! Entering BeforeTransfer

192 298 Thu Oct 21 15:42:53 2010 ! Initialization for Site 'DF5D09601C10B7F1AE35005056BB25F7' succeeded, Server version info: - unknown -

192 298 ! Leaving BeforeTransfer with 'OK'

192 298 ! Entering Transfer

192 298 ! Entering PushTransfer

192 298 ! First time: Messages found to send in Outbound Queue: 597 (16 msecs)

192 298 Thu Oct 21 15:42:57 2010 E

ERROR in TransferService - Send: 'Send' call to Communication Station/CRM Server

failed with fffffffb:

(null)

192 298 E

NO ERROR POPUP DISPLAYED !!!

192 298 E

_TransferPushMessages failed with fffffffb

192 298 E

Process modules loaded:

115 modules found in process:

Location Module name File version Prog.version File size File date/time

00400000 C:\Program Files\SAP\Mobile\Bin.NET\ConnTrans.exe 5,13,0,773 5,13,0,773 376902 15. 5.2009 1:22

00af0000 C:\Program Files\TeamViewer\Version5\tv.dll 5, 0, 0, 0 5.0 103720 18. 3.2010 9:37

00b50000 C:\WINDOWS\system32\xpsp2res.dll - - 2986496 13. 4.2008 9:36

01700000 C:\Program Files\SAP\Mobile\Bin.NET\CHTLUtil.DLL 5,13,0,773 5,13,0,773 53248 15. 5.2009 1:21

01980000 C:\Program Files\SAP\Mobile\Bin.NET\ConnectionHandling.dll 5,13,0,837 5,13,0,837 581711 16. 7.2009 21:52

02f20000 C:\Program Files\SAP\Mobile\Bin.NET\TransactionLayerTS.dll 5,13,0,773 5,13,0,773 98304 15. 5.2009 1:22

02f40000 C:\Program Files\SAP\Mobile\Bin.NET\NewQmtClient.dll 5,13,0,837 5,13,0,837 151552 16. 7.2009 21:53

05300000 C:\Program Files\SAP\Mobile\Bin.NET\MsgTransClient.dll 5.13.0.837 5.13.0.837 57344 16. 7.2009 21:47

05450000 C:\Program Files\SAP\Mobile\Bin.NET\MsgTransServer.dll 5.13.0.837 5.13.0.837 98304 16. 7.2009 21:47

05490000 C:\Program Files\SAP\Mobile\Bin.NET\SAP.Connector.dll 2.0.0.25 2.0.0.25 114688 14. 5.2009 22:32

05960000 C:\WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll 2.0.50727.42 (RTM.050727-4200) 2.0.50727.42 114176 19.10.2009 14:52

059a0000 C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\System.EnterpriseSe#\40dadc66ec08aa45a6b7982236369227\System.EnterpriseServices.Wrapper.dll 2.0.50727.42 (RTM.050727-4200) 2.0.50727.42 294912 20.10.2009 8:27

05ba0000 C:\WINDOWS\system32\hccutils.DLL 6.14.10.4977 6.14.10.4977 106496 11. 8.2008 17:23

05be0000 C:\Program Files\SAP\Mobile\Bin.NET\TransferQueues.dll 5.13.0.773 5.13.0.773 28672 15. 5.2009 1:17

10000000 C:\Program Files\SAP\Mobile\Bin.NET\CHUtil.DLL 5,13,0,773 5,13,0,773 389120 15. 5.2009 1:21

11000000 C:\Program Files\SAP\Mobile\Bin.NET\RFCGlue.dll 5.13.0837 5.13.0837 204800 16. 7.2009 21:51

1b5d0000 C:\WINDOWS\system32\MSWSTR10.DLL - - 621344 28. 3.2007 3:56

1f370000 C:\Program Files\Fichiers communs\System\msadc\msadcer.dll - - 20480 28. 3.2007 3:56

rohit_sharma2
Active Contributor
0 Kudos

With the ClientConsole.exe can you try and test the adapter connection to commstation?

And check if You see something like "QmtServer component initialized" in the log that appears on screen.

Former Member
0 Kudos

Thre are all messages:

Trying to access Communication Station 172.23.... please wait

Trying to initialize Qmtserver component, please wait...

QmtServer intialize call returns successfuly. Please wait...

Trying to acces CRM Server (destination"), please wait...

CRM Server call returns successfully

Anther idea: maybe the send queue is too large and cause a time out when the conntrans is initialising transfer process (about 10sec)

Thank you a lot for your time and your valuable help.

rohit_sharma2
Active Contributor
0 Kudos

Initializtion comes even before SEND phase and has got nothing to do with heavy messages. That comes later.

Maybe the send queue(MW_U_QOUT_50 in IDES) is the problem here. Under key HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\NewTransferService\Parameters create a DWORD parameter "TransferRate" with value 10 (decimal). Lower the TransferRate Value if Send still fails.

If the above soln. doesn't work try this :

1036377[Middleware HOTFIX for CommStation] and in addition note 1022089. Specifically check if steps 9 and 11 are applied on the CommStation.

This ensures that the CommStation resources are always freed when it is not used anymore. Re-start the COM+ services to get the changes to effect.

This should help to get ur issue resolved..

Thanks,

Rohit

Former Member
0 Kudos

Ok.Let's go!

Could you explain me how to Re-start the COM+ services at the end?

Big thanks, I'll come to you with results.

Best regards!

rohit_sharma2
Active Contributor
0 Kudos

Restarting the COM+ services is explained in the 2 notes i've mentioned. It can be done by typing 'dcomcnfg' in RUN command and then browsing under Component Services tree till COM+ Applications. You'd see a SAP CRM Transfer Service.