EPM 11.1.2.1 Installation problem on Laptop (Windows Server 2008 R2 x64)
Dear All,
I hope someone can help me here with EPM 11.1.2.1 installation problem on my notebook - Windows Server 2008 R2 x65, 8 GB RAM, running SQLServer 2008 Express.
I installed Hyperion Foundation. The installation and configuration went through successfully.
I am facing two problems:
Problem 1
When I try to access the workspace through the URL http://hostname:19000/workspace/index.jsp, I get error:
Quote
Failure of server APACHE bridge:
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.
End-quote
Problem 2
Also, the service "Hyperion EPM Server" service not able to start. When I try to start, I get error message:
Quote
The Hyperion EPMA Server service on Local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
End-quote
I tried checking everything but can't seem to figure out what's going wrong.
I have uploaded (1) EPM Config Manager screenshot (2) EPM System diagnostic report (3) EPM Registry editor output and (4) system services listing at
http://www.mediafire.com/?pr9l1v99w4d9u4r,c3vggxeibqkxbo2,lyzclu2aggbn8qh,8kur9gxal5b361z
It would be very grateful if someone can have a look and help me.
Many thanks in advance for any help / pointers / suggestions.
- Neil
Hi Pablo,
Thanks to your suggestion for database, problem #2 seem to be resolved. I am now able to start EPMA Service.
Re: Problem 1
a) Log for C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FoundationServices-sysout is as below
-----<start>--------
<Feb 15, 2012 4:04:47 AM > <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Feb 15, 2012 4:04:47 AM > <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Feb 15, 2012 4:04:47 AM > <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.2-11-135406-1.6.0_20-20100624-2119-windows-x86_64 from Oracle Corporation>
<Feb 15, 2012 4:04:48 AM > <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:
------<end>-----
I am intrigued by the last line "Enter username to boot WebLogic server:" - is there anything wrong going here?
Log for C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\logs\FoundationServices0 is as below:
-----<start>--------
####<Feb 15, 2012 12:49:49 AM <Info> <WebLogicServer> <RCPL02> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1329324589459> <BEA-000000> <WebLogic Server "FoundationServices0" version:
WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
####<Feb 15, 2012 12:49:49 AM <Notice> <Log Management> <RCPL02> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1329324589568> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\logs\FoundationServices0.log is opened. All server side log events will be written to this file.>
####<Feb 15, 2012 12:49:49 AM <Info> <Log Management> <RCPL02> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1329324589584> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Feb 15, 2012 12:49:49 AM <Info> <Diagnostics> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324589631> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "t3" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "t3s" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "http" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "https" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "iiop" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "iiops" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "ldap" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "cluster" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002622> <The protocol "clusters" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002622> <The protocol "snmp" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002622> <The protocol "admin" is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Feb 15, 2012 12:49:54 AM <Info> <RJVM> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594950> <BEA-000570> <Network Configuration for Channel "FoundationServices0"
Listen Address :28080
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Feb 15, 2012 12:49:54 AM <Info> <RJVM> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594950> <BEA-000570> <Network Configuration for Channel "FoundationServices0"
Listen Address :28443 (SSL)
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594982> <BEA-002609> <Channel Service initialized.>
####<Feb 15, 2012 12:49:55 AM <Info> <Socket> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595013> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
>
####<Feb 15, 2012 12:49:55 AM <Info> <Socket> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595075> <BEA-000436> <Allocating 4 reader threads.>
####<Feb 15, 2012 12:49:55 AM <Info> <Socket> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595075> <BEA-000446> <Native IO Enabled.>
####<Feb 15, 2012 12:49:55 AM <Info> <IIOP> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595216> <BEA-002014> <IIOP subsystem enabled.>
####<Feb 15, 2012 12:49:59 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324599818> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600286> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600442> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600722> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\data\ldap\XACMLAuthorizermyrealmInit.initialized, will load full LDIFT.>
####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600738> <BEA-090074> <Initializing Authorizer provider using LDIF template file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\XACMLAuthorizerInit.ldift.>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601050> <BEA-090075> <The Authorizer provider has had its LDIF information loaded from: C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\XACMLAuthorizerInit.ldift>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601315> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\data\ldap\DefaultCredentialMappermyrealmInit.initialized, will load full LDIFT.>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601315> <BEA-090827> <LDIF template file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DefaultCredentialMapperInit.ldift was empty. The WebLogic provider CredentialMapper has been bootstrapped but has not been initialized with any LDIF data.>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601331> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\data\ldap\XACMLRoleMappermyrealmInit.initialized, will load full LDIFT.>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601331> <BEA-090074> <Initializing RoleMapper provider using LDIF template file C:\Oracle\Middleware\user_projects\domains\EPMSystem\security\XACMLRoleMapperInit.ldift.>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601346> <BEA-090075> <The RoleMapper provider has had its LDIF information loaded from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\security\XACMLRoleMapperInit.ldift>
####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601565> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server FoundationServices0 for security realm myrealm.>
####<Feb 15, 2012 12:50:01 AM <Notice> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601565> <BEA-090082> <Security initializing using security realm myrealm.>
####<Feb 15, 2012 12:50:01 AM <Notice> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601658> <BEA-090083> <Storing boot identity in the file: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\security\boot.properties>
------<end>-----
Similar Messages
-
Oralce EPM Fails to install Weblogic on Windows Server 2008 R2 x64
I've run the installer on Windows Server 2008 R2 x64 and it fails to install Weblogic. I don't have MIDDLEWARE_HOME/oracle_common. Config tool log says missing jars. When I go back to install and choose products individually, Weblogic Server is gray. When I click on Weblogic Server, the message at the bottom says can not be installed.
I have checked that I have extracted the following assemblies:
Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.2.0.0
Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.0.0 - Parts 1 - 4
Oracle Hyperion Enterprise Performance Management System Additional Content Release 11.1.2.0.0
I have run this same set of files on another server and Weblogic was installed. Am I missing something?I am not sure if it is your problem but I don't think R2 is officially supported, I did have problems with it when I first installed 11.1.2 so I installed with R1 SP2.
Cheers
John
http://john-goodwin.blogspot.com/ -
64 bit Weblogic Server 10.3.2 installation on Windows Server 2008 R2 x64 ?
Hi,
I'm trying to install 64 bit version of Weblogic Server 10.3.2 on my 64 bit OS Windows Server 2008 R2 SP2.
Firstly I downloaded "jdk-6u24-windows-x64.exe" and installed it on my 64 bit platform.
I downloaded "wls1032_generic.jar" and try to install it by the command below
"java -d64 -jar wls1032_generic.jar"
however I got the message below
Unrecognized option: -d64
Couldn't create the Java virtual machine
Any options about this problem. Where am I making mistake?Hi,
You need to make sure the following things :
1). If you want to run your WLS on W 64 bit mode then You need to use Generic Jar installer Example: *"java -jar wls1032_generic.jar"*
2). The above Jar should be installed only using a 64 Bit JVM so that all the 64 bit libraries will be available with the WebLogic while installing it. So first of all Download a 64 Bit JVM in your Woindows box.
Then just run the following command to check if the JVM is 6t4 bit or not:
set JAVA=HOME=C:\My64BitJDK\jdk1.6.0_21
*$JAVA_HOME\bin\java -version*
3). Now u can run your WebLogic Installer like following:
*$JAVA_HOME\bin\java -jar wls1032_generic.jar* -
Installation 12c R1 on Windows Server 2008 R2
Hello,
I had a bad idea - try the new database.
So:
1) Downloading oracle DB files, but download interrupted (lost Wi-Fi - my fault), but auth token was expired and I have to redownload 90%.
2) Installing Windows Server 2008 R2 Standard Edition (I want to install English edition, but I had only Russian one)
3) Spending a lot of time to install, and wont install.
I made some attempts (each with new OS installation):
with/without UAC, from network/local drive, desktop/server class, existing/new user, each editions, both charset... But all of them were unsuccessful.
Installation show popup errors like that:
"DIM-00019: create service error
O/S-Error: (OS 1387) ?? ??????? ???????? ??? ??????? ????? ????????? ??????, ??? ??? ?? ?? ??????????. "
Ora error
Log file have a lot of useful information, like this:
"[main] [ 2013-11-22 17:16:12.449 EST ] [KfodUtil.kfodOutput:333] Cannot run program "null\rdbms\bin\kfod.exe": CreateProcess error=2, ?? ??????? ????? ????????? ????
java.io.IOException: Cannot run program "null\rdbms\bin\kfod.exe": CreateProcess error=2, ?? ??????? ????? ????????? ????"
Any ideas what should be done for success installation?
It works as well as installed?
Interestingly, does Oracle have any testing stuffI have no doubt that the problem in the OS localization.
But, taking into account some facts:
World population is estimated to number 7.126 billion people.
Anglosphere is about 740 million people.
I have not found information about the supported OS languages.
I'm worried about losing my non-English data.
I am for the licensed software, but a trial and registered OS has the same functionality, and displays messages/data in the same way.
I doubt that the OS registration will allow installer to properly finish and even display the error correctly. (Java strings is UTF-based, so, developers should set correct code page. Probably, because system code page can be different with console code page (cp866 for Russian). Current codepage could be view by executing "chcp" in console).
In any case Enterprise-class product should operate correctly on each supported systems, or inform about problems before. -
Problem WLC - LDAP windows server 2008
Hello People
I'm having a problem with a WLC 5508 and a LDAP on windows server 2008, I already config everything on the WLC, but when a user try to authenticate I have this debug result:
*aaaQueueReader: Jul 15 19:27:07.384: 00:1b:77:7b:19:aa Returning AAA Error 'No Server' (-7) for mobile 00:1b:77:7b:19:aa
*aaaQueueReader: Jul 15 19:27:07.385: AuthorizationResponse: 0x3c9ceac4
*aaaQueueReader: Jul 15 19:27:07.385: structureSize................................32
*aaaQueueReader: Jul 15 19:27:07.385: resultCode...................................-7
*aaaQueueReader: Jul 15 19:27:07.385: protocolUsed.................................0xffffffff
*aaaQueueReader: Jul 15 19:27:07.385: proxyState...................................00:1B:77:7B:19:AA-8F:00
*aaaQueueReader: Jul 15 19:27:07.385: Packet contains 0 AVPs:
*aaaQueueReader: Jul 15 19:27:07.474: AuthenticationRequest: 0x2bc35ca0
*aaaQueueReader: Jul 15 19:27:07.474: Callback.....................................0x10e5d758
*aaaQueueReader: Jul 15 19:27:07.474: protocolType.................................0x00140001
*aaaQueueReader: Jul 15 19:27:07.474: proxyState...................................00:1B:77:7B:19:AA-90:00
*aaaQueueReader: Jul 15 19:27:07.474: Packet contains 16 AVPs (not shown)
*aaaQueueReader: Jul 15 19:27:07.474: 00:1b:77:7b:19:aa [Error] Client requested no retries for mobile 00:1B:77:7B:19:AA
*aaaQueueReader: Jul 15 19:27:07.474: 00:1b:77:7b:19:aa Returning AAA Error 'No Server' (-7) for mobile 00:1b:77:7b:19:aa
*aaaQueueReader: Jul 15 19:27:07.474: AuthorizationResponse: 0x3c9ceac4
*aaaQueueReader: Jul 15 19:27:07.474: structureSize................................32
*aaaQueueReader: Jul 15 19:27:07.474: resultCode...................................-7
So please if somebody know how to troubleshot this issue.
Thanks For all.Is there any solution upcome with WLC intigrated with LDAP, all old solution's are dummy solutions result is fail
(Cisco Controller)
User: admin
Password:********
(Cisco Controller) >debug aaa all enable
(Cisco Controller) >*LDAP DB Task 1: May 10 16:08:40.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:10:45.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:10:45.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:45.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:10:45.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:45.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:45.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:45.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:45.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:45.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:45.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:45.543: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:45.543: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:45.543: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:45.545: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.545: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:45.545: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:45.545: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:45.545: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.547: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:45.547: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:45.547: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:45.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:10:50.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:10:50.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:50.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:10:50.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:50.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:50.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:50.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:50.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:50.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:50.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:50.543: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:50.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:50.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:50.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:50.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:50.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:50.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:50.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:50.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:50.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:10:55.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:10:55.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:55.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:10:55.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:55.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:55.542: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.542: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:55.542: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:55.542: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:55.542: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.544: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:55.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:55.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:55.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:55.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:55.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:55.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:10:55.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:10:55.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:10:55.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:10:55.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:10:55.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:00.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:00.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:00.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:00.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:00.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:00.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:00.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:00.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:00.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:00.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:00.543: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:00.543: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:00.543: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:00.545: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.545: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:00.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:00.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:00.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:00.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:00.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:00.548: LDAP server 1 changed state to ERROR
*aaaQueueReader: May 10 16:11:01.273: AuthenticationRequest: 0x2ab585a0
*aaaQueueReader: May 10 16:11:01.273: Callback.....................................0x11113630
*aaaQueueReader: May 10 16:11:01.273: protocolType.................................0x00000002
*aaaQueueReader: May 10 16:11:01.273: proxyState...................................5C:0A:5B:91:CD:26-00:00
*aaaQueueReader: May 10 16:11:01.273: Packet contains 11 AVPs (not shown)
*aaaQueueReader: May 10 16:11:01.273: ReProcessAuthentication previous proto 2, next proto 8
*aaaQueueReader: May 10 16:11:01.273: Unable to find requested user entry for ispc-wlc
*aaaQueueReader: May 10 16:11:01.273: ReProcessAuthentication previous proto 8, next proto 1
*aaaQueueReader: May 10 16:11:01.273: AuthenticationRequest: 0x2ab29a54
*aaaQueueReader: May 10 16:11:01.273: Callback.....................................0x11113630
*aaaQueueReader: May 10 16:11:01.273: protocolType.................................0x00000001
*aaaQueueReader: May 10 16:11:01.273: proxyState...................................5C:0A:5B:91:CD:26-00:00
*aaaQueueReader: May 10 16:11:01.273: Packet contains 11 AVPs (not shown)
*aaaQueueReader: May 10 16:11:01.273: 5c:0a:5b:91:cd:26 Returning AAA Error 'No Server' (-7) for mobile 5c:0a:5b:91:cd:26
*aaaQueueReader: May 10 16:11:01.273: AuthorizationResponse: 0x435e9454
*aaaQueueReader: May 10 16:11:01.273: structureSize................................32
*aaaQueueReader: May 10 16:11:01.273: resultCode...................................-7
*aaaQueueReader: May 10 16:11:01.273: protocolUsed.................................0xffffffff
*aaaQueueReader: May 10 16:11:01.273: proxyState...................................5C:0A:5B:91:CD:26-00:00
*aaaQueueReader: May 10 16:11:01.274: Packet contains 0 AVPs:
*LDAP DB Task 1: May 10 16:11:05.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:05.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:05.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:05.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:05.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:05.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:05.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:05.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:05.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:05.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:05.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:05.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:05.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:05.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:05.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:05.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:05.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:05.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:05.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:05.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:10.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:10.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:10.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:10.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:10.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:10.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:10.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:10.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:10.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:10.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:10.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:10.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:10.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:10.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:10.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:10.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:10.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:10.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:10.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:10.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:15.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:15.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:15.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:15.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:15.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:15.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:15.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:15.542: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:15.542: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:15.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:15.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:15.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:15.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:15.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:15.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:15.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:15.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:15.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:15.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:15.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:20.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:20.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:20.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:20.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:20.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:20.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:20.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:20.542: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:20.542: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:20.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:20.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:20.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:20.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:20.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:20.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:20.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:20.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.547: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:20.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:20.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:20.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:25.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:25.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:25.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:25.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:25.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:25.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:25.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:25.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:25.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:25.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:25.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:25.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:25.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:25.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:25.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:25.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:25.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.547: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:25.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:25.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:25.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:30.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:30.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:30.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:30.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:30.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:30.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:30.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:30.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:30.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:30.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:30.543: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:30.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:30.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:30.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:30.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:30.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:30.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:30.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:30.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:30.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:35.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:35.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:35.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:35.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:35.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:35.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:35.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:35.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:35.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:35.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:35.543: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:35.543: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:35.543: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:35.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:35.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:35.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:35.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:35.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:35.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:35.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:40.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:40.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:40.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:40.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:40.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:40.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:40.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:40.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:40.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:40.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:40.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:40.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:40.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:40.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:40.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:40.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:40.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:40.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:40.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:40.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:45.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:45.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:45.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:45.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:45.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:45.542: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.542: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:45.542: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:45.542: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:45.542: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.544: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:45.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:45.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:45.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:45.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:45.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:45.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:45.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:45.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:45.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:45.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:45.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:50.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:50.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:50.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:50.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:50.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:50.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:50.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:50.542: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:50.542: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.544: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:50.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:50.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:50.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:50.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:50.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:50.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:50.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:50.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:50.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:50.549: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:50.549: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:11:55.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:11:55.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:55.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:11:55.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:55.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:55.542: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.542: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:55.542: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:55.542: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:55.542: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.544: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:55.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:55.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:55.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:55.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.546: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:55.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:55.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:11:55.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:11:55.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:11:55.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:11:55.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:11:55.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:12:00.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:12:00.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:00.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:12:00.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:00.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:00.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:00.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:12:00.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:00.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:00.543: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.543: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:00.543: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:12:00.543: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:00.543: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:00.545: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.545: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:00.545: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:12:00.545: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:00.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.547: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:00.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:00.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:00.548: LDAP server 1 changed state to ERROR
*LDAP DB Task 1: May 10 16:12:05.539: ldapTask [1] received msg 'TIMER' (1) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:12:05.539: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:05.539: LDAP server 1 changed state to INIT
*LDAP DB Task 1: May 10 16:12:05.539: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:05.539: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.541: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:05.541: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.541: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:05.541: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:12:05.541: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:05.541: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.543: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:05.544: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.544: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:05.544: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:12:05.544: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:05.544: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.545: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:05.546: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.546: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:05.546: LDAP server 1 changed state to RETRY
*LDAP DB Task 1: May 10 16:12:05.546: LDAP_OPT_REFERRALS = -1
*LDAP DB Task 1: May 10 16:12:05.546: ldapInitAndBind [1] called lcapi_init (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.548: ldapInitAndBind [1] configured Method Authenticated lcapi_bind (rc = 49 - Invalid credentials)
*LDAP DB Task 1: May 10 16:12:05.548: ldapClose [1] called lcapi_close (rc = 0 - Success)
*LDAP DB Task 1: May 10 16:12:05.548: LDAP server 1 changed state to IDLE
*LDAP DB Task 1: May 10 16:12:05.548: LDAP server 1 changed state to ERROR
*emWeb: May 10 16:12:09.260: aaaLdapServerStateSet [1] changed state to 'DISABLED'.
*emWeb: May 10 16:12:09.260:
Log to TACACS server(if online): ldap disable 1
*emWeb: May 10 16:12:09.260:
Log to TACACS server(if online): ldap retransmit-timeout 1 2
*emWeb: May 10 16:12:09.260:
Log to TACACS server(if online): ldap user base 1 ou=Al Tuwairqi,DC=altuwairqi,DC=com,DC=sa
*emWeb: May 10 16:12:09.260:
Log to TACACS server(if online): ldap user attr 1 sAMAccountName
*emWeb: May 10 16:12:09.260:
Log to TACACS server(if online): ldap user type 1 user
*emWeb: May 10 16:12:09.260: aaaLdapServerStateSet [1] changed state to 'ENABLED'.
*emWeb: May 10 16:12:09.260:
Log to TACACS server(if online): ldap enable 1
*LDAP DB Task 1: May 10 16:12:09.263: ldapTask [1] received msg 'CLOSE' (4) in state 'ERROR' (5)
*LDAP DB Task 1: May 10 16:12:09.263: ldapClose [1] called lcapi_close (rc = 1008 - Invalid client handle)
*LDAP DB Task 1: May 10 16:12:09.263: LDAP server 1 changed state to IDLE
*emWeb: May 10 16:12:17.260:
Log to TACACS server(if online): save
*emWeb: May 10 16:12:56.402: aaaLdapServerStateSet [1] changed state to 'DISABLED'.
*emWeb: May 10 16:12:56.403:
Log to TACACS server(if online): ldap disable 1
*LDAP DB Task 1: May 10 16:12:56.403: ldapTask [1] received msg 'CLOSE' (4) in state 'IDLE' (1)
*emWeb: May 10 16:12:56.403:
Log to TACACS server(if online): ldap retransmit-timeout 1 2
*LDAP DB Task 1: May 10 16:12:56.403: ldapClose [1] called lcapi_close (rc = 1008 - Invalid client handle)
*emWeb: May 10 16:12:56.403:
Log to TACACS server(if online): ldap user attr 1 sAMAccountName
*LDAP DB Task 1: May 10 16:12:56.403: LDAP server 1 changed state to IDLE
*emWeb: May 10 16:12:56.403:
Log to TACACS server(if online): ldap user type 1 User
*emWeb: May 10 16:12:56.403: aaaLdapServerStateSet [1] changed state to 'ENABLED'.
*emWeb: May 10 16:12:56.403:
Log to TACACS server(if online): ldap enable 1
*emWeb: May 10 16:13:02.957:
Log to TACACS server(if online): save
*emWeb: May 10 16:13:35.531: aaaLdapServerStateSet [1] changed state to 'DISABLED'.
*emWeb: May 10 16:13:35.531:
Log to TACACS server(if online): ldap disable 1
*emWeb: May 10 16:13:35.531:
Log to TACACS server(if online): ldap retransmit-timeout 1 2
*emWeb: May 10 16:13:35.531:
Log to TACACS server(if online): ldap user attr 1 uid
*emWeb: May 10 16:13:35.531:
Log to TACACS server(if online): ldap user type 1 Person
*emWeb: May 10 16:13:35.531: aaaLdapServerStateSet [1] changed state to 'ENABLED'.
*emWeb: May 10 16:13:35.531:
Log to TACACS server(if online): ldap enable 1
*LDAP DB Task 1: May 10 16:13:35.531: ldapTask [1] received msg 'CLOSE' (4) in state 'IDLE' (1)
*LDAP DB Task 1: May 10 16:13:35.532: ldapClose [1] called lcapi_close (rc = 1008 - Invalid client handle)
*LDAP DB Task 1: May 10 16:13:35.532: LDAP server 1 changed state to IDLE
*emWeb: May 10 16:13:42.880:
Log to TACACS server(if online): save
*webauthRedirect: May 10 16:12:06.438: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:12:05.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:12:00.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:11:55.542: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:11:50.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:11:45.542: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:11:40.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:11:36.593: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:35.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:11:35.118: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:30.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*apfRogueTask: May 10 16:11:27.352: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:25.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:11:23.092: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:20.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:11:15.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:11:14.880: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:10.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:11:08.873: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:05.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
May 10 16:11:01.275: [ERROR] ews.c 870: ewsRun: Bad State - should be suspended: 0x0
*ewmwebWebauth1: May 10 16:11:01.275: %PEM-1-WEBAUTHFAIL: pem_api.c:5532 Web authentication failure for station 5c:0a:5b:91:cd:26
*ewmwebWebauth1: May 10 16:11:01.273: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:11:00.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:55.542: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:50.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:45.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:40.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:10:36.250: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:10:35.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:10:34.938: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:10:30.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:10:30.408: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:10:25.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:10:22.905: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:10:20.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:15.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:10:14.377: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:10:10.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:05.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:10:00.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:09:58.579: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:09:55.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:09:50.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:09:45.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:09:44.024: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:09:40.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:09:36.185: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:09:35.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:09:30.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:09:25.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:09:22.795: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:09:20.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:09:15.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:09:12.789: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:09:10.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:09:05.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:09:04.675: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:09:00.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:08:57.956: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:55.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:08:54.049: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:50.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:08:47.778: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:45.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:08:40.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
May 10 16:08:39.811: [ERROR] ews.c 870: ewsRun: Bad State - should be suspended: 0x0
*ewmwebWebauth1: May 10 16:08:39.810: %PEM-1-WEBAUTHFAIL: pem_api.c:5532 Web authentication failure for station 5c:0a:5b:91:cd:26
*apfRogueTask: May 10 16:08:36.029: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:35.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*apfRogueTask: May 10 16:08:34.262: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:30.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*apfRogueTask: May 10 16:08:25.838: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:25.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:08:20.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:08:16.731: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:15.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:08:15.043: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:08:10.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:08:05.542: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:08:00.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*webauthRedirect: May 10 16:07:57.849: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:07:55.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:50.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:45.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).
*apfRogueTask: May 10 16:07:44.163: %LOG-3-Q_IND: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 2 times.!]
*LDAP DB Task 1: May 10 16:07:40.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:35.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:30.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:25.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:20.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:15.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:10.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 Could not connect to LDAP server 1, reason: 49 (Invalid credentials).[...It occurred 3 times/sec!.]
*LDAP DB Task 1: May 10 16:07:05.541: %AAA-3-LDAP_CONNECT_SERVER_FAILED: ldap_db.c:1052 C -
Asmca hangs during grid installation on windows server 2008 r2 x64
Hi all,
searched the web, but did not found a solution to this right now.
The Grid Infrastructure installation (11.2.0.2) hangs every time i tried the installation (Basic, Advanced) on a two node configuration. Had the same issue with 11.2.0.1.
Environment:
- W2K8 Server EE x64, all patches installed
- FC Storage attached
- UAC disabled
- Firewall diabled
- Prereqs implemented as recommended by RAC Assurance Team
- Using Domain-User (Member of the local Administrator Group) for installation
- Public-IPs and SCAN-IPs in DNS has been configured
- GNS and IMPI not used
Used diskpart to create extended partition and logical partition as described in the manuals. Stamped GRID-disk using asmtoolg.
Whatever I tried, asmca seems to hang while creating the diskgroup for OCR/Voting ...
... maybe someone out there has an idea what may cause this?
Some logs that explain the problem:
cluvfy
C:\install\11.2.0.2\grid>runcluvfy.bat stage -pre crsinst -n BKO-dbqc01,BKO-dbqc
02 -verbose
Vorpr³fungen f³r Cluster-Services-Setup werden ausgef³hrt.
Knotenzugõnglichkeit wird gepr³ft...
Pr³fung: Knotenzugõnglichkeit von Knoten "BKO-dbqc01"
Zielknoten Zugõnglich?
BKO-dbqc02 ja
BKO-dbqc01 ja
Ergebnis: Pr³fung auf Knotenzugõnglichkeit von Knoten "BKO-dbqc01" erfolgreich
Benutzerõquivalenz wird ³berpr³ft...
Pr³fung: Benutzerõquivalenz f³r Benutzer "sup-bko-him"
Knotenname Kommentar
BKO-dbqc02 erfolgreich
BKO-dbqc01 erfolgreich
Ergebnis: Pr³fung auf Benutzerõquivalenz erfolgreich f³r Benutzer "sup-bko-him"
Knotenkonnektivitõt wird gepr³ft...
Schnittstelleninformationen f³r Knoten "BKO-dbqc02"
Name IP-Adresse Subnet Gateway Standard-Gateway HW-Adre
sse MTU
PublicLAN 10.0.145.35 10.0.144.0 On-link UNKNOWN D4:85
:64:C8:A3:FA 1500
PrivateLAN 192.168.123.4 192.168.123.0 On-link UNKNOWN D4:8
5:64:C8:A3:FE 1500
Schnittstelleninformationen f³r Knoten "BKO-dbqc01"
Name IP-Adresse Subnet Gateway Standard-Gateway HW-Adre
sse MTU
PublicLAN 10.0.145.32 10.0.144.0 On-link UNKNOWN D4:85
:64:C9:28:3E 1500
PrivateLAN 192.168.123.2 192.168.123.0 On-link UNKNOWN D4:8
5:64:C9:28:42 1500
Pr³fung: Knotenkonnektivitõt von Subnet "10.0.144.0"
Quelle Ziel Angemeldet?
BKO-dbqc02[10.0.145.35] BKO-dbqc01[10.0.145.32] ja
Ergebnis: Pr³fung auf Knotenkonnektivitõt f³r Subnet "10.0.144.0" mit Knoten BKO
-dbqc02,BKO-dbqc01 erfolgreich
Pr³fung: TCP-Konnektivitõt von Subnet "10.0.144.0"
Quelle Ziel Angemeldet?
BKO-dbqc01:10.0.145.32 BKO-dbqc02:10.0.145.35 erfolgreich
Ergebnis: Pr³fung der TCP-Konnektivitõt f³r Subnet "10.0.144.0" erfolgreich
Pr³fung: Knotenkonnektivitõt von Subnet "192.168.123.0"
Quelle Ziel Angemeldet?
BKO-dbqc02[192.168.123.4] BKO-dbqc01[192.168.123.2] ja
Ergebnis: Pr³fung auf Knotenkonnektivitõt f³r Subnet "192.168.123.0" mit Knoten
BKO-dbqc02,BKO-dbqc01 erfolgreich
Pr³fung: TCP-Konnektivitõt von Subnet "192.168.123.0"
Quelle Ziel Angemeldet?
BKO-dbqc01:192.168.123.2 BKO-dbqc02:192.168.123.4 erfolgreich
Ergebnis: Pr³fung der TCP-Konnektivitõt f³r Subnet "192.168.123.0" erfolgreich
Folgende Schnittstellen wurden auf Subnet "10.0.144.0" gefunden, die f³r ein Pri
vate Interconnect in Frage kommen:
BKO-dbqc02 PublicLAN:10.0.145.35
BKO-dbqc01 PublicLAN:10.0.145.32
Folgende Schnittstellen wurden auf Subnet "192.168.123.0" gefunden, die f³r ein
Private Interconnect in Frage kommen:
BKO-dbqc02 PrivateLAN:192.168.123.4
BKO-dbqc01 PrivateLAN:192.168.123.2
WARNING:
Es konnte keine geeignete Schnittstellengruppe f³r VIPs gefunden werden
Ergebnis: Pr³fung auf Knotenkonnektivitõt erfolgreich
Pr³fen: Gesamter Speicher
Knotenname Verf³gbar Erforderlich Kommentar
BKO-dbqc02 7,99GB (8378164.0KB) 922MB (944128.0KB) erfolgreich
BKO-dbqc01 7,99GB (8378164.0KB) 922MB (944128.0KB) erfolgreich
Ergebnis: Gesamter Speicher ▄berpr³fung erfolgreich
Pr³fen: Verf³gbarer Speicher
Knotenname Verf³gbar Erforderlich Kommentar
BKO-dbqc02 6,6797GB (7004176.0KB) 50MB (51200.0KB) erfolgreich
BKO-dbqc01 5,7739GB (6054412.0KB) 50MB (51200.0KB) erfolgreich
Ergebnis: Verf³gbarer Speicher ▄berpr³fung erfolgreich
Pr³fen: Swap-Bereich
Knotenname Verf³gbar Erforderlich Kommentar
BKO-dbqc02 15,9783GB (1.6754428E7KB) 7,99GB (8378164.0KB) erfolgreich
BKO-dbqc01 15,9783GB (1.6754428E7KB) 7,99GB (8378164.0KB) erfolgreich
Ergebnis: Swap-Bereich ▄berpr³fung erfolgreich
Pr³fen: Freier Datentrõgerspeicher f³r "BKO-dbqc02:C:\Windows\temp"
Pfad Knotenname Mount Point Verf³gbar Erforderlich Komm
entar
C:\Windows\temp BKO-dbqc02 C 105,3048GB 1GB erfo
lgreich
Ergebnis: Freier Datentrõgerspeicher ▄berpr³fung erfolgreich f³r "BKO-dbqc02:C:\
Windows\temp"
Pr³fen: Freier Datentrõgerspeicher f³r "BKO-dbqc01:C:\Windows\temp"
Pfad Knotenname Mount Point Verf³gbar Erforderlich Komm
entar
C:\Windows\temp BKO-dbqc01 C 91,5306GB 1GB erfo
lgreich
Ergebnis: Freier Datentrõgerspeicher ▄berpr³fung erfolgreich f³r "BKO-dbqc01:C:\
Windows\temp"
Pr³fen: Systemarchitektur
Knotenname Verf³gbar Erforderlich Kommentar
BKO-dbqc02 64-bit 64-bit erfolgreich
BKO-dbqc01 64-bit 64-bit erfolgreich
Ergebnis: Systemarchitektur ▄berpr³fung erfolgreich
Lõnge des Wertes der Umgebungsvariable "PATH" wird gepr³ft
Pr³fung: Lõnge des Wertes der Umgebungsvariable "PATH"
Knotenname Festgelegt? Maximale Lõnge Aktuelle Lõnge Kommentar
BKO-dbqc02 ja 1023 136 erfolgreich
BKO-dbqc01 ja 1023 189 erfolgreich
Ergebnis: Pr³fung auf Lõnge des Wertes der Umgebungsvariable "PATH" erfolgreich.
Pr³fung auf Media Sensing-Status von TCP/IP
Knotenname Aktiviert? Kommentar
BKO-dbqc02 nein erfolgreich
BKO-dbqc01 nein erfolgreich
Ergebnis: Pr³fung auf Media Sensing-Status von TCP/IP erfolgreich
Uhrensynchronisationspr³fungen mit dem Network Time Protocol (NTP) werden gestar
tet...
Es wird gepr³ft, ob Daemon aktiv ist...
Pr³fung: Aktiv f³r "W32Time"
Knotenname Wird ausgef³hrt?
BKO-dbqc02 ja
BKO-dbqc01 ja
Ergebnis: Aktivitõtspr³fung erfolgreich f³r "W32Time"
Pr³fung, ob der NTP-Daemon oder -Service aktiv ist, war auf allen Knoten erfolgr
eich
Ergebnis: Uhrensynchronisationspr³fung mit Network Time Protocol (NTP) erfolgrei
ch
Es wird gepr³ft, ob der aktuelle Benutzer ein Domain-Benutzer ist ...
Es wird gepr³ft, ob Benutzer "sup-bko-him" ein Domain-Benutzer ist
Ergebnis: Benutzer "sup-bko-him" ist Bestandteil der Domain "EUROPE"
Pr³fen: Zeitzonenkonsistenz
Ergebnis: Zeitzonenkonsistenz ▄berpr³fung erfolgreich
Pr³fung auf Status des Features zur automatischen Bereitstellung
Knotenname Aktiviert? Kommentar
BKO-dbqc02 ja erfolgreich
BKO-dbqc01 ja erfolgreich
Ergebnis: Pr³fung auf Status des Features zur automatischen Bereitstellung erfol
greich
Vorpr³fung f³r Cluster-Services-Setup war erfolgreich.
C:\install\11.2.0.2\grid>
* All tests were successful, sorry for the german :-) *
rootcrs log
... cutted ...
2010-12-22 21:21:01: Executing cmd: C:\grid\bin\crsctl check css
2010-12-22 21:21:01: Command output:
CRS-4529: Cluster Synchronization Services ist online
End Command output2010-12-22 21:21:01: CRS-2672: Versuch, "ora.mdnsd" auf "bko-dbqc01" zu starten
2010-12-22 21:21:01: CRS-2676: Starten von "ora.mdnsd" auf "bko-dbqc01" erfolgreich
2010-12-22 21:21:01: CRS-2672: Versuch, "ora.gpnpd" auf "bko-dbqc01" zu starten
2010-12-22 21:21:01: CRS-2676: Starten von "ora.gpnpd" auf "bko-dbqc01" erfolgreich
2010-12-22 21:21:01: CRS-2672: Versuch, "ora.cssdmonitor" auf "bko-dbqc01" zu starten
2010-12-22 21:21:01: CRS-2672: Versuch, "ora.gipcd" auf "bko-dbqc01" zu starten
2010-12-22 21:21:01: CRS-2676: Starten von "ora.gipcd" auf "bko-dbqc01" erfolgreich
2010-12-22 21:21:01: CRS-2676: Starten von "ora.cssdmonitor" auf "bko-dbqc01" erfolgreich
2010-12-22 21:21:01: CRS-2672: Versuch, "ora.cssd" auf "bko-dbqc01" zu starten
2010-12-22 21:21:01: CRS-2676: Starten von "ora.cssd" auf "bko-dbqc01" erfolgreich
2010-12-22 21:21:01: Querying for existing CSS voting disks
2010-12-22 21:21:01: Performing initial configuration for cluster
2010-12-22 21:21:01: Executing cmd: C:\grid\bin\crsctl start resource ora.ctssd -init
2010-12-22 21:21:04: Command output:
CRS-2672: Versuch, "ora.ctssd" auf "bko-dbqc01" zu starten
CRS-2676: Starten von "ora.ctssd" auf "bko-dbqc01" erfolgreich
End Command output2010-12-22 21:21:04: Start of resource "ora.ctssd" Succeeded
2010-12-22 21:21:04: Configuring ASM via ASMCA
2010-12-22 21:21:05: Executing as europe\sup-bko-him: C:\grid\bin\asmca -silent -diskGroupName GRID -diskList '\\.\ORCLDISKGRID0' -redundancy EXTERNAL -configureLocalASM
2010-12-22 21:21:05: Running as user europe\sup-bko-him: C:\grid\bin\asmca -silent -diskGroupName GRID -diskList '\\.\ORCLDISKGRID0' -redundancy EXTERNAL -configureLocalASM
2010-12-22 21:21:05: s_run_as_user: Running C:\grid\bin\asmca -silent -diskGroupName GRID -diskList '\\.\ORCLDISKGRID0' -redundancy EXTERNAL -configureLocalASM
2010-12-22 21:21:05: Executing C:\grid\bin\asmca -silent -diskGroupName GRID -diskList '\\.\ORCLDISKGRID0' -redundancy EXTERNAL -configureLocalASM
2010-12-22 21:21:05: Executing cmd: C:\grid\bin\asmca -silent -diskGroupName GRID -diskList '\\.\ORCLDISKGRID0' -redundancy EXTERNAL -configureLocalASM
*^^ hangs here*
asmca log:
... cutted ...
[Finalizer] [ 2010-12-22 21:21:15.070 CET ] [ClusterUtil.finalize:102] ClusterUtil: finalized called for oracle.ops.mgmt.has.ClusterUtil@68814013
[main] [ 2010-12-22 21:21:15.128 CET ] [OracleHome.getVersion:953] Current Version From Inventory: null
[main] [ 2010-12-22 21:21:15.129 CET ] [OracleHome.getVersion:960] using sqlplus: C:\grid\bin\sqlplus.exe
[main] [ 2010-12-22 21:21:15.174 CET ] [OracleHome.getVersion:1001] C:\grid\bin\sqlplus.exe Banner:
SQL*Plus: Release 11.2.0.2.0 Production
[main] [ 2010-12-22 21:21:15.174 CET ] [OracleHome.getVersion:1019] Current version from sqlplus: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.175 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.175 CET ] [OracleHome.getVersion:953] Current Version From Inventory: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.175 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.176 CET ] [OracleHome.getVersion:953] Current Version From Inventory: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.176 CET ] [SQLPlusEngine.getCmmdParams:222] m_home 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.176 CET ] [SQLPlusEngine.getCmmdParams:223] version > 112 true
[main] [ 2010-12-22 21:21:15.177 CET ] [SQLEngine.getEnvParams:552] Default NLS_LANG: GERMAN_GERMANY.AL32UTF8
[main] [ 2010-12-22 21:21:15.177 CET ] [SQLEngine.getEnvParams:562] NLS_LANG: GERMAN_GERMANY.AL32UTF8
[main] [ 2010-12-22 21:21:15.178 CET ] [SQLEngine.initialize:322] Execing SQLPLUS/SVRMGR process...
[main] [ 2010-12-22 21:21:15.180 CET ] [SQLEngine.initialize:359] m_bReaderStarted: false
[main] [ 2010-12-22 21:21:15.180 CET ] [SQLEngine.initialize:363] Starting Reader Thread...
[main] [ 2010-12-22 21:21:15.226 CET ] [UsmcaLogger.logExit:123] Exiting oracle.sysman.assistants.usmca.backend.USMInstance Method : createSQLEngine
[main] [ 2010-12-22 21:21:15.227 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: null
[main] [ 2010-12-22 21:21:15.229 CET ] [InventoryUtil.getOUIInvSession:347] setting OUI READ level to ACCESSLEVEL_READ_LOCKLESS
[main] [ 2010-12-22 21:21:15.229 CET ] [OracleHome.getVersion:904] Homeinfo C:\grid,1
[main] [ 2010-12-22 21:21:15.318 CET ] [OracleHome.getVersion:953] Current Version From Inventory: null
[main] [ 2010-12-22 21:21:15.318 CET ] [OracleHome.getVersion:960] using sqlplus: C:\grid\bin\sqlplus.exe
[main] [ 2010-12-22 21:21:15.369 CET ] [OracleHome.getVersion:1001] C:\grid\bin\sqlplus.exe Banner:
SQL*Plus: Release 11.2.0.2.0 Production
[main] [ 2010-12-22 21:21:15.369 CET ] [OracleHome.getVersion:1019] Current version from sqlplus: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.370 CET ] [UsmcaLogger.logInfo:142] Role SYSASM
[main] [ 2010-12-22 21:21:15.370 CET ] [UsmcaLogger.logInfo:142] OS Auth true
[main] [ 2010-12-22 21:21:15.777 CET ] [SQLEngine.done:2167] Done called
[main] [ 2010-12-22 21:21:15.778 CET ] [UsmcaLogger.logException:172] SEVERE:method oracle.sysman.assistants.usmca.backend.USMInstance:configureLocalASM
[main] [ 2010-12-22 21:21:15.778 CET ] [UsmcaLogger.logException:173] ORA-01034: ORACLE not available
[main] [ 2010-12-22 21:21:15.779 CET ] [UsmcaLogger.logException:174] oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-01034: ORACLE not available
oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeImpl(SQLEngine.java:1655)
oracle.sysman.assistants.util.sqlEngine.SQLEngine.executeQuery(SQLEngine.java:828)
oracle.sysman.assistants.usmca.backend.USMInstance.configureLocalASM(USMInstance.java:3003)
oracle.sysman.assistants.usmca.service.UsmcaService.configureLocalASM(UsmcaService.java:1049)
oracle.sysman.assistants.usmca.model.UsmcaModel.performConfigureLocalASM(UsmcaModel.java:926)
oracle.sysman.assistants.usmca.model.UsmcaModel.performOperation(UsmcaModel.java:779)
oracle.sysman.assistants.usmca.Usmca.execute(Usmca.java:174)
oracle.sysman.assistants.usmca.Usmca.main(Usmca.java:369)
[main] [ 2010-12-22 21:21:15.779 CET ] [UsmcaLogger.logEntry:114] Entering oracle.sysman.assistants.usmca.backend.USMInstance Method : createSQLEngine
[main] [ 2010-12-22 21:21:15.779 CET ] [SQLEngine.done:2167] Done called
[main] [ 2010-12-22 21:21:15.780 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: null
[main] [ 2010-12-22 21:21:15.782 CET ] [InventoryUtil.getOUIInvSession:347] setting OUI READ level to ACCESSLEVEL_READ_LOCKLESS
[main] [ 2010-12-22 21:21:15.783 CET ] [OracleHome.getVersion:904] Homeinfo C:\grid,1
[main] [ 2010-12-22 21:21:15.874 CET ] [OracleHome.getVersion:953] Current Version From Inventory: null
[main] [ 2010-12-22 21:21:15.874 CET ] [OracleHome.getVersion:960] using sqlplus: C:\grid\bin\sqlplus.exe
[main] [ 2010-12-22 21:21:15.926 CET ] [OracleHome.getVersion:1001] C:\grid\bin\sqlplus.exe Banner:
SQL*Plus: Release 11.2.0.2.0 Production
[main] [ 2010-12-22 21:21:15.926 CET ] [OracleHome.getVersion:1019] Current version from sqlplus: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.926 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.927 CET ] [OracleHome.getVersion:953] Current Version From Inventory: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.927 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.927 CET ] [OracleHome.getVersion:953] Current Version From Inventory: 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.928 CET ] [SQLPlusEngine.getCmmdParams:222] m_home 11.2.0.2.0
[main] [ 2010-12-22 21:21:15.928 CET ] [SQLPlusEngine.getCmmdParams:223] version > 112 true
[main] [ 2010-12-22 21:21:15.928 CET ] [SQLEngine.getEnvParams:552] Default NLS_LANG: GERMAN_GERMANY.AL32UTF8
[main] [ 2010-12-22 21:21:15.929 CET ] [SQLEngine.getEnvParams:562] NLS_LANG: GERMAN_GERMANY.AL32UTF8
[main] [ 2010-12-22 21:21:15.929 CET ] [SQLEngine.initialize:322] Execing SQLPLUS/SVRMGR process...
[main] [ 2010-12-22 21:21:15.931 CET ] [SQLEngine.initialize:359] m_bReaderStarted: false
[main] [ 2010-12-22 21:21:15.932 CET ] [SQLEngine.initialize:363] Starting Reader Thread...
[main] [ 2010-12-22 21:21:15.982 CET ] [UsmcaLogger.logExit:123] Exiting oracle.sysman.assistants.usmca.backend.USMInstance Method : createSQLEngine
[main] [ 2010-12-22 21:21:15.983 CET ] [OracleHome.getVersion:885] OracleHome.getVersion called. Current Version: null
[main] [ 2010-12-22 21:21:15.985 CET ] [InventoryUtil.getOUIInvSession:347] setting OUI READ level to ACCESSLEVEL_READ_LOCKLESS
[main] [ 2010-12-22 21:21:15.986 CET ] [OracleHome.getVersion:904] Homeinfo C:\grid,1
[main] [ 2010-12-22 21:21:16.079 CET ] [OracleHome.getVersion:953] Current Version From Inventory: null
[main] [ 2010-12-22 21:21:16.079 CET ] [OracleHome.getVersion:960] using sqlplus: C:\grid\bin\sqlplus.exe
[main] [ 2010-12-22 21:21:16.132 CET ] [OracleHome.getVersion:1001] C:\grid\bin\sqlplus.exe Banner:
SQL*Plus: Release 11.2.0.2.0 Production
[main] [ 2010-12-22 21:21:16.133 CET ] [OracleHome.getVersion:1019] Current version from sqlplus: 11.2.0.2.0
[main] [ 2010-12-22 21:21:16.133 CET ] [UsmcaLogger.logInfo:142] Role SYSASM
[main] [ 2010-12-22 21:21:16.133 CET ] [UsmcaLogger.logInfo:142] OS Auth true
*^^no further entries here, so hangs, too*hmm, it is getting more misterious:
if i enable DTrace on the asmca-commandline (-DTRACING.ENABLED=true -DTRACING.LEVEL=2), asmca works ... -
Is my OLE DB installation done correctly on Windows Server 2008 R2 64bit?
I have installed Instant Client thru Instant Client option in Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64) NOT thru Instant Client package.
Then I installed the oledb from 64-bit ODAC 11.2 Release 3 (11.2.0.2.1) for Windows x64 by executing install.bat oledb c:\oracle odac.
I find the following values in registries:
under HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\KEY_odac:
NLS_LANG has the value AMERICAN_AMERICA.WE8MSWIN1252
OLEDB has the value c:\Oracle\oledb\mesg
ORACLE_GROUP_NAME has the value Oracle - odac
ORACLE_HOME has the value c:\Oracle
ORACLE_HOME_NAME has the value odac
under HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\KEY_OraClient11g_home1:
NLS_LANG has the value AMERICAN_AMERICA.WE8MSWIN1252
ORACLE_GROUP_NAME has the value Oracle - OraClient11g_home1
ORACLE_HOME has the value C:\Oracle\product\11.2.0\client_1
ORACLE_HOME_NAME has the value OraClient11g_home1
I wonder whether I have done the installations incorrectly since some keys have different values between the 2 registries.I have no doubt that the problem in the OS localization.
But, taking into account some facts:
World population is estimated to number 7.126 billion people.
Anglosphere is about 740 million people.
I have not found information about the supported OS languages.
I'm worried about losing my non-English data.
I am for the licensed software, but a trial and registered OS has the same functionality, and displays messages/data in the same way.
I doubt that the OS registration will allow installer to properly finish and even display the error correctly. (Java strings is UTF-based, so, developers should set correct code page. Probably, because system code page can be different with console code page (cp866 for Russian). Current codepage could be view by executing "chcp" in console).
In any case Enterprise-class product should operate correctly on each supported systems, or inform about problems before. -
Windows Server 2008 R2 Service Pack 1 installation failed with error code 0x800f0a12
Hello,
I'm facing problem to install windows server 2008 R2 SP1. I cannot install SP1. In this server have running Exchange 2010 server. to update Win2008 R2 SP1 facing the following error:
1. Service Pack installation failed with error code 0x800f0a12.
2. Installation Failure: Windows failed to install the following update with error 0x80070643: Windows Server 2008 R2 Service Pack 1 for x64-based Systems (KB976932).
Please suggestPlease run the system update readiness tool.
http://windows.microsoft.com/en-us/windows7/What-is-the-System-Update-Readiness-Tool?SignedIn=1
Then post the complete contents of;
%SYSTEMROOT%\Logs\CBS\CheckSUR.log
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. -
Installation problem on windows server 2008 r2 datacenter edition 64bit
hi
today, i tried to install the current maxdb 7.8 release on my virtual server with a windows server 2008 r2 datacenter 64bit edition os. at the first installation, i got an error message something with "rte runtime error". at this point, the installation stopped.
because of this error, i tried to uninstall the failed installation. this was not possible, in the uninstaller, i didn't see any components, so i can't uninstall.
so i tried to delete the files manually: the entries in the start menu, and the application's path under "program files"... first, i need to kill a process named "serv.exe", that creates a tcp daemon under port 7200... after killing it, the deletion of the dir in program files was successful.
this is very very weird, now my server is "contaminated" with an uncomplete uninstallation of maxdb...
why maxdb 7.8 has problems on windows server 2008 r2 datacenter 64bit edition???
thanks for feedbacks!
regards, jan> no, because i canceled this virtual server - another method to solve this problem. (i have really no time for things like that..!)
If you take the time to give exact error messages then someone will be certainly able to help
> on windows server 2003, there are NO problems.
Windows 2003 != Windows 2008 - they use a different kernel, a different security system (UAC) and other features that may prevent a succesfull installation in the first place.
I installed a MaxDB 7.8 just today on Windows 2008 R2 and it worked fine.
Markus -
Problems LMS-4.2 Installation on Windows Server 2008 R2 Enterprise SP1
Hi all,
During the installation of the LMS-4.2,
It passed the "Initializing" and "Copying" stages,
but, in the "Configuring", it never finishes,
Anyone had have a similar problem?
the installer is for - LMS-4.2 and the OS is Windows Server 2008 R2 Enterprise SP1Thanks for the update. Glad to know it has installed now.
There can be some port clashes and resource scarcity when other applications may be using it. Hence we recommend to have majorly LMS as the primary software on the server's.
Also, LMS is not supported in other languages installers or setups except English and Japanese.
There are a couple more things you can do/check prior to running the installation.
LMS generally need Naming convention to handle long names/path etc. By default C: has 8.3 Naming convention enabled. However if you installed on different drive (for eg E:), for which this may be disabled.
To check naming convention you can run the following command from Windows Command prompt:
cmd>fsutil.exe 8dot3name query <Drive>
Example:
C:\Users\winlau>fsutil 8dot3name query C:
The volume state for Disable8dot3 is 0 (8dot3 name creation is enabled).
The registry state of NtfsDisable8dot3NameCreation is 2, the default (Volume level setting).
Based on the above two settings, 8dot3 name creation is enabled on C:.
8dot3 needs to be enabled for all drives LMS will potentially use, including:
Drive where TEMP/TMP is located
The drive LMS is installed to
The drive LMS backs up to
Drive used for a relocated RME Shadow directory or other nonstandard paths written to.
In some cases, altering the TEMP and TMP variables to be a short path (eg C:/temp or C:/tmp) may avoid the issue, but not always.
Hence, to be safe, it is best to enable 8dot3name creation globally, either via the registry or Windows CLI
Sample command to enable globally:
"fsutil 8dot3name set 0"
Sample command to enable on one volume:
"fsutil 8dot3name set X: 0"
Note that this needs a reboot to take effect. You should not disable 8dot3name creation which already has it enabled, especially the system volume (usually C:).
For further information http://technet.microsoft.com/en-us/library/cc778996%28v=ws.10%29.aspx
-Thanks
Vinod
**Encourage Contributors. RATE them** -
Oracle 11gR2 installation problem on Windows Server 2008 R2 datacenter
Hi
I am trying to install Oracle 11Gr2 64 bit on Windows server 2008 R2.The system configuration is "Intel Xeon, RAM 8.00 GB.
i
The installation is getting paused at the 8th step of Oracle installation.Neither i am getting any error message nor an entry is recorded in the Oracle inventory log.
It is showing a blank screen after the prerequiste checks are complete.
Request you to help me out in resolving the issue.
Thanks in advance for your cooperation.Hi Helios
Thanks for the response. The database is still not created to check in the Alert log .It is still in the phase of pre-requisite checks. I did not go with Silent installation.It is a plain single instance installation.
The installation screen is greyed out with out any message or error.
Please could you share if you have any thoughts on this. -
Hello
I am trying to install Exchange Server 2010 beta 1 onto a Windows Server 2008 R2 (build 7000) machine which has also been set up as a domain controller.
However when attempting to install the Client Access role, setup fails with the error below.
Does anyone know of a way to get around this please?
I have already searched for this error and not found any similar threads.
Also every time I press the code button on this forum it crashes the browser and I keep losing the message! (IE8 from within Server R2). Also the message box is very small, will not expand and keeps jumping to the top.
Thanks
Robin
[code]
Summary: 4 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:00:01
Preparing Setup
Completed
Elapsed Time: 00:00:00
Client Access Role
Failed
Error:
The execution of: "$error.Clear(); Install-ExchangeCertificate -services "IIS, POP, IMAP" -DomainController $RoleDomainController", generated the following error: "Could not grant Network Service access to the certificate with thumbprint 2F320F5D5B5C6873E54C8AB57F604D8AFA31D18C because a cryptographic exception was thrown.".
Could not grant Network Service access to the certificate with thumbprint 2F320F5D5B5C6873E54C8AB57F604D8AFA31D18C because a cryptographic exception was thrown.
Access is denied.
Elapsed Time: 00:00:01
Mailbox Role
Cancelled
Finalizing Setup
Cancelled
[/code]
Robin WilsonHello
Thanks for all the replies.
I have since wiped the system and installed everything again and it all worked this time so not sure what was wrong last time. I did try to uninstall all Exchange components and then uninstall IIS and Application server, reboot and re-install but I received the same error still when it came to installing the client access role.
Walter: I just attempted the standard installation which should have used the default self-signed certificate. Everything was a fresh install done at the same time on a freshly formatted PC.
For info last time when it failed to work:
- Installed Windows Server 2008 R2
- Installed Domain Controller role using dcpromo. I set the forest and domain as Windows Server 2008 R2
- Added a forest trust between main domain and test Exchange domain (set up as ex2010.local)
- Installed IIS and Application Server role
- Installed Hyper-v role
- Installed Desktop Experience feature
- Installed Exchange and recieved the error
When it worked I set up the forest and domain in Windows Server 2008 mode (i.e. not R2), installed Exchange first and then set up the forest trust and then Hyper-v. It did say it failed to configure dns which was probably because it started trying to do automatic updates half way through the dcpromo! DNS seems to work ok though.
I did notice this time that Hyper-v gave a warning about the virtual network adapter not being set up correctly and the local network did not work correctly although I could access the internet. Not sure if this could have been related to the cause of the problem previously. For now I have disabled the virtual network until I get time to try and get it working and so the mail will work in the meantime.
I also noticed that Hyper-v added an extra 443 ssl binding to the default website so as it had 2 bindings on port 443 it refused to start. After deleting one it worked.
I decided to install Exchange onto a domain controller as it is only a test and I wouldn't do it in a live environment. I am also short of test machines! It didn't give me any warnings about this actually, I think previous versions warn you that it is not recommended.
Andreas and Chinthaka: I did not know about the requirement to run the domain at 2003 mode. The main domain is running in 2008 mode with Exchange 2007 so I assume this is just a temporary beta related requirement. It does seem to be working (second attempt) so far in a 2008 mode domain although I haven't had a chance to fully test it yet.
Thanks
Robin
P.S. Sorry it's taken me a while to reply!
Robin Wilson -
Installation Server Slow on Windows Server 2008 R2
Previously I had two identical servers setup to service SAPGui installs in our corporate office. Both were configured for SAPGui 7.20 Patch 3 and the servers were Windows Server 2003 SP2.
Recently one of these servers was replaced with a newer/faster with more memory Windows Server 2008 R2 box.
I immediately noticed installs to front ends were taking longer when run off the 2008 system. Today I timed installs to two identical front end Win XP computers.
Server 2003 SP2 installed in 7 minutes.
Server 2008 R2 installed in 23 minutes.
Has anyone else experienced this?
Bob HI have no doubt that the problem in the OS localization.
But, taking into account some facts:
World population is estimated to number 7.126 billion people.
Anglosphere is about 740 million people.
I have not found information about the supported OS languages.
I'm worried about losing my non-English data.
I am for the licensed software, but a trial and registered OS has the same functionality, and displays messages/data in the same way.
I doubt that the OS registration will allow installer to properly finish and even display the error correctly. (Java strings is UTF-based, so, developers should set correct code page. Probably, because system code page can be different with console code page (cp866 for Russian). Current codepage could be view by executing "chcp" in console).
In any case Enterprise-class product should operate correctly on each supported systems, or inform about problems before. -
Windows Server 2008 R2 problem
Hi there
I'm a newbie to Flash media server and I would like to explore its usage.
Does any one have experience with Flash Media Server 3.5.3 running on Windows Server 2008 R2? I installed FMS on my Windows Server 2008 R2, but the admin console cannot start.
By the way, I installed FMS on a Windows Server 2003 32-bit machine. And I'm able to use the admin console on Server 2003 to connect to the Server 2008 R2 installation.
Also, I have a separate disk that is used to hold the media content to be streamed via FMS. How can I configure FMS to use that disk as root for media file instead of using "c:\program files (x86)\...\webroot\vod"
Thanks very much in helping me to start the project.
Best Regards
Steve YauForThanks very much for your prompt response.
For (1), if I start "Flash Media Administration Console" from the Start menu, an IE prompts up and it tries to open "c:\program files(x86)\Adobe\Flash Media Server 3.5\tools\fms_adminConsole.htm" with the following in the information bar:
"An add-on for this website failed to run. Check the security settings in Internet Options for potential conflicts"
I thought it was the problem of flash player that cannot be run on 64-bit IE, so i tried 32-bit IE, but still in vain. I also tried to install flash player using 32-bit IE on Windows server 2008 R2 but the installation cannot start.
The FMSAdmin service is surely running with firewall configured. I've also installed FMS on another Windows Server 2003 32-bit. There I can start the admin console and connect to the Windows Server 2008 R2 FMSAdmin service.
For (2), I've added the line as per your kind help. But my question will be: How can I test whether my FMS is correctly streaming the video? For Windows Media Service, I can easily open URL in WMP and the streaming can be verified easily. But I don't know how to test FMS setup from web client side. Any clues? For your information, I don't have Adobe Flash or Dreamweaver stuff.
Thanks again for your kind help
Regards
Steve Yau -
Error while performing SAP Installation in HA Env on Windows Server 2008
Hello,
I am performing a SAP Installation in HA Environment on Windows Server 2008. I am at the ASCS installation step.
As per the guide before installing ASCS there are some activities to be carried out on Failover Cluster Management.
I have done all the steps except one as per the guide. I am stuck in the Add FileServer Step. In this step the guide says to go to the Dependencies tab and add the cluster disk resource to the dependencies list. It also says to add the Name:Virtual NetworkName to the dependencies list.
Now in my scenario I have 3 shared drives for SAP and I have added each of them in the dependencies list of the new FileServer. The only problem is how do I add the Name:Virtual NetworkName to this list
When I continue without giving the Network name the system issues a warning "This resource requires dependencies on instances of the following resource types or classes:Network Name. Not adding these dependencies will prevent the resource from working properly. Do you want to save the current settings anyway"
If I click on Yes and bring this resource online it fails with this error message
"The action Bring this resource online did not complete.An error occured while attempting to bring the resource 'SAPECC FileServer online'. The cluster resource could not be brought online by resource monitor."
My question is how to add the Name:VirtualNetworkName to the dependencies list of the FileServer.
Regards
Mitesh NairHi,
I have resolved the issue with the help of cluster admin
Regards
Mitesh
Maybe you are looking for
-
Dates not showing up in Metadata Library filter
I sometimes use the Library filter to filter pictures by date, which has worked very well before. When using it today, I discovered that only 23 (edit: the 23 first) of 43 pictures taken on Oct. 26 would show up, and the pictures taken on the 27th an
-
How to monitor messages going out of XI? Kindly help!
Hi Experts, I have a XI scenario where my IDOC message is going out from XI to TIBCO. I am using the JMS adapter as the receiver here. Once message is sent from XI we don't know if it really reached TIBCO? How do we monitor such messages? Basic
-
Possible to split one large pdf into multiple pages (in the same pdf?)
I have some well logs that have been scanned - problem is they're coming is as one loooong page in the pdf. Is it possible to split it up into several 8.5 x 11 pages within Acrobat, or do I need special software?
-
Hi, I am working on CE 7.1 SP11. I am trying to connect to EJB application running on IBM WebSphere using RMI/IIOP protocol. The JNDI look up is working, java methods without arguments are working but it is failing when I try to execute methods with
-
Hi, I was wondering if you have any tips on using bc4j in applets. The 2 biggest problems I'm having is the jar size of the applet after all libs are included (4MB+) and the fact that I can't use XDK, JNDI, BC4J and some other libs from applets unles