This topic has 8 replies, 3 voices, and was last updated 1 year ago by 
-
Posts
-
Our MSPControl just updated from 2.0.950 to 2.0.953 and although the login screen comes up fine no one can login to MSPControl any longer due to “Too Many Redirects”. The URL & Query String post-login is \Default.aspx?pid=Licensing"aInvalid=MsSQL2017.Databases&localValue=300&licenseQuota=0.
Any ideas how to proceed?
We already tried clearing cookies, but it appears to be an error in the Licensing (again).
MSPControl is totally down for us again, which is becoming a regular occurrence this past year and is proving to be more a liability to doing business than an assistance.
Sorry, please execute this SQL
DELETE FROM [dbo].[SystemSettings] WHERE [PropertyName]= 'CurrentLicense'It will drop your license and you will get a new one on Sign In.
Alexander,
Thanks. I was trying to find it in MSSQL and the closest I found was [dbo].[SystemSettings].[LicenseSettings] but wasn’t able to delete it. I executed the SQL cmd you provided and that indeed got me in and was greeted with a 5-Step Setup Installer routine (that’s new, never seen that before) that obtained a new license on Step 1. Unfortunately, after finishing the 5-Step Setup it went right back to the same problem…”Too many redirects” trying to redirect to /Default.aspx?pid=Licensing"aInvalid=MsSQL2017.Databases&localValue=300&licenseQuota=0
So promising…so close.
Apparently automatic updates are still working as I got email notification that it upgraded successfully to v2.0.954, but problem still persists and all users are still unable to login.
I tested your license – it’s good. What returns this SQL?
SELECT * FROM [dbo].[Quotas] where QuotaName like '%MsSQL2017%' or QuotaName like '%MsSQL2019%'
Alexander,
The results of the query are as follows:
QuotaID GroupID QuotaOrder QuotaName QuotaDescription QuotaTypeID ServiceQuota ItemTypeID HideQuota Editor
780 54 1 MsSQL2017.Databases Databases 2 0 376 NULL NULL
781 54 2 MsSQL2017.Users Users 2 0 377 NULL NULL
782 54 3 MsSQL2017.MaxDatabaseSize Max Database Size 3 0 NULL NULL NULL
783 54 5 MsSQL2017.Backup Database Backups 1 0 NULL NULL NULL
784 54 6 MsSQL2017.Restore Database Restores 1 0 NULL NULL NULL
785 54 7 MsSQL2017.Truncate Database Truncate 1 0 NULL NULL NULL
786 54 4 MsSQL2017.MaxLogSize Max Log Size 3 0 NULL NULL NULL
790 55 1 MsSQL2017.Databases Databases 2 0 380 NULL NULL
791 55 2 MsSQL2017.Users Users 2 0 381 NULL NULL
792 55 3 MsSQL2017.MaxDatabaseSize Max Database Size 3 0 NULL NULL NULL
793 55 5 MsSQL2017.Backup Database Backups 1 0 NULL NULL NULL
794 55 6 MsSQL2017.Restore Database Restores 1 0 NULL NULL NULL
795 55 7 MsSQL2017.Truncate Database Truncate 1 0 NULL NULL NULL
796 55 4 MsSQL2017.MaxLogSize Max Log Size 3 0 NULL NULL NULL
Apparently non-admin users are now able to login without the session being redirected until it gives a browser error, but instead they are receiving the following error upon successful login:
“Unexpected error. Please try to log out and log in again. Object reference not set to an instance of an object.“
Although they can login they are not able to access any of the functions from their account.
Please rename quotas with ids 790-796 from MsSQL2017 to MsSQL2019
It will help your issue. Sorry seems it was short bad build1 user thanked author for this post.
You must be logged in to reply to this topic.