Unity fails on batch mode, it seems license problem

Our CI workstation is running with unity5.3.6p2. and MacOs 10.12.2. Every thing is OK until yesterday.

All build action from batch model fails, and its log :

We switched license from pro-license to plus-license. And we also found here is no license mode of plus for 5.3.6p2. Although we succeed activate unity5.3.6p2 as pro-version with plus-key.

Our project cost million funds and time, so we had to using the old version for a long time.

Should we buy the pro-license ?

Or just use the plus-license ? Or anything else?

Please Help~~~

Thanks

Perhaps try:

-skipMissingProjectID
-skipMissingUPID
-force-free
-username = ‘me@example.com’
-password = ‘mypassword’

OK.
I tried “-force-free”. It’s working. So my plus license can’t using on unity5.3.6p2. And the 5.3.6p2 has no UI to activation as plus-version.
Although plus-key can complete activation. It’s not working in batch mode.

Please help.

Having a similar problem here. We are activating the pro license in batchmode. All was working in 2017.1 , After the Update to 2017.2 on Windows Server 2016 we cannot activate the license in batchmode anymore.
Please help.

1 Like