Load Balance Manager Error

Got the error below:
Unable to create load balance manager object!
Please verify that the user name, password, and dom,ain name are correct.
Error = Cannot create ActiveX component.
Source = Microsoft.VisualBasic
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Can anyone help please? Thanks!

What version of FDM are you using?

Similar Messages

Can't see Native Authentication Provide while configuing Load Balance Manag

I am configuring Load Balance Manager in FDM 11.1.1.3. I followed the steps as per Oracle, and am setting my local Windows 2003 default Adminstrator account as the username for everything. Everything worked fine upto the point where I specify the authentication provider. I wanted to use Native Authentication, but when I try to "add" an authentication provider, the only option I have is to add Shared Services, Visual Basic Script Authentication and Visual Basic SSO. Can't figure out why Native authentication is not there.
to be completely honest, I don't care what mode it uses as long as it works. What are the implications of using Native vs Shared Services. Say I choose Shared services, do I have to do anything in shared services as part of the configuration?
I am running Hyperion Planning, Essbase.

When you say "native authentication" are you referring to the shared services native directory or are you expecting to see NTLM, MSAD, or LDAP as available authentication providers?
All authentication is now handled via shared services in 11.1.1.3. You will need to specify the provider as shared services and then add your MSAD or LDAP providers within shared services and provision the users for the FDM application(s).
NTLM is no longer supported and has been removed from the FDM list of providers as well as an available external provider option in shared services.

Load Balancing cockpit error

          We are testing clustering and load balancing using WLS 6SP1. We have found that
          the fail over works fine (i.e. we kill a server and the next call is invoked on
          another server). However, we find that all calls (modulo failover) always go to
          the same server. We expected to get round-robin for each home access. I've attached
          the config.xml and deployment descriptors. What am I missing here? Is there anything
          special I should be doing code wise?
          BTW: All calls are going to a stateless session bean.
          Regards,
          Andy
          [config.zip]


          Viresh Garg <[email protected]> wrote:
          >The attached config.zip seems to be corrupted. I can't download it.
          Wierd, I've just managed to download it. Anyway, I'll paste the
          contents into the text below.
          >
          >I am assuming that you are using a JAVA client. Could you describe your
          >test case to
          >test the load balancing between home methods of EJB ( what kind of EJB??)
          We have a stateless session bean. At each request we use JNDI to
          obtain a handle to a stateless session bean. We invoke an
          operation on it and then call remove on the stateless session
          bean. We run several of these clients (Java clients) and observe
          the system load and network traffic. We see that network traffic
          is almost minimal and system load on the "other" server is non-
          existent. We know that other server can satisfy calls to the
          stateless session bean because fail over (between calls) works
          correctly. I'm sure we are doing something daft, but I can't spot it.
          --------------------- config.xml ---------------------------
          <?xml version="1.0" encoding="UTF-8"?>
          
          <Domain Name="myDomain">
          <Security Name="petstore"
          PasswordPolicy="wl_default_password_policy" Realm="myRealm"/>
          <Application Name="wl_management_internal2" Path="C:\bea\wlserver6.0sp1\config\tmp">
          <WebAppComponent Name="wl_management_internal2"
          Targets="petstoreServer" URI="wl_management_internal2.war"/>
          </Application>
          <PasswordPolicy Name="wl_default_password_policy"/>
          <Server Cluster="PetStoreCluster" ClusterWeight="80"
          IIOPEnabled="false" JavaCompiler="C:\bea\jdk130/bin/javac"
          ListenAddress="194.152.80.29" ListenPort="7001" Machine="ROWAN"
          Name="petstoreServer" NativeIOEnabled="false"
          RootDirectory="C:\bea\wlserver6.0sp1" StdoutDebugEnabled="true"
          StdoutEnabled="true" StdoutSeverityLevel="64"
          ThreadPoolSize="15" TransactionLogFilePrefix="config/myDomain/logs/">
          <Log FileName="./config/myDomain/logs/weblogic.log" Name="petstoreServer"/>
          <ServerDebug DebugAbbreviation="false" DebugCluster="true"
          DebugClusterAnnouncements="true"
          DebugClusterFragments="true" DebugClusterHeartbeats="true"
          DebugConnection="true" DebugEJB="true" DebugEJBCache="true"
          DebugEJBCalls="false" DebugEJBDeployment="true"
          DebugEJBFreepool="true" DebugEJBLocking="true"
          DebugEJBPersistence="true" DebugEJBSecurity="true"
          DebugEventManager="true" DebugFailOver="true"
          DebugHttp="true" DebugJMSBackEnd="true" DebugJMSBoot="true"
          DebugJMSCommon="true" DebugJMSConfig="true"
          DebugJMSDurableSubscribers="true" DebugJMSFrontEnd="true"
          DebugJMSJDBCScavengeOnFlush="true" DebugJMSLocking="true"
          DebugJMSStore="true" DebugJMSXA="true" DebugJNDI="true"
          DebugJNDIFactories="true" DebugJNDIResolution="false"
          DebugLoadBalancing="true" DebugMessaging="true"
          DebugRC4="true" DebugRSA="true" DebugReplication="true"
          DebugReplicationDetails="true" DebugRouting="true"
          DebugSSL="true" DebugSecurityPasswordPolicy="true"
          DebugSecurityRealm="true" DebugTunnelingConnection="true"
          DebugTunnelingConnectionTimeout="true"
          DebugURLResolution="true" JDBCConn="true" JDBCSQL="true"
          JTA2PC="true" JTAAPI="true" JTAJDBC="true"
          JTAPropagate="true" JTARMI="true" JTARecovery="true"
          JTATLOG="true" JTAXA="true" ListenThreadDebug="true"
          LogDGCStatistics="true" MagicThreadDumpBackToSocket="false"
          MagicThreadDumpEnabled="false"
          MagicThreadDumpFile="debugMagicThreadDumpFile"
          MagicThreadDumpHost="localhost" Name="petstoreServer"/>
          <SSL CertificateCacheSize="3" Enabled="true" ListenPort="7002"
          Name="petstoreServer"
          ServerCertificateChainFileName="./config/myDomain/ca.pem"
          ServerCertificateFileName="./config/myDomain/democert.pem"
          ServerKeyFileName="./config/myDomain/demokey.pem" TrustedCAFileName="./config/myDomain/ca.pem"/>
          <WebServer DefaultWebApp="tour"
          LogFileName="./config/myDomain/logs/access.log"
          LoggingEnabled="true" Name="petstoreServer"/>
          <KernelDebug Name="petstoreServer"/>
          </Server>
          <Application Name="wl_management_internal1" Path="C:\bea\wlserver6.0sp1\config\tmp">
          <WebAppComponent Name="wl_management_internal1"
          Targets="petstoreServer" URI="wl_management_internal1.war"/>
          </Application>
          <Application Deployed="true" Name="tour" Path="C:\bea\wlserver6.0sp1\config\myDomain\applications">
          <WebAppComponent Name="tour" Targets="petstoreServer" URI="tour.war"/>
          </Application>
          <FileRealm Name="myFileRealm"/>
          <Security Name="myDomain"
          PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
          <Application Deployed="true" Name="monitorApp1_1" Path="C:\bea\wlserver6.0sp1\config\myDomain\applications\monitorApp1_1.ear">
          <EJBComponent Name="monitorBeans1_1" Targets="PetStoreCluster" URI="monitorBeans1_1.jar"/>
          <WebAppComponent Name="monitorClient1_1"
          Targets="PetStoreCluster" URI="monitorClient1_1.war"/>
          </Application>
          <ApplicationManager Name="petstore"/>
          <FileRealm Name="wl_default_file_realm"/>
          <JDBCConnectionPool CapacityIncrement="1"
          DriverName="com.inet.tds.TdsDriver" InitialCapacity="1"
          JDBCXADebugLevel="0" LoginDelaySeconds="0" MaxCapacity="10"
          Name="monitorSimplePool"
          Properties="sql7=true;user=sa;port=1433;password=;url=jdbc:inetdae7:194.152.80.29;host=194.152.80.29;database=poc3a"
          RefreshMinutes="0" ShrinkPeriodMinutes="15"
          ShrinkingEnabled="true" SupportsLocalTransaction="false"
          Targets="PetStoreCluster" TestConnectionsOnRelease="false"
          TestConnectionsOnReserve="false" URL="jdbc:inetdae7:194.152.80.29"/>
          <Machine Name="ROWAN"/>
          <Log FileName="./config/myDomain/logs/wl-domain.log" Name="petstore"/>
          <Server AcceptBacklog="50" AdministrationPort="0"
          Cluster="PetStoreCluster" ClusterWeight="100"
          CompleteHTTPMessageTimeout="480"
          CompleteIIOPMessageTimeout="480" CompleteT3MessageTimeout="480"
          ConsoleInputEnabled="false" DGCIdlePeriodsUntilTimeout="2"
          DefaultIIOPPassword="guest" DefaultIIOPUser="guest"
          DefaultProtocol="t3" DefaultSecureProtocol="t3s"
          EnabledForDomainLog="true" HelpPageURL="/docs/adminhelp/"
          HttpdEnabled="true" IIOPEnabled="false"
          IdlePeriodsUntilTimeout="4" InstrumentStackTraceEnabled="false"
          JDBCLoggingEnabled="false"
          JMSDefaultConnectionFactoriesEnabled="true"
          JavaCompiler="C:\bea\jdk130/bin/javac"
          ListenAddress="194.152.80.1" ListenPort="7001"
          ListenThreadStartDelaySecs="0"
          LogRemoteExceptionsEnabled="false" LoginTimeout="1000"
          LoginTimeoutMillis="5000" Machine="MOUSE"
          MaxHTTPMessageSize="10000000" MaxIIOPMessageSize="10000000"
          MaxT3MessageSize="10000000" Name="petstoreServerClone"
          NativeIOEnabled="false" NetworkClassLoadingEnabled="false"
          PeriodLength="60000" ResponseTimeout="0"
          ReverseDNSAllowed="false" RjvmIdleTimeout="0"
          RootDirectory="C:\bea\wlserver6.0sp1"
          SocketReaderTimeoutMaxMillis="1000"
          SocketReaderTimeoutMinMillis="100" StdoutDebugEnabled="true"
          StdoutEnabled="true" StdoutSeverityLevel="64"
          ThreadPoolPercentSocketReaders="33" ThreadPoolSize="15"
          TransactionLogFilePrefix="config/myDomain/logs/"
          TunnelingClientPingSecs="45" TunnelingClientTimeoutSecs="40"
          TunnelingEnabled="false" WorkspaceShowUserKeysOnly="false"
          ZACEnabled="true" ZACPublishRoot="exports">
          <WebServer ClusteringEnabled="false" DefaultWebApp="tour"
          HttpsKeepAliveSecs="60" KeepAliveEnabled="true"
          KeepAliveSecs="30" LogFileBufferKBytes="8"
          LogFileFlushSecs="60" LogFileFormat="common"
          LogFileName="./config/myDomain/logs/access.log"
          LogRotationPeriodMins="2147483647" LogRotationType="size"
          LoggingEnabled="true" MaxLogFileSizeKBytes="0"
          MaxPostSize="-1" MaxPostTimeSecs="-1"
          Name="petstoreServerClone" PostTimeoutSecs="0" WAPEnabled="false"/>
          <SSL CertificateCacheSize="3" ClientCertificateEnforced="false"
          Enabled="true" ExportKeyLifespan="500" HandlerEnabled="true"
          KeyEncrypted="false" ListenPort="8002"
          LoginTimeoutMillis="25000" MDAcceleration="Java"
          Name="petstoreServerClone" PeerValidationEnforced="0"
          RC4Acceleration="Native/Java" RSAAcceleration="Native/Java"
          ServerCertificateChainFileName="./config/myDomain/ca.pem"
          ServerCertificateFileName="./config/myDomain/democert.pem"
          ServerKeyFileName="./config/myDomain/demokey.pem"
          TrustedCAFileName="./config/myDomain/ca.pem" UseJava="true"/>
          <Log FileCount="7" FileMinSize="500"
          FileName="./config/myDomain/logs/weblogic_clone.log"
          FileTimeSpan="24" Name="petstoreServerClone"
          NumberOfFilesLimited="false" RotationType="none"/>
          <KernelDebug Name="petstoreServerClone"/>
          <ServerDebug DebugAbbreviation="false" DebugCluster="true"
          DebugClusterAnnouncements="true"
          DebugClusterFragments="true" DebugClusterHeartbeats="true"
          DebugConnection="true" DebugEJB="true" DebugEJBCache="true"
          DebugEJBCalls="false" DebugEJBDeployment="true"
          DebugEJBFreepool="true" DebugEJBLocking="true"
          DebugEJBPersistence="true" DebugEJBSecurity="true"
          DebugEventManager="true" DebugFailOver="true"
          DebugHttp="true" DebugJMSBackEnd="true" DebugJMSBoot="true"
          DebugJMSCommon="true" DebugJMSConfig="true"
          DebugJMSDurableSubscribers="true" DebugJMSFrontEnd="true"
          DebugJMSJDBCScavengeOnFlush="true" DebugJMSLocking="true"
          DebugJMSStore="true" DebugJMSXA="true" DebugJNDI="true"
          DebugJNDIFactories="true" DebugJNDIResolution="false"
          DebugLoadBalancing="true" DebugMessaging="true"
          DebugRC4="true" DebugRSA="true" DebugReplication="true"
          DebugReplicationDetails="true" DebugRouting="true"
          DebugSSL="true" DebugSecurityPasswordPolicy="true"
          DebugSecurityRealm="true" DebugTunnelingConnection="true"
          DebugTunnelingConnectionTimeout="true"
          DebugURLResolution="true" JDBCConn="true" JDBCSQL="true"
          JTA2PC="true" JTAAPI="true" JTAJDBC="true"
          JTAPropagate="true" JTARMI="true" JTARecovery="true"
          JTATLOG="true" JTAXA="true" ListenThreadDebug="true"
          LogDGCStatistics="false" MagicThreadDumpBackToSocket="false"
          MagicThreadDumpEnabled="false"
          MagicThreadDumpFile="debugMagicThreadDumpFile"
          MagicThreadDumpHost="localhost" Name="petstoreServerClone"/>
          </Server>
          <Log FileName="myDomain.log" Name="myDomain"/>
          <JTA Name="myDomain"/>
          <Machine Name="MOUSE"/>
          <ApplicationManager Name="myDomain"/>
          <Realm FileRealm="myFileRealm" Name="myRealm"/>
          <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          <Cluster ClusterAddress="194.152.80.1,194.152.80.29:7001"
          DefaultLoadAlgorithm="round-robin"
          MulticastAddress="224.10.10.1" Name="PetStoreCluster" ServiceAgeThresholdSeconds="180"/>
          <Application Name="console" Path="C:\bea\wlserver6.0sp1\config\examples\applications">
          <WebAppComponent Name="console" Targets="petstoreServer" URI="console.war"/>
          </Application>
          <JDBCDataSource JNDIName="monitorSimplePool"
          Name="monitorSimpleDB_1" PoolName="monitorSimplePool" Targets="PetStoreCluster"/>
          </Domain>
          ---------------------- ejb-jar.xml -------------------------
          <?xml version="1.0"?>
          <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
          1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
          <ejb-jar>
          <enterprise-beans>
          <entity>
          <ejb-name>ContractCMP</ejb-name>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.cmp.ContractCMPBean</ejb-class>
          <persistence-type>Container</persistence-type>
          <prim-key-class>com.liffe.monitor.general.ContractPK</prim-key-class>
          <reentrant>False</reentrant>
          <cmp-field>
          <field-name>contractCode</field-name>
          </cmp-field>
          <cmp-field>
          <field-name>tradeVolume</field-name>
          </cmp-field>
          <cmp-field>
          <field-name>suspended</field-name>
          </cmp-field>
          </entity>
          <entity>
          <ejb-name>ContractBMP</ejb-name>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.bmp.ContractBMPBean</ejb-class>
          <persistence-type>Bean</persistence-type>
          <prim-key-class>com.liffe.monitor.general.ContractPK</prim-key-class>
          <reentrant>False</reentrant>
          </entity>
          <session>
          <ejb-name>ContractMonitor</ejb-name>
          <home>com.liffe.monitor.contractonly.server.ContractMonitorHome</home>
          <remote>com.liffe.monitor.contractonly.server.ContractMonitor</remote>
          <ejb-class>com.liffe.monitor.contractonly.server.ContractMonitorBean</ejb-class>
          <session-type>Stateful</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          </session>
          <session>
          <ejb-name>InjectorTarget</ejb-name>
          <home>com.liffe.monitor.injector.server.InjectorTargetHome</home>
          <remote>com.liffe.monitor.injector.server.InjectorTarget</remote>
          <ejb-class>com.liffe.monitor.injector.server.InjectorTargetBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          <ejb-ref>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <ejb-ref-type>Entity</ejb-ref-type>
          <home>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</home>
          <remote>com.liffe.monitor.contractonly.server.Contract</remote>
          </ejb-ref>
          </session>
          </enterprise-beans>
          <assembly-descriptor>
          <method-permission>
          <role-name>everyone</role-name>
          <method>
          <ejb-name>InjectorTarget</ejb-name>
          <method-name>*</method-name>
          </method>
          </method-permission>
          <container-transaction>
          <method>
          <ejb-name>ContractCMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>ContractMonitor</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>InjectorTarget</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          ------------------- weblogic-ejb-jar.xml -----------------
          <?xml version="1.0"?>
          <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB//EN'
          'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>ContractCMP</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>1000</max-beans-in-cache>
          </caching-descriptor>
          <persistence-descriptor>
          <persistence-type>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>5.1.0</type-version>
          <type-storage>META-INF/weblogic-cmp-rdbms-jar-contractonly-cmp.xml</type-storage>
          </persistence-type>
          <persistence-use>
          <type-identifier>WebLogic_CMP_RDBMS</type-identifier>
          <type-version>5.1.0</type-version>
          </persistence-use>
          </persistence-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>random</home-load-algorithm>
          </clustering-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>15</trans-timeout-seconds>
          </transaction-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          <transaction-isolation>
          <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
          <method>
          <ejb-name>ContractCMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          </transaction-isolation>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>ContractBMP</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>1000</max-beans-in-cache>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>random</home-load-algorithm>
          </clustering-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>15</trans-timeout-seconds>
          </transaction-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          <transaction-isolation>
          <isolation-level>TRANSACTION_READ_COMMITTED</isolation-level>
          <method>
          <ejb-name>ContractBMP</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          </transaction-isolation>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>ContractMonitor</ejb-name>
          <caching-descriptor>
          <max-beans-in-cache>100</max-beans-in-cache>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          <reference-descriptor>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          </ejb-reference-description>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          <jndi-name>com.liffe.monitor.contractonly.server.ContractMonitorHome</jndi-name>
          </weblogic-enterprise-bean>
          <weblogic-enterprise-bean>
          <ejb-name>InjectorTarget</ejb-name>
          <caching-descriptor>
          <max-beans-in-free-pool>50</max-beans-in-free-pool>
          </caching-descriptor>
          <clustering-descriptor>
          <home-is-clusterable>true</home-is-clusterable>
          <home-load-algorithm>round-robin</home-load-algorithm>
          </clustering-descriptor>
          <reference-descriptor>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractCMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.cmp.ContractCMPHome</jndi-name>
          </ejb-reference-description>
          <ejb-reference-description>
          <ejb-ref-name>ejb/ContractBMPHome</ejb-ref-name>
          <jndi-name>com.liffe.monitor.contractonly.server.bmp.ContractBMPHome</jndi-name>
          </ejb-reference-description>
          </reference-descriptor>
          <jndi-name>ejb/InjectorTargetHome</jndi-name>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          ---------------------- weblogic-cmp-.... ---------------------
          <!DOCTYPE weblogic-rdbms-bean PUBLIC
          '-//BEA Systems, Inc.//DTD WebLogic 5.1.0 EJB RDBMS Persistence//EN'
          'http://www.bea.com/servers/wls510/dtd/weblogic-rdbms-persistence.dtd'>
          <weblogic-rdbms-bean>
          <pool-name>monitorSimplePool</pool-name>
          <table-name>Contract</table-name>
          <attribute-map>
          <object-link>
          <bean-field>contractCode</bean-field>
          <dbms-column>contractCode</dbms-column>
          </object-link>
          <object-link>
          <bean-field>tradeVolume</bean-field>
          <dbms-column>tradeVolume</dbms-column>
          </object-link>
          <object-link>
          <bean-field>suspended</bean-field>
          <dbms-column>suspended</dbms-column>
          </object-link>
          </attribute-map>
          <finder-list>
          <finder>
          <method-name>findByGTVolume</method-name>
          <method-params>
          <method-param>int</method-param>
          </method-params>
          <finder-query><![CDATA[(> tradeVolume $0)]]></finder-query>
          </finder>
          <finder>
          <method-name>findAllContracts</method-name>
          <finder-query><![CDATA[(isNotNull contractCode)]]></finder-query>
          </finder>
          </finder-list>
          <options>
          <use-quoted-names>false</use-quoted-names>
          </options>
          </weblogic-rdbms-bean>

Load Balancing Server Error

Hi Expert's
          I am working on Netweaver BI integrated with EP. while creating JCo destinations for both model and meta data, we have an option of selecting load balancing server and application server. the connection with application server is working fine but when come's to load balancing server it is asking for system group.
         Added to this we are working on single server. Pls let us know is system group is necessary? also let us know where to create system group?
Regards
Subbaraju

Hi Ashok,
           As I already mentioned we are working on BI 7.0 We are facing problem while Configuring JCo destinations In JCo we have maintained Meta and Model Data using load balancing server and application server Now when using Tr.RSPLAN and selecting START MODELER it is routing into local host. But after logging, It is routing to standard SAP host (host=pwdfm101) instead of our local host .
Note: Routing means opening the web Dynpro page.
I hope this makes things clear.
Regards
Subbaraju

FDM keeps give me DCOM Security Error when I configure the Load Balance

Hello, everyone.
I installed FDM on the Windows 2008 Server.
When I configure the Load Balance Server for FDM.
It keeps give me error:
Unable to create Load Balance Manager Object!
Please verify that the user name, password, and domain name are correct.
However, I am pretty sure the user name and password input are correct.
I have tried the solution provides on Oracle Support. And changes the DCOM component's security settings.
However, the issue is still existed.

If after clearning out the security on the DCOM object and attempting to reset the Load Balance Config the same issue occurs, you will need to un-install FDM using the EPM System Un-installer and reboot. Following the reboot you will then choose to install FDM again, configure FDM using the EPM System Configuration utility, and then reset the FDM configuration items.

Error while selecting Load Balancing in JCO creation

While creating JCO i am facing this error.It is working fine with Single server connection,but when i chose Load balancing i error comes out.Please tell me the solution.
I have read couples of forum mentioned you need to start both Portal and ECC.
For you information my Portal and Java are both on diffrrent Box.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=olameccpdvr GROUP=PUBLIC R3NAME=DVR MSSERV=sapmsDVR PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service 'sapmsDVR' unknown TIME Thu Feb 24 12:19:54 201 RELEASE 701 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 5

Is your backend system configured correctly in your SLD ?
Go to transaction SMMS on your backend system that your are connecting to. Click on Goto=>Parameters=>Display. Look for "server port" value.
This should give you the TCP/IP port for your message server. It could be 3600 or 3601 (36NN - where NN is the instance number).
In your services file, if you made the entry at the end of the file, press Enter (Return) after your entry.
Try restarting your server after making the above changes.
- Shanti

FDM Load balancer Configuration issue

We are doing the installation for Hyperion Planning, ODI and DRM on DEV environment
The EPM version we are using - 11.1.2.2
Server 1 (Windows 2008 x64)
Foundation Services
Calculation Manager
Planning Web Application
Analytical Provider Services
Essbase Administration Services web application
Oracle HTTP Server
Server 2 (Windows 2008 x64)
R & A Framework Services
R & A Framework Web Application
Financial Reporting Web Application
Web analysis Web Application
Server 3 (Windows 2008 x64)
FDM
EPMA
ODI
DRM
Essbase Integration Services
Essbase Studio
IIS 7.x
Server 4 (Windows 2008 x64)
Essbase Server
Server 5(Windows 2008 x64)
SQL Server 2008
All our services are running fine for Planning. We are in process of configuring FDM.
FDM Application Server Configuration is completed.
While doing FDM Load Balancer Configuration, we also able to connect to Shared Service directory successfully. But when we click ok to complete the configuration it gives following error -
Unable to Create Load Balancer Object!
Please verify that the user name, password, and domain are correct
Error=Cannot create ActiveX component
When checked in Event Log we found -
Unable to create Load Balance Manager object! Configuration directory could not be located. Error=-2147023878 - Retrieving the COM class factory for component with CLSID *{E652643D-6CC1-48AC-915D-01842B04F292}*
Source=TaskManagerService - at TaskManagerService.TaskItem.fGetConfigFolder()
We tried the below steps but issue still persists -
•     Start the ‘dcomcnfg’ tool in Windows
•     Expand Component Services\Computers\My Computer\Dcom-Config and locate the following object: {E652643D-6CC1-48AC-915D-01842B04F292}
•     Right-click and choose "Properties" and click on the "Security" tab
•     Click the "Edit" button and remove all users except the default: "Everyone" and "System" and click OK, then set the radio button to "Use Default"
•     Click the "Edit" button under Access Permissions and remove all users/groups except the default items and click OK, and set the radio button to "Use Default"
•     Now click the "Identity" tab and remove the ID in the "This User" field and set the radio button to "The Launching User" and click "Apply" and "OK"
•     Now try to launch the FDM Load Balance Config and all the extra tools for FDqM
We are using hypadmin as domain account but it is part of Administrators group on FDM Server (Server 3). The administrators group is also part of -
Act as part of the operating system
Bypass traverse checking
Log on as a batch job
Log on as a service
Please let us know in case if you encountered similar error on this version and possible solution for the issue.
Thanks in advance.
Regards,

I woudl clear out all users/groups on the security tab of the FDM Load Balance Server DCOm object for "Launch and Activation" and "Access" permisisons and then set the identity to the "Launching User" radio button and apply. Then re-set the config.
If that still fails, try rebooting the server and then set it.
Make sure the domain and password are also correct that is being entered.

Bug with Network Load Balancing Services and SkipAsSource always reverting to true

Steps to reproduce:
Add an IP address to the cluster (2 nodes running Windows Server 2012) using the Network Load Balancing Manager
Using PowerShell set the SkipAsSource flag on the IP Address to true (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $true). The flag is correctly set.
Try to reverse the setting (Set-NetIpAddress -IpAddress 192.168.1.10 -SkipAsSource $false). Flag stays as true.
It appears as though Network Load Balancing Services is remembering the setting from someone.
Things I've tried all without success (in no particular order):
Removing the IP address from the cluster and adding it back in
Using PowerShell to remove the IP address and add it back in manually (on each host).Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
Using netsh to remove the IP address and add it back in manually (on each host). Flag stays set as true on the 1st node but takes a second before it reverts back to true on the 2nd node.
Deleting each host from the cluster (one at a time), removing the registry keys CurrentControlSet\Services\WLBS and
Removing both hosts from the cluster
Restarting the hosts
Using processmon (sysinternals) to try and find a registry entry that might be set when SkipAsSource is set
Does anyone know:
How to resolve this issue? I'm guessing resetting the TCP/IP stack would work but that's a last resort as it requires an on sight visit to the datacentre.
Where the SkipAsSource flag it stored?
How to reset the master/global cluster config?
Thank in advance,
Antony

Hi Antony,
I am trying to involve someone familiar with this topic to further look at this issue.
There might be some time delay. Appreciate your patience.
Best Regards.
Steven Lee
TechNet Community Support

Internet load balancing with two machine (NLB)

i have install two TMG 2010 and one is manger and one managed , but seems once manager down , other server not passing the traffic with vip , my question is does it supported like NLB with two machine ?

Hi,
Coud you confirm you can ping sucecssfully both of two machine before?
To check if the NLB status is green:
In the Forefront TMG Management console, in the tree, click the Monitoring node.
In the Alerts tab, check that NLB Started for each array member.
In the Network Load Balancing Manager (nlbmgr), check the status of the current node for all clusters define. Repeat this for each member.
Run nlb display to view the current state of the NLB cluster and hosts. Repeat this for each membe
http://technet.microsoft.com/es-es/library/ff849728.aspx#s3
Best Regards
Quan Gu

Load Balancing Directory Servers with Access Manager - Simple questions

Hi.
We are in the process of configuring 2 Access Manager instances (servers) accessing the same logical LDAP repository (comprising physically of two Directory Servers working together with Multi-Master Replication configured and tested) For doing this, we are following guide number 819-6258.
The guide uses BigIP load balancer for load balancing the directory servers. However, we intend to use Directory Proxy Server. Since we faced some (unresolved) issues last time that we used DPS, there are some simple questions that I would be very grateful to have answers to:
1. The guide, in section 3.2.10 (To configure Access Manager 1 with the Directory Server load balancer), talks about making changes at 4 places, and replacing the existing entry (hostname and port) with the load balancer's hostname and port (assuming that the load balancer has already been configured). It says that changes need not be made on Access Manager 2 since the LDAPs are in replication, and hence changes will be replicated at all places. However, the guide also states that changes have to be made in two files, namely AMConfig.properties, and the serverconfig.xml file. But these changes will not be reflected on Access Manager 2, since these files are local on each machine.
Question 1. Do changes have to be made in AMConfig.properties and serverconfig.xml files on the other machine hosting Access Manager 2?
Question 2: What is the purpose of putting these values here? Specifically, what is achieved by specifying the Directory server host and port in AMConfig.properties, as well as in serverconfig.xml?
Question 3. In the HTTP console, there is the option of specifying multiple primary LDAP servers, as well as multiple secondary LDAP servers. What is the purpose of these? Are secondary servers attempted when none of the list in the primary list are accessible? Also, if there are multiple entries in the primary server list, are they accessed in a round robin fashion (hereby providing rudimentary load balancing), or are other servers accessed only when the one mentioned first is not reachable etc.?
2. Since I do not have a load balancer setup yet, I tried the following deviation to the above, which, according to me, should have worked. If viewed in the HTTP console, LDAP / Membership / MSISDN and Policy configuration all pointed to the DS on host 1. When I changed all these to point to the directory server on host 2 (and made AMConfig.properties and serverconfig.xml on host 1 point to DS of host 2 as well), things should have worked fine, but apparently Access manager 1 could not be started. Error from Webserver:
[14/Aug/2006:04:30:36] info (13937): WEB0100: Loading web module in virtual server [https-machine_1_FQDN] at [search]
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Exception in thread "EventService" java.lang.ExceptionInInitializerError
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.iplanet.services.ldap.event.EventServicePolling.run(EventServicePolling.java:132)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at java.lang.Thread.run(Thread.java:595)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Caused by: java.lang.InterruptedException
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.sun.identity.sm.ServiceManager.<clinit>(ServiceManager.java:74)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: ... 2 more
In effect, AM on 1 did not start. On rolling back the changes, things again worked like previously.
Will be really grateful for any help / insight / experience on dealing with the above.
Thanks!

Update to the above, incase anyone is reading:
We setup a similar setup in Windows, and it worked. Here is a detailed account of what was done:
1. Host 1: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST1:389)
2. Host 2: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST2:389)
3. Host 1: Started replication. Set to Master
4. Host 2: Started replication. Set to Master
5. Host 1: Setup replication agreement to Host 2
6. Host 2: Setup replication agreement to Host 1
7. Initiated the remote replica from Host 1 ----> Host 2
Note that since default installation uses abc.....xyz as the encryption key, setting this to same was not an issue.
9. Started webserver for Host 1 and logged into AM as amadmin.
10. Added Host 2 FQDN in DNS Aliases / Realms
11. Added http://HOST2_FQDN:80 in the Platform server (instance) list.
12. Started Host 2 webserver. Logged in AM on Host 2, things worked fine.
At this stage, note the following:
a) Host 1:
AMConfig.properties file has
com.iplanet.am.directory.host=host1_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host1_FQDN" port="389" type="SIMPLE" />
b) Host 2:
AMConfig.properties file has
com.iplanet.am.directory.host=host2_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host2_FQDN" port="389" type="SIMPLE" />
c) If one logs into AM, and checks LDAP servers for LDAP / Policy Configuration / Membership etc services, they all contain Host2_FQDN:389 (which makes sense, since replica 2 was initialized from 1)
Returning back to the configuations:
13. On Host 1, login into the Admin server console of the Directory server. Navigate to the DPS, and confgure the following:
a) Network Group
b) LDAP servers
c) Load Balancing
d) Change Group
e) Action on-bind
f) Allow all actions (permit modification / deletion etc.).
g) any other configuations required - Am willing to give detailed steps if someone needs them to help me / themselves! :)
So now, we have DPS configured and running on Host1:489, and distributing load to DS1 and DS2 on a 50:50 basis.
14. Now, log into AM on Host 1, and instead of Host1_fqdn:389 (for DS) in the following places, specify Host1_fqdn:489 (for the DPS)--
LDAP Authentication
MSISDN server
Membership Service
Policy configuation.
Verified that this propagated to the Policy Configuration service and the LDAP authentication service that are already registered with the default organization.
15. Log out of AM. Following the documentation, modify directory.host and directory.port in AMConfig.properties to point to Host 1_FQDN and 489 respectively. Make this change in AMConfig.properties of both Host 1 as well as 2.
16. Edit serverconfig.xml on both hosts, and instead of they pointing to their local directory servers, point both to host1_FQDN:489
17. When you start the webserver, it will refuse to start. Will spew errors such as:
[https-host1_FQDN]: Sun ONE Web Server 6.1SP5 B06/23/2005 17:36
[https-host1_FQDN]: info: CORE3016: daemon is running as super-user
[https-host1_FQDN]: info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_04] from [Sun Microsystems Inc.]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amserver]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [ampassword]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amcommon]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amconsole]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [search]
[https-host1_FQDN]: warning: CORE3283: stderr: netscape.ldap.LDAPException: error result (32); matchedDN = dc=sun,dc=com; No such object (DN changed)
[https-host1_FQDN]: warning: CORE3283: stderr: Got LDAPServiceException code=-1
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getConnection(DSConfigMgr.java:357)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewFailoverConnection(DSConfigMgr.java:314)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewConnection(DSConfigMgr.java:253)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:184)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:194)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.initLdapPool(DataLayer.java:1248)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.(DataLayer.java:190)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:215)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:246)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:156)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.(SMSLdapObject.java:124)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance0(Class.java:350)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance(Class.java:303)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.SMSEntry.(SMSEntry.java:216)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ServiceSchemaManager.(ServiceSchemaManager.java:67)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetector.java:219)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.(AMClientDetector.java:94)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:322)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:120)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3271)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3747)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: failure: WebModule[amserver]: WEB2783: Servlet /amserver threw load() exception
[https-host1_FQDN]: javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: ----- Root Cause -----
[https-host1_FQDN]: java.lang.NullPointerException
[https-host1_FQDN]: at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]:
[https-host1_FQDN]: info: HTTP3072: [LS ls1] http://host1_FQDN:58080 [i]ready to accept requests
[https-host1_FQDN]: startup: server started successfully
Success!
The server https-host1_FQDN has started up.
The server infact, didn't start up (nothing even listening on 58080).
However, if AMConfig.properties is left as it originally was, and only serverconfig.xml files were changed as mentioned above, web servers started fine, and things worked all okay. (Alright, except for some glitches when viewed in /amconsole. If /amserver/console is accessed, all is good. Can this mean that all is still not well? I am not sure).
So far so good. Now comes the sad part. When the same is done on Solaris 9, things dont work. You continue to get the above error, OR the following error, and the web server will refuse to start:
Differences in Solaris and Windows are as follows:
1. Windows hosts have 1 IP and hostname. Solaris hosts have 3 IPs and hostnames (for DS, DPS, and webserver).
No other difference from an architectural perspective.
Any help / insight on why the above is not working (and why the hell does the documentation seem so sketchy / insecure / incorrect).
Thanks a bunch!

The load balancer is not provisioned error when attempting to deploy a SP 2013 App

Hello:
I am in VS 2013 with SP 2013 colocated on same Win 2008 R2 server. I opened a SP 2013 App and directly hit F5 and got this error:
Error occurred in deployment step 'Install app for SharePoint': The load balancer is not provisioned. Verify the load balancer was provisioned successfully before retrieving endpoint addresses. When creating the project, the first screen asks for a
site to deploy to, and I just took the default, which was http://<servername> for the colocated server.
I googled this and could not find a solution. Would anyone have any direction?
thank you
Harvey
Regards, Harvey

Hi Harvey Flaisher,
Based on the error message, this seems to be a service application not working issue.
Please check the ULS log or Event log to check in which service application the error occurs, like BCS, secure store service, app management service, then re-provision the service application using PowerShell command, or re-create the service application
from UI to check the result.
Thanks,
Qiao Wei
TechNet Community Support

Error in creation of JCO with Load balancing server

Hi,
We are using a ABAP user base for our WEBAS server 6.40 (with ABAP+JAVA). i have created a Public group in concerned ECC 5.0 system. I have already configured SLD, and then i maintain data supplier bridge in SLD and run RZ70 in ECC 5.0 system to load system information.. i can see details in SLD ..
now i am trying to create JCO connections .. here i am unable to create JCO with load balancing option.. i get
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=<servername> GROUP=PUBLIC R3NAME=SID MSSERV=sapms<SID> PCS=1 ERROR service 'sapms<SID>' unknown TIME Fri Jun 16 12:41:20 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 505 DETAIL NiPGetServByName2: service 'sapms<SID>' not found SYSTEM CALL getservbyname_r COUNTER 1
i am able to create single server JCO, but it fails in load balancing.. is there anything i have missed out in settings...
Thanks and regards,
Sudhir

Thanks, Bogdan Rokosa
I have the same problem,and solved it following the steps provided by Bogdan Rokosa :
you must insert an entry for your R3 system
(like: sapms<SID> 3600/tcp)
in services file
(C:\WINDOWS\system32\drivers\etc\services) on Java WAS.
I test the Jco successful without restart J2EE Engine.

Load Balancer on Oracle Identity Manager 9.1.0.2

Hello friends,
I have configured an environment Oracle Identity Manager 9.1.0.2 on 2 nodes in Oracle WebLogic Server 11g.
As I configured balancer Apache HTTP Server with Apache Proxy Plug-in, when loading the page through a web browser will not display the page of the web management console of Oracle Identity Manager.
Here the result after entering the web address below: http://192.168.1.10/xlWebApp :
(404 Not Found)
Not Found
The requested URL /xlWebApp was not found on this server.
Apache/2.0.63 (Unix) DAV/2 Server at 192.168.1.10 Port 80
Any suggestions for viewing the website of IDM through the load balancer Apache HTTP Server.
Very grateful for the support

httpd.conf is placed at /etc/httpd/httpd.conf, if you are using unix like systems. It's configuration file used by Apache http server. Paste its content to see what functions are configured.
regards,
GP

Load Balancing Error

Scenario breakdown :
I have two app servers on hand version 6 (App1) and (App2) and a singular web server - IWS 4.1(Web1).
Solution thus far :
I have chosen to use App2 as the Sync Primary and App1 as the Backup. Created a new cluster "mohrelxcluster" in kregedit and created two entries at location Clusters\mohrelxcluster\SyncServers to include both servers at port 10818(kxs). I have futher setup round robin polling under CCS0\LoadDb. I set the following values under CCS0\LoadDb\ServerWeights:
- ipaddressApp1:10818=50
- ipaddressApp2:10818=50
Finally, created the needed entry under CCS0\ClusterName:
-mohrelxcluster=0
Upon doing so, I started both servers according to order of precedence App2 first then App1.
Log Findings :
As anticipated, according to the kxs log files on both machines shows the broadcasting and processing of information between Sync Primary and Backup. (indicated by the sending to and receiving from <ipaddressinhex:10818>).
In the iasdsync log file on App2(Sync Primary) - App2 has be recognized as Primary and App1 as backup.
Problem :
Upon starting up the ksvradmin interface, the following error is trigged : An error occured while reading in load balancing values server app1. Upon clicking on app1's icon and clicking on the cluster tab, the "mohrelxcluster" cannot be seen.
Many thanks for reviewing. Here's hoping some one can help
Regards
Sathya

HI
Are you sharing single LDAP for these two application servers. If not, you have to create those cluster entries in two regitries (Kregedit). (both syncserver entries and clustername=0 entries)
If you are sharing single LDAP, the entries under SyncServers can be created once but you need to create ,
<clustername>=0 entry under CCSO\ClusterName in two registries.
Hope this helps.
-Srinivas

Error while configuring logon load balancing

Hi,
I am trring to configure logon load balancing in cluster environment.
I had created the logon group using T-Code SMLG and assigned the message server to logon group.
I am using SAP GUI 720.
In the front end system, i had added the host file entry as well as added u201Csapma<SID> 3600/tcpu201D as my CI instance number is 00.
I had created u201Csapmsg.iniu201D and put the entries as below based on sapnote 38119
Message Server
System ID 1>=<Name or IP address of message server 1>
Ex: <SID>=x.x.x.x
     <SID>=x.x.x.x
Message Server Description
<System ID 1>=<Description of message server 1>
Ex: <SID>=CI
But while selecting u201CGroup/Server Selectionu201D I am getting error   u201CError: partner x.x.x.x:sapms<SID> not reached u201C.
On the logon pad I had given the following information:
Description: PRD
System ID: <SID>
Message Server: IP address of CI package
I am not able to find the exact reason of the error and how to proceed to resolve the error.
Regards
Dusmanta

> In the front end system, i had added the host file entry as well as added u201Csapma<SID> 3600/tcpu201D as my CI instance number is 00.
> But while selecting u201CGroup/Server Selectionu201D I am getting error   u201CError: partner x.x.x.x:sapms<SID> not reached u201C.
> On the logon pad I had given the following information:
> Description: PRD
> System ID: <SID>
Did you enter sapma<SID> or sapms<SID> to the services file on the Windows machine?
Markus

Load Balance Manager Error

Similar Messages

Maybe you are looking for