FM Server Advanced / Auto Sender 3 Connection Issues
Hello,
We cannot get our FileMaker Server Advanced 11 server to work with Auto Sender 3.
Everything appears to be set up properly, the "Test Connections" come back properly, we see AutoSender logged into the files, but we get the following error. We have the exact same files running on a FileMaker Server Advanced 10 server connecting to Auto Sender 2.5 with no problems.
We are running the most recent version of FileMaker Server Advanced, 11.0.3.309.
Please help, this is really holding us back.
Sep 15, 2011 12:30:24 PM INFO AutoSender (c) 2005-2010
SHpartners
Sep 15, 2011 12:30:24 PM INFO Version: 3.0.1.267 date: 2010/12/02
19:26
Sep 15, 2011 12:30:24 PM INFO JVM version: 1.6.0_24
Sep 15, 2011 12:30:24 PM INFO Sep 15, 2011 12:30:24 PM
Sep 15, 2011 12:30:24 PM INFO AutoSender: licensed: myFMbutler
AutoSender 3 # 1102030613 - licensed to iDONATEpro
Sep 15, 2011 12:30:25 PM SEVERE AutoSenderJDBC.checkSource:
Exception "null" thrown. Unable to fetch message: do you have an
error in the fieldnames?
Sep 15, 2011 12:30:30 PM SEVERE AutoSenderJDBC.checkSource:
Exception "null" thrown. Unable to fetch message: do you have an
error in the fieldnames?
Thank you!
- Forrest
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Forrest Howell on 16 Sep, 2011 07:41 PM
Hello,
Have you had a chance to read the prior post? Suggestions?
We have tried changing field names, type, etc. and we still get errors. The exact configuration in FileMaker Server 10 Advanced connecting to Autosender 2.5 works perfectly. Is there something we should be looking for?
Please respond. This is really holding us back.
Thank you,
Forrest
3 Posted by gagelerp on 19 Sep, 2011 12:57 AM
Sorry - I don't think I can help.
AutoSender 3 has been working fine for me with FileMaker Server Advanced 11 server, but I am not using a JDBC connection, just http (xml).
I note however that on the Connection Info Tab of myFMbutler AutoSender Configuration that there are two "Protocol" settings for jdbc - one for FMS10 and one for FMS11. So presumably something changed in jdbc with the latest version of FMS. Make sure you have that setting correct.
Otherwise, you will need to contact the vendor. They have been very responsive in the past when I have had issues.
All the best.
luk closed this discussion on 17 Oct, 2011 07:05 AM.