can't see the initial window

Discussion in '3CX Phone System - General' started by zpvgu7608, Jul 4, 2009.

Thread Status:
Not open for further replies.
  1. zpvgu7608

    Joined:
    Jul 4, 2009
    Messages:
    2
    Likes Received:
    0
    I have two machines ,one works well with 3CX Gateway for Skype,but the other has problem.

    After 3CX Gateway for Skype installation steps have been completed,i click Finish on the last screen,i can't see the initial window that will enable you to start the configuration for the Skype Gateway,so i click the 3CXSkypeGateMon.exe,but it says"gateway configuration program is already in use by another computer user,please try again later!",can anyone help me,please?
     
  2. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,479
    Likes Received:
    67
    Hi

    Regarding this message:
    please open a TaskManager, Processes tab, check the "Show processes from all users" on the bottom side, then sort processes by clicking the "Image name" list column header, and verify how many 3CXSkypeGateMon.exe are listed. Now, supposing you're logged on as "zpvgu7608", check the "User Name" column:

    1- if there is only 3CXSkypeGateMon.exe as "SYSTEM", the message box means user "zpvgu7608" has no administrative rights to run the gateway monitor. Therefore, you have to logoff and then logon as an administrator to run the gateway monitor.
    2 - if there is any 3CXSkypeGateMon.exe as "USER_X", that means this user has an active connection to the machine (either by Remote Desktop Connection, either by "Switch user") having the gateway monitor running, so you have to check what's about with that user.

    In any case, if you have administrative rights, you may try to use the force :mrgreen: from Task Manager, try to kill 3CXSkypeGateMon.exe'(s). If you're not able, it means - again - you're not an administrator and you will have to logon as one and then you will go to (1).

    Which OS you're using in this case?

    Regards
    vali
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. zpvgu7608

    Joined:
    Jul 4, 2009
    Messages:
    2
    Likes Received:
    0
    Thank you for your reply!Now the problems have been solved.Because the terminal services is closed,in taskmanage,all user names are blank,now i open the terminal services,all ok .
     
  4. farmerskid

    Joined:
    Sep 4, 2009
    Messages:
    4
    Likes Received:
    0
    same problem: Gateway configuration program is already in us

    error message: Gateway configuration program is already in use by another computer user, please try again later

    Your help would be very much appreciated.

    1. My PC is runninng XP Pro
    2. Installed 3CX Phone System vers. v7.1.7139
    3. Installed 3CX VoIP Phone build v3.8571
    4. Installed 3CX Assistant build v7.1.3438
    5. Installed 3CX Gateway for Skype .msi
    6. Skype is also installed.

    Then I followed the instructions on http://www.3cx.com/voip-gateways/skype.html -

    Everythings seems to install and configure fine.

    The Phone system works perfectly fine and it is going through all the wizard and configuration.

    The GatewayforSkype installed and goes to the final FINISH screen where it asks to LAUNCH.

    Then this error pops up.

    I checked in the WINDOWS TASK MANAGER > PROCESSES > IMAGE NAME and i do see only one
    3CXSkypeGateMon.exe in the task manager.

    I checked MY COMPUTER > MANAGE > LOCAL USERS > USERS > and i see
    Phonesystem__3cx__ and the User (Administrator Permission) for logging in.

    If anyone has any ideas and can help with this - i very much appreicate it.

    Thanks.

    Raymond
     
  5. farmerskid

    Joined:
    Sep 4, 2009
    Messages:
    4
    Likes Received:
    0
    Re: additional info

    I am logged in as Administrator and i can delete the gateway process in the Task Manager.
    I have tried deleting everything and reinstalling everything all over - still same error message.
    I installed skype from skype website - still same problem.
    I followed the instructions exactly - still same problem with subsequent re-install.

    Any help would be appreciated.

    Raymond
     
  6. farmerskid

    Joined:
    Sep 4, 2009
    Messages:
    4
    Likes Received:
    0
    more information :

    FIREWALL checker results:


    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <16:33:59>: Phase 1, checking servers connection, please wait...
    <16:34:00>: Stun Checker service is reachable. Phase 1 check passed.
    <16:34:00>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <16:34:00>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

    <16:34:00>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <16:34:00>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

    <16:34:00>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <16:34:00>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

    <16:34:00>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <16:34:05>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <16:34:05>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <16:34:05>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <16:34:05>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <16:34:05>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <16:34:05>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <16:34:05>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <16:34:05>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <16:34:05>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <16:34:05>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <16:34:05>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <16:34:05>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <16:34:05>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <16:34:05>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <16:34:05>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <16:34:05>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <16:34:05>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <16:34:05>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <16:34:05>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <16:34:05>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <16:34:05>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <16:34:05>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <16:34:05>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <16:34:05>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <16:34:05>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <16:34:05>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <16:34:05>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <16:34:05>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <16:34:05>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <16:34:05>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <16:34:05>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <16:34:05>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <16:34:05>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <16:34:05>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <16:34:05>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <16:34:05>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <16:34:05>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <16:34:05>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <16:34:05>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <16:34:05>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <16:34:05>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <16:34:05>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <16:34:05>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <16:34:05>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <16:34:05>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <16:34:05>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <16:34:05>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <16:34:05>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <16:34:05>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <16:34:05>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


    Application exit code is 0
     
  7. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,126
    Likes Received:
    150
    Hi

    This is definately not related to the firewall. I would assume that you have the main process already running on a different user since you mentioned earlier that this is a terminal services environment.

    It might be better if you paste a screenshot of task manager showing all the processes.

    Also check whether you have a disconnected user. Open task manager, click on users tab, if you see a disconnected user showing there, log of this user. This will close any processes under this session whilst logging off and then re-launch the skype gateway again.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. farmerskid

    Joined:
    Sep 4, 2009
    Messages:
    4
    Likes Received:
    0
    nickybrg,

    THANK UUUUUUUUUUU very much -

    I went to TASK MANAGER, then i looked under user, found a previous 'deleted user' - and
    after i loged off of it, everything started working immediately.

    Thank u again.
     
  9. nb

    nb Support Team
    Staff Member 3CX Support

    Joined:
    Jun 7, 2007
    Messages:
    2,126
    Likes Received:
    150
    No problem

    Good that it works. We will try and include a fix for this when we release the final of version 8.
    When you close a terminal services session, log off - don't just close the rdp session. Failure to do so will leave a disconnected user and its application instances running.

    What we can do is if the application is already launched in the background, under that same user, clicking on the application will re-launch the same instance and simply bring to front. Rgds
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.