• Replies 1 reply
  • Subscribers 40 subscribers
  • Views 382 views
  • Users 0 members are here
Options
Related

The statement terminated. The maximum recursion 100 has been exhausted before statement completion.

bankim
Offline

Version : 11.0 SP5; Buld : 6296

As an admin, I have tried to assign my colleague by giving him by

While identity update

Add him a new identity as below " All Employee"

Add him with Solidworks integration " Solidworks User"

While saving after the change,

The system got into non-responsive mode and when restarted /back in, couldn't log in, and the admin login was giving me an error.

"The statement terminated. The maximum recursion 100 has been exhausted before statement completion."

I remember when some of my colleagues gave the privileges under his ID and added me into Alias ID. I was getting the same error.

But I sorted it with an admin login.

But now can not go into admin ID, even though I know the password.

Anyways I can reset the roles?

Or I can reassign the roles?

Or I can reset it to a back date?

The problem is every ID in the user group is now locked out and having the same issue.

  • Wow, what a great way to start a new week!

    I have seen the error message when building complex SQL queries. As Innovator uses SQL in the background, I assume you created a situation that creates such an overcomplex query (e.g. Users referencing to same users which creates and infinitive loop of death)

    Quote: "I remember when some of my colleagues gave the privileges under his ID and added me into Alias ID."

    If I understand your description correct, somebody added an additional Alias to a User manually? That could be the root cause. By default Innovator prevents that you manipulate the Aliases, but maybe this is something still possible in your 11SP5. 

    The only option I know to fix such a situation is SQL manipulation (if you don´t have or want to use a backup).

    1. Go to SSMS.
    2. Open the "Alias" table of your Innovator table.
    3. Connect it to the User table.
    4. Order the User table to sort for "modified_by".
    5. Check if there is a User with more than one Alias. 

    If there is data, that looks obviously wrong to you, you can try to delete the wrong Alias entry. 

    Important: Before trying this, definitely make a copy of your database and link it to your InnovatorServerConfig.xml so you can use it for testing

    This way you can try to delete the wrong data in the test database first. If my tip is wrong and you delete stuff in the database, you can make the situation even worse!
    Keep in mind that you follow a tip by a complete stranger from the internet that may have not understand your issue. So definitely use a test database!

    Edit: I made a small mistake. Don´t sort by modified_by but modified_on. The idea is to get the recently changed users items