Skip to main content
myang888
Participant
May 2, 2008
Question

ConnectError with FMS 3.0.1

  • May 2, 2008
  • 4 replies
  • 725 views
I just installed the FMS 3.0.1 and followed the instruction to create a vobtest under ../application dir

I run the vobtest.hmtl and got ConnectionError with all media under rmtp://localhost/vob/sample.flv ...etc.
So I went to admin console to check and manual loaded vob and live application

The problem is still the same

I checked connection and they showed exact amount I tried to test vobtest.swf

At last, I checked the server log and got this message.

"Fri 12:48:44 PM: Core (2240) connection to admin accepted.
Fri 12:48:50 PM: Core (2512) connection to admin accepted.
Fri 12:51:33 PM: Asynchronous I/O operation failed (Failed to attach to completion port: The parameter is incorrect. 87).
Fri 12:52:08 PM: Asynchronous I/O operation failed (Failed to attach to completion port: The parameter is incorrect. 87).
Fri 12:53:33 PM: Asynchronous I/O operation failed (Failed to attach to completion port: The parameter is incorrect. 87).
Fri 12:54:13 PM: Asynchronous I/O operation failed (Failed to attach to completion port: The parameter is incorrect. 87).
Fri 12:56:22 PM: Asynchronous I/O operation failed (Failed to attach to completion port: The parameter is incorrect. 87).

Does anyone have the same problem? or any solution for this problem.

Thanks.

MYang
    This topic is closed to new replies. Start a new post to keep the conversation going.

    4 replies

    madpat76
    Participant
    June 4, 2008
    I had the same problem:

    If you have IIS installed on this server it grabs all the connections, also the connections on port 1935.
    Solution:

    http://www.flashcomguru.com/tutorials/fcs_iis.cfm
    Anonymous
    May 8, 2008
    It usually happens in following cases.

    1. Antivirus on the affected machine messing up with FMS' socket operations.
    2. any Network analyzer which is interfering with normal operations of FMS.
    3. Mal ware on the system.
    4. Firewalls.

    in all the cases, the best would be to install FMS on a clean/fresh system. however, you may try by uninstaling if you remember having any such software on your machines.
    ajtcf
    Participant
    May 7, 2008
    Hi,

    i'm the same problema.

    my server runs Windows Server 2003

    any ideas ?

    regards from Portugal
    Anonymous
    May 5, 2008
    ohh.. on which operating system you have installed it? is it among Windows XP, 2003 server Or RHEL4 ?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices