Server Busy Error When Logging into Custom Siebel Automotive Application Using Custom Object Manager
(Doc ID 2334261.1)
Last updated on MARCH 17, 2020
Applies to:
Siebel CRM - Version 17.1 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
User is unable to login to custom application "Siebel_Automotive_Custom" after upgrade to IP2017.
Errors reported:
Steps
• Upgrade Siebel version to IP2017
• Deploy AI profile for the custom Object Manager - Siebel_Automotive_CustomAppObjMgr_enu
• On the custom object manager change Application Name , Title and splash text to "Siebel_Automotive_Custom"
• Also change config file to auto.cfg
• When accessing the custom application "Siebel_Automotive_Custom", application doesn't load up
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |