E-mail problem with PC 11 on W7 Pro 64

[eraccusa]

Hi all,

A church for which we do the systems support has recently had us build new systems to upgrade some of their XP Pro systems to W7 Pro 64-bit. The data is on a SAMBA 3.5.3 Linux server. All appears okay on the new systems until they attempt to send any e-mail from within PC 11. When they attempt to send an e-mail they are getting the error in the attached image. A test of the e-mail logs an error saying something about an "invalid token", but we did not get a screen capture of that. This is only on the new systems running Windows 7 Professional 64-bit. The old systems still on XP Professional 32-bit work fine for sending e-mail from PowerChurch.

Yes, all the e-mail settings for each user are correct. E-mail from Outlook 2010 is working just fine with the same e-mail settings and server as in the PowerChurch settings (This is going through a gmail associate business customer for those who will ask. So it is standard gmail settings with the port number: server.name:port.). The new systems have AVG Internet Security 2011 64-bit installed and PowerChurch is allowed through the firewall on each system. IOW the C:\ProgramData\PowerChurch\PCPLUS11\PCPLUS11.EXE file is allowed full network access. Is there anything else we can do to make this work? Thanks.

[tborgal]

I had some issues running PC+ on W7 when I was not running it directly from the root directory. You might want to try moving the Powerchurch directory directly under the C: drive and see if that resolves your problem.

[Tracy]

That path is correct for an application which is running from a workstation.

The actual problem is the CSMail object is outdated. There was an issue with SSL type connectivity and Windows Vista/7 64-bit machines. I'm not sure how this old build is running on your system.

If running the PC11EMAIL.EXE in the PCPLUS11\Install folder on the network does not correct this problem, download this file and overwrite the existing one.

[eraccusa]

The downloaded update to PC11EMAIL.EXE appears to have fixed the problem once we ran it on the new PC systems. Thank you.