In this post, I tried to summarize the solution of some common Tibco BusinessWorks development errors.
If I find much more time, I will try to continue this serie.
To solve BW-JDBC-100000 error code you must put OJDBC5.jar file to your Tibco directory such as “C:\tibco\bw\5.9\lib”
” at least two fragment ….” error from JMS queue starter
If you use same WSDL file or same core XSD in another location, you will get this error. To fix this problem you must select first WSDL and remove second WSDL. In the related process you must update the WSDL address with new one.
caused by: Configuration error in field [ Configuration error in field [ Identity ]]
Your_Project_Name\Resources\Identities\Identity.id file missing in your EAR.
Don’t forget to include these 4 files to your LibraryBuilder, if you used them:
- JMS Configuration
- SSL Certificate
- XSD Schema
“failed to execute called process”
If you get the error shown below, your process probably missing in your EAR file.
"Job-6518033 Error in [Services/Special/Genel/Starters/genelspecial.process/Call Implementation] failed to execute called process at com.tibco.pe.core.CallProcessActivity.eval(CallProcessActivity.java:273) at com.tibco.pe.plugin.Activity.eval(Activity.java:240) at com.tibco.pe.core.TaskImpl.eval(TaskImpl.java:775) at com.tibco.pe.core.Job.step(Job.java:729) at com.tibco.pe.core.Job.checkStep(Job.java:518) at com.tibco.pe.core.JobDispatcher$JobCourier.runx(JobDispatcher.java:249) at com.tibco.pe.core.JobDispatcher$JobCourier.run(JobDispatcher.java:200) caused by: com.tibco.objectrepo.NotFoundException: Specified uri does not exist"