Skip to main content
Question

CBS - Unhandled Exception


Forum|alt.badge.img+5

Hi All,

 

I’m getting below error when installing CBS in a customer application server. This customer is in Apps10 UPD13. CBSSERVER user is active in application and db. Also, it is possible access the db using sqlplus. Can anyone help to solve this issue?

Thanks,

Dilshani

This topic has been closed for comments

3 replies

Forum|alt.badge.img+3
  • Do Gooder (Partner)
  • 6 replies
  • May 12, 2022

I got the same error. Windows Server 2016, Oracle Client 19c 64bit, Apps10 UPD13.

 

The CBS works only with 32 bit version of Oracle client.


Forum|alt.badge.img+7
  • Sidekick (Employee)
  • 88 replies
  • May 12, 2022

LABAHU is correct about the 32 bit version of Oracle client when using CBS.  This is likely the cause of the Oracle error shown above.  Make sure the CBSSERVER user’s credential is valid (it’s case sensitive, of course).  Also make sure to use the correct version of CBS installation media, i.e. probably the one from the most recent UPD-level delivery, when installing.

Also, once the Oracle connectivity issue has been resolved, note there is Manufacturing-related configuration which should be done prior to (or concurrent with) CBS server installation.  Make sure the CBSSERVER user has been authorized for the company and site which is intended for use with the CBS process.  Once the initial installation has been completed the CBS service will throw errors unless this has been done and at least one valid flow has been created for the service.  A business analyst with background in Manufacturing can help in this area.


Forum|alt.badge.img+1

Make sure the CBSSERVER user’s credential is valid (it’s case sensitive, of course).  Also make sure to use the correct version of CBS installation media, i.e. probably the one from the most recent UPD-level delivery, when installing.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings