Conenct Talend with Snowflake cloud - connection

I am new using Talend and Snowflake cloud.
I am trying to conet Talend using the component "Snowflake Connection", and complete with this settings:
user:XXX
password: YYY
Schema: TPCH_SF1
Database: SNOWFLAKE_SAMPLE_DATA
and give me this error: .net.snowflake.client.jdbc.SnowflakeSQLException: Incorrect username or password was specified.
But this user I can enter in Snowflake.
Can anyone help me please.

I tried reproducing it. Just to clarify different component what error comes through i have written down all different error come when which component throws error.
If snowflake account is wrong
java.lang.RuntimeException: JDBC driver encountered communication error. Message: HTTP status=403.Incorrect Snowflake Account was specified
For this error we need to change the account name
Snowflake Region is wrong for valid snowflake account. 403 error is thrown
something like below.
"ERROR [main, net.snowflake.client.jdbc.SnowflakeUtil:logResponseDetails:449] -- Response content: 403 ERROR "
you can define region name in Advance setting by checking in use Custom Snowflake Region for connection.
Snowflake username or password is incorrect for the account.
JDBC driver not able to connect to Snowflake. Error code: 390100, Message: Incorrect username or password was specified..
Hope this helps.

Related

Configuring futuretense.ini in wcs 11gR1

I have webcenter sites 11gR installed. In the futuretense.ini file I have the following fields blank:
satellite.blob.cachecontrol.default=
cs.satellitehosts=
cs.satelliteusers=
cs.satellitepassword=
Additionally it has two satellites to which access like this:
x.xx.xx.xx:port/servlet/Inventory?username=SatelliteServer&password=pass1
x.xx.xx.yyy:port/servlet/Inventory?username=SatelliteServer&password=pass2
in sites.los the following error is presented:
Error code:REMOTE SATELLITE SERVER CONNECTOR ERROR
Is the furetetense.inio file related to the error?
Do I need to set the host , user and password?
Which password should I use?

how to disable the ODBC connection wizard

I use ADO connectionstring to MariaDB in dBase and when the connection is unsuccessful (invalid userid, pwd, port number, IP address, databasename or if the server is not running), I get the MariaDB datasource connector wizard. Once I cancel or complete the wizard (both successfully or unsuccessfully), I get the ADO error into dBase.
Is there a way to disable this wizard and just return the error?
For anyone interested, adding 16 (for NO_PROMPT) to the "option" part of the connectionstring disables the popup.
Just in case anyone is looking for the same option for SQLserver, look here: https://learn.microsoft.com/en-us/sql/ado/reference/ado-api/connectpromptenum?view=sql-server-ver15
oConn.Properties("Prompt") = adPromptNever or any other desired option from the above link
oConn.Open "Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;"

Unable to issue identity in Hyperledger Composer

I am trying to issue an identity to a participant that already exists in the network.
return this.bizNetworkConnection.connect(this.cardname)
.then((result) => {
let email = 'user#gmail.com',
username = email.split('#')[0];
this.businessNetworkDefinition = result;
return this.bizNetworkConnection.issueIdentity('org.test.Person#user#gmail.com', username);
})
.then((result) => {
console.log(`userID = ${result.userID}`);
console.log(`userSecret = ${result.userSecret}`);
})
I expect that I will see the userID and the userSecret logged on the console but I am getting errors as described below.
Following the developer tutorial on their documents:
If I use the card name for PeerAdmin#hlfv1 on the connect function above, I get the error. "Error trying to ping. Error: Error trying to query business network. Error: Missing \"chaincodeId\" parameter in the proposal request"
If I use the card name for admin#tutorial-network on the connect function above, I get the error "fabric-ca request register failed with errors [[{\"code\":400,\"message\":\"Authorization failure\"}]]"
For option 1, I know the network name is missing in the given card, whie option 2 means that the admin has no rights to issue an identity. However, I cannot seem to find any documentation directing me on how to use either to achieve my objective. Any help is highly welcome.
While I have listed the javascript code I am using to achieve the same, I would not mind if anyone can explain what I am missing using the composer cli.
see https://hyperledger.github.io/composer/latest/managing/identity-issue.html
you would definitely use the admin#tutorial-network card, as PeerAdmin does not have authority to issue identities (admin does).
Did you already do: 1) a composer card import -f networkadmin.card (per the tutorial) ? 2) a composer network ping -c admin#tutorial-network to use the card (now in the card store) and thereby populate the admin's credentials (certificate/private key).
Only at that point would admin be recognised as the identity to issue further identities. Is it possible you spun up a new dockerized CA server at some stage since you did the import etc ?
What happens if you issue a test identity through the command line (using admin#tutorial-network? Does it fail)

getting error when enter uri for timeseries ingest

Hi I am trying to save data in timeseries db but I am facing an error at timeseries ingest when I enter wss://gateway-predix-data-services.run.aws-usw02-pr.ice.predix.io/v1/stream/messages in websocket uri it shows an error like this when I click on open socket
The request failed with status code: 500
{
"error": "Error: unexpected server response (401)",
"url": "wss://gateway-predix-data-services.run.aws-usw02-pr.ice.predix.io/v1/stream/messages"
}
and see this screenshot once.
Thanks&regards
Eswar G
From the error log, it looks you got authorization error. Check if you are using correct predix-zone-id of the time-series instance in the request header or you have configured correct UAA instance in predix tool kit.
Have you updated your UAA client with timeseries authorities?
To inserting time series data with particular user or client need permission. For getting permission, you need to add authorities into your UAA client.
Following are the authorities for timeseries.
Experiencing a similar problem. I'm posting only one of several received error messages. I've cycled through combos of the following for uri and zone id:
uri:
wss://gateway-predix-data-services.run.aws-usw02-pr.ice.predix.io/v1/stream/messages
https://time-series-store-predix.run.aws-usw02-pr.ice.predix.io/v1/datapoints
zone-id:
44853a54-3ecd-4589-85da-b54f2fda7cce
and the zone id shown in the photo, with .ingest at the end.
so, 401 unauthorized.
Did you happen to re-create the timeseries or uaa? Perhaps they are not associated. Also, I'm assuming you did "login as client" in the top menu.
Might be a good idea to create a new timeseries tied to that uaa. Then use the new zoneId.
Did you add predix..ingest and predix..user to the scope and authorities section in uaa client in your predix.io account. Please check the client id to add permission for in websocketriver.config file.

LDAP-Error in Identity Server 4.6 when using user registration with "Ask password from user"

I wanted to try the password-notification feature of the IS 4.6 but it throwing an exception.
I followed those links:
https://docs.wso2.org/display/IS460/Recover+with+Notification
http://cgchamath.blogspot.mx/2013/12/wso2-identity-server-user-creation-with.html
This is the error I am getting
Here is the Stacktrace
Caused by: org.wso2.carbon.identity.base.IdentityException: Error
while persisting identity user data in to user store at
org.wso2.carbon.identity.mgt.store.UserStoreBasedIdentityDataStore.store(UserStoreBasedIdentityDataStore.java:81)
at
org.wso2.carbon.identity.mgt.IdentityMgtEventListener.doPostAddUser(IdentityMgtEventListener.java:420)
... 124 more Caused by: org.wso2.carbon.user.core.UserStoreException:
One or more attributes you are trying to add/update are not supported
by underlying LDAP. at
org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doSetUserClaimValues(ReadWriteLDAPUserStoreManager.java:874)
at
org.wso2.carbon.identity.mgt.store.UserStoreBasedIdentityDataStore.store(UserStoreBasedIdentityDataStore.java:73)
... 125 more Caused by:
javax.naming.directory.NoSuchAttributeException: [LDAP: error code 16
- NO_SUCH_ATTRIBUTE: failed for Modify Request
Object : 'uid=testUser,ou=Users,dc=wso2,dc=org'
Modification[0]
Operation : replace
Modification
http://wso2.org/claims/identity/passwordTimestamp: 1398394865706
Modification1
Operation : replace
Modification
initials: false : ERR_04269 ATTRIBUTE_TYPE for OID http://wso2.org/claims/identity/passwordtimestamp does not exist!];
remaining name 'uid=testUser' at
com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3108) at
com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3033) at
com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2840) at
com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1411) at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:253)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:165)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:154)
at
org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager.doSetUserClaimValues(ReadWriteLDAPUserStoreManager.java:859)
... 126 more
I can imagine that the application is generating a timestamp for the expiration of the password and tries to save in a field in the LDAP which is mapped by the combination:
http://wso2.org/claims/identity/passwordtimestamp -> nickName
This mapping is wrong obviously.
How can I force an adequate mapping so the process is saving the user in the right way (and hopefully sending the email after that ...)?
Thanks in advance.
First problem on this way solved:
I had to re-add the claim of the password time stamp, but with the correct uri:
http://wso2.org/claims/identity/passwordTimestamp
Also helpful was:
https://wso2.org/jira/browse/IDENTITY-1200
The LDAP-error is fixed, but still it is not sending the email. But that is another issue

Resources