Email Contribution Statements

[DarlingtonHRP]

I've tried three times to email my Contribution Statements for 2009. Each time it says they were sent successfully. My report shows NO email addresses on it. I checked my own email, and it was not sent.
HELP !!

[Tracy]

What version of PowerChurch Plus are you using?
Are you on the latest Maintenance Release? http://www.powerchurch.com/mr

Do you have an E-mail set on one of the profiles with the envelope number, and it has "E-mail contribution statement" checked?

[DarlingtonHRP]

I am using version 10. I have done all of the maint releases.
It worked when I sent just one contribution statement, but does not work when I try to send all.

[Tracy]

What is on the report, since no emails are listed?

[DarlingtonHRP]

It shows the message I typed, but does not list ANY email addresses.

[Tracy]

Is the message long enough to have forced the email list, and success/fail status to the second page?

[DarlingtonHRP]

No, it was very short...just saying that contrib. statement was attached, and thanking for support.
the "subject" line did not print on report either. that just said 2009 Contribution Statement.

[Tracy]

The behavior you are explaining suggests there is an odd paper size settings, or margin settings on the default printer.

One of the solutions which works is installing the HP LaserJet III printer driver to print to the FILE: port. Set this as the Default printer, Start PowerChurch Plus, then e-mail the Contribution Statements. To Print the reports, you will need to select your normal printer in the dialogs. After the process is complete, you should be able to return your default printer to normal and continue working as normal.

[DarlingtonHRP]

I am printing to screen. The emails DO NOT send, yet the report (on screen) says they were sent successfully. I verified, through my own personal email, that they do no send.
When I sent ONE single contribution statement, it sent, and report was correct.
The problem occurs only when I send ALL contribution statements.

[Tracy]

The processes still use the default printer and its current settings to create the reports.

You selected a single envelope number, and processed it the same way as though it was the All Contributions process? I ask this specifically because when a single contribution statement is displayed on the screen, it is possible to e-mail it via the button on the toolbar. This would be two different processes.

Verify that you are running the latest MR in the Help -> About screen.

Are you setting the e-mail settings during the process, or through the system/user screen?

[DarlingtonHRP]

I sent the single statement through the "Individual Contribution Statement" option. I attempted to send all through the "All Contribution Statements" option. Wouldn't they both use the default printer settings?
I chose email statements, in both cases, through the process...I did not use the toolbar.

[Tracy]

Yes, the process is the same code base.
Since the e-mail report is only displaying a part of the information, it suggests printer settings.

Since "Individual Contribution Statement" and "All Contribution Statements" runs the same code internally for sending the e-mails, there is not a reason why one works and the other does not.

There is the possiblity of user authentication issues with the out going mail server. If your individual test went to the same domain as you are using, it may have gone through, the others may not. The "Report" after the e-mails have been sent should display reasons for this information. Since it isn't, talking with a support tech when you are at this point would be the next step.

[PCIMFinance]

I am having a similar problem. I can e-mail contribution statements individually, but when I try to use the "All Contributions Statements" option and try to bulk e-mail the statements I get the following error:
"A problem occurred in the data connection prior to sending the e-mails".

[Tracy]

Get the 1/25/2010 Maintenance Release. Then run pc11oledb.exe in the install folder on the workstation having the problem. This should fix the problem.