The case of the missing Previous Version licenses

In this case, a customer received his new 2013 license for four seats of Softimage. He was able to start Softimage 2013 on four machines, but he could run Softimage 2012 on two machines only. What could be the problem?!?

Now, to diagnose this problem, you could do any one of a number of things:

  • Check the license file to make sure it has the right licenses.
  • Check the Perform Status Enquiry output from LMTOOLS, to make sure the license is actually installed.
  • Check the LMTOOLS debug log file, to see why the workstations are being refused Softimage 2012 licenses.
  • Check the workstations, to make sure they are configured properly for licensing.
  • Verify that when the customer tries to start 2012, they don’t have copies of Softimage 2013 still running.
  • Check the customer’s assets in our database (make sure they really have four licenses).

In this particular case, I could identify the issue by either checking the customers assets OR checking the actual license file. Because the problem was this:

The customer had two seats of 2013 on Subscription, and two seats of 2013 not on Subscription. Previous version usage (aka running 2012) is a Subscription benefit, so he had two 2012 licenses only.

Here’s a video walkthrough of a license file, where I point out what to look for when you’re trying to understand a license file.

In this video, I show you to tell what you’ve got in a license file.

Changing the Licensing Method

After the install is finished, edit C:\Softimage\Softimage_2010_x64\Application\bin\setenv.bat.

  • SILicMethod specifies whether to use Network or Standalone licensing.
  • _ADSK_LicServers specifies the license server. By default, this env var is set to the value entered during Setup.
rem Licensing method: Standalone | Multi Seat Standalone | Network
set SILicMethod=Network
rem License servers specified from the setup. Format: [port1]@host1[;[port2]@host2]...
set _ADSK_LicServers=@server;

Installing Softimage 2010

When you install Softimage 2010, you’ll have to enter a product key and a serial number. Just use the product key 00000 and the serial number 000-00000000. That will install Softimage in Trial mode. And if you need to switch to Network licensing later, all you have to do is change an environment variable.

Product Information

Product Key Description
00000 Trial mode product key. Installs Softimage in Standalone licensing mode.
590B1 Softimage product key. You can choose between Standalone, Multiseat Standalone, and Network licensing modes. If you choose Network, you’ll be prompted to enter the license server name.
If you choose Standalone, or if you choose Network and enter the serial 000-00000000, you’ll get the 30-day trial period.
You can switch licensing methods between Standalone and Network.
591B1 Softimage Advance product key. You’ll be prompted to enter the license server name.
If you use the serial number 000-00000000 you can run in Trial mode. You cannot switch back to Standalone mode without reinstalling.

Installing your new 2010 network license

To get your 2010 license, get your 2010 serial number and then go to

  1. Save your 2010 license file in C:\Program Files\Autodesk Network License Manager.
  2. Start LMTOOLS.
  3. On the Start/Stop/Reread tab, click Stop Server.
  4. On the Config Services tab, change the Path to license file to point to the 2010 license file.
  5. Click Save Service.
  6. On the Start/Stop/Reread tab, click Start Server.
  7. Now double-check that the 2010 license is installed. On the Server Status tab, click Perform Status Enquiry. Scroll down to the Feature usage info and look for 2010 features (84000SFTIM_2010_0F for Softimage 2010, 84100SFTIMASIB4_2010_0F for Softimage Advanced 2010)

Unlimited xsibatch processing

As of Softimage 7.5, you get unlimited batch processing. Before, you got 8 Processing tokens with Advanced and 4 with Essentials.

Batch processing is where you run “xsibatch -processing -script”. Batch processing can includes things like exporting .mi2 files, exporting rib files, baking, committing, asset management, custom render management/submission, dynamics, … anything in a complex pipeline that requires automation and remote processing, but not rendering. (Ref: