Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

no-fms error

daveyha
Level 2
Level 2

Hi-

I've done external auth for my room, and it seems to be working fine (from a network trace, the ticket it gets has the correct display name and user name).

However, when AFCS then tries to get a FMS ticket, I get the following error:

AFCS Beta Build # : 1.02
requestInfo http://connectnow.acrobat.com/[removed but it contains the room name, exx=some base 64 string, mode=xml and x=0.56...]
Warning: Ignoring 'secure' attribute in policy file from http://connectnow.acrobat.com/crossdomain.xml.  The 'secure' attribute is only permitted in HTTPS and socket policy files.  See http://www.adobe.com/go/strict_policy_files for details.
Warning: Domain connectnow.acrobat.com does not specify a meta-policy.  Applying default meta-policy 'master-only'.  This configuration is deprecated.  See http://www.adobe.com/go/strict_policy_files to fix this problem.
#TicketService# ticket received: 15aqb3o1dpjq6
Getting FMS at https://na2.connectnow.acrobat.com/fms?ticket=15aqb3o1dpjq6, attempt #1/3
result: <fms>
  <error>no-fms</error>
</fms>
Error: no-fms
        at com.adobe.rtc.session.managers::SessionManagerBase/receiveError()
        at com.adobe.rtc.session.managers::SessionManagerFMS/receiveError()
        at com.adobe.rtc.session.managers::SessionManagerAdobeHostedServices/receiveError()
        at com.adobe.rtc.session.managers::SessionManagerAdobeHostedServices/onLoaderComplete()
        at flash.events::EventDispatcher/dispatchEventFunction()
        at flash.events::EventDispatcher/dispatchEvent()
        at flash.net::URLLoader/onComplete()

After that, my app just does nothing (the ConnectSessionContainer never completes).
I guess I'm doing something wrong and it's probably obvious to anyone else. Do you have any ideas?

Many thanks

David

1 Accepted Solution
Raff_
Correct answer by
Employee
Employee

First of all, it always help if you can post information about the URL for the room that failed, it makes my life much easier

Anyway, this was a tricky one: the reason why you got no-fms is because you managed to create a room with a name that FMS doesn't accept (my fault for letting you do that ) so the error wasn't really "there is no FMS server available" but more a "there is no FMS that wants to talk to you"

Anyway, looks like you are using rooms with a name that looks like has some data converted to base64. In this particular case the room name ended with "==" (the base64 padding characters) and that makes it an invalid instance name for FMS. I was able to reproduce the problem by using your room name, and I was able to connect to FMS after creating a new room with the same name minus the '==' characters.

I'll add a bug report to make sure we don't accept room names that are invalid FMS instance names, but in the mean time just make sure you remove the trailing '=' from your names or use a different encoding scheme (hex characters ?)

View solution in original post

2 Replies
Raff_
Correct answer by
Employee
Employee

First of all, it always help if you can post information about the URL for the room that failed, it makes my life much easier

Anyway, this was a tricky one: the reason why you got no-fms is because you managed to create a room with a name that FMS doesn't accept (my fault for letting you do that ) so the error wasn't really "there is no FMS server available" but more a "there is no FMS that wants to talk to you"

Anyway, looks like you are using rooms with a name that looks like has some data converted to base64. In this particular case the room name ended with "==" (the base64 padding characters) and that makes it an invalid instance name for FMS. I was able to reproduce the problem by using your room name, and I was able to connect to FMS after creating a new room with the same name minus the '==' characters.

I'll add a bug report to make sure we don't accept room names that are invalid FMS instance names, but in the mean time just make sure you remove the trailing '=' from your names or use a different encoding scheme (hex characters ?)

View solution in original post

daveyha
Level 2
Level 2

Great, thanks - that works a treat.

Apologies for not putting the room URL in.