Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 2 of 2
  1. #1
    Join Date
    December 2009
    Location
    Switzerland
    Posts
    439

    Protocol mismatch

    I have a program running on the server that creates tokens, moves users, assigns groups, etc.

    It seems this is causing many errors in the client log
    Code:
    2010-01-26 20:13:16.425535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.425535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.436535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.436535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.446535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.446535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.457535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.457535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.467535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.467535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.477535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.477535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.489535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.489535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.497535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.497535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.508535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.508535	SCHandler	Warning	Error while parsing packet: parameter not found	
    2010-01-26 20:13:16.517535	ParamParser	Error	Protocol mismatch, old client or old server?	
    2010-01-26 20:13:16.518535	SCHandler	Warning	Error while parsing packet: parameter not found
    How can this happen with standard server query?

  2. #2
    Join Date
    January 2010
    Location
    Germany
    Posts
    2,029
    Depending on when you created the program running on your Server you might not have covered changes that happened with the latest betas.

    You could try to manually execute the Commands to see the exact error message that appears for the commands and on which commands they happen. That would help in determining whats going wrong...

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Protocol mismatch, old client or old server?
    By Ar2rJke in forum Linux / FreeBSD
    Replies: 1
    Last Post: June 19th, 2012, 10:13 AM
  2. qt trouble version mismatch
    By obiwahn in forum Bug Reports [EN/DE]
    Replies: 0
    Last Post: May 19th, 2011, 02:21 PM
  3. [Solved] protocol mismatch in sendtextmessage
    By faralsimbor in forum Server Support
    Replies: 4
    Last Post: February 11th, 2010, 12:16 PM
  4. Protocol mismatch Serverlog entrys
    By H4ns! in forum Linux / FreeBSD
    Replies: 2
    Last Post: January 19th, 2010, 11:45 PM
  5. databaseversion mismatch
    By Maxys in forum Windows
    Replies: 4
    Last Post: January 8th, 2010, 02:39 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •