Page 3 of 3 FirstFirst 1 2 3
Results 21 to 27 of 27

Thread: Command Workstation 5.5.035 will not launch on Mac

  1. #21
    Join Date
    Nov 2013
    Posts
    13

    Default

    On your advice, after it failed to boot up again, I blocked 69.16.143.107 with LS but it didn't force it to work. Hopefully now that it is blocked it won't cause it to fail again.

    Can I ask how you knew what IP address you needed to for this to work? Might the address be different on my iMac?

    I have a real problem with CWS, I can't get it to quit and I have to force quit and now and again it won't load so I have to remove the EFI Rel3.Fiery Command WorkStation.dj file get it to work again.

    David

  2. #22
    Doyle is offline Fiery Forum Expert Contributor Doyle is on a distinguished path
    Join Date
    Apr 2010
    Posts
    256

    Default

    After I updated to 5.5.0.35 I am getting a hang at this address 198.105.251.20

    For those of you that want to check this. Open Activity Monitor before you open Command Workstation.

    When you open Command Workstation go to Activity Monitor and select Command Workstation if it is hanging then click on the Inspect icon at the top. Then choose Open Files and Ports in the Inspect window. At the bottom of the list you will see the ip address it is trying to connect to.
    Last edited by Doyle; 12-27-2013 at 12:00 PM.

  3. #23
    Join Date
    Nov 2013
    Posts
    13

    Default

    OK it's happening again and I've just had a look in Activity Monitor and clicked on CWS and the Open Files and Ports setting. Here are the last few lines of the code...

    ->0x470d58740d5c06db
    ->0x470d58740d5bfc8b
    192.168.1.72:51979->192.168.1.188:intu-ec-client
    192.168.1.72:51980->192.168.1.188a-system
    ->0x470d58740d5bee1b
    ->0x470d58740d5bed6b
    192.168.1.72:51981->192.168.1.188:intu-ec-client
    192.168.1.72:51982->192.168.1.188a-system
    ->0x470d58741b43172b
    ->0x470d58740d5bec0b
    192.168.1.72:52022->192.168.1.188:gds_db
    /private/var/folders/wr/k72mrdd15yb4xwdn07bpddgm0000gn/T/xdo4z4PXR
    /private/var/folders/wr/k72mrdd15yb4xwdn07bpddgm0000gn/T/xdo4z4PXR.lob


    I can see my IP address for the RIP which is 192.168.1.188 but not sure what the other address is and not sure which one I need to block in LS to make this work.

    Some assistance would be greatly appreciated.

  4. #24
    Doyle is offline Fiery Forum Expert Contributor Doyle is on a distinguished path
    Join Date
    Apr 2010
    Posts
    256

    Default

    Is what you posted while it is hanging. If it is I would try repairing permissions.

    When I get the hang the IP address in question is the last entry with a port number after it.

    What you posted I see after it has completely booted.

    Funny thing is, I have 5.5.035 on another 10.8.5 mac here that does not hang and I don't see it looking for that IP address either.

  5. #25
    Join Date
    Nov 2013
    Posts
    13

    Default

    Thanks for your help so far, I'm still struggling to get CWS to quit naturally.

    CWS boots fine, it's just quitting the app is where the problem is and I end up having to force quit to kill it. I've been checking the Activity Monitor as CWS boots up and here are the last 7 lines of code...

    192.168.1.104:52817->192.168.1.188:intu-ec-client
    192.168.1.104:52855->192.168.1.188:gds_db
    192.168.1.104:52818->192.168.1.188a-system
    ->0x3c46d43b38f28391
    ->0x3c46d43b38f284f1
    /private/var/folders/wr/k72mrdd15yb4xwdn07bpddgm0000gn/T/xdoroRW73
    /private/var/folders/wr/k72mrdd15yb4xwdn07bpddgm0000gn/T/xdoroRW73.lob

    Then when I press Cmd Q to quit CWS, nothing happens in the app and nothing happens in Activity Monitor. Then I force quit CWS and the Open Files and Ports window in AM goes away as it can't see CWS open any longer.

    I had already blocked port 69.16.143.107 and now I have blocked port 192.168.1.104 in Little Snitch...
    Name:  192.168.1.104-block.jpg
Views: 1833
Size:  43.1 KB
    but still it won't quit without forcing it.

    The only other visible port in AM is the IP address that the CWS is connected to...
    192.168.1.188
    but I'm reluctant to block that in case it prevents CWS working at all, would I be correct in my assumption?

    I hope you can resolve this for me as it's quit frustrating.

  6. #26
    Doyle is offline Fiery Forum Expert Contributor Doyle is on a distinguished path
    Join Date
    Apr 2010
    Posts
    256

    Default

    If CWS boots fine with 69.16.143.107 blocked then there is nothing else you can do as that was only for when booting hangs.

    As for not quitting I haven't a clue, but I do have that problem sometimes.

  7. #27
    Join Date
    Nov 2013
    Posts
    13

    Default

    Maybe somebody else can help me?

Page 3 of 3 FirstFirst 1 2 3

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