Protocol Error 6410
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
long idle Wrist PDA, I ran into HotSync error 6410 - connection lost. Palm's knowledge base had some suggestions, however, none of their workarounds resolved my problem. Instead, the problem went away by enabling just the "Local USB" connection (and disabling the other "Local", "Modem", and "Network" connection types by right clicking on the HotSync menu in the System tray). Like this:Like Loading... Related Posted in Fun, Palm OS. 1 Comment » One Response to "Fixing HotSync https://groups.google.com/d/topic/comp.sys.palmtops/EjnsxTn8jWw Manager 6410 Error - ConnectionLost" Hotsync 6410 | Gotcustomers Says: March 13, 2012 at 3:27 am […] Fixing HotSync Manager 6410 Error - Connection Lost « MusingsMay 6, 2010 … While reviving my long idle Wrist PDA, I ran into HotSync error 6410 - connection lost. Palm's knowledge base had some suggestions, however … […] Reply https://markwarren.wordpress.com/2010/05/06/fixing-hotsync-manager-6410-error-connection-lost/ Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. « Why the iPad Succeeds Where OthersFailed… Sprint TV Streams ESPN World Cup forFree » Proudly powered by WordPress Archives May 2015(1) September 2014(1) July 2014(1) January 2014(1) July 2013(1) June 2013(2) May 2013(1) April 2013(2) February 2013(1) January 2013(1) November 2012(2) September 2012(1) August 2012(1) March 2012(1) February 2012(1) October 2011(2) August 2011(1) July 2011(1) June 2010(1) May 2010(1) April 2010(1) March 2010(2) December 2009(1) October 2009(1) August 2009(1) April 2009(1) December 2008(2) September 2008(1) August 2008(2) Search Amazon Amazon.com Widgets Blogroll Mark Warren McInblog Well-to-Wheel WordPress.com Blog at WordPress.com. %d bloggers like this:
further replies. Page 1 of 2 1 2 Next > rvanbeek Mobile Enthusiast Messages: 10 Likes Received: 0 Trophy Points: 1 I've got a Palm tx http://forum.brighthand.com/threads/palm-tx-windows-7-compatibility.281559/ and desktop 6.2 on a Windows 7 64bit computer. I have followed the http://www.yqcomputer.com/762_3978_1.htm procedure for syncing via wifi and it makes a connection but I am not getting any information transfered to the desk top from the tx. What am I doing wrong. rvanbeek, Mar 29, 2011 #1 BAB2000 An "Olde Moderator" #2 Super Moderator Messages: 13,427 Likes Received: 139 Trophy Points: 258 Palm desktop and protocol error hotsync manager are not compatible with any 64 bit operating system. Can you set Windows 7 to operate the Palm software under compatibility mode for a earlier OS that is 32 bit functional? Welcome to Brighthand The Three Rs of Life - Respect for self, Respect for others, and Responsibility for your own actions. "Life isn't like a box of chocolates....it's more like a jar of protocol error 6410 jalapenos.What you do today might burn your backside tomorrow!" BAB2000, Mar 29, 2011 #2 rvanbeek Mobile Enthusiast Messages: 10 Likes Received: 0 Trophy Points: 1 would it be possible to run in 32 mode, or reboot in xp mode for the desktop and sync. rvanbeek, Mar 29, 2011 #3 RickAgresta Peanut, leader of the Peanutty Forces Messages: 18,038 Likes Received: 8,042 Trophy Points: 288 would it be possible to run in 32 mode, or reboot in xp mode for the desktop and sync.Click to expand... from what I've read, that should work; guessing, I'd think the reboot in xp mode would be a more sure thing (only if xp is 32-bit, of course) My useful BH links -- BH FAQS/repair options/digitizer discussions "Friends are the Fambly we choose" ~Shared pain is diminished, shared joy is increased inanimate objects are smarter than we give them credit for~our lives are too short to not help others ~when you find a big kettle of crazy, it's best not to stir it Dilbert 9/22/09 ~ making no decision is really making the choice to do nothing, about something ~The organic spell-checker is nearly 100% accurate, but sometimes, it just doesn't care. Ri
could benefit, directly or via Google. I couldn't get my Palm Tungsten|E2 to HotSync correctly. Whenever I plugged in the HotSync cable, the HotSynce would start automatically, whether or not I wanted it to or did anything to make it start. The HotSync would only go a little into the process and would then freeze, displaying a blinking line at the top of the screen. A soft boot was needed to recover from this. The HotSync log displayed the message: "HotSync session completed with errors - Protocol Error: Unknown error. (6410)" Turned out the root cause was a bad / damaged HotSync cable. I happen to have three HotSync cables for my E2. The one I use by default (and therefore the most) gave the problem. When I happened to try one of my other HotSync cables, more or less by chance, the HotSync ran properly and finished without error. Tried my third HotSync cable - same story. The HotSync ran properly and finished without error. Hope this proves useful to someone else. Bob Pownall Top 1. Protocol Error: Unknown error. (6410) 2. Query error: Protocol error in TDS stream/Unknown token received I have had some users contacting me and reporting this error message when refreshing SQL Server queries in their Excel 2003 spreadsheets: "Unknown token received from SQL Server" They are using Excel installed on a Citrix server. My locally installed Excel 2003 returns this error message when refreshing the same spreadsheets: "Protocol error in TDS stream" If I open the query, it will return the query data to MS Query, but not to Excel. The query I have been looking at is very simple. It has one ORDER statement in it. If I remove this ORDER statement, the query works. If I put it back again, it fails as above. The only errors I can find in the SQL Server logs are: "Error: 15457, Severity: 0, State: 1" Followed by: "Process 12:0 (840) UMS Context 0x00278480 appears to be non-yielding on Scheduler 0." This is SQL Server 2000 and is service packed up to SP4. The only other thing I can think of is that we had a serious hardware error on our Windows 2000 Server primary domain controller last Friday which also housed our network profiles and we had login problems most of that day. This SQL Server problem appears to have appeared since then. I've gone through the Knowledgebase, but most of the stuff on there suggests installing the latest service pack, which the server already has. Anyone with some brilliant ideas? Many thanks. 3. Query error: Protocol error in TDS stream/Unknown token receiv 4. "unknown mailer error 4" "unknown mailer error 32" 5. UNKNOWN ERROR WHEN IT SAY UNKNOWN ERRO