Thanks, I think this line of the XML (.dnn) file simply points out what the class name of the Business Controller is.

Now in the web.config file sections, this true.  The first item is the class, the next is the assembly it compiles to.  Good answer, perhaps there just isn't enough data in the screen shots, my bad.

What we ended up doing was leaving the <businesscontroller> tag empty.  That allowed the module to be injected.

It's not ideal but since the optional interfaces are not being used and indeed, they're even commented out 'out of the box' we can get the functionality we need to the site now and clean up things like this later.  I only say this because the module had been compiling all along with no issues and this 'ERROR' class of tag in the logs only started coming up now.

Would love to solve this ASAP, obviously so if anyone has answers, thanks much ahead of time.