DMXzone Server Connect Support Product Page
Cannot connect to a database
Reported 24 Sep 2018 08:46:50
2
have this problem
24 Sep 2018 08:46:50 Jamie F posted:
HiAm trying to create a connection to a database and I add the db name and the user plus the password - in the aerver address I have tried localhost, the server IP and the server url
Every attempt I try I get this error when testing the connection: prntscr.com/kxzfvv
Replies
Replied 24 Sep 2018 10:44:02
24 Sep 2018 10:44:02 Teodor Kuduschiev replied:
Hello Jamie,
This error means your testing/remote server configuration is wrong. Either the site remote folder, or URL or both are wrong, please check this in DW site config options.
This error means your testing/remote server configuration is wrong. Either the site remote folder, or URL or both are wrong, please check this in DW site config options.
Replied 24 Sep 2018 11:09:46
24 Sep 2018 11:09:46 Jamie F replied:
Thanks Teodor. Well I am not sure what needs to be changed as am able to access both the site remotely as well as the database with another app.
Clearly am missing something / not know what to do on this topic.... appreciate any and all help
Clearly am missing something / not know what to do on this topic.... appreciate any and all help
Replied 24 Sep 2018 11:12:40
24 Sep 2018 11:12:40 Teodor Kuduschiev replied:
When your path/url in remote/testing server configuration is wrong, then DW generates wrong link,s and the database connector receives a wrong path.
Check if these are properly configured in DW site configuration:
- remote directory
- web url
Check if these are properly configured in DW site configuration:
- remote directory
- web url
Replied 24 Sep 2018 11:22:13
24 Sep 2018 11:22:13 Jamie F replied:
thanks...have duplicated the live server and set it to 'testing' so I have the exact same as 'remote'
have tried again and getting this error: prntscr.com/ky1hxc
I have checked the db settings and they are 100% right as I have accessed it using HeidiSQL client using the exact same details. The url in the server sttings is correct and the root directory is set to /public_html/
have tried again and getting this error: prntscr.com/ky1hxc
I have checked the db settings and they are 100% right as I have accessed it using HeidiSQL client using the exact same details. The url in the server sttings is correct and the root directory is set to /public_html/
Replied 24 Sep 2018 11:27:32
24 Sep 2018 11:27:32 Teodor Kuduschiev replied:
I am not referring to database settings, i am referring to the URLs in your DW site config, which appear you have fixed, but the error is related now to your db user not having the rights to access this db/table.
Also i think you are following an outdated tutorial, as the screenshot shows an outdated method to connect to database. Please make sure to follow only this manual: www.dmxzone.com/go/32764/dmxzone-app-connect-manual
Also i think you are following an outdated tutorial, as the screenshot shows an outdated method to connect to database. Please make sure to follow only this manual: www.dmxzone.com/go/32764/dmxzone-app-connect-manual
Replied 24 Sep 2018 11:43:55
24 Sep 2018 11:43:55 Jamie F replied:
Yes, thats why I duplicated the live server and made the testing the same as the remote
as I said, " the db settings and they are 100% right as I have accessed it using HeidiSQL client using the exact same details."
The manual I am using was for Database Connector PHP which seems to be the only one with any mention of connecting to database - and with all due respect, I did actually make a suppoirt request over 3 weeks ago to get this ball rolling so I could undertand how to do it and no-one ever replied.
So, now that we have that established- what are my next steps?
as I said, " the db settings and they are 100% right as I have accessed it using HeidiSQL client using the exact same details."
The manual I am using was for Database Connector PHP which seems to be the only one with any mention of connecting to database - and with all due respect, I did actually make a suppoirt request over 3 weeks ago to get this ball rolling so I could undertand how to do it and no-one ever replied.
So, now that we have that established- what are my next steps?
Replied 24 Sep 2018 12:13:28
24 Sep 2018 12:13:28 Teodor Kuduschiev replied:
You are following an outdated tutorial, as the screenshot shows an outdated method to connect to database. Please make sure to follow only this manual: www.dmxzone.com/go/32764/dmxzone-app-connect-manual
Replied 24 Sep 2018 12:49:26
24 Sep 2018 12:49:26 Jamie F replied:
and having gone through the link you added, where is the connecting to the database tutorial?
if I go through the app connect as you suggest, it seems that you have to have already set up a database connection in server connect - and I am not able to do this.
The db credentials that I am using are 100% the same as the ones I am using in another app to access the exact same database....
if I go through the app connect as you suggest, it seems that you have to have already set up a database connection in server connect - and I am not able to do this.
The db credentials that I am using are 100% the same as the ones I am using in another app to access the exact same database....
Replied 24 Sep 2018 13:20:23
24 Sep 2018 13:20:23 Jamie F replied:
ok, just trying to add it through app connect and it wont let me prntscr.com/ky37xq
it has to be added first through server connect it seems and that brings me back to the problem of not being able to connect with the correct database settings
it has to be added first through server connect it seems and that brings me back to the problem of not being able to connect with the correct database settings
Replied 25 Sep 2018 07:25:34
25 Sep 2018 07:25:34 Teodor Kuduschiev replied:
Well, yes of course it has to be added in server connect first, then you use your server actions in app connect to bind the data on the page - just as it is described in the manual i sent you.
As for the error messages saying access denied - just to clarify, connecting to your database through a desktop app and connecting to your database through a web script are two totally different things.
When creating a database connection with our database tools, the connection script is being uploaded to your server, then from your server (!!!note - we do NOT connect remotely!!!) this file is being executed, and the connection is made.
The error you see says that you have no set proper rights for your user to connect from the server your site is hosted. You need to make sure your user has rights to connect there. If you have no clue what i am talking about, then better contact your hosting provider and ask them to provide the proper access rights for your database user.
As for the error messages saying access denied - just to clarify, connecting to your database through a desktop app and connecting to your database through a web script are two totally different things.
When creating a database connection with our database tools, the connection script is being uploaded to your server, then from your server (!!!note - we do NOT connect remotely!!!) this file is being executed, and the connection is made.
The error you see says that you have no set proper rights for your user to connect from the server your site is hosted. You need to make sure your user has rights to connect there. If you have no clue what i am talking about, then better contact your hosting provider and ask them to provide the proper access rights for your database user.
Replied 25 Sep 2018 10:45:05
25 Sep 2018 10:45:05 Jamie F replied:
Hey Teodor
I already have a server connection which happily connects to the database on the same domain and have used for years - using the exact same credentials as that db connection causes the error on the DMX server connect.
I already have a server connection which happily connects to the database on the same domain and have used for years - using the exact same credentials as that db connection causes the error on the DMX server connect.
Replied 25 Sep 2018 11:21:34
25 Sep 2018 11:21:34 Teodor Kuduschiev replied:
The permissions error you see is returned from the server, not from our extension, our extension just shows you the error returned by the server.
I really suggest you to check this with your server admins.
I really suggest you to check this with your server admins.