Switch to standard view 
  Sybase logo
 
 
 



When developers try to troubleshoot a particular sync problem in M-Business Anywhere, they generally start looking into the sync log to get some idea of what the problem might be. But, they may face a problem of not understanding the meaning of the error messages that get generated.

Required software

  1. M-Business 6.x
  2. Pocket PC, Desktop

Errors

Error 1
 [Tue Jun 12 07:54:57 2007] [error] [client 198.203.175.175] (32)Broken pipe: mod_iaredirect: socket write error: 32
[Tue Jun 12 07:54:57 2007] [error] [client 198.203.175.175] (32)Broken pipe: mod_iaredirect: error sending posted data to ML server

Explanation: Communication between the redirector and MobiLink is down.
MobiLink is a synchronization server that allows you to synchronize your mobile device with your back-end database.

 

Error 2
[Wed Jun 20 13:33:34 2007] [warn] (26267) Fetching sync event URL [http://localhost:8091/device/start.jsp] failed.
[Wed Jun 20 13:33:36 2007] [warn] (26267) TIMED: fetching: never finished

Explanation: The M-Business Anywhere Sync server could not fetch the device UI start page. It is likely that either the admin server is busy (for example it timed out) or it is down.

 

Error 3
[Mon Jul  2 09:43:43 2007] [warn] (11876) Sync ending with error message: code==1, message==Please upgrade your AvantGo software by visiting http://prodserver:8091/admin/install user=11111

Explanation: This message usually means that an unsupported client is syncing to the server. It could also occur because client version record on the device was corrupted. A refresh-all sync should fix the problem.

 

Error 4
[Thu Jul 12 10:22:23 2007] [warn] (19489) Sync ending with error message: code==1, message==Invalid login.  Please check your username and password and try again. user=ali

Explanation:  The client provided an incorrect user ID/password pair.

 

Error 5
[Wed Jul 25 06:19:27 2007] [error] [client 58.150.210.187] client sent HTTP/1.1 request without hostname (see RFC2068 section 9, and 14.23): /w00tw00t.at.ISC.SANS.DFind

Explanation: This is an Apache error message. It is the result of someone running an auto-port scanning script against the sync server port 80.

 

Error 6
[Wed Jul 25 07:59:19 2007] [error] [client 10.7.160.21] (145)Connection timed out: proxy connect to 192.168.128.193 port 8091 failed

Explanation: The admin server is busy or down. For example, if you write scripts to perform monitoring against the servers by issuing a ping against a URL that is on the admin server, but is proxied through the sync server, This would be why the error appears in the sync_error.log file.

 

Error 7
[Tue Jun 26 04:53:47 2007] [error] [client 10.8.120.11] (131)Connection reset by peer: ap_bgets() - proxy receive - Error reading from remote server ddcwxpcld02 (length -1

Explanation: A connection drop occurred.

 

Error 8
[Fri Jun 29 20:15:34 2007] [error] (25639) ASA: retcode(): invalid type or handle
[Fri Jun 29 20:15:34 2007] [error] (25639) ASA: fatal error: can't open ODBC data source 'AGDB_80

Explanation: The M-Business Anywhere Sync server lost its ASA database connection.
ASA (Adaptive Server Anywhere) is the back-end database where configuration and user information is stored.


Back to Top
© Copyright 2010, Sybase Inc.