Resing MAX will not connect no matter what - AI Engine Unreachable

General Discussions
22

Hi. I’ve figured out a more reliable method, so I’ll share that with you.

(Preparation)

(1) First, open the most recent log file in the /Users/Library/Application Support/IK Multimedia/ReSing/ReSingEngine/logs folder to see which port your Mac(ReSing) is attempting to use. In my setup, it was port 50000, but I think it’s probably the same for everyone.
By the way, since the Library folder is hidden, if you can’t find it in Finder, you’ll need to press Command+Shift+. (period) to make it visible .

(2) Next, make sure to have the Terminal window open. Launch ReSing, and when you see the “Starting AI Engine” screen, switch to the Terminal window to perform the operation .

(Practical Step s)

(3) Launch ReSing and, while waiting for the AI Engine to start, run the following command in the termin al:

sudo lsof -P -i :50 000

* If the port number is not 50000, please change it to match your environm ent.

This should list the components currently using port 50000.

Pay attention to the component name in the far left column and the PID immediately next to it. (The PID is usually a 2- to 4-digi t number.)

Next, use the following command to stop every component except Resing one by one:

sudo kill -9 PID

(4) If you can close all components other than Resing while Resing is searching for the AI Engine, Resing should launc h shortly.

(5) In my environment, port 50000 is frequently accessed by printer-related software, which causes interference. Therefore, the steps described above are not a one-time fix; if Resing fails to start, you have to repeat the same procedure (using `lsof` and `kill`) each time.

I hope this helps more people get Resing up a nd running.

23

Thank you so much for taking the time to write such a detailed explanation and workaround!

I have exactly the same issue on one of my MacBook Pros, so your findings are extremely valuable. I haven’t had the chance to test your method yet, but I definitely will as soon as possible.

It’s also very interesting to know that other software, such as printer-related services, can interfere with port 50000. Hopefully IK Multimedia will address this properly in a future update, but in the meantime your workaround could be a real lifesaver.

Thanks again for sharing your research and helping the community!

24

I’ve been having a similar problem in Windows 10.

I’ve tried to view the log files in the directory:

C:\Users\xxxxxxx\AppData\Roaming\IK Multimedia\ReSing\ReSingEngine\logs

The files in there have the extension .cry and these are not read properly by Phoenix Code (or Notepad), Phoenix Code is what I usually use to read code and log files in text formats.

  • By the way - I have replaced my username with xxxxxxxx in the directory I’ve pasted above. Every PC will have the (probably unique) username of their account where I’ve replaced with the xxxxxxxx string.

I don’t think it’s an encoding problem. Phoenix recognises all the standard text encodings by default if you open the file from within Phoenix (rather than drag and drop). Still no joy reading the logs, however.

By the way, I have uninstalled and reinstalled ReSing, but it was still stuck at the connection error message.

Port 50000

To view ports in use, I open a Command Window (type cmd into the search bar) and, just to ensure I have full access, I click on the ‘open as administrator’ selection line.

In the command window that comes up, I typed:

netstat -ano | find “LISTEN”

This command gives me a list of the ports in use, but 50000 was not in the list.

To be sure, I typed:

netstat -an | find “:50000”

Which searches specifically for the 50000 port. Nothing came up. So the port wasn’t in use, my problem was different to the one Mac users have been having in this thread.

SOLUTION!

Having another look at the ReSing directory, I found a file:

lock.txt

This was in the directory:

C:\Users\xxxxxxxx\AppData\Roaming\IK Multimedia\ReSing\ReSingEngine

I renamed it to:

lock.txt.OLD

Bingo!

ReSing had crashed badly in a previous build and apparently it left the lock.txt file in place.

The next time I opened ReSing, it came up perfectly and once it was running, it created a new lock.txt file. I deleted the file I’d renamed to lock.txt.OLD.

Now I’m going to try to use the app in anger again! Assuming it doesn’t crash, it should delete the lock.txt file when it closes. If it does crash and leaves the file, I will just delete it.

TLDR - A Windows fix (Win 10, but it should work in 11)

Replacing xxxxxxxx with your username on the Windows PC you are using, open the following directory/folder:

C:\Users\xxxxxxxx\AppData\Roaming\IK Multimedia\ReSing\ReSingEngine

If ReSing is not open and this file exists:

lock.txt

Delete it. Try to open ReSing. If you have the same problem as I did, it should now move to the main screen where the programme can be used.