[talos72]

I updated to v3.0.1, now the license is not working. I also have Mari which also got updated and uses RLM. So I am not sure what is causing Maxwell issues. I had before managed to get Maxwell running by having the license point to port 504 through modifying .lic fille (both Mari and Maxwell seemed to try using same port). So I tried modding the port in Maxwell .lic again, but it still does not work.

please help. thanks. my guess is updating both Mari and Maxwell which use RLM scewed up the Maxwell license. I wish Maxwell had the old system for licensing.

I appreciate any feedback.

[Q2]

+1

Same here. After installing version 3.0.1 only ONE of my 2 licenses is working.....

WAIT-----

I reinstalled it using the method below....

"License could not be saved" - This means Maxwell doesn't have enough permissions on your computer to write the license file to disk. Start the install process again, making sure to right-click on the installed and chosen "Run as Administrator".

Now it works!

Hope that helps....

Q!

[Mihai]

Make sure no firewalls are running and try again. More people have reported the same issue, and it has always been because the FW blocked Maxwell again, since it figures it's a new application. So Maxwell can't contact the RLM server anymore.

The V3 update changes absolutely nothing in your license files, which are stored separately, outside the V3 install folder.

[architecturegeek]

agree, new licensing system is a cluster f***

Having same issue, firewall has been off throughout install process, still no dice. NO 3.0.1. NODES can activate currently, we're dead in the water.

---- Here's our error message:

License Error!
Error validating license.
The license file has been correctly written but this system cannot connect to license manager.
Please check the IP and Port specified are correct.
It also maybe due to a firewall blocking the connection.

Please visit our support site.

---

Maxwelllog.log looks like this:
------
04/23 10:56 (rlm) License server started on localhost
04/23 10:56 (rlm) Server architecture: x64_m1
04/23 10:56 (rlm) License files:
04/23 10:56 (rlm) /Users/Shared/NextLimit/rlm_nl/licenses/maxwell_suite_floating.lic
04/23 10:56 (rlm)
04/23 10:56 (rlm) Web server starting on port 5054
04/23 10:56 (rlm) Using TCP/IP port 5053
04/23 10:56 (rlm) Unable to create ISV socket, comm error: -216, errno: 1
------


EDIT (3)
------------


Ok, figured out my particular issue. There's a weird Bonjour bug related to file sharing in OSX. When file sharing is on bonjour can occasionally not release a machine when it restarts, when the machine logs back on to the network it's name is automatically appended to HOSTNAME(2) and then 3, 4, 5 and so on. The problem is the local system and RLM still believe the machine name is simply HOSTNAME so they error out.

Turning off OSX filesharing then renaming computer back to it's original name then forcing a RLM reread/restart (via web interface) resolves the issue.

[Q2]

same here.... AGAIN.....

Every time I do an update the whole "Maxwell can not find license file hickup " starts all over.

This is what I get now:

Error validating license.
The license file has been correctly written but this system cannot connect to license manager.
Please check the IP and Port specified are correct.
It also maybe due to a firewall blocking the connection.

Please visit our support site.


Last login: Tue Apr 29 09:37:47 on ttys000
12core:~ carstenquilitz$ /Users/Shared/NextLimit/rlm_nl/rlm ; exit;
04/29 09:45 (rlm)
04/29 09:45 (rlm) WARNING: No license file for this host (12core.local)
04/29 09:45 (rlm) The hostname in the license file(s)
04/29 09:45 (rlm) may be incorrect
04/29 09:45 (rlm)
04/29 09:45 (rlm) License files:
04/29 09:45 (rlm)
04/29 09:45 (rlm) RLM License Server Version 11.0BL2

Man, this sucks... Firewalls are off and all files and infos are correct in the license file, the rlm server is running but for some reason I CAN Not get Maxwell to work properly...

Any ideas?

Q!


UPDATE: I reactivated my first license through Maxwell Render again (Third time now!) and I get Studio to work again on my MacPro (OSX), at last. BUT, again, My MacPro running Win 8 will not accept the license....Activated it there too (5 Times already) but it can not be validated. Man this is frustrating......

UPDATE 2: GOT IT TO WORK... Somehow only one of my licenses was written to the .lic file and therefore Maxwell on my PC could not find it... obviously . Activated it on the MacPro (OSX) where the rlm is running an voila...works.

BUT WHY DO I HAVE TO FIGHT SO HARD EVERY TIME TO GET THIS SORTED OUT?

[talos72]

FYI, I updated Maxwell over the weekend few weeks back. I went through license activation wizard half a dozen times. I tried modding the ports. I tried turning off firewall...none was working. Yet, by some miracle I fire up my computer on the following monday and I got my license back. I don't know what the heck was going on, but there was some definite screwy stuff with the license. I thought maybe Next Limit or whatever remote servers that manage license activation were off line or in maintenance right when I was updating Maxwell...maybe I am completely wrong. And come monday, the hiccup was corrected. I still don't know why my license got screwed up after updating, which is of little comfort since I am not sure how to fix the problem next time.

Maybe as mentioned earlier my firewall was still causing issues and preventing my computer from contacting license servers, but why would it suddenly work few days later...I had not changed any settings on my FW.

I wish I can share what or how my licensing issue got fixed, except I still don't know. I really hope I don't have to go through it again.

I am still trying to figure out how the RLM thing works since I have at least two apps that use the system.

[Mihai]

Just want to repeat that when you update Maxwell, DON'T run through the whole licensing process again. It makes no sense. Nothing has been changed about your license files when Maxwell is updated. If you get a license error it is most likely, like I said, that something is now blocking the connection to the RLM server, because a FW thinks Maxwell is a new or changed application. So re-licensing Maxwell won't help.