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
Similar Messages
-
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.
- NeilHi 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>----- -
WLC 5508 & Windows Server 2008 radius
Hello guys, I need some bailout here. I have a WLC 5508 which i have configured for AP's but i would like to use the windows server 2008 as the radius server to authenticate the Active directory users.
Can i use a separate windows server 2008 as the radius server or I have to use the same server working as the Active directory?
I don't want to request unnecessary server from my client.
Rgds,
AnthonyI am trying to take my WLC 5508 and have backend authentication through LDAP using web auth. i have tried and tried to set this up but it fails everytime.
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008067489f.shtml
I used that document to get me most of the way there but i cant get the part in the WLC where i go to SECURITY>AAA>LDAP, from here i click on the SERVER index that I want to use which is 1 and not sure what creditenals to put in some of those fields on there. the fields are USER BASE DN: , USER ATTRIBUTE: , and USER OBJECT TYPE: . I have tried to do it as the link says from above but it just does not work. -
This server (Windows Server 2008 R2 Standard with SP1) is used to host thin clients as well as RDP sessions. One morning the office is fine, they come back from lunch and all of the sudden they can't load certain web pages, such as adobe.com
and pandora.com to name a couple. This was roughly 3 days ago.
1.) I have tried machines that are not connected to this server (not thin client or RDP), but are on the same network, they can load up any web page fine with no issues.
2.) On the server I have tried Opera, Chrome, IE and Firefox, all have the same exact problem.
3.) Tried different DNS servers just to be sure, even though it only effects the server and no one else.
Based on these facts I know that it is something wrong with the server, but not tied to a specific brower. In all browsers when you load up a page in question it just sits there with a blank screen trying to load, it never generates any errors.
The Event Viewer is also clean, no errors. So with no errors I have had trouble trying to find a starting place for this. Things I have tried:
1.) ipconfig /flushdns to try and clear out any DNS issues
2.) Changing the DNS servers for the server to 8.8.8.8 and 4.2.2.2
3.) Scanning for Viruses and Malware/Spyware
4.) Checking proxy settings on the server
5.) Updating and then removing Adobe Flash (thought it was tied to flash at first). Problem persists even with no flash player installed.
6.) Completed a failed update of .net, no effect
7.) Loading up browsers in debug mode to try and find anything in the site code that I could relate between failed sites. I found nothing I could identify
Of all issues to finally be stumped on this seems like an easy one, but I can't even begin to come up with an idea at this point.
I have tried to lay out all of the facts that I know as plainly as I can. I am hoping that someone has seen this before as this issue is effecting a number of differnt users and keeping them from doing portions of their job.
Help is most appreciated, thank you!I was able to figure out a solution.
CAUSE:
It appears that the Internet isn’t fully up to date and ready to use EDns -- which is enabled on Windows Server 2008 R2 by default. The solution for this is to disable Edns. Note that this isn’t
a problem for most Windows Server 2008 R2 member servers. It’s only a problem for DNS *servers* that do recursive lookups. i.e. likely only your domain controller will be affected if that is where your DNS Server role exists.
SOLUTION:
To disable EDns, you can do it from the command prompt, or by editing the registry.
Create a DWORD called EnableEDNSProbes and set to 0 in HKLM\SYSTEM\CurrentControlSet\services\DNS\Parameters
Restart the DNS Server service for it to take effect. -
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. -
Insatallation von Adobe CS5 auf Windows Server 2008 R2
Hallo miteinander!
Hat jemand schon Erfahrungen gemacht mit der Installation von Adobe CS5 auf Windows Server 2008 R2/ Remote Desktop host? Auch im Hinblick auf den Einsatz von Virenscannern?
Über jeden Tipp/ link/ Hinweis/ Anregung usw. bin ich dankbar.
Vielen Dank im Voraus.I was able to figure out a solution.
CAUSE:
It appears that the Internet isn’t fully up to date and ready to use EDns -- which is enabled on Windows Server 2008 R2 by default. The solution for this is to disable Edns. Note that this isn’t
a problem for most Windows Server 2008 R2 member servers. It’s only a problem for DNS *servers* that do recursive lookups. i.e. likely only your domain controller will be affected if that is where your DNS Server role exists.
SOLUTION:
To disable EDns, you can do it from the command prompt, or by editing the registry.
Create a DWORD called EnableEDNSProbes and set to 0 in HKLM\SYSTEM\CurrentControlSet\services\DNS\Parameters
Restart the DNS Server service for it to take effect. -
Problem instaliing sun one LDAP server on windows server 2008 r2
Hi all ,
I am trying to install Ldap server (Sun ONE Directory Server) on windows server 2008
I am using apache-tomcat-7.0.28 and java jdk1.7.0_05
I am following this manual for installing :
https://blogs.oracle.com/marginNotes/entry/installing_directory_server_enterprise_edition1
I have a problem with the cacao agent and how to install it .
I've got this error message :
c:\Program Files\Sun\dsee7\bin>dsccsetup cacao-reg
Configuring Cacao...
## Failed to run "c:/Program Files/Sun/dsee7/ext/cacao_2/bin/cacaoadm.bat" set-
aram "jdmk-home=c:/Program Files/Sun/dsee7/lib/private"
#### Cannot create service for instance: [cacao.instance.name].
#### Cannot perform firstime inialisation and configuration.
## Exit code is 1
Failed to configure Cacao.
I stuck and with no other solutions . I hope if you could to help with this issue .
i will glad to know if there is any other ways to install this specific Ldap server ,
Thanks,
AlonYou most likely skipped the step of starting the installed server prior to trying to access admin URL. Please check this document:
http://docs.sun.com/source/817-1830-10/win.html
Relevant section is:
You can start the Administration Server in either of the following ways:
# Select Start Menu -> Programs -> Sun ONE Web Server, and choose Start Web Server Administration Server.
# From the Control Panel�s Services item.
HTH... -
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** -
Problem of SAPConsle 7.10 (Patch 13) on Windows server 2008 R2 (64bit)
My company is moving from server 2003 to Server 2008 R2 (64bit). We installed SAPConsole 7.10 (Patch level 13) on test server without any problem and configured the profiles in SAPConsole administrator. However when we running the sapcnsl.exe from command prompt, it prompt with error message "*** ERROR => ***AgCom (006FC558): Error: Internal error" and failed to get the SAP login screen.
I checked SAP Note 1043241 saying SAPConsole 710 as patch level 7 could support Windows server 2008 (32/64bit) both.
Can anyone help advise on my issue? or is there anyone has testl the SAPConsole 710 on Server 2008 R2 64bit successfully?
Thank you very much!Hello Jackcd,
I am not an expert in this area but I did a message search for "AgCom error internal error" and I found a message where the customer solved the problem by using a patch. In the customers own words:
"I installed sapgui 7.10 Patch level 6 on the server where I installed SAPCONSOLE 7.10. Now, the sapconsole working."
The Sapinator -
Application/DLL problem on Windows Server 2008 R2
I have an issue with an application which needs to run on a Windows Server 2008 R2 environment. The issue concerns "msvbvm60.dll" which results in an "APPCRASH" when I try to run the application.
The APPCRASH reports the issue is with msvbvm60.dll version number "6.0.98.15". We have another customer with Windows Server 2008 (not R2) which has version "6.0.98.2" of the same file and the application works fine there.
I've got 2 questions really then ...
Could I replace the .15 version with .2? There appear to be 2 "system" folders on the server "C:\windows\system32" and "C:\Windows\syswow64" - would both of these need to be addressed
Would a later version than .15 cure the problem?
I've trawled this site but unable to find an exact solution or advice that fits my situation.
Thank you.Which application? Is that a Microsoft product? If not, I would suggest you contact the software developer for assistance.
---Could I replace the .15 version with .2? There appear to be 2 "system" folders on the server "C:\windows\system32" and "C:\Windows\syswow64" - would both of these need to be addressed
Yes, you may give it a try. Usually, put it in WoW64 folder if it's a 32bit DLL. Otherwise, put it in System32 folder. -
Problems after print server migration to Windows Server 2008 R2
Hi all,
New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
Environment
I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
Problems
Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
Attempted Fixes
These are some of the attempted fixes that I have tried:
Turning it off and on
Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
Upgrading the firmware on the CM3530's to resolve garbled printing
Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
If anyone is able to provide any assistance that would be greatly appreciated.
Many thanks,
Hartz.
tldr; our printers are screwed since migrating to Windows Server 2008 R2.Hi all,
New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
Environment
I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
Problems
Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
Attempted Fixes
These are some of the attempted fixes that I have tried:
Turning it off and on
Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
Upgrading the firmware on the CM3530's to resolve garbled printing
Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
If anyone is able to provide any assistance that would be greatly appreciated.
Many thanks,
Hartz.
tldr; our printers are screwed since migrating to Windows Server 2008 R2. -
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 -
Development Platform:
Visual Studio 2003 (VB)
Crystal Reports XI Developers Edition (Version 11.0.0.895)
Developed on Windows XP (SP3)
Deployed (VB) Program Normally Runs Windows Server 2003 (No problems)
Problem: Cannot run on Windows Server 2008 (32 Bit nor 64 Bit Versions)
THREE QUESTIONS:
Q1. Is the CR XI Dev Ed (11.0.0.895) the same as CR XI R1?
Q2. Is there a known conflict between this version and Windows Server 2008 ( either 32 Bit or 64 Bit)? If so, is there a fix?
Q3. There is a service pack (SP4) which is for CR XI R1. Does this apply to my version of Crystal Reports? Are there updated Merge Modules as well?
The program deploys to both versions of WS 2008 fine. However, it does not work on either. The errors are different. On the 64 bit version, a simple u201Ccannot access the file in c:\windows\tempu201D message. Permissions have been checked and are ok. On the 32 bit version, we get a 503 error (Service Unavailable) and the Internet Server gets u201Chungu201D and will not clear without a reboot of the machine, literally.
This is an updated question to an eariler post, which is unresolved. Many thanks to whoever can help.Hi David,
Q1. Is the CR XI Dev Ed (11.0.0.895) the same as CR XI R1?
answer- Yes, both are same
Q2. Is there a known conflict between this version and Windows Server 2008 ( either 32 Bit or 64 Bit)? If so, is there a fix?
Answer-
unfortunately my help is very limited in this scenario.
Please do not deploy CR XI to win2008 OS.
This OS is not tested and not supported with CR XI.
Please see a full list of supported OS [here|https://websmp104.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000086718&_OBJECT=011000358700001092722008E]
Even the latest edition Reports [XI Release 2 u2013 Service Pack 4|https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000086812&_OBJECT=011000358700001080932008E] is not supported for Win2008.
Q3. There is a service pack (SP4) which is for CR XI R1. Does this apply to my version of Crystal Reports? Are there updated Merge Modules as well?
Answer- Yes, that SP4 is for CR version 11.0 - to download click [here|http://resources.businessobjects.com/support/additional_downloads/service_packs/crystal_reports_en.asp#CRXIR1].
Latest merge modules for CR XI R1 SP4 can be downloaded from [here|http://resources.businessobjects.com/support/additional_downloads/runtime.asp#05]
Hope that helps!!
Regards,
Amit
Best regards -
Printing problem with Konica Minolta BizHub282 using RDP on Windows Server 2008 R2
Hello,
I have an office setup as follows: Local office IP adress scheme 192.168.201.x. There is a Konica Minolta BizHub 282 printer connected to the 192.168.201.x network as well as around 10 workstations running Windows 7. There are also about
10 additional teleworkers WHO DO NOT NEED print access to the Minolta 282. All of their data is on a cloud server. I have them setup to first connect to the cloud server using a RRAS PPTP VPN and then to start an RDP session to the separate
RDP server. The Konica Minolta works ??okay?? with the easy print services and until now, we have just dealt with the lack of features and the occasional print job that goes crazy and prints out 400 blank pages (btw, this is usually on Excel) or a job
that cuts off the margins even when you have it set to "fit to page" (this usually happens in Adobe.) When I originally set this up, I tried loading the native Konica drivers on the server, but there was no joy because I couldn't get it to
work using the native drivers. The problem at hand is a feature called "account track." This feature authenticates your print job by using an account code. If there is no code, the job just disappears. When I load the native
Konica driver, the ability to turn on this feature is greyed out (see below):
When I use easy print, the codes seem to go through, but as I mentioned earlier, sometimes the print job just goes insane. After researching this, it seems to me that there are two ways to overcome this if we can't turn off the account track feature:
1) Overcome the driver problem. I've tried both of their current drivers without success: VXL and Visual Postscript. When I login to RDP, the (redirected) Konica 282 printer is listed, but when I try to print, it fails due to the missing account track code.
I'm hoping that there is a registry hack to turn this feature on by default with the code or a driver version that works with RDP. They have a WHQL driver available, but it didn't work any better. Is there a way to report this issue to the WHQL labs? Maybe
I can light a fire under Konica's rear end and motivate them to fix the driver.
2) I saw one discussion where the guy installed the printer out in the clouds as a local printer. He seemed to have a site-to-site VPN, not a client-to-site VPN, so this worked. Is there a way to do something similar when the customer connects to the
VPN through standard "connect to workplace" setup? I tried pinging the Konica 282 from the server while logged into the VPN, but the printer could not be found.
3) I considered setting it up as a google cloud print prnter, but that would require everyone to setup a google account and add a layer of complexity.
Anyone else run into this and have a solution? If not, does anyone have any ideas on a solution or workaround?
Thanks,
Jeffery SmithHi Jeffery,
Thank you for your comment.
Yeah, you can use universal print driver by configuring Remote Desktop Easy print on RDS Server. Install the driver on RDS server. Now to configure Easy print you need to have minimum client RDP 6.1(But suggest you to install RDP 8.1), .Net Framework 3.5 or
above and RDSH role.
Also under GPO setting need to check below settings.
Do not allow client print redirection: Disable
Use Terminal Service Easy print printer driver first: Enable
Computer Configuration > Administrative templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Printer redirection
For more information, you can refer below articles.
How to configure Microsoft RDS Universal Printing
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/microsoft-hyper-v/how-configure-microsoft-rds-universal-printing.html
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx?Redirected=true
Hope it helps!
Thanks.
Dharmesh Solanki
Maybe you are looking for
-
Since installing Mavericks I am unable to scan to my Mac from my Canon MP160. I had no problem with Mountain Lion, everything just worked. Canon do not have a new driver because they think the problem is with Mavericks.
-
Satellite P - How to disable hibernation and standby?
I have set power configuration to say Never for both Hibernation and Standby - both occur. What am I doing wrong? I would be happy with Standby but do NOT want Hibernation!
-
My location bar won't suggest sites, but my settings are telling it to. What's wrong?
You know, when you start typing a letter or two into the location bar and a list of sites you've visited appear in the dropdown. On the privacy settings page, I have History set to "Firefox will: Remember History" and Location Bar "When using locatio
-
Shiping labels print from LM19 Transaction in WM
Hi all, This is regarding shipping labels print from RF transaction LM19. How it can be done? I saw in some document that we can do it with the user exit provided by SAP, Which is accessed by function module LE_MOB_PRINT. Please let me know the proce
-
Monthly return for production and removal of goods - ER 1
How to generate -Monthly return for production and removal of goods - Form ER 1 is there any standard reports in SAP which directly can be submitted to Excise Authorities. regards Rajesh