License data corrupt

Use the System File Checker tool to repair missing or corrupted system files. How can this be solved? Does MS have a record of my digital license or upgrade history? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. Why your drive is locked - I dont know, maybe someone else might chime in here for that. How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site. In reply to 'Mike P's post on February 26, Anyone tell me how I can repair or replace the licence bank to allow me to transfer the licenses back? Regards, Phil. Suggestion To thank Quote Answer. JMJ Posts: Rating: I am not sure if this is legally allowed. I think you can see that option by right click on the corrupt license. Copying the file from outside ALM does not work. You can alsomanually deletethem from Windowsexplorer if you know what you are doing.

If you have other licenses, then you can loose them if you make mistakehere. Butthe best solution is to contact Siemens techsupport. They will be able to fix it foryou and giveyou anew license over the phone. Thanks for the replies.

I am using the Automation License Manager to do my transferring. I have a good working copy of the original license. When the API deals with an unknown error code. Hence, it cannot print the error message. Bad index. No additional units are available for this feature. The feature cannot run anymore because the license expiration date has reached.

Make sure that your machine date and time zone are correct. Else, contact your vendor for a new license. The feature cannot run as the total number of "days" allowed in the grace period have been consumed. This feature cannot run as the grace period cannot be determined. The feature cannot run as the total number of "hours" allowed in the grace period have been consumed.

All rights reserved. Account Settings Logout. All Files. Submit Search. Check the calling parameters. Contact another failover License Manager. Check the given parameters. The error can also appear for repository licenses when insufficient units are left with the License Manager. Allocate sufficient memory. It cannot be revoked. It cannot be revoked again. The licenses can be checked out only from the primary License Manager.

The commuted license must be checked in back into the primary License Manager from which it was checked out. One or more records are either modified or missing from the usage log file. Verify if the client and License Manager protocols are incompatible. This is applicable to network license revocation only, where the maximum number of operations should not exceed Try reducing the number of operations from the permission ticket.

The permission ticket cannot be used for revoking licenses of other vendors. This cannot be done for the feature until all its licenses scheduled for revocation are revoked. Successful operation. A generic error when the RMS is unable to obtain licensing token for the given feature.

Feature name or version cannot be NULL. Attempt to return a non-existent token by the client application. No more clients exist for this feature. No more features available on the License Manager. Error in calling the API function. Probably no License Managers are running in this subnet. The given license code could not be added to the specified License Manager.

Failed to delete the specified license from the License Manager on host. The last update was done by the License Manager. The specified feature is licensed by multiple vendors other than your vendor. Cannot perform this operation on the domain name specified. The specified log filename not found on the specified License Manager host. Machine's fingerprint mismatch for this feature. The attempts to update license have failed to reach the License Manager.

Returned all the tokens for this feature. Could not find the specified client for this feature. The file open error. The specified host name is either not valid or cannot be resolved. Message forwarded to the leader License Manager.

Update Failure. IP address given cannot be resolved. Hostname given is unresolved. Invalid IP address format. License Manager is synchronizing the distribution table. Configuration file modifications failed. A non-redundant feature given for redundant feature-related operation.

Cannot find trial usage information for the given feature. Failure in retrieving the trial usage information for the given feature. Not enough tokens are available with the License Manager for commuting. The client commuter license already exists on this system. Error specific to the redundant License Manager pool setup. This commuter license is checked out remotely, so it cannot be checked-in. Error in installing the commuter authorization code. Error in obtaining the locking information of the client.

The remote locking code string is invalid. Feature is not supported in network-only licensing library. The specified file type is not supported. The requested operation is not supported on the License Manager. The given license code is already added to the specified License Manager. The contacted feature is a repository license. Most of the time ANSYS Mechanical does a great job of keeping track of all our input and output files needed for a particular simulation.

Every once in a while though, a glitch can happen which could lead to a corrupt database that gives you errors, say, if you try to reopen the ANSYS Mechanical editor.

If you suspect that somehow your project database for a Mechanical model or any other model that uses the same interface as ANSYS Mechanical has been corrupted, you just might be able to recover it using these steps:.

Copy any. Rename them to a.