AM BW 6.3.4 - Module Configuration Error

Salman Riaz 2 · December 23, 2016

Hi,

I am new to TIBCO BW world and trying out some examples like hello world.

I am constantly getting this annoying 'Module Configuration error. The BusinessWorks module [MyProj.module] has no process to execute' when ther is already a simple process with 'Timer' and 'Log' Activity.

Additionally, Module Desccripts always shows red cross sign represending errors. When i open 'Components' tab i see nothing. This is very annoying as i am unable to run a basic project and continue to have create a new project everytime.

I am sure i am missing some basic tips/tecniqus here which could reset/refresh the errors when

The problemusuallyoccurs when i start developing a new process and it has some errors. Despite resolving any visible errors the project remains undeployable and continue to fail when starting application.

Many thanks in advance!

Saliaz

Error =================================================================================

22:36:58.559 INFO [main] com.tibco.bw.frwk.engine.BWEngine - TIBCO-BW-FRWK-300002: BW Engine [Main] started successfully.

22:36:58.646 INFO [Framework Event Dispatcher: Equinox Container: c0f66d4b-60c9-0016-1d8c-e59468c6a058] com.tibco.thor.frwk.Deployer - TIBCO-THOR-FRWK-300001: Started OSGi Framework of AppNode [bWEclipseAppNode] in AppSpace [bWEclipseAppSpace] of Domain [bWEclipseDomain]

22:36:58.731 INFO [Framework Event Dispatcher: Equinox Container: c0f66d4b-60c9-0016-1d8c-e59468c6a058] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300018: Deploying BW Application [MyProj1:1.0].

22:36:58.763 ERROR [Framework Event Dispatcher: Equinox Container: c0f66d4b-60c9-0016-1d8c-e59468c6a058] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-600026: Failed to start BW Application [MyProj1:1.0]. Reason: TIBCO-THOR-FRWK-600011: Error occured processing property initialization of Application [MyProj1{MyProj1, [bw-application,], 1.0, MyProj1_1.0.0.qualifier [288], Deploying {creating bw-application }}].

com.tibco.neo.exception.BaseException: TIBCO-THOR-FRWK-600040: The value of the Module Configuration Property [/newGroup/newProperty] is not set or null

22:36:58.767 INFO [Framework Event Dispatcher: Equinox Container: c0f66d4b-60c9-0016-1d8c-e59468c6a058] com.tibco.thor.frwk.Application - Started by BusinessStudio, ignoring .enabled settings.

!SESSION 2016-12-23 22:36:49.829 -----------------------------------------------

eclipse.buildId=unknown

java.version=1.8.0_102

java.vendor=Oracle Corporation

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB

Command-line arguments: -dev file:E:/Workspaces/tibco/.metadata/.plugins/org.eclipse.pde.core/BWApplication/dev.properties -os win32 -ws win32 -arch x86_64 -consoleLog -console -clean

!ENTRY org.eclipse.osgi 4 0 2016-12-23 22:36:58.770

!MESSAGE Bundle MyProj1_1.0.0.qualifier [288] is not active.

Vivek Ojha · December 27, 2016

Hi Salman,

Assuming you are using Applicaiton Module. Go to Module descriptor -->Componentsand make sure your process is displayed there.

If not then go ahead and add the process. This should resolve the isssue. If not then please attach the error screenshot.

Milan sahoo 3 · January 2, 2017

Check in Studio you have created a new module propery "/newGroup/newProperty" and forget to asign its value , So at run time when BW engine starts its finds some property value missing and deactivate your module.

Error:

com.tibco.neo.exception.BaseException: TIBCO-THOR-FRWK-600040: The value of the Module Configuration Property [/newGroup/newProperty] is not set or null

Thanks,

Martin Meijer 2 · September 6, 2019

It can also be another resolution to this problem! I just solved the same error in my project and I found that the TIBCO.xml in my applicationcontained an entry that was erroneous

The wrong entry was:

/newGroup/newProperty

xsd:string

public

true

false

And it also contained the correct entry (I made the difference bold):

//Module///newGroup/newProperty

xsd:string

public

true

false

So I just closed Business Studio (as a precaution), removed the wrong entry in the file, saved the file and opened Business Studio again. The result was that debugging worked again!

charulatha Thirumalaisamy · August 16, 2023

I have tried all the possibilities given above still I am getting the below issue,