FMPS 11 Compatability
Alan Barker
via web
I keep checking back hoping that there is a new compatible version of AutoSender that will work with the new FMP Server Advanced V11. I've sent a couple of e-mails, but have yet to get a reply. The web site states that a compatible version should be available end of April-May time frame. It is now June-1; I would really like to get realistic update time-frame.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by luk on 01 Jun, 2010 09:03 PM
We are very sorry for the delay… but expect to have a public beta version available by June 18, with the final release now planned before FileMaker DevCon in August.
We'll make sure that you are notified as soon as the beta goes public.
3 Posted by Alan Barker on 09 Jun, 2010 12:13 PM
Thanks you for the update. I can live with that, I was fearful that there was a more serious delay, I am holding back deploying FMPSA11.
4 Posted by Alan Barker on 22 Jun, 2010 06:11 PM
Any news on the FMPSA-11 compatible update?
Support Staff 5 Posted by luk on 24 Jun, 2010 05:10 AM
Unfortunately, we are still having a number of issues with our internal beta release that prevent us from releasing an external beta version. You are already on the list of people to contact as soon as the beta build is ready.
6 Posted by Alan Barker on 23 Aug, 2010 04:24 PM
Hello - Still looking for a version I can use on Server11Advanced. I was hoping you would have something before Dev-Con.
Could you please share with me what the issues are? Do I need to start looking for an alternate solution because there is little hope of AutoSender ever working on FMPSA11?
Thanks,
Alan Barker
Emerson Motors
Support Staff 7 Posted by luk on 23 Aug, 2010 04:28 PM
Hi Alan,
Sorry for the delay. We think we've finally ironed out the remaining problems and should have a stable beta release by the end of the week. You will automatically be notified.
8 Posted by j.b on 26 Aug, 2010 03:40 PM
Hey Luk! I'm under pressure to upgrade my client's six Mac OS X 10.6 servers from FMSA9 to FMSA11. And the only real holdup is AutoSender. I know you're up to your eyes in it at the moment, but is there a real likelihood that I could schedule the update for Monday 31st? It's a public holiday in the UK so it would be ideal. Kind regards, JB
Support Staff 9 Posted by luk on 26 Aug, 2010 03:45 PM
Hi John,
We have finalized the external beta for the Windows build today, but have some pending issues with the Mac installer - I could, however, provide you instructions for manual removal and new installation by the weekend, I guess.
Luk
Support Staff 10 Posted by luk on 27 Aug, 2010 02:44 PM
Hi John, if they are using JDBC to connect to the data source(s), then they will need the upgrade to version 3. The upgrade will be Eur 49,-.
What's new ?
- Works with FileMaker Server 11's new JDBC engine - Added "Test connection" option for checking the connection to the data source - Added ability to move sources up and down in list view - Added ability to make a source active or inactive from the list view - Added "Notes" field to add comments about a certain source - Added "From (name)" and "To (name)" fields, e.g. "from"="***@apple.com" and "From (name)"="Steve Jobs" - Added ability to send e-mail admin notifications when AutoSender encounters certain types of errors
11 Posted by j.b on 27 Aug, 2010 05:02 PM
Ta!
12 Posted by Alan Barker on 30 Aug, 2010 12:20 PM
Sorry for double posting, I sent this same information back to your E-Mail address; but thought that potentially others were seeing the same problems.
I've just installed the AutoSender 3 beta on my FMPSA11 machine. The Installshield program went all the way through it's process. I have a new myFMbutler Auotsender folder on my desktop. Along with a AutoSender service - but that service is not started.
When I double click on the "myFMbutler AutoSender Config.exe" application, it does not resond.
When I try to manually start the Service, I get an error message "Error 1067: The process terminated unexpectedly.
My environment is a Virtual Machine running Windows Server 2003 R2 SP2 with 4GB of RAM.
FileMaker Server Advanced Version 11 is installed, and running fine.
I have even rebooted the server (something that I can NOT do during the workday), but the results are the same, I can not start the service.
Support Staff 13 Posted by luk on 30 Aug, 2010 12:28 PM
Hi Alan,
Please uninstall the build you had, and redownload from the same link. There was an issue that occurred only on "legacy" systems, i.e. XP and Win 2003. It should be resolved now.
Luk
14 Posted by Alan Barker on 30 Aug, 2010 02:49 PM
Ok, I've un-installed & then re-installed the new version (that has the same build Number). Now the service starts, and I can bring up the AutoSender configu utility, but that is as far as I can go. Adding a new datasource, or even trying to get the existing example to work locks up the service - I have to shut it down by TaskManager. I need to use the JDBC/ODBC mail function, and simply pressing the Test SMTP button locks it up.
Support Staff 15 Posted by luk on 31 Aug, 2010 06:53 AM
Hi Alan,
Using the same build on one of our Windows 2003 test servers, we seem to be unable to reproduce the issue.
Are you using AutoSender with a JDBC data source on FMS 10 or 11 ? Did you select the correct connection protocol for either FMS10 or FMS11 ?
If the data source information is incorrect, the AutoSender Config app will indeed temporarily seem to "lock-up", but it will time out after about 20 seconds.
16 Posted by Alan Barker on 31 Aug, 2010 06:24 PM
Yes this is on the Windows 2003 Server R2 SP 2 platform.
Within the AutoSender configuration, I have selected the jdbc >= FMS11 radio button.
FMPSA11 is also configured to use ODBC/JDBC; although I do have XML.XSLT turned off.
On the Notifications tab, it does successfully connect to our smtp server, but pressing the test connection button on the Connection info tab still causes the lock-up condition.
Alan
17 Posted by Alan Barker on 02 Sep, 2010 01:22 PM
I have restarted my FMPSA11 machine, and have had a little bit of luck getting the new AutoSender utility to work. The service was completely hung prior to the reboot, and would not even shut down cleanly.
I dropped my 2.5 license files into the Preferences folder, but apparently it does not like the format of the old file, and it states that it is running in demo mode.
The Configuration utility does now startup and shutdown cleanly, and it passes the "Test Connection" test, but it does not actually send an e-mail.
I've turned on the Chatty Log level, and am including a little bit of the Autosender.log file. Can you suggest something to get this software to function properly?
Sep 1, 2010 8:16:37 AM INFO AutoSender (c) 2005-2008 SHpartners
Sep 1, 2010 8:16:37 AM INFO Version: 3.0.0.262 date: 2010/08/19 19:36
Sep 1, 2010 8:16:37 AM INFO JVM version: 1.6.0_20
Sep 1, 2010 8:16:37 AM INFO Sep 1, 2010 8:16:37 AM
Sep 1, 2010 8:16:37 AM INFO AutoSender: license corrupt, running in trial mode - 28 days remaining.
Sep 1, 2010 8:16:38 AM CONFIG AutoSenderJDBC.checkSource: processing 1 mails
Sep 1, 2010 8:16:38 AM SEVERE AbstractAutoSender.sendMailRecords: Exception thrown while sending selected mails: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
Sep 1, 2010 8:16:43 AM CONFIG AutoSenderJDBC.checkSource: processing 1 mails
Sep 1, 2010 8:16:44 AM SEVERE AbstractAutoSender.sendMailRecords: Exception thrown while sending selected mails: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
Sep 1, 2010 8:16:49 AM CONFIG AutoSenderJDBC.checkSource: processing 1 mails
Sep 1, 2010 8:16:49 AM SEVERE AbstractAutoSender.sendMailRecords: Exception thrown while sending selected mails: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
Sep 1, 2010 8:16:54 AM CONFIG AutoSenderJDBC.checkSource: processing 1 mails
Sep 1, 2010 8:16:54 AM SEVERE AbstractAutoSender.sendMailRecords: Exception thrown while sending selected mails: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
Sep 1, 2010 8:16:59 AM CONFIG AutoSenderJDBC.checkSource: processing 1 mails
Sep 1, 2010 8:16:59 AM SEVERE AbstractAutoSender.sendMailRecords: Exception thrown while sending selected mails: javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client
Support Staff 18 Posted by luk on 02 Sep, 2010 01:30 PM
Hi Alan,
Version 3 requires new license files - so it's normal that the old licenses no longer function.
The error seems to point to an e-mail autentication problem. Can you turn on smtp logging, then restart AutoSender, and see what's in the smtp.log file ?
Support Staff 19 Posted by luk on 03 Sep, 2010 09:36 AM
Alan,
Can you confirm that "Test SMTP settings" returns "Connection successfully tested " ?
Luk
Support Staff 20 Posted by luk on 03 Sep, 2010 12:23 PM
Hi Alan, I have forwarded the issue to development. I'll keep you posted.
Support Staff 21 Posted by luk on 09 Sep, 2010 08:44 AM
Hi Alan,
Here's the extensive reply from our development team:
The bottom of the log shows unsuccessful SMTP connections for AutoSent-e-mails. The thing is - AutoSender has multiple sets of SMTP connection setups, and all this really tells us is that the first set (for notification) is correct, whereas the second set (for the database-originating outgoing e-mails) is incorrect.
The message "No authentication mechansims supported by both server and client" means that the SMTP server does not accept any of the authentication mechanisms that AutoSender understands. Normally that means that the e-mail server should be reconfigured to allow one of the authentication mechanisms that JavaMail (which underpins AutoSender) understands.
I checked a bit deeper, and if I had to guess, it looks to me like the initial part of the log was created from SMTP settings without authentication (i.e. I am guessing the 'Notification' setup screen has an empty username/password, whereas the 'SMTP Server' setup probably has authentication information, i.e. non-empty username/password). That would explain the observed behavior, and also mean that this mail server is currently configured to only accept anonymous connections.
To examine this further, we'd need to see the configuration that was used on the 'Notification' tab, as well as the configuration on the 'Sources' - 'SMTP server' tab: the first question is: are these set up identically?
Support Staff 22 Posted by luk on 15 Sep, 2010 01:46 PM
Hi ALan,
Would it be possible to do two things:
1° send us a copy of the Prefs file com.myfmbutler.autosender.configuration.xml
2° the latest log was probably with a log level set to "info". Could you temporarily set the log level to e.g. chatty and then send us a copy of that log? - Be sure to set the log level to normal again after the test, as the file size can grow rapidly when "chatty' is on.
Support Staff 23 Posted by luk on 16 Sep, 2010 12:50 PM
Alan,
We are pretty sure it has to do with the mail server configuration.
We found this snippet of info - I am assuming this is a Microsoft e-mail server:
... By default Exchange 2007 is configured to only accept SMTP email for domains it is authoritative for, and will only relay email onto other domains for authenticated local users. Usually for Outlook/OWA based clients this is entirely sufficient as even when connecting from remote locations the clients appear to be local to the Exchange Server so it is happy to relay for them. This is thanks to the connection mechanism, Outlook Anywhere and OWA both route the email data through the IIS server, or a user on a VPN will appear to be on the LAN.
...
So, if it is an Exchange server, the SMTP server will accept unauthenticated connections as long as you send to a local (internal) e-mail address, but will not accept unauthenticated connections for sending to 'outside' e-mail.
The only way to get the mail to go out is to enable authentication on the mail server, and to make sure the SMTP server accepts one of the authentication protocols used by AutoSender: CRAM-MD5, LOGIN, PLAIN, DIGEST-MD5, NTLM.
The system administrator should understand those and be able to reconfigure the mail server so it allows relaying for authenticated connections, and should be able to enable at least one of the above authentication protocols.
Let me know if this helps,
Luk
24 Posted by Alan Barker on 05 Oct, 2010 08:45 PM
Luk -
Have you guys found any solution to the problem?
I'll attach the reply I got back from our email administrator, which didn't seem to resolve anything, from what I could see. My question to you (again) is that AS 2.5 seems to work perfectly as the anonymous login, why doesn't 3.0?
Additionally, the AS 3.0 fails on "internal" e-mail addresses, as well as external.
Alan
-----Original Message----- From: Barker, Al [MOTORS/EMC/STL]
Sent: Thursday, September 16, 2010 7:58 AM
To: '***@myfmbutler.com'
Subject: RE: FMPS 11 Compatability [AutoSender]
Luk -
I will approach our email administrator, yes you are correct we are using MS Exchange 2007.
I have a question, however, I'm using this exact same setup with AutoSender 2.5 on my production FMPS-10 machine. Shouldn't AS 2.5 be having the same problems? It is working perfectly.
Alan
Support Staff 25 Posted by luk on 06 Oct, 2010 08:05 AM
Hi Alan,
1° We didn't get the reply from your administrator. Could you send that to us ?
2° Sorry to ask this again, but would it be possible to create some new SMTP logs at the highest setting, both with AS3.0 and AS2.5 using the same SMTP server ? That way we could do a side by side comparison.
26 Posted by al.barker on 03 Jan, 2011 08:56 PM
Still looking for a resolution to the problems described numerous times with the Beta version of AS 3 and our FMPS11 running on a VM. It still does not work never has. This has been dragging on for quite some time, does FM Butler intend to field a product that works with the current version of FMPS, or not?
Alan
Support Staff 27 Posted by luk on 04 Jan, 2011 08:30 AM
Hi Alan,
Just to be sure, have you tested with the final candidate version, released on Dec. 3rd: http://blog.myfmbutler.com/?p=695 ?
The final candidate did contain an update for some of the SMTP code, so it may make a difference.
I'm afraid this is an issue we may not have been able to address - but it also seems to be an isolated issue that we haven't seen anywhere else with people using the AutoSender 3 beta, even in environments with Microsoft Exchange.
28 Posted by al.barker on 04 Jan, 2011 06:46 PM
Luk - The new version does indeed fix the problems I was having, and it is now working on my development v11 machine! I never received any sort of message or notice from FMbutler that there was a new version to try - I certainly would have tried earlier, had I known.
So, now the next step - how do I go about getting an upgrade to the v3.0 from my current v2.5 software? When do you intend to finalize this beta, and release it as production?
Alan
Support Staff 29 Posted by luk on 04 Jan, 2011 08:03 PM
Hi Alan,
Mea culpa, I'm very sorry you weren't notified.
We'll be releasing later this month, most likely within the next two weeks. At that time you will be able to order the upgrade.
luk closed this discussion on 05 Jan, 2011 08:53 AM.