License Troubleshooting

<< Click to Display Table of Contents >>

Navigation:  Professional > Licensing >

License Troubleshooting

Here are some common errors related to licensing.

 

Error acquiring license for appID=101 from server (local)\SQLEXPRESS. Exception Message: Warning: Fatal error 9001 occurred at [Date] [time]. Note the error and time, and contact your system administrator.

 

This is followed by a Registration pop-up window showing that all licenses are available before the program terminates. The error may be caused by a corruption in the *.LDF file or, in some cases, by a virus checker locking the database. To resolve the issue, close all connections to the database, take the database offline, and then restart it.

 

Error acquiring license for appID=40 from server apc-sql. Exception Message: Object referenced not set to an instance of an object.

 

This error is typically a result of old licenses left in ST_LICENSE or non-applicable licenses for a different server ID. To resolve this error, delete all rows in the license database ST_LICENSE, except rows pertaining to Custom EDP or EDGE formats, restart Professional and reapply all current, valid keys.

 

System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'sq_euid'.

 at EarthSoft.Common.Data.Connection.ExecuteScalar(String CommandText)

 at EarthSoft.Common.Data.SqlConnection.NextValue(String sequenceName)

 at EarthSoft.Common.Data.Connection.NewId()

 at EarthSoft.Common.Data.User.CreateUser(Connection Connection)

 at EarthSoft.Common.Data.User.GetUser(Connection Connection)

 at EarthSoft.Common.Data.Facility.Initialize()

ClientConnectionId:11d83d11-6ce2-4563-aab5-a839c5fd7d8c

Error Number:208,State:1,Class:16

 

The above error occurs due to an out-of-date license database and may also occur alongside an EQuIS Professional message, "Please register - EQuIS licensing is required but missing or not accessible. Review the EarthSoft Software Registration information and use the links provided to request additional keys as needed." To resolve, follow the Update instructions on the License Database Setup page.