When configuring a new migration tasks I am asked for the application ID and the key. I created the app id and copied the key from the created account id under the target details. When I save it I get the following error:
Unhandled scenario exception. Scenario 'ConnectToTarget.AzureSqlDbMI.Sync.LRS', TaskId '1fa8b4eb-5a2f-4450-adb6-c1a96504f985'.
One or more errors occurred.
Failed to collect data for Azure Resource '/subscriptions/my subscription/resourceGroups/target resource group/providers/Microsoft.Sql/managedInstances/managed-instance' using application ID 'adminsql'.
Object reference not set to an instance of an object.
I suspect I configured the application ID incorrectly for the migration service but I don't know where to start fixing it
dont know if this is the problem your having, but i got the exact same error when i put the ID of the secret, not the ID of the App into the migration tool... I realized i put in the wrong ID and it works now...
Related
I am working on database 19c and Apex 21.1..when I open Apex normal, I get the error message
The request could not be mapped to any database. Check the request URL is correct, and that URL to database mappings have been correctly configured
I checked the service to turn it on, and I got a new service that was not included in the Oracle service
Its name is OracleRemExecServiceV2
And it is the causes a problem, when I run it, the error message appears
windows could not start the oracleremexecservicev2 service on local computer
the system can not find the file specified..enter image description here
please help me to solution this problem
I am trying to create Google App Engine using create application option but i am getting below error :
An internal error occurred while ensuring the default service account exists.
Can you please help me with the solution
Tried creating with different location getting same error
Make sure the default App Engine Service Account is not missing (due to an accidental deletion e.g) from the IAM & admin > Service accounts section of the Cloud Console. It is named after your project followed by "#appspot.gserviceaccount.com".
If you do not see it, you can recover it by doing for example a REST API call as documented here:
POST https://iam.googleapis.com/v1/projects/[PROJECT-ID]/serviceAccounts/[SA-NAME]#[PROJECT-ID].iam.gserviceaccount.com:undelete
If the deletion was made more than 30 days ago, the only way left to fix the issue would be to create a new project and use its brand new default Service Account.
We have implemented WSO2 API Manager (v1.10.0) in a distributed architecture as outlined in the online documentation here.
This consists of the following (on 5 separate servers):
Gateway (x2)
Publisher & Store (on a single server)
Key Manager (x2)
These are wired-up to the 3 normal API Manager databases (Registry, User Manager & API Manager), which are on a SQL Server 2014 instance.
We are using the Key Managers for the authentication (login, forgotten password, etc.) of the website users, as well as for authenticating API calls.
However, when trying to log in to the site I'm seeing the following (Violation of UNIQUE KEY constraint) error on the Key Manager:
TID: [-1] [] [2016-10-06 00:36:47,842] ERROR
{org.wso2.carbon.identity.oauth2.dao.TokenPersistenceTask} - Error
occurred while persisting access token
:c5a0a11e63388dCHANGEDea34b0533445
{org.wso2.carbon.identity.oauth2.dao.TokenPersistenceTask}
org.wso2.carbon.identity.oauth2.IdentityOAuth2Exception: Error when
storing the access token for consumer key :
fpA6AhOfbVCHANGEDgH0WzBDOga at
org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.storeAccessToken(TokenMgtDAO.java:246)
at
org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.persistAccessToken(TokenMgtDAO.java:284)
at
org.wso2.carbon.identity.oauth2.dao.TokenPersistenceTask.run(TokenPersistenceTask.java:52)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745) Caused by:
com.microsoft.sqlserver.jdbc.SQLServerException: Violation of UNIQUE
KEY constraint 'CON_APP_KEY'. Cannot insert duplicate key in object
'dbo.IDN_OAUTH2_ACCESS_TOKEN'. The duplicate key value is (15,
williams.j2#CHANGED.org.uk, -1234, ,
APPLICATION_USER, 369db21a386ae4CHANGED0ff34d35708d, ACTIVE, NONE). at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
at
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
at
com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:332)
at
org.wso2.carbon.identity.oauth2.dao.TokenMgtDAO.storeAccessToken(TokenMgtDAO.java:224)
... 5 more
This is resulting in the following .NET error on the website:
I've tried Googling this, but cannot find an up-to-date answer.
I have not configured the Key Managers to have master and worked nodes (as outlined here) as the documentation seems to suggest that this isn't needed.
Any help would be much appreciated please!
After some debugging found the issue! Before we put this config,
<JDBCPersistenceManager>
<SessionDataPersist>
<PoolSize>0</PoolSize>
</SessionDataPersist>
</JDBCPersistenceManager>
APIM can save more than one ACTIVE OAUTH token to the IDN_OAUTH2_ACCESS_TOKEN table for single token obtaining call.
When the token validation endpoint queries the tokens, only the last one is returned (Time based sorting and Limits are used). When that one is expired token validation mark it as inactive. But the previous one is kept as it is.
When the refresh token happens, it check whether the latest token is inactive. Since it is inactive, it issues a new token. But when the token endpoints tries to persist the token, there is another ACTIVE token. That caused this exception.
To sort this out we can run a update query on IDN_OAUTH2_ACCESS_TOKEN table to mark all the ACTIVE tokens to INACTIVE.
update IDN_OAUTH2_ACCESS_TOKEN set TOKEN_STATE="INACTIVE" where TOKEN_STATE="ACTIVE"
Then the old faulty tokens will be removed and server will start working fine!
I use mysql and was facing the same problem. Changing the poolsize was also not a full solution. Then I noticed something strange about the idn_oauth2_access_token table. There is a column time_created, but the contents was not the time created. It was the last update timestamp. I read somewhere the systems orders on several columns among the time_created column. I inspected my sql script and saw that the database updated this column when a update was fired. I removed this rule and I have no more errors.
Can you change below configuration (<PoolSize>0</PoolSize>) in <APIM_HOME>/repository/conf/identity.xml, and see? By default, the PoolSize is set to 100.
<JDBCPersistenceManager>
<SessionDataPersist>
<PoolSize>0</PoolSize>
</SessionDataPersist>
</JDBCPersistenceManager>
Hope this Will resolve your issue.
Reference: http://sanjeewamalalgoda.blogspot.com/2015/08/how-to-avoid-getting-incorrect-access.html
I am suddenly getting a 403 error when I try to POST an update to the Retrieve and Rank service. This code is under development but it has been working up until yesterday. The failure occurs only when doing a POST to /v1/solr_clusters/{solr_cluster_id}/solr/{collection_name}/update, and it fails the same way whether I do it via my program, the Swagger API documentation, or cURL. All other operations to this service that I've tried work fine when using the same credentials that I'm using with this POST. The error message I'm getting back is
Error: WRRCSH004: Service [1d111267-76b7-417a-98bd-4e9a58072ef9] is not authorized for cluster [sc262b05e8_dcf5_40b4_b662_ae85058ff07f]!. I don't know where the identifier (1d111267-76b7-417a-98bd-4e9a58072ef9) is coming from; that's not the userid I'm sending in.
Looking into your issue it appears your Bluemix organization has multiple service instances. The 403 issue you were seeing is because you're trying to access a Solr cluster using credentials from one of your instances against a cluster in the other instance. The 1d111267-76b7-417a-98bd-4e9a58072ef9 represents one of these service instances—but the issue is that the cluster you're trying to access is not part of that instance. A good way to test this is to ensure you're using the same credentials that generate the 403 but simply try to list the Solr clusters you have created by doing a GET against https://gateway.watsonplatform.net/retrieve-and-rank/api/v1/solr_clusters/.
As for the 500 issue, I wasn't able to see anything on our end. If you're still experiencing that I would suggest posting another question and we can look into things again.
Thanks,
-Scott
guys! I've got a very strange error when trying to connect two portals.
When I press whatever 'connect portals' or 'test connection' buttons a red error appears sayin' "An unexpected Error has occurred while validating your request". Yikes!
So, I ensured the similar workflow is running on both sites. Next, I've done some debugging and discovered the malfunctioning method in
DotNetNuke.Enterprise.ContentStaging.StagingClientController.cs
public bool PingServer(string address, int portalId, Guid token)
{
/*====somecode====*/
client.PairService(request);
/*====somecode====*/
return true;
}
So, the pair service. After some more advanced debugging I've found a root of evil:
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_PortalSettings_Portals". The conflict occurred in database "MyDNNDatabase", table "dbo.Portals", column 'PortalID'.
The statement has been terminated. Gosh!
So, I've removed the specified constraint and saw a strange thing in my database. DNN tried to add another LocalServerToken with testing site ID though a targetServerAddress and TargetServerToken with Production site ID were expected to be added.
So, I've deleted a site and created a new one using the template. No luck as I expected.
THe last thing I did was manual adding a targetServerAddress & TargetServerToken in my database. The sites seemed to be connected but when I couldn't authenticate as Host and publishing content caused the same unexpected Error.
Anyone know the damn module so deep?
As mentioned on the DNN community exchange, please open a support ticket to get this addressed. That is what paid support is for with PE and EE ;)