Skip to Content
0
Former Member
Sep 21, 2011 at 07:07 PM

Error client communication sup 2.0.1

24 Views

Help guys!!!!!

When I tried communicated with sup 2.0.1 the connection was stabilised but any callbackevent did not occurs in my application (I use message based application with DOE)

I think this is the error:

Note that a MOCA Async object was not registered on the device. This is not an error if the callback was not important. Object Name:

anybody know how fix it or why this occurs?

bellow the MOCA (sybase settings log)

05T170016, T4,         10| OPENED DATABASE VERSION 22. REQUIRED VERSION22.
05T170016, T4, Got request from server - RequestID = 53
05T170016, T4, Found results from previous MOCA request for RequestID = 53
05T170016, T5, Connect--Fixedup URL: /tm/?cid=0
05T170016, T5, Connected D2S connection
05T170016, T5, 	ParseTMPublicHeader succeeded 
05T170016, T5, Got Results from server for ReqID: 6
05T170016, T5, 5627, 0 Note that a MOCA Async object was not registered on the device. This is not an error if the callback was not important.  Object Name: 'GetDeviceSettings' 
05T170016, T5, Client side processing finished for ReqID: 6
05T170017, T5, Processing Queued request.  ReqID: 7  Obj: monet:SettingsExchange.dll:SettingsExchange  Meth: SetServerPropGroup
05T170017, T5, 	ParseTMPublicHeader succeeded 
05T170017, T5, Got Results from server for ReqID: 7
05T170017, T5, 5627, 0 Note that a MOCA Async object was not registered on the device. This is not an error if the callback was not important.  Object Name: 'SetServerPropGroup' 
05T170017, T5, Client side processing finished for ReqID: 7
05T170017, T5, Disconnected D2S connection
05T170018, T5, Disconnected D2S connection