Errors running CMs in 10.1

Errors running CMs in 10.1

Postby » Wed May 06, 2015 1:53 pm

Hi all.
I'm just upgrading to 10.1.1.1 at the moment, and having trouble getting my custom modules to run.
Initially, the services would start but nothing was happening. I figured out that I needed to add some lines to the .config file (p48 of the Installation Guide). With that done, some modules work, but others give me a kernelbase error when I start the service like this:

Faulting application name: AALWCBatchProcSrv.exe, version: 1.0.0.0, time stamp: 0x5549af57
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0x158
Faulting application start time: 0x01d088447573037e
Faulting application path: C:\Program Files (x86)\Kofax\CaptureSS\ServLib\Bin\AALWCBatchProcSrv.exe
Faulting module path: C:\WINDOWS\system32\KERNELBASE.dll
Report Id: b3707fb7-f437-11e4-9a5f-005056875324

I'm trying to track this down on the web, and it sounds like it might be something to do with my .Net 2.0 code pointing to something else, but I haven't quite found the answer yet. Has anyone come across this before, or has anyone with a better knowledge of .Net than me (which wouldn't be too hard) got any ideas?
Cheers
- Hayden
Participant
 
Posts: 45
Joined: Tue Dec 14, 2010 8:42 pm
Location: Sydney, Australia

Re: Errors running CMs in 10.1

Postby » Thu May 28, 2015 1:55 pm

Have you tried creating a configuration file for your Custom Module per this KB article?

http://knowledgebase.kofax.com/faqsearch/results.aspx?QAID=18552
If they are going to hate you anyway for what you do, then you might as well put forth your best effort.
User avatar
Participant
 
Posts: 62
Joined: Tue Apr 10, 2007 8:11 am

Re: Errors running CMs in 10.1

Postby » Sun May 31, 2015 2:37 pm

Thanks, yes I made them create that knowledgebase artical, because you had to read the release notes, reference a page in the installation guide, and find a file in the "sources" folder to find that config change.

That worked for some of my CM's, but others are still having the issue. I'm just about to redo them all in .Net 4.0, which will hopefully resolve this... but I'm just a .Net hack, forced into learning it since developing Kofax for the last 5 years...

I'll post an update in case others come across this, but it looks like it might be a straight .Net issue (when working with com objects), as opposed to Kofax related...
Cheers
- Hayden
Participant
 
Posts: 45
Joined: Tue Dec 14, 2010 8:42 pm
Location: Sydney, Australia


Return to Custom Modules General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest