Welcome, Guest
  • Author Topic: NetConnection.Call.BadVersion  (Read 18822 times)

    Ben L.

    • Server what's that
    • *
    • Posts: 4
      • View Profile
      • Email
    NetConnection.Call.BadVersion
    « on: 03/12/03, 12:11 »
    I've tried a few different examples and variations of PHP Remoting and always get this error in the Net Connection Debugger (NetConnection.Call.BadVersion). Even when I've used the 'ready to go' Google web service example. Does anyone know anything I can check or do differently?

    Ben L.

    • Server what's that
    • *
    • Posts: 4
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #1 on: 03/12/03, 17:17 »
    Can I clarify my problem better, or has nobody seen this before? (Sorry, I'm just impatient.)

    Jorge Solis

    • Global Moderator
    • Systems Administrator
    • *****
    • Posts: 14616
      • View Profile
    Re:NetConnection.Call.BadVersion
    « Reply #2 on: 03/12/03, 17:47 »
    This problem was reported in the developpers list

    Quote
    Whats needed is an example specific to the current CSV, the example AS code in both
    the registered.php and discovery.php files sets up services that no longer exist, ie. the 'myservice' and 'typedservice'


    Check last files in CSV

    Jorge

    Ben L.

    • Server what's that
    • *
    • Posts: 4
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #3 on: 03/12/03, 17:57 »
    Thanks for pointing me in the right direction! I'll dig through the information in the CVS.

    Thanks Again,
    BenL

    ev

    • Global Moderator
    • Systems Administrator
    • *****
    • Posts: 502
      • View Profile
    Re:NetConnection.Call.BadVersion
    « Reply #4 on: 03/14/03, 18:38 »
    strange,
    i just installed the flash remoting updater and...low and behold
    i get that same bad version error in the net connection debugger.

    Micha

    • Server what's that
    • *
    • Posts: 7
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #5 on: 03/15/03, 05:07 »
    yep, i experienced the same problem.

    when i call a service-method which does not exist, onStatus fires as supposed with the appropriate error-message.

    if there i.e. is a syntax-error in my class, onStatus does not fire but i get the "NetConnection.Call.BadVersion" error in the nc-debugger.

    strange...

    micha

    Micha

    • Server what's that
    • *
    • Posts: 7
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #6 on: 03/15/03, 05:29 »
    p.s.:

    the php-version installed on my pc is 4.2.1 and i have installed the remoting updater.

    i will update the php-version to 4.3.1,  maybe this will solve the problem.

    micha

    ev

    • Global Moderator
    • Systems Administrator
    • *****
    • Posts: 502
      • View Profile
    Re:NetConnection.Call.BadVersion
    « Reply #7 on: 03/15/03, 10:27 »
    lets us know how that works out, micha

    Micha

    • Server what's that
    • *
    • Posts: 7
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #8 on: 03/15/03, 11:32 »
    updating the php version to 4.3.1 did not help a bit. the problem described above still exists, at least on my wamp.

    another test:

    lamp, php 4.2.3 -> the same problem here.

    hm... ???

    micha


    « Last Edit: 03/15/03, 11:33 by Micha »

    ev

    • Global Moderator
    • Systems Administrator
    • *****
    • Posts: 502
      • View Profile
    Re:NetConnection.Call.BadVersion
    « Reply #9 on: 03/15/03, 11:45 »
    well i know the following:
    i ran php 4.2 and i had the original remoting components and amf-php
    everything worked
    i updated to the new remoting components
    not working
    i updated all my amf-php files and read the docs and made sure i had the amf-php set up correctly
    not working
    upgraded to php 4.31
    not working
    ev

    Micha

    • Server what's that
    • *
    • Posts: 7
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #10 on: 03/15/03, 11:58 »
    hi ev!

    by saying 'not working', do you mean the services do not work at all or does only onStatus not get fired when there is a syntax error in the class file?

    everything works and has worked fine for me except this strange exception problem.

    i also updated the remoting components and i thought this would update some of the .as files as well. ok, it did not - all the .as files in my include directory have a 'last modified' date of 2002.

    i am pretty sure i compiled the swfs on my lamp system before i updated the remoting components but i have the same problem there.

    micha



    ev

    • Global Moderator
    • Systems Administrator
    • *****
    • Posts: 502
      • View Profile
    Re:NetConnection.Call.BadVersion
    « Reply #11 on: 03/15/03, 12:49 »
    when i say "not working" i mean, in net connection debugger
    it registers that i call the remoting methods, and then it says NetConnection.call.BadVersion.  no data is returned in the net connection debugger.
    my onResult handlers do not get called, nothing happens.
    « Last Edit: 03/15/03, 12:50 by ev »

    Micha

    • Server what's that
    • *
    • Posts: 7
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #12 on: 03/15/03, 13:08 »
    hm...

    do you think replacing the updated remoting .as files with the older ones would be worth a try?

    i still have the old .as files if you need them.

    moreover i think i still have the first release of the mm remoting components installer file for win32 systems.

    micha

    ev

    • Global Moderator
    • Systems Administrator
    • *****
    • Posts: 502
      • View Profile
    Re:NetConnection.Call.BadVersion
    « Reply #13 on: 03/15/03, 13:12 »
    yeah, im gonna try doing that.  but i'd like to know why this is happening.

    Micha

    • Server what's that
    • *
    • Posts: 7
      • View Profile
      • Email
    Re:NetConnection.Call.BadVersion
    « Reply #14 on: 03/15/03, 13:19 »
    yeah, me too.

    what about not using NetService.as but only NetConnection to call the services?

    does this help?

    micha