I followed the tutorial as mentioned on the website "Create Azure database"
https://learn.microsoft.com/en-us/azure/mysql/quickstart-create-mysql-server-database-using-azure-portal
Still while trying to connect to the database from local cmd it gives me this error:-
ERROR 9002 (28000): The server name you tried cannot be found. Please use the correct name and retry. Please check your server name eztolluser1.
I am trying for the past two days but in vain.
Related
I am attempting to create and use an oracle DB.
Was able to create the DB using sql plus however when I attempt to connect to it via sqldeveloper I get the following error
Status : Failure -Test failed: IO Error: The Network Adapter could not establish the connection
When I check that all services are running I notice OracleVssWriterORCL is not running.
However upon attempting to start it I get the following error:
Windows could not start OracleVssWriterORCL service on local machine Error 0x80070005: Access is Denied
This is my first time using Oracle for DB so any help is greatly appreciated.
I should also note this is on a windows 10 VM
As stated above my listener was not running and going into cmd using the lsnrctrl start command fixed that issue but now I get a ORA-12505 error. Oh the fun of learning new things
I'm desperate since my Google Cloud SQL instance went down. I could connect to it yesterday without problem but since this morning i'm unable to connect to it in any way, it produces the following error: The database server returned this error: SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading initial communication packet', system error: 0
This is what I did to try to fix this:
restart instance
added authorized ip-addresses in CIDR notation
reset root password
restored backup
pinged the ip-address and I get response
All these actions completed but i'm still unable to connect through:
PHP
MySQL workbench
Ubuntu MySQL command line
All without luck. What could I do to repair my Cloud SQL instance. Is anyone else having this problem?
I'm from the Cloud SQL team. We are looking into this issue, it should be resolved soon. See https://groups.google.com/forum/#!topic/google-cloud-sql-announce/SwomB2zuRDo. Updates will be posted on that thread (and if there's anything particularly important I'll edit this post).
The problem seems to only affect connections from outside Google Cloud. Clients connecting from App Engine and Compute Engine should work fine.
Our company has same problem.
We are unable to connect through both MySQL workbench and MySQL command line.
Our Google Appengine application has no problems to connect since its not using external IP.
there.I encountered the same problem.You need to find out your public ip address,for that type "my public ip" in Google.Now click on your Cloud SQL instance that you created,under that click on ACCESS CONTROL tab and then click on Authorization tab under that.Under Authorized network,give any name you want to the network and copy your public ip address in the network.Now save changes and try to run the command from console.It should work fine.
I am trying to add a connection to the server in postgreSQL. But when I fill all the details I get this error
Error connecting to the server: FATAL: role "abc" does not exist.
"abc" is the username I want to create.
I am using Tomcat server eclipse for this.
Please help me find a solution to this problem.
Thanks in advance!
If the user does not yet exist, you will have to login as the admin and create it before you can login as that user.
Hi I am working with ReplicAction tool to transfer data from Lotus Notes View to Oracle Database.
When i Create the link document for Oracle DB it is created successfully without any error
When I create the Include Table for Oracle Db it is created successfully and all columns are listed
When i create the Replication it is also created successfully,
But when the job executes it gives the error is log :
05/08/2012 01:37:16 AM Starting Replication: BADtoProductPortal
05/08/2012 01:37:19 AM Error: <ODBC Error> [DataDirect][ODBC Oracle driver][Oracle]ORA-12154: TNS:could not resolve service name
05/08/2012 01:37:19 AM Error: Information: Unable to open Link: PPLink
05/08/2012 01:37:19 AM Error: Replication to Link <PPLink> did not complete
05/08/2012 01:37:20 AM End of Replication: BADtoProductPortal
If the error is with service name, Then i think we should not be able to create Link document also.
When i use ODBC connection for link, then i am unable to create Replication job, giving the error like Notes Data field "ID" does not match the source data field.
But i know it was working before.
I suggest to check that the TASK runing the job uses the same TNS entry as you are doing "manually".
I suggest to check that the TASK has also access to your Oracle driver. This tasks has right to run it?
ORA-12154 error is thrown during the logon process to a database. This error indicates that the communication software (TNS) in Oracle ( SQL *Net or Net8 ) did not recognize the host/service name specified in the connection parameters.
So the issue is clearly a type en "environment difference" between your configuration when you run manually the replication and when the job run it.
Hope I help
I'm assuming here that when you successfully replicate you're doing it manually from your local machine, and when the job fails it's running scheduled on a server. If that's the case I agree with Emmanuel. Remember running the job locally uses the local tnsnames.ora file, running it scheduled uses the tnsnames.ora file on the server. You may not be aware of anything changing but are you responsible for maintainance on the server?
i have plesk 10.1.1 install in centos 5 when i want to add a customer i got this error
Error: system user update is failed: unable to create system user: usermng: PAM password change failed: 24, Failed preliminary check by password service
i searched manay times and i have no idea what to do
tnx
We got this fix and we wrote an article (in Spanish) with all the related info in http://www.hackingballz.com/articulos/104/1/Plesk-PAM-Error-system-user-update-is-failed-Unable-to-create-system-user/Page1.html
Basically, you should replace the passwd and the system-auth with the configuration that we publish and it will start working. Tested in 3 different servers with those errors and all are working properly.