How get past repeated 5321 error on AWS Jaspersoft Pro datasource connect?

[andy_1]

Hi,

I followed all AWS Jaspersoft Pro install instructions in the installation video http://www.youtube.com/watch?v=JSMUBxj8P40&feature=youtu.be.  I have a running RDS data source in same EC2 .  I even logged into the EC2 instance running my Jaspersoft Pro and from there can even successfully open MySQL command-line client into my RDS database.  So no security or access errors, even from the running Jaspersoft EC2 instance on EC2.  However when I follow instructions in the "Connect" video

and I go to add the datasource to my Jaspersoft Pro EC2 instance, I get alert:  "An error has occurred. Please contact your system administrator. (5321)" as pictured below.

(I whited out my username above)

From my terminal into the EC2 instance I navigated to /var/log/jasperserver and look at file jasperserver.log and for every failed connection attempt with alert box like above, there's an entry like the two below:

 

2013-05-02 02:14:19,318 ERROR Validator,http-bio-80-exec-1:408 - [sECURITY FAILURE context=password-addDataSourceFlow_context, key=reportDataSource.password, type(AlphaNumPunctuation)=^[p{L}p{M}p{N}p{Pd}p{Pi}p{Pf}p{Pc}p{Po}p{Sc}p{So}p{Sm}p{Cf}p{Z}s=()[]~|{}`^+&&[^]]*$, input=M->kab7-=FDIj3N, maxLength=500, isBlacklist=false]

2013-05-02 02:28:38,256 ERROR Validator,http-bio-80-exec-4:408 - [sECURITY FAILURE context=password-addDataSourceFlow_context, key=reportDataSource.password, type(AlphaNumPunctuation)=^[p{L}p{M}p{N}p{Pd}p{Pi}p{Pf}p{Pc}p{Po}p{Sc}p{So}p{Sm}p{Cf}p{Z}s=()[]~|{}`^+&&[^]]*$, input=M->kab7-=FDIj3N, maxLength=500, isBlacklist=false]

I even assumed maybe somehow the installed EC2 instance was somehow corrupted.  Spent another couple hours installing a 2nd Jaspersoft Pro EC2 instance from scratch, this time using one-click and just using AWS credentials to access RDS.  So slightly different install approach.  But everything worked, could even see my RDS instance.  But died again at exact same point above.  So I've now got two separately installed fulling running Jaspersoft Pro server instances, BOTH dying with this 5231 internal error.  Very frustrating that Jaspersoft Pro doesn't seem to work at all.  Can't even get it off the ground.

Please help!  Let me know if any other info needed to help isolate root cause.

Thanks!

-Andy

 andy@theresumator.com

 

[andy_1]

Figured it out.  Jaspersoft does not allow for special characters within database passwords.  I re-generated a DB password with only letters and digits on my RDS database and then repeated the Datasource Connect steps above and I did NOT get the 5321 error...it worked.  Be forewarned:  Jaspersoft will not connect to a MySQL/RDS database that has a password with certain special characters.

-Andy