VERIFIED SOLUTION i

EngageOne error: "The following EJB could not be allocated: ConfigInterfaceEJB"

JBoss 5.1.0 
EngageOne: 3.1.2.26471 Build 46 
Designer: 6.4.0.52 
EngageOne OS: Windows Server 2008 r2 Enterprise 
JDK 1.6.0_45 
Not clustered. 
New EngageOne installation.
Never successfully ran NA-batch any template or delivery channel.
Template resources all green check-marks. 
SQL: 10.50.6000.34 (2008 R2 Service Pack 3) 64-bit
EngageOne Generate: 6.1.1444.0 upgraded to 6.4.0.52

Issue

This is a new installation of EngageOne.  When running NA-batch processing, the logs show the EngageOne error: "The following EJB could not be allocated: ConfigInterfaceEJB"

Cause

I believe the editing of the EAR file to update the version was not done correctly.  File permissions on the server likely caused this issue.
 

Resolution

UPDATED: March 30, 2017
I recommended the client perform edits of the EAR on their local machines next time.