I've experienced this issue if the application is using a SQL login and the @ character is in the password. I could never get the application to connect properly so had to change the password (the application was running on a standalone legacy server so windows authentication wasn't an option)