My Oracle Support Banner

OBIEE 12.2.1.4: Presentation server fails to start after adding Attributes For Custom Skin In Instanceconfig.xml File : Invalid settings in config : Element 'UI' is not valid for content model : The server 'obips1' with process id xxxxx is no longer alive (Doc ID 2524994.1)

Last updated on APRIL 10, 2019

Applies to:

Business Intelligence Server Enterprise Edition - Version 12.2.1.4.181016 and later
Information in this document applies to any platform.

Symptoms


OBIEE 12.2.1.4: Failing attributes for custom skin in instanceconfig.xml file


 When  adding the UI attributes (see below) for the custom skin in instanceconfig.xml file, presentation services fail to start.


<UI>
<DefaultStyle>Alta</DefaultStyle>
<DefaultSkin>CBP</DefaultSkin>
<SkinMappings>
<skinMapping>
<biadfSkinFamily>bi-alta</biadfSkinFamily>
<biSkin>AltaBitech</biSkin>
</skinMapping>
</SkinMappings>
</UI>
<URL>
<CustomerResourcePhysicalPath>/data/obiee/12.2.1.4/obiee-skin/res
</CustomerResourcePhysicalPath>
<CustomerResourceVirtualPath>/analyticsRes/res
</CustomerResourceVirtualPath>
</URL>
  
  
  

LOG FILE
-----------------------
<Mar xx, 2019 5:22:49 PM EDT> <INFO> <NodeManager ComponentManager> <ORACLE_OBICCS_HOSTS=abc.com:8009>
[Util Logger] Exception occurred:
Severity:5
Type:PKN3saw9ExceptionE
File:project/webutil/configreaderinstance.cpp
Line:725
Message:Invalid settings in config file: Bad config instance '/data/obiee/weblogic/12.2.1.4/domains/taspo_sat_obiee/config/fmwconfig/biconfig/OBIPS/instanceconfig.xml'!

Element 'UI' is not valid for content model: 'All(BIforOfficeURL,SmartViewInstallerURL,BIClientInstallerURL32Bit,BIClientInstallerURL64Bit,SmartSpaceInstallerURL,SESSearchUrl,CatalogPath,CustomerMessageDBPath,EnableCloudRepositoryHelp,CloudRepositoryHelpBaseURL,EnableProductTour,EnableCloudBieeHome,MultipleServiceInstancesSharedLocation,TenancyMode,DefaultTimeoutMinutes,DSN,LightWriteback,RequirePrivilegeForErrorDetailDisplay,ReportAggregateEnabled,XPLowFragmentationHeap,EnablePartialReportUpdate,ActionFramework,ActionLinks,SoapClient,AdvancedReporting,Alerts,AsyncLogon,Authentication,RpdAutoSwitchOver,BriefingBook,CustomLinks,BISearch,TestMDSCatalog,EnableClientState,ClientStorage,FavoritesSyncUpIdleSeconds,Cache,Catalog,BIComposer,Views,Analysis,Formatters,CSV,Cursors,Dashboard,Disconnected,DiscovererServers,HTTP,Hypercube,Drilling,JavaHostProxy,IcapiScanAgent,HTTPSClient,Listener,Localization,Logging,CatalogCrawlerLogging,CatalogManagerLogging,ValidateLogging,LogonParam,Marketing,MessageTables,MiniDump,TestOnlySystemCredentials,OC4JServer,ODBC,PDF,Prompts,RDS,ReportCache,CatalogObjectSchemaValidation,Scheduler,Scorecard,Security,ServerConnectInfo,SpatialMaps,StatePool,SSLCredentialStore,UsernamePasswordCredentialStore,SubjectAreaMetadata,TestAutomation,ThreadPoolDefaults,TimeZone,UI,URL,XmlCacheDefaults,CatalogCrawler,UserprefCurrenciesConfigFile,UserCurrencyPreferences,ContextVariablesConfigFile,EnableHostsLookupInSessionsScreen,BIEEHomeLists,FijiFeatures,Utilities,QueryManager,ExecutionContext,ClientSideCaching,DeploymentProfile,AnalyticsEAR,LoadCredentialStore,Thumbnails,PresentationSuggestionEngine,PerformanceMonitoring,MemoryProfiling,ActivityReporting,OracleHardwareAcceleration,ScaleFactor,MonitorMutexContentions,VirusScannerConfiguration,Download,TotalsAtBottom,AnalysisEditorStartTab,AnalysisEditorMode,SubjectAreaTreeOrder,Enable508,DatasetService,Members,BulkDataProcessing)'


<Mar xx, 2019 5:22:50 PM EDT> <INFO> <NodeManager ComponentManager> <The server 'obips1' with process id 46382 is no longer alive; waiting for the process to die.>
<Mar xx, 2019 5:22:50 PM EDT> <FINEST> <NodeManager ComponentManager> <Process died.>
<Mar xx, 2019 5:22:50 PM EDT> <INFO> <NodeManager ComponentManager> <Server failed during startup. It may be retried according to the auto restart configuration.>
<Mar xx, 2019 5:22:50 PM EDT> <FINEST> <NodeManager ComponentManager> <get latest startup configuration before deciding/trying to restart the server>
<Mar xx, 2019 5:22:50 PM EDT> <INFO> <NodeManager ComponentManager> <Server failed but will not be restarted because the maximum number of restart attempts has been exceeded>
<Mar xx, 2019 5:22:50 PM EDT> <FINEST> <NodeManager ComponentManager> <runMonitor returned, setting finished=true and notifying waiters>

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.