Hmmm, email issues can be pretty complex. Are there any hints in the tomcat and other logs? What platform are you running on, including all the infrastructure?

I'm looking somewhat blindly here but...

In the stdout log it had an error saying it couldn't write the centric logs (path didn't exist). I made the path and now I have centric logs.

Nothing seems out of the ordinary. The only thing that I noticed was in the stdout log it makes mention of an email key and where it is supposed to reside. Email.key is not there. survey2.key does exist.

Like I said what is strange is that I can send a 'instant campaign' and that seems to go through just fine. It almost seems as though the chron job isn't picking this up.

Any directions on what I should be looking for in the log files?

Thanks!

Hey Bryan --

i have a few questions to start out --

Which version of Concourse Suite are you working with?
What OS are you running Tomcat in?
Also, which versions of Java and Tomcat are you using?

I suspect that the group that you have selected for the email campaign may not all have properly defined email addresses. That can cause the sendmail cycle to unexpectedly terminate.

Thanks,
J

Bryan Lumbra wrote:
I'm looking somewhat blindly here but...

In the stdout log it had an error saying it couldn't write the centric logs (path didn't exist). I made the path and now I have centric logs.

Nothing seems out of the ordinary. The only thing that I noticed was in the stdout log it makes mention of an email key and where it is supposed to reside. Email.key is not there. survey2.key does exist.

Like I said what is strange is that I can send a 'instant campaign' and that seems to go through just fine. It almost seems as though the chron job isn't picking this up.

Any directions on what I should be looking for in the log files?

Thanks!

-Apache Tomcat/5.5.26
-Concourse Suite 5.0.5 Enterprise (2008-03-18)
-Windows Server 2003
-Java 6 update 5

I have added just one contact to the group (myself) and this is the same contact I have used to sent the emai (instant campaign). So I'm 100% the email is valid.

Is there a log of the sendmail chron job that I would be able to find to see if its even happening?

Joshua Fielek wrote:
Hey Bryan --

i have a few questions to start out --

Which version of Concourse Suite are you working with?
What OS are you running Tomcat in?
Also, which versions of Java and Tomcat are you using?

I suspect that the group that you have selected for the email campaign may not all have properly defined email addresses. That can cause the sendmail cycle to unexpectedly terminate.

Thanks,
J

Okay, Bryan, I see one conflict -- we don't support Java 6 yet. There are some changes that we have not yet accommodated that could be having an influence here. Try using Java 5, any of the later revisions, for starters.

To see more detail on the process for the Campaign emails, you can enable debugging output by locating the build.properties file for the installation and adding the following line:

DEBUG=true

The build.properties file will be in the fileLibrary that you specified when you installed the product.

Debug output is sent to the Tomcat log file -- catalina.out. You can trace the actions within the debug output to see if there is anything readily apparent.

Thanks,
J

Bryan Lumbra wrote:
-Apache Tomcat/5.5.26
-Concourse Suite 5.0.5 Enterprise (2008-03-18)
-Windows Server 2003
-Java 6 update 5

I have added just one contact to the group (myself) and this is the same contact I have used to sent the emai (instant campaign). So I'm 100% the email is valid.

Is there a log of the sendmail chron job that I would be able to find to see if its even happening?

Ok, I think I might be on to something.

I did go back and install Java 5.

I verified it through javatester.org as version 1.5.0_12.

It still doesn't work. Here is a sample of the output from the stdout.log.

---> EmailKey is y:\CentricCRM\fileLibrary\centric\centric_crm\keys\email.key
---> EmailKey is y:\CentricCRM\fileLibrary\centric\centric_crm\keys\email.key
---> EmailKey is y:\CentricCRM\fileLibrary\centric\centric_crm\keys\email.key
---> EmailKey is y:\CentricCRM\fileLibrary\centric\centric_crm\keys\email.key
---> EmailKey is y:\CentricCRM\fileLibrary\centric\centric_crm\keys\email.key
java.io.IOException: Wrong key size
at org.aspcfs.utils.PrivateString.loadEncodedKey(Unknown Source)
at org.aspcfs.utils.PrivateString.loadEncodedKey(Unknown Source)
at org.aspcfs.utils.PrivateString.generateEncodedKeyFile(Unknown Source)
at org.aspcfs.utils.PrivateString.<init>(Unknown Source)
at org.aspcfs.apps.notifier.Notifier.buildCommunications(Unknown Source)
at org.aspcfs.modules.admin.jobs.NotifierJob.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)

Then it repeats the above pasted.

Hi Bryan,

Thanks for the stackTrace fragment. The Notifier.buildCommunications method actually relies on a key found in the survey2.key file located in the same directory as indicated by your log file (y:\CentricCRM\fileLibrary\centric\centric_crm\keys\survey2.key). This file should contain a 16 digit hex number.

Can you verify the file exists and if there is anything inside of it?

File Exists = Confirmed

Anything Inside = Negative!

Lorraine Bittner wrote:
Hi Bryan,

Thanks for the stackTrace fragment. The Notifier.buildCommunications method actually relies on a key found in the survey2.key file located in the same directory as indicated by your log file (y:\CentricCRM\fileLibrary\centric\centric_crm\keys\survey2.key). This file should contain a 16 digit hex number.

Can you verify the file exists and if there is anything inside of it?

Okay, The key should have been generated and then written to the file, the first time the method was invoked. For some reason the file was created, but no key was saved that first time, and now campaigns throw an error when it finds the file is empty.

You may want to try either of the following:

1) Delete the survey2.key file, and try running the campaign again. When the file cannot be found it should generate a key and save the file. If the problem still persists then we know that there is a bug that needs to be addressed. Since the key is generated fine in my own testing I'm guessing it is something in the deployment environment that leads to the bug.

2) If #1 fails, while the bug is being addressed, you can create a random 16 digit hex number and save it to the file and see if email campaigns will run successfully. An example of a valid random hex would be: 689be5c785cbd389

Success!!!

I tried deleting the file and it wasn't recreated. I didn't, however, try restarting the server or anything.

I recreated the file and added a random hex number and lift off!

Thanks so much for all your help. I'm pretty excited to use this product. The campaigns were the biggest reason I wanted it.

-Bryan

Lorraine Bittner wrote:
Okay, The key should have been generated and then written to the file, the first time the method was invoked. For some reason the file was created, but no key was saved that first time, and now campaigns throw an error when it finds the file is empty.

You may want to try either of the following:

1) Delete the survey2.key file, and try running the campaign again. When the file cannot be found it should generate a key and save the file. If the problem still persists then we know that there is a bug that needs to be addressed. Since the key is generated fine in my own testing I'm guessing it is something in the deployment environment that leads to the bug.

2) If #1 fails, while the bug is being addressed, you can create a random 16 digit hex number and save it to the file and see if email campaigns will run successfully. An example of a valid random hex would be: 689be5c785cbd389