SCOUG-HELP Mailing List Archives

Date:	Sun, 23 May 2004 13:31:31 PDT7
From:	Tom Brown <thombrown@san.rr.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: jSyncManager error

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> In <40AFE532.6090204@san.rr.com>, on 05/22/04
> at 04:41 PM, Tom Brown said:
>
>
>>[G:\tools\jsyncmanager]java -jar jsyncmanager.jar
>
>
> FWIW, the tee utility is your friend here. It captures messages and lets
> you see them at the same time. I use it with:
>
> java blah blah | tee tmp.out

I have NOT been able to make tee produce anything with jSyncManager. I
just get a zero-length file after it ends. :-( I also tried:
java -jar jsyncmanager.jar > temp.out 2>&1
with the same results.

>>java.util.MissingResourceException: Can't find bundle for base name
>>org.jSyncManager.Conduit.Resourc
>>es.Text.DefaultConduitResources, locale en_US
>
>
> Try:
>
> SET LANG=EN_US

I have tried both en_US and EN_US, no change. :-(

> Java is very case sensitive.
>
>
>>I have the API installed in
>
>
>>D:\java131\jre\lib\ext\jsyncmanager-api.jar
>
>
> You don't need this. jsyncmanager.jar contains it along with the default
> jConduits. The API jar is for those writing custom apps that don't need
> the jSyncManager UI.

I removed D:\java131\jre\lib\ext\jsyncmanager-api.jar. Now jSyncManager
starts, and I get the GUI. Still won't sync. I tried the --comm-api-test
thingy. Hmmm, errors. OK, I had the cable going thru a switch so I could
change it over to my other system. Connected it directly to my main
system. The --comm-api-test thingy now works! Hey some progress!

I still get a zero-length file with logging attempts as above, but the
jSyncManager log shows:

Waiting for Wakeup.
Synchronization started at: Sun May 23 12:22:37 PDT 2004
Starting Synchronization Session...
Retrieving System Info.
Handheld Owner: thombrown
Retrieving Storage Info.
Synchronizing Date/Time
Retrieving Database Info...
Starting Synchronization Session...
Backing up flagged Databases
Backing up Database: Transfer
Backing up Database: psysLaunchDB
Backing up Database: Graffiti ShortCuts
The default jConduit caught an exception:
org.jSyncManager.API.Conduit.ConduitHandlerException:
org.jSyncManager.API.Protocol.DLPFunctionCallException: *** Caught DLP
Error number 5 in JHotSync.openDatabase()
Finalizing Synchronization...
Synchronization Successful!
Total Synchronization Time: 0:0:28.244
===================================
Waiting for Wakeup.

Now the questions: What is DLP, and where can I find out about this error?

Thanks!

--
Tom Brown
thombrown at san dot rr dot com
Member SCOUG, V.O.I.C.E. & SDAA
running eComStation GA + FP 3
eCS system uptime is 0 days 00:42 hours

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 23 | May | 2004 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.