Forum Discussion
Hi,
based on your shown images you made a role model installation. Which unfortunately makes it hard to tell what is wrong.
OAuthServer 500 error is caused by a missing 2.1.8 Core Runtime. You have installed this one, but have your really installed the "Hosting bundle"? In my case non of the other versions worked.
See the difference at minute 9:40 in this video: https://www.youtube.com/watch?v=A5QEtOO86ik
Maybe also the .NET 5.0.5 Windows Server Hosting has some influence. But I am not sure.
- subramaniank5 years agoIdeator I
Thanks AngelaIp that helped me cross that hurdle. But I'm stuck in login screen
I’m currently not able to login. Displays the following error
I restored the database and also ran following commands. After restarting SQL server and IIS, still see the same error.
-- Query 1 (should succeed)
-- use $(dbname);
sp_change_users_login 'Update_One','innovator_regular','innovator_regular'
sp_change_users_login 'Update_One','innovator','innovator'-- Query 2 (should fail)
-- use $(dbname);
sp_grantdbaccess 'innovator','innovator'-- Query 3 (should succeed)
-- use $(dbname);
sp_addrolemember 'db_owner','innovator'- AngelaIp5 years agoIdeator I
Hi Subramaniank,
"license key is invalid" is a typical hint that there is something wrong with the license key in the InnovatorServerConfig.xml.
I address a similar issue in minute 14:10 of my video. In my case the license key was "missing", while it is "invalid" in your case. So I assume you have a license key, but there is something wrong with it.
Did you pass the correct MAC address to Aras to get the correct license key for the instance you are currently using? You cannot reuse license keys that you may have requested for other servers or previous Innovator versions. Each instance needs a new one.
Let me know if this one was the reason. It would be a good addition for the video.
- subramaniank5 years agoIdeator I
Hi AngelaIp
I requested new license with my mac address, and updated in InnovatorServerConfig.xml. Also restarted SQL server & IIS. Now the previous error is gone. I'm not clear, why the license that worked during installation, fails later.
With this issue fixed, now I'm facing the next issue 'The Database is not available:Login failed for database user, contact your system administrator.'