11G: Unable to start Managed Server — Oracle Analytics

Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

11G: Unable to start Managed Server

Received Response
3
Views
1
Comments
user11183570
user11183570 Rank 3 - Community Apprentice

Hi Experts,

I was configuring AD Authentication. After setup changes, while restarting servers and managed server did not start with following error -

<Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0.13 PSU Patch for BUG21984589 TUE NOV 26 15:54:42 IST 2015 WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >

<BEA-141223> <The server name bi_server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.>

<Mar 4, 2016 9:24:25 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:There are 1 nested errors:

weblogic.management.ManagementException: [Management:141223]The server name bi_server1 specified with -Dweblogic.Name does not exist. The configuration includes  the following servers {AdminServer}.

I made following changes for AD-

WLS Console

1. Entered New AD Authentication Provider As AD Authenticator - CORP

Host: corp.irco.com

Port: 389

Principal: CN=cci_obisync,OU=Service Accounts,OU=Administration,DC=corp,DC=irco,DC=com

Credential: XXX

Confirm Credential: XXX

User Base DN: DC=corp,DC=irco,DC=com


2. Ordered this Below Default Authenticator.

EM:

Weblogic-->bifoundation-->Security-->Security Provider Configurations --> Identity Store Provider --> Configure

Added the following 3 Custom Properties

user.login.attr: sAMAccountName

username.attr : sAMAccountName

virtualize : true

After this I stopped OPMN, Managed Server, Admin Server.

Then started Admin Server. While starting Managed Server I got Errors mentioned above.

Does anybody know where it went wrong?

Thanks & Regards,

Avi

Answers

  • handat
    handat Rank 5 - Community Champion

    I don't think your changes and the error you are seeing are directly related. What probably happened is that your configuration was already corrupted but your change made it override the corrupted config with your new updates and losing the bi_server instance configuration. Do you have a backup of config.xml? You could restore that, then start up your servers again, and the re-apply those changes