The Indicium log might show some more information regarding to this issue. Can you post it here? Edit: Also, you are connecting from an Azure Web App to OnPremise database if I understand correctly? Did you configure an hybrid connection endpoint or how did you make your database server accessible? Yes, we are connecting from azure web app to on-premise. we have a site-to-site tunnel setup between our corporate network and Azure.Indicium didn’t show anything. I’m going to attempt this again, but for now we can close this ticket. I’ve shutdown this test environment to focus on something else.
Just in case, you can double check if you have sufficient rights to copy these preferences. Being a User or Root admin should be sufficient. We also started on building export and import functionality to migrate user preferences to other IAM's for 2023.2 i do have sufficient rights. i am an admin.
So i attempted a creation but i keep receiving this error in the last step to execute the source code: /* Login failed for Indicium pool user. *//* Please make sure the Indicium pool user has sufficient rights. */ I am sure the pooluser account is db_owner on the app database and also has root admin, db_owner and end user rights on the IAM database. so i don’t know why this message keeps returning
Hi @rustie, Can you please let us know if you still require assistance, or if Mark pointed you in the right direction? for now you can close this ticket. i am currently focusing on something else
Hi, Have you followed these steps?: Users | Thinkwise Documentation (thinkwisesoftware.com) . Can you provide screenshots of Before, During (the task pop-up with values) and After execution of the Task? yes i followed these steps.
@Zachery
will let you know if the creation from azure to onprem works.
I deleted the secret, restarted the web app. Indicium created the secret and I was able to create pool user. Thanks
We can make Indicium maybe a bit more lenient with invalid secret contents, to make it easier in case this happens. Right now, it can be solved by deleting the key and let Indicium create it (which it does automatically when the secret does not exists). (on first use, Indicium was not supposed to find anything and it would create a key with the correct contents - now it finds a key with no contents which it didn't expect). Okay understood. i will do that and let you know what happens.
Did you manually created the secret with the name: `myvault`? If so, that might be the problem - Indicium needs to create the key with the correct contents. Can you check the secret and validate that the content is an xml document? If not, (and nothing is encrypted with this key), you can delete it and let Indicium recreate the secret with the correct contents. Yes i did, because the documentation says to add a URL which end in a key file. e.g.: So i had to create a file otherwise the URL wouldn’t be able to find anything
@Freddy @Zachery
and when i remove the configurations for the encryption key my indicium is back to normal.
Hi Rustie, Did you restart Indicium after changing the appsettings.json? yes i did. always do
2022-12-29T13:15:17.5601005+00:00 [inf] License refresh not required. Current license state: Valid. "License valid until 2023-03-29T11:18:13" (6a3d1cf0)2022-12-29T13:15:17.5791293+00:00 [inf] License refresh scheduled for 2023-01-05 11:18:13. (09ff7cde)2022-12-29T13:15:59.9885403+00:00 [inf] Initiating startup license check (a070e428)2022-12-29T13:16:00.1276582+00:00 [inf] Reading license from IAM. (d4563d62)2022-12-29T13:16:00.1848274+00:00 [inf] License successfully read from IAM. (66b06fb5)2022-12-29T13:16:01.1409965+00:00 [inf] License refresh not required. Current license state: Valid. "License valid until 2023-03-29T11:18:13" (6a3d1cf0)2022-12-29T13:16:01.1594351+00:00 [inf] License refresh scheduled for 2023-01-05 11:18:13. (09ff7cde)2022-12-29T13:16:01.8123211+00:00 [err] An error occurred while reading the key ring. (54b25ea0)System.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.at System.Xml.XmlTextReaderImpl.Throw(Exception e)at System.Xml.XmlTextRea
i tried enabling data encryption by using the appsettings.json file:"MetaSourceConnection": {"Server": "","Database": ""},"Agent": {"Enabled": true},"DataProtectionSettings": {"AzureKeyVault": {"KeyVaultSecretUrl": "https://myvault.vault.azure.net/secrets/myvault"}}} then I deleted the setting in the json file and used this option:App Service, select Settings > Configuration from the menu.Add the following Application settings:name:DataProtectionSettings:AzureKeyVault:KeyVaultSecretUrlvalue: https://myvault.vault.azure.net/secrets/myvaultwill post the result of the indicium log
same as Freddy. cannot find that option. i want to use it to easily create changes from my on prem SF to my end application on Azure
I just followed the steps as outlined in the reference docs. select the user for which you want to copy the settings and then click on copy user preferences. and nothing changes.
In our case the mixed mode authentication in SQL was turned off. We had to turn it on enable the users for the IAM databases and logins were working again.
running this statement on the IAM of software factory and this is the result:Msg 2627, Level 14, State 1, Line 1Violation of PRIMARY KEY constraint 'usr_root_admin_pk'. Cannot insert duplicate key in object 'dbo.usr_root_admin'. The duplicate key value is (1, duane). But my user was a main administrator as i recall
So as it is all my IAM databases are displaying the old server. all, except the iam for SF. which shows the current server. how do i fix the other ones?
okay so for another IAM database i see the old server name:
isorry, performed the statement wrong. this is hte result:
i only get a message saying : Invalid object name 'server'
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
