Installing after building an executable

[yahya]

Running into a problem where I have installed an application from the executable that was built in AwareIM and for some reason is not reading the password.

Message in the startup log:

Message returned from the database Access denied for user 'root'@'localhost' (using password: NO)
Server startup error. Access to database is denied.

Yet in the BASServer.props the password is defined for the MySQL.

#Thu Oct 01 08:49:09 CAT 2020
DriverTestURL=jdbc\:mysql\://localhost/BASDBTEST?user\=root&password\=335PtNgAVrjGTdyw
StatusPort=9005
UIProcessTimeout=1800000
ChannelTypeTimer=com.bas.basserver.channels.TimerChannelType
AwaresoftPort=8080
DirectoryServiceProvider=tcp\://localhost\:61616
SystemPort=9000
DirectoryService=org.apache.activemq.jndi.ActiveMQInitialContextFactory
ChannelTypeMail=com.bas.basserver.channels.EmailChannelType
MaxNmbOfRepeats=1000
ChannelTypeSK=com.bas.basserver.channels.SocketChannelType
NotificationInQueue=dynamicQueues/notifinqueue
EndRange=100000
MaxNmbOfRepeatsWithoutChange=50
AwaresoftHost=localhost
DriverURL=jdbc\:mysql\://localhost/BASDB?user\=root&password\=335PtNgAVrjGTdyw
NotificationOutTopic=dynamicTopics/notifouttopic
JMSFactory=ConnectionFactory
DatabaseName=BASDB
Hub=true
SessionTimeout=1800000
ChannelTypeWebServices=com.bas.basserver.channels.WebServicesChannelType
DatabaseComponent=com.bas.basserver.persistence.dbplugins.MySQLInterface
BusinessName=HUDA
JMS_BROKER_CONNECTOR=tcp\://localhost\:61616
BootstrapURL=jdbc\:mysql\://localhost/?user\=root&password\=335PtNgAVrjGTdyw
ChannelTypeURL=com.bas.basserver.channels.URLChannelType
LocalTopic=dynamicTopics/defaultoutputtopic
LocalQueue=dynamicQueues/defaultinputqueue
DriverClassName=com.mysql.jdbc.Driver
DatabaseNameTest=BASDBTEST
StartRange=1
DocumentEngines=com.bas.basserver.documents.JasperReportsEngine,com.bas.basserver.documents.MSWordDocumentEngine,com.bas.basserver.documents.TextDocumentEngine,com.bas.basserver.documents.HtmlDocumentEngine,com.bas.basserver.documents.MSExcelDocumentEngine,com.bas.basserver.documents.MSWordXMLDocEngine
RequestQueue=dynamicQueues/skinputqueue
ReplyTopic=dynamicTopics/skoutputtopic

[Jaymer]

Never built an executable.
Why would you do this?

[ACDC]

I don't think its got to do with the executable, unless at build time it took on DB settings that don't match your MySql runtime site

Your password in the BASServer.props file is not the same as your MySql DB password.Have you tried connecting to the DB with an external program of some sort using the same password OR the setup of the Port setting on Mysql is wrong (maybe connecting to the wrong DB instance)

[ACDC]

Never built an executable.
Why would you do this?

I am not sure about this case, but building an Executable runtime version of your BSV allows a developer to brand the installation files and the control panel with customised License and copyright acknowledgement and then ship the exe to your customer for easy installation. Best used with Derby Database for easy database setup

[yahya]

If I connect to mySql with the workbench using the same password everything connects without a problem.

In troubleshooting, I setup an EC2 instance on Amazon with a mySQL db instance aswell within the same security group and ran the executable and no errors everything worked. Yet on this hosted server where mySQL is running on the same server I get the error.

So it has told me that the executable is working fine but something to do with the configuration of the windows server. The trouble is to figure out what that problem is.

[Jaymer]

just to clarify for us...

-------- I don't think this is your setup: --------------
you installed AIM executable on PC1
MySQL is on Server1
This gives connection error when starting AIM
On PC1, you can connect (using MySQL workbench) to Server1

--------- after re-reading, possibly this -------------

Yet on this hosted server where mySQL is running on the same server I get the error.

you installed AIM executable on Server1
MySQL is on Server1
This gives connection error when starting AIM
On Server1, you can connect (using MySQL workbench) to Server1

if so, then Firewall has nothing to do with it.
And "localhost" should work just fine.
Try adding your port #, even if you're still on default 3306

--------- for testing, you tried this -------------
you installed AIM executable on AWS server Windows Server instance
MySQL is on AWS
Executable installed on AWS connects fine

FWIW, remember that we (AIM) had a severe Email limitation on Upcloud.
For some reason, emailing from Aware had a significant problem - yet all other things were fine.
Perhaps you need to try ANOTHER hosting service in case you are chasing a problem which has no solution... because you have proved this works fine on AWS.