Results 1 to 9 of 9

Thread: error : architect cannot start one of its internal parts.

  1. #1
    Sencha User
    Join Date
    Oct 2016
    Posts
    14

    Default Answered: error : architect cannot start one of its internal parts.

    Sencha Cmd service cannot be launched, it uses a local port which is occupied by another application .
    i don't even know the port.
    how can i know the port.

    thank you.Screenshot.png

  2. Hello

    This can happen when there is problem with start up of Sencha Cmd (does not start-up at all, starts with errors, very slow start)
    The Cmd should be located at:
    Code:
    C:\Users\<user>\bin\Sencha\Architect\Cmd\6.2.0.103
    You can try to open this folder in windows command line and run:
    Code:
    sencha.exe service start --port 0
    The service should start without any errors.

    Also if you ware on Windows 8+, you can check the disk utilization in the task manager. Sometimes it can happen that Windows is currently installing updates, antivirus is doing something or some other program is heavily using disk. This can lead to very delayed start-up of the Cmd and SA thinks that Cmd is not working.

    Does this happens every-time you start SA?

    Please report if you were able to resolve the issue / what exactly was the problem.

    Thank you
    Petr

  3. #2
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985
    Answers
    506

    Default

    Here's a similar thread which I hope will help.
    https://www.sencha.com/forum/showthread.php?329917

  4. #3
    Sencha User
    Join Date
    Oct 2016
    Posts
    14

    Default

    thank you,
    i already upgraded sencha cmd to 6.0.2, and i have Architect 4.0.2 but the problem is always the same.
    should i de-install and re-install Architect ?

    Best regards

  5. #4
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985
    Answers
    506

    Default

    Do you mean Cmd 6.2.0? You might try re-installing Architect since it seems to have helped another user.

  6. #5
    Sencha User
    Join Date
    Sep 2014
    Location
    Central Europe
    Posts
    795
    Answers
    103

    Default

    Hello

    This can happen when there is problem with start up of Sencha Cmd (does not start-up at all, starts with errors, very slow start)
    The Cmd should be located at:
    Code:
    C:\Users\<user>\bin\Sencha\Architect\Cmd\6.2.0.103
    You can try to open this folder in windows command line and run:
    Code:
    sencha.exe service start --port 0
    The service should start without any errors.

    Also if you ware on Windows 8+, you can check the disk utilization in the task manager. Sometimes it can happen that Windows is currently installing updates, antivirus is doing something or some other program is heavily using disk. This can lead to very delayed start-up of the Cmd and SA thinks that Cmd is not working.

    Does this happens every-time you start SA?

    Please report if you were able to resolve the issue / what exactly was the problem.

    Thank you
    Petr

  7. #6
    Sencha User
    Join Date
    Oct 2016
    Posts
    14

    Default

    Hello petr,

    i'm using SA since 5 days ago and this happens just today morning and it happens every-tiem i start SA.
    i'm using window 10, and i think that it happens because of windows defender.
    after running the command line, the service start with an other error, (port 63553 is currently occupied by java.exe [496]).

    Thank you,
    Best regards
    sencha.exe service start --port 0

  8. #7
    Sencha User
    Join Date
    Oct 2016
    Posts
    14

    Default

    I will try by re-installing SA tonight,
    Thank you.

  9. #8
    Sencha User
    Join Date
    Sep 2014
    Location
    Central Europe
    Posts
    795
    Answers
    103

    Default

    Also don't forget try to restart your computer. Also have you tried to click on ignore button and proceed to your project? It probably won't work but you can give it a try. You can open your project and check the output log window on the bottom if you see any stats output from Sencha Cmd.

  10. #9
    Sencha User
    Join Date
    Oct 2016
    Posts
    14

    Default

    Oh, it works with any errors now, i runned :
    sencha.exe service start --port 1841.

    Thank you.

Similar Threads

  1. Replies: 6
    Last Post: 19 Apr 2016, 1:52 AM
  2. 500 (Internal Server Error)
    By clebersm in forum Sencha Touch 2.x: Q&A
    Replies: 2
    Last Post: 17 Aug 2012, 8:00 AM
  3. 500 Internal Server Error
    By andylah in forum Ext 3.x: Help & Discussion
    Replies: 2
    Last Post: 19 Jan 2012, 4:47 PM
  4. Internal compiler error -> GXT 2.2.1 + GWT 2.2.0, bug?
    By vielinko in forum Ext GWT: Discussion
    Replies: 9
    Last Post: 22 Mar 2011, 8:52 PM

Tags for this Thread

Posting Permissions

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