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'
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.
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.'
During installation the license is not needed and not verified. You mainly enter it in the installer for your own convenience, because it´s then automatically written to the InnovatorServerConfig.xml.
You should become a subscriber to my Youtube channel. It has tons of valuable content, e.g. this one regarding the database is not available error message:
https://www.youtube.com/watch?v=QosEbd5ohDY
Actually solution is the same that you have mentioned in your previous post with the sp_change_users_login commands. In my case I also had to refresh/restart the database. Shouldn´t be hard to fix.
