Problem reinstalling WSUS on Server 2008 R2

I tried following these steps in these two articles but I am still having problems re-installing wsus.
http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/799c2276-96de-4373-bebe-acb1b7b3c8c8
http://blogs.technet.com/b/sus/archive/2008/11/05/how-to-manually-remove-all-of-wsus.aspx
Please Help
Here is WSUSSetup.log 
2012-11-01 10:18:55 Error MWUSSetup ParseCommandLine: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.)
2012-11-01 10:19:41 Error MWUSSetup DoInstall: ParseCommandLine failed (Error 0x80041453)
2012-11-29 12:19:30 Success MWUSSetup Detected that setup was launched through Server Manager
2012-11-29 12:19:31 Success MWUSSetup Validating pre-requisites...
2012-11-29 12:19:31 Error MWUSSetup Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2012-11-29 12:19:31 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2012-11-29 12:19:34 Success MWUSSetup ReportViewer is not installed on this machine
2012-11-29 12:19:34 Success MWUSSetup ReportViewer is not installed on this machine
2012-11-29 12:20:24 Success MWUSSetup Initializing installation details
2012-11-29 12:20:24 Success MWUSSetup Skipping Asp.Net install since not running on win2k3...
2012-11-29 12:20:24 Success MWUSSetup Installing wYukon using ocsetup
2012-11-29 12:20:24 Success MWUSSetup Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
2012-11-29 12:20:56 Error MWUSSetup The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
2012-11-29 12:20:56 Error MWUSSetup ExecCmd failed (Error 0x80070643: Fatal error during installation.)
2012-11-29 12:20:56 Error MWUSSetup Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
2012-11-29 12:20:56 Error MWUSSetup CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
2012-11-29 12:20:56 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2012-11-29 12:21:02 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
2013-01-31 14:43:33 Success MWUSSetup Detected that setup was launched through Server Manager
2013-01-31 14:43:34 Success MWUSSetup Validating pre-requisites...
2013-01-31 14:43:34 Error MWUSSetup Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2013-01-31 14:43:34 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2013-01-31 14:43:36 Success MWUSSetup ReportViewer is not installed on this machine
2013-01-31 14:43:36 Success MWUSSetup ReportViewer is not installed on this machine
2013-01-31 14:44:32 Success MWUSSetup Initializing installation details
2013-01-31 14:44:32 Success MWUSSetup Skipping Asp.Net install since not running on win2k3...
2013-01-31 14:44:32 Success MWUSSetup Installing wYukon using ocsetup
2013-01-31 14:44:32 Success MWUSSetup Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
2013-01-31 14:45:01 Error MWUSSetup The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
2013-01-31 14:45:01 Error MWUSSetup ExecCmd failed (Error 0x80070643: Fatal error during installation.)
2013-01-31 14:45:01 Error MWUSSetup Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
2013-01-31 14:45:01 Error MWUSSetup CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
2013-01-31 14:45:01 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2013-01-31 14:46:06 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
2013-04-04 11:43:48 Success MWUSSetup Detected that setup was launched through Server Manager
2013-04-04 11:43:50 Success MWUSSetup Validating pre-requisites...
2013-04-04 11:43:50 Error MWUSSetup Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
2013-04-04 11:43:50 Error MWUSSetup WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
2013-04-04 11:43:52 Success MWUSSetup ReportViewer is not installed on this machine
2013-04-04 11:43:52 Success MWUSSetup ReportViewer is not installed on this machine
2013-04-04 11:44:40 Success MWUSSetup Initializing installation details
2013-04-04 11:44:40 Success MWUSSetup Skipping Asp.Net install since not running on win2k3...
2013-04-04 11:44:40 Success MWUSSetup Installing wYukon using ocsetup
2013-04-04 11:44:40 Success MWUSSetup Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
2013-04-04 11:45:05 Error MWUSSetup The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
2013-04-04 11:45:05 Error MWUSSetup ExecCmd failed (Error 0x80070643: Fatal error during installation.)
2013-04-04 11:45:05 Error MWUSSetup Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
2013-04-04 11:45:05 Error MWUSSetup CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
2013-04-04 11:45:05 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2013-04-04 11:46:11 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

Hi Jignesh, 
Can you please try to install pre-requisites for the WSUS, seems the following things need to be taken care. 
rtViewer is not installed on this machine
2012-11-29 12:19:34 Success MWUSSetup ReportViewer is not installed on this machine (Please install report viewer, before you install WSUS). 
Seems you're trying to use internal DB for database, thought is is failing, can you try to use SQL on point to remote SQL. 
Is this evaluation ver of 2008R2 ? 
Installed user is local admin on that server ? is UAC set to low ? 
Regards/Papi Reddy 
Papi Reddy -----------------------------------------------------

Similar Messages

  • Silverlight: 2 - WSUS - Windows Server 2008 Core

    2 Months ago I reported that Silverlight was being offered by WSUS for Server Core and on the 15th of this month I added a comment to the same thread to ensure that this would not be the case when Silverlight 2 KB 957938 gets pushed through WSUS.
    Surprise! (Or not :P) - Silverlight 2 is being offered by WSUS to Server 2008 Core.
    And what the following the statement in KB957938 means is anyone's guess:-
    Silverlight 2 contains an auto-updating mechanism. By default, this mechanism is disabled in the Windows Server Update Services (WSUS) package.
    Cheers,
    Stephen Edgar

    Thanks Andrew,
    I lay the blame directly with the WSUS team as it is more than just the Silverlight team, I see 'many' issues with WSUS be it Exchange Server, SQL, Visual Studio, Windows Live and many other updates that simply fail any form of QA process and are deployed to WSUS without proper testing. It typically is language specific, i.e. only 'English Updates' that can blow out from 60MB to 1.3GB and the fact that Silverlight is still being thrown to Server Core as an update is sad that the WSUS team have not worked out a solution for this, some may call this a bug, some may say it is a slight oversight, I say it is a lack of Quality Assurance Testing on Microsoft's part.
    With Silverlight 3 just announced at MIX09 the issue now will be when Silverlight 3 first gets published to WSUS if the products it applies to actually fixes this issue and does not report that it is needed for 'Server Core' then the previous Silverlight 2 updates will NOT be superseeded by this update for Server Core and Server Core will continue to report that it needs the Silverlight 2 updates until an update to WSUS is released that 'supersedes' the Silverlight 2 update requirements for Server Core.
    So the WSUS team need to release a hotfix for the WSUS, Server Core and Silverlight issue in advance to even thinking about publishing Silverlight 3 to WSUS otherwise Server Core will continue wanting the SL2 updates OR it will report that Server Core needs the SL3 update.Cheers,
    Stephen Edgar

  • EPM 11.1.2.1 Installation problem on Laptop (Windows Server 2008 R2 x64)

    Dear All,
    I hope someone can help me here with EPM 11.1.2.1 installation problem on my notebook - Windows Server 2008 R2 x65, 8 GB RAM, running SQLServer 2008 Express.
    I installed Hyperion Foundation. The installation and configuration went through successfully.
    I am facing two problems:
    Problem 1
    When I try to access the workspace through the URL http://hostname:19000/workspace/index.jsp, I get error:
    Quote
    Failure of server APACHE bridge:
    No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.
    End-quote
    Problem 2
    Also, the service "Hyperion EPM Server" service not able to start. When I try to start, I get error message:
    Quote
    The Hyperion EPMA Server service on Local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
    End-quote
    I tried checking everything but can't seem to figure out what's going wrong.
    I have uploaded (1) EPM Config Manager screenshot (2) EPM System diagnostic report (3) EPM Registry editor output and (4) system services listing at
    http://www.mediafire.com/?pr9l1v99w4d9u4r,c3vggxeibqkxbo2,lyzclu2aggbn8qh,8kur9gxal5b361z
    It would be very grateful if someone can have a look and help me.
    Many thanks in advance for any help / pointers / suggestions.
    - Neil

    Hi Pablo,
    Thanks to your suggestion for database, problem #2 seem to be resolved. I am now able to start EPMA Service.
    Re: Problem 1
    a) Log for C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services\HyS9FoundationServices-sysout is as below
    -----<start>--------
    <Feb 15, 2012 4:04:47 AM > <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Feb 15, 2012 4:04:47 AM > <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Feb 15, 2012 4:04:47 AM > <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.2-11-135406-1.6.0_20-20100624-2119-windows-x86_64 from Oracle Corporation>
    <Feb 15, 2012 4:04:48 AM > <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:
    ------<end>-----
    I am intrigued by the last line "Enter username to boot WebLogic server:" - is there anything wrong going here?
    Log for C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\logs\FoundationServices0 is as below:
    -----<start>--------
    ####<Feb 15, 2012 12:49:49 AM <Info> <WebLogicServer> <RCPL02> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1329324589459> <BEA-000000> <WebLogic Server "FoundationServices0" version:
    WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
    ####<Feb 15, 2012 12:49:49 AM <Notice> <Log Management> <RCPL02> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1329324589568> <BEA-170019> <The server log file C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\logs\FoundationServices0.log is opened. All server side log events will be written to this file.>
    ####<Feb 15, 2012 12:49:49 AM <Info> <Log Management> <RCPL02> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1329324589584> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Feb 15, 2012 12:49:49 AM <Info> <Diagnostics> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324589631> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "http" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "https" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594904> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594919> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Feb 15, 2012 12:49:54 AM <Info> <RJVM> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594950> <BEA-000570> <Network Configuration for Channel "FoundationServices0"
    Listen Address          :28080
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Feb 15, 2012 12:49:54 AM <Info> <RJVM> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594950> <BEA-000570> <Network Configuration for Channel "FoundationServices0"
    Listen Address          :28443 (SSL)
    Public Address          N/A
    Http Enabled          true
    Tunneling Enabled     false
    Outbound Enabled     false
    Admin Traffic Enabled     true>
    ####<Feb 15, 2012 12:49:54 AM <Info> <Server> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324594982> <BEA-002609> <Channel Service initialized.>
    ####<Feb 15, 2012 12:49:55 AM <Info> <Socket> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595013> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
    >
    ####<Feb 15, 2012 12:49:55 AM <Info> <Socket> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595075> <BEA-000436> <Allocating 4 reader threads.>
    ####<Feb 15, 2012 12:49:55 AM <Info> <Socket> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595075> <BEA-000446> <Native IO Enabled.>
    ####<Feb 15, 2012 12:49:55 AM <Info> <IIOP> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324595216> <BEA-002014> <IIOP subsystem enabled.>
    ####<Feb 15, 2012 12:49:59 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324599818> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
    ####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600286> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600442> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
    ####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600722> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\data\ldap\XACMLAuthorizermyrealmInit.initialized, will load full LDIFT.>
    ####<Feb 15, 2012 12:50:00 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324600738> <BEA-090074> <Initializing Authorizer provider using LDIF template file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\XACMLAuthorizerInit.ldift.>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601050> <BEA-090075> <The Authorizer provider has had its LDIF information loaded from: C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\XACMLAuthorizerInit.ldift>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601315> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\data\ldap\DefaultCredentialMappermyrealmInit.initialized, will load full LDIFT.>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601315> <BEA-090827> <LDIF template file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DefaultCredentialMapperInit.ldift was empty. The WebLogic provider CredentialMapper has been bootstrapped but has not been initialized with any LDIF data.>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601331> <BEA-000000> <BootStrapServiceImpl.loadLDIFTemplate - Did not find C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\data\ldap\XACMLRoleMappermyrealmInit.initialized, will load full LDIFT.>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601331> <BEA-090074> <Initializing RoleMapper provider using LDIF template file C:\Oracle\Middleware\user_projects\domains\EPMSystem\security\XACMLRoleMapperInit.ldift.>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601346> <BEA-090075> <The RoleMapper provider has had its LDIF information loaded from: C:\Oracle\Middleware\user_projects\domains\EPMSystem\security\XACMLRoleMapperInit.ldift>
    ####<Feb 15, 2012 12:50:01 AM <Info> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601565> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server FoundationServices0 for security realm myrealm.>
    ####<Feb 15, 2012 12:50:01 AM <Notice> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601565> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Feb 15, 2012 12:50:01 AM <Notice> <Security> <RCPL02> <FoundationServices0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1329324601658> <BEA-090083> <Storing boot identity in the file: C:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\FoundationServices0\security\boot.properties>
    ------<end>-----

  • 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

  • Problem with Windows Vista Server 2008 - Font characters replaced with square blocks on login screen

    Hi!  Last week, I set up a server for a client (Windows Vista Server 2008).  Everything was working fine until this week when I did a remote login, and the server's screen shows all blocks instead of character (ie. "Administrator" shows up as Rectangular blocks) - and when I type in the password box, my characters come out the same blocks. The computer lets me login like this but then when the desktop displays, all texts is Blocks - like the windows default font is missing. 
    Anybody else run into this mystery and is there a fix?
    Thanks.

    Hello,
    Based on my experience, this issue might be caused by compatibility issues of video card driver and language options settings.
    I’d like to suggest you try the following steps to fix the issue.
    1.    Please check whether you have installed correct video card drivers on both client and server machines. You’d better download the latest drivers from Video card manufacture and reinstall the drivers on both of the machines.
    2.    Please confirm whether the regional and language options settings on client and server machines are the same. If not, please temporarily change the settings on two machines to be the same and have another test.
    3.    If you use some third-party remote desktop connection tools to connect to the server, please have another try with Windows build-in remote desktop connection.
    I hope this helps, thanks.
    Regards,
    Neo Zhu

  • Problems importing MS SQL Server 2008 DDL

    I'm trying to import DDL into SQL Developer DM 4.0 from an MS SQL 2008 DDL dump.   It fails to recognise ANY of the statements in the (perfectly legitimate) SQL file.    I'm clearly doing something wrong, but I have no idea what!   Any help/guidance gratefully received.

    Hi David - thanks for responding.    There are no messages relating to the attempted import in the external log.    The version I'm using is 4.0.3.853.    Here are the first few lines of the "output" file:
    Oracle SQL Developer Data Modeler 4.0.3.853
    Oracle SQL Developer Data Modeler Import Log
    Date and Time: 2014-11-27 11:15:55 GMT
    Design Name: Untitled_1
    RDBMS : SQL Server 2008
      All Statements:   2004
      Imported Statements:  0
      Failed Statements:   0
      Not Recognized Statements:  2004
    <<<<< Not Recognized >>>>>
    ÿþU
    The odd characters in the last line seem to be a feature of importing SQL Server DDL files.   I've done all sorts of things to eliminate them, but they actually seem to be added in by the parser!
    Here are the first few lines of the actual DDL file:
    USE [master]
    GO
    /****** Object:  Database [MyDatabase]    Script Date: 10/29/2014 11:45:32 ******/
    CREATE DATABASE [MyDatabase] ON  PRIMARY
    ( NAME = N'MyDatabasedata', FILENAME = N'M:\Databases\MyDatabasesqldb01\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\MyDatabase.mdf' , SIZE = 20992512KB , MAXSIZE = UNLIMITED, FILEGROWTH = 512000KB )
    LOG ON
    ( NAME = N'MyDatabaselog1', FILENAME = N'M:\Logs\MyDatabasesqllogs01\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\MyDatabase.ldf' , SIZE = 10769408KB , MAXSIZE = UNLIMITED, FILEGROWTH = 512000KB )
    GO
    ALTER DATABASE [MyDatabase] SET COMPATIBILITY_LEVEL = 80
    GO
    IF (1 = FULLTEXTSERVICEPROPERTY('IsFullTextInstalled'))
    begin
    EXEC [MyDatabase].[dbo].[sp_fulltext_database] @action = 'disable'
    end
    GO
    ALTER DATABASE [MyDatabase] SET ANSI_NULL_DEFAULT OFF
    GO
    ALTER DATABASE [MyDatabase] SET ANSI_NULLS OFF
    GO
    ALTER DATABASE [MyDatabase] SET ANSI_PADDING OFF
    GO
    ALTER DATABASE [MyDatabase] SET ANSI_WARNINGS OFF
    GO
    ALTER DATABASE [MyDatabase] SET ARITHABORT OFF
    GO
    ALTER DATABASE [MyDatabase] SET AUTO_CLOSE OFF
    GO
    ALTER DATABASE [MyDatabase] SET AUTO_CREATE_STATISTICS ON
    GO
    ALTER DATABASE [MyDatabase] SET AUTO_SHRINK OFF
    GO
    I've change the database name.   Apart from that, this is the DDL I have.
    Any help, pointers, anything would be appreciated!

  • Facing problem when install sql server 2008 on windows7

    Hi I installed sqlserver 2008 on windows7 ultimate sp1 then i got one error like below
    MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{64CDE8F2-3791-46F5-BAD2-72FFF5252FAB}'. Error code: 1608..
    how to rectify this error please help me...
    Thanks in advance

    There are some blogs/msdn posts talking about the same issue  and below are the links
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/66a2044c-7251-466b-9b22-40d155ed949b/sql-server-2008-setup-fails-on-windows-7-enterprise-error-code-1608?forum=sqlgetstarted
    http://superuser.com/questions/414795/error-code-1608-during-sql-server-install
    http://gaurangpatel.net/solving-msigetproductinfo-failed-to-retrieve-productversion-for-package-with-product-code-8bdd006d-d5f0-4aaa-ba13-65995063ec44-error-code-1608
    Hope it Helps!!

  • Problems with Crystal reports server 2008 VI (Invalid logon information)

    I have added a report that connects to the SQL server and also I set up the required ODBC for the report on the server. I could run the report without any issues.
    When I add the same report to another folder in CMC or add a new report that uses the same connection, and try to run it, I get the following error.
    I did set location and verify database in Crystal designer many times and added the report into CMC, but still it gives me the error.
    However the first report that I added still works fine. For some reports it shows the parameter screen and when I enter them and click OK it gives the same error. I checked the logon information and they are correct. Reports work fine in Crystal designer. When I added the report, in the database configuration I selected "Use original database logon information from the report." and entered the SQL user id and password.
    error message:
    "The database logon information for this report is either incomplete or incorrect"
    I then went back to the database configuration and selected "Use custom database logon information specified here." and entered the ODBC connection info.
    With this when I run the report it takes a little longer and again asks me to enter the user id and password, even though I selected "Use same database logon as when report is run" option. Still when I enter the user id and password and click ok it keeps on prompting the same. I kept on entering it for 20 times, still it kept on prompting for the same. I am not sure how to make this work.
    The report that I am trying to run has an SQL command (that links with 10+ tables), views and some tables. It also got one dynamic parameter prompt.
    Also when I select the item from dropdown box "Table Prefix" and save and come back to the database configuration the option I selected is blank. It seems like CMC is not saving this. I found out that this sometimes happens with the password too.
    I have checked on SAP forum and could not find a solution for either of these problems yet.
    I do have created a web site with CR developer 2008 that runs the same report and it works there without any issues.
    Could any one help me with this?

    I assume that you have built your reports with the CR Designer 2008 V1. Try to open the affected report in the CR Designer and select Database->VErify database and save it back into the repository. Does it work?
    Regards,
    Stratos

  • 1 Server getting 8007000B error through WSUS (Windows Server 2008 x86)

    All servers/workstations are updating fine except for 1 server.
    A 2008 Windows Server 32 bit has 11 updates that it errors out on with 8007000B
    I've googled it and tried all solutions and none seem to work, I'm open to anything at this point.

    I don't see anything out of the ordinary (this is just an excerpt of the file)
    2014-01-14 13:11:07.058 UTC Info
    w3wp.8 AuthorizationManager.GetUpstreamServerUriHeader
    Found config says USS is MU site
    2014-01-14 13:32:36.570 UTC Warning
    WsusService.8 DBConnection.OnReceivingInfoMessage
    The join order has been enforced because a local join hint is used.
    2014-01-14 13:34:11.277 UTC Info
    w3wp.10 ThreadEntry
    PipelineRuntime.ProcessRequestNotification
    2014-01-14 13:34:11.277 UTC Warning
    w3wp.10 DBConnection.OnReceivingInfoMessage
    The join order has been enforced because a local join hint is used.
    2014-01-14 13:42:36.764 UTC Warning
    WsusService.8 DBConnection.OnReceivingInfoMessage
    The join order has been enforced because a local join hint is used.
    2014-01-14 18:18:23.464 UTC Warning
    w3wp.10 DBConnection.OnReceivingInfoMessage
    The join order has been enforced because a local join hint is used.
    2014-01-14 18:18:37.176 UTC Warning
    w3wp.10 DBConnection.OnReceivingInfoMessage
    The join order has been enforced because a local join hint is used.
    2014-01-14 18:18:37.566 UTC Warning
    w3wp.10 DBConnection.OnReceivingInfoMessage
    The join order has been enforced because a local join hint is used.
    2014-01-14 18:19:15.802 UTC Info
    WsusService.3 ThreadEntry
    _ThreadPoolWaitCallback.PerformWaitCallback
    2014-01-14 18:19:15.802 UTC Info
    WsusService.3 SusService.OnStop
    EventId=502,Type=Information,Category=WsusService,Message=Update Services Service Has Stopped
    2014-01-14 18:22:28.883 UTC Info
    WsusService.5 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:28.883 UTC Info
    WsusService.5 SusService.SusServiceStartUpThreadProc
    WSUS Server Version: 3.2.7600.251
    2014-01-14 18:22:28.977 UTC Info
    WsusService.5 SusService.CleanUpIntermediateFileDownload
    CleanupIntermediateFileDownload
    2014-01-14 18:22:29.694 UTC Info
    WsusService.5 SusService.SusServiceStartUpThreadProc
    EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started
    2014-01-14 18:22:29.819 UTC Info
    WsusService.7 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:29.819 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
    2014-01-14 18:22:29.835 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
    2014-01-14 18:22:29.835 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
    2014-01-14 18:22:29.835 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
    2014-01-14 18:22:29.835 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
    2014-01-14 18:22:29.835 UTC Info
    WsusService.11 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:29.835 UTC Info
    WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2014-01-14 18:22:29.835 UTC Info
    WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2014-01-14 18:22:29.850 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-01-14 18:22:29.850 UTC Info
    WsusService.12 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:29.850 UTC Info
    WsusService.12 CatalogSyncAgent.HandleCatalogSyncStateCorrection
    Handling systemStartup work...
    2014-01-14 18:22:29.850 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-01-14 18:22:29.850 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-01-14 18:22:29.850 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-01-14 18:22:29.850 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-01-14 18:22:29.850 UTC Info
    WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
    2014-01-14 18:22:29.866 UTC Info
    WsusService.15 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:29.866 UTC Info
    WsusService.15 ResetStateMachineAgent.WakeUpWorkerThreadProc
    State Machine Reset Agent Starting
    2014-01-14 18:22:29.866 UTC Info
    WsusService.12 CatalogSyncAgent.HandleCatalogSyncStateCorrection
    Finished systemStartup work.
    2014-01-14 18:22:29.866 UTC Info
    WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2014-01-14 18:22:29.882 UTC Info
    WsusService.12 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError
    ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2014-01-14 18:22:29.913 UTC Info
    WsusService.13 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:29.913 UTC Info
    WsusService.13 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 18:22:29.913 UTC Info
    WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2014-01-14 18:22:29.928 UTC Info
    WsusService.17 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:29.928 UTC Info
    WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc
    Email Notification Agent Starting
    2014-01-14 18:22:29.928 UTC Info
    WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-01-14 18:22:30.006 UTC Info
    WsusService.13 EventLogEventReporter.ReportEvent
    EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2014-01-14 18:22:30.006 UTC Info
    WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc
    Email Notification Agent Finished
    2014-01-14 18:22:30.100 UTC Info
    WsusService.15 ResetStateMachineAgent.WakeUpWorkerThreadProc
    State Machine Reset Agent Finished
    2014-01-14 18:22:30.147 UTC Info
    WsusService.13 ContentSyncAgent.WakeUpWorkerThreadProc
    ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2014-01-14 18:22:30.318 UTC Info
    WsusService.13 ContentSyncAgent.WakeUpWorkerThreadProc
    ContentSyncAgent found no more Jobs, thread exitting
    2014-01-14 18:22:30.318 UTC Info
    WsusService.13 EventLogEventReporter.ReportEvent
    EventId=363,Type=Information,Category=Synchronization,Message=Content synchronization succeeded.
    2014-01-14 18:22:30.443 UTC Info
    WsusService.13 ContentSyncAgent.WakeUpWorkerThreadProc
    ServerHealth: Updating Server Health for Component: ContentSyncAgent, Marking as Not Running
    2014-01-14 18:22:33.033 UTC Info
    WsusService.8 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 18:22:33.033 UTC Info
    WsusService.8 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 19:42:40.007 UTC Info
    WsusService.5 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:40.038 UTC Info
    WsusService.5 SusService.SusServiceStartUpThreadProc
    WSUS Server Version: 3.2.7600.251
    2014-01-14 19:42:41.021 UTC Info
    WsusService.5 SusService.CleanUpIntermediateFileDownload
    CleanupIntermediateFileDownload
    2014-01-14 19:42:48.810 UTC Info
    WsusService.7 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.810 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
    2014-01-14 19:42:48.810 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
    2014-01-14 19:42:48.810 UTC Info
    WsusService.9 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.810 UTC Info
    WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2014-01-14 19:42:48.826 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
    2014-01-14 19:42:48.826 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
    2014-01-14 19:42:48.826 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
    2014-01-14 19:42:48.857 UTC Info
    WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2014-01-14 19:42:48.873 UTC Info
    WsusService.10 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.873 UTC Info
    WsusService.10 CatalogSyncAgent.HandleCatalogSyncStateCorrection
    Handling systemStartup work...
    2014-01-14 19:42:48.873 UTC Info
    WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
    2014-01-14 19:42:48.873 UTC Info
    WsusService.13 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.873 UTC Info
    WsusService.13 ResetStateMachineAgent.WakeUpWorkerThreadProc
    State Machine Reset Agent Starting
    2014-01-14 19:42:48.873 UTC Info
    WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2014-01-14 19:42:48.873 UTC Info
    WsusService.12 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.873 UTC Info
    WsusService.12 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 19:42:48.888 UTC Info
    WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2014-01-14 19:42:48.888 UTC Info
    WsusService.15 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.888 UTC Info
    WsusService.15 EmailNotificationAgent.WakeUpWorkerThreadProc
    Email Notification Agent Starting
    2014-01-14 19:42:48.888 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-01-14 19:42:48.888 UTC Info
    WsusService.16 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:42:48.888 UTC Info
    WsusService.16 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-01-14 19:42:48.904 UTC Info
    WsusService.10 CatalogSyncAgent.HandleCatalogSyncStateCorrection
    Finished systemStartup work.
    2014-01-14 19:42:48.920 UTC Info
    WsusService.10 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError
    ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2014-01-14 19:42:48.935 UTC Info
    WsusService.13 ResetStateMachineAgent.WakeUpWorkerThreadProc
    State Machine Reset Agent Finished
    2014-01-14 19:42:48.935 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-01-14 19:42:48.951 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-01-14 19:42:48.951 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-01-14 19:42:48.951 UTC Info
    WsusService.7 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-01-14 19:42:49.076 UTC Info
    WsusService.5 SusService.SusServiceStartUpThreadProc
    EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started
    2014-01-14 19:42:49.091 UTC Info
    WsusService.12 EventLogEventReporter.ReportEvent
    EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2014-01-14 19:42:49.138 UTC Info
    WsusService.15 EmailNotificationAgent.WakeUpWorkerThreadProc
    Email Notification Agent Finished
    2014-01-14 19:42:53.680 UTC Info
    WsusService.12 ContentSyncAgent.WakeUpWorkerThreadProc
    ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2014-01-14 19:42:54.008 UTC Info
    WsusService.12 ContentSyncAgent.WakeUpWorkerThreadProc
    ContentSyncAgent found no more Jobs, thread exitting
    2014-01-14 19:42:54.008 UTC Info
    WsusService.12 EventLogEventReporter.ReportEvent
    EventId=363,Type=Information,Category=Synchronization,Message=Content synchronization succeeded.
    2014-01-14 19:42:54.024 UTC Info
    WsusService.12 ContentSyncAgent.WakeUpWorkerThreadProc
    ServerHealth: Updating Server Health for Component: ContentSyncAgent, Marking as Not Running
    2014-01-14 19:42:58.316 UTC Info
    w3wp.6 ThreadEntry
    PipelineRuntime.ProcessRequestNotification
    2014-01-14 19:42:58.332 UTC Info
    w3wp.6 WebService..cctor
    Initializing Reporting WebService ProcessID = 5184, Process Start Time = 1/14/2014 2:42:50 PM, Product Version = 3.2.7600.251
    2014-01-14 19:43:01.875 UTC Info
    w3wp.6 ThreadEntry
    PipelineRuntime.ProcessRequestNotification
    2014-01-14 19:43:01.875 UTC Info
    w3wp.6 ApiRemoting..cctor
    Initializing ApiRemoting WebServiceProcessID = 5184, Process Start Time = 1/14/2014 2:42:50 PM, Product Version = 3.2.7600.251
    2014-01-14 19:43:03.405 UTC Info
    WsusService.8 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:03.405 UTC Info
    WsusService.8 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 19:43:04.326 UTC Info
    w3wp.6 ThreadEntry
    PipelineRuntime.ProcessRequestNotification
    2014-01-14 19:43:04.326 UTC Info
    w3wp.6 ServerImplementation..ctor
    Initializing ServerSyncWebService ProcessID = 5184, Process Start Time = 1/14/2014 2:42:50 PM, Product Version = 3.2.7600.251
    2014-01-14 19:43:04.498 UTC Info
    w3wp.6 RevisionIdCache.UpdateCategoryAndRevisionIdCache
    Fetching the category and revision id change for cache from database
    2014-01-14 19:43:15.752 UTC Info
    w3wp.6 RevisionIdCache.UpdateCategoryCache
    Refreshing the category cache
    2014-01-14 19:43:15.752 UTC Info
    w3wp.6 RevisionIdCache.UpdateRevisionCache
    Refreshing the revision cache
    2014-01-14 19:43:16.142 UTC Info
    w3wp.6 DependencyCache.RefreshThreadStart
    read 80343 UpdateIDs from DB in 250 ms
    2014-01-14 19:43:16.158 UTC Info
    w3wp.6 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: DeploymentChange
    2014-01-14 19:43:16.204 UTC Info
    w3wp.9 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:16.204 UTC Info
    w3wp.9 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-01-14 19:43:16.251 UTC Info
    w3wp.6 AuthorizationManager.GetUpstreamServerUriHeader
    Found config says USS is MU site
    2014-01-14 19:43:16.267 UTC Info
    w3wp.9 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-01-14 19:43:16.267 UTC Info
    w3wp.9 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-01-14 19:43:16.267 UTC Info
    w3wp.11 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:16.267 UTC Info
    w3wp.11 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: DeploymentChange
    2014-01-14 19:43:16.267 UTC Info
    w3wp.9 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-01-14 19:43:16.267 UTC Info
    w3wp.11 DeploymentChangeNotification.InternalEventHandler
    deployment change event received
    2014-01-14 19:43:16.267 UTC Info
    w3wp.9 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-01-14 19:43:16.470 UTC Info
    w3wp.6 CabUtilities.CheckCertificateSignature
    File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402
    2014-01-14 19:43:16.470 UTC Info
    w3wp.6 WsusTestKeys.AreTestKeysAllowed
    Server test key check: test keys are NOT allowed
    2014-01-14 19:43:16.470 UTC Info
    w3wp.6 CabUtilities.CheckCertificateSignature
    File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402
    2014-01-14 19:43:16.470 UTC Info
    w3wp.6 WsusTestKeys.AreTestKeysAllowed
    Server test key check: test keys are NOT allowed
    2014-01-14 19:43:16.485 UTC Info
    w3wp.14 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:16.485 UTC Info
    w3wp.14 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: DeploymentChange
    2014-01-14 19:43:16.485 UTC Info
    w3wp.14 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 19:43:16.485 UTC Info
    w3wp.14 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: LanguageChange
    2014-01-14 19:43:16.485 UTC Info
    w3wp.14 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: FileLocationChange
    2014-01-14 19:43:16.485 UTC Info
    w3wp.14 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: HardwareIDChange
    2014-01-14 19:43:18.561 UTC Info
    w3wp.6 ThreadEntry
    PipelineRuntime.ProcessRequestNotification
    2014-01-14 19:43:18.561 UTC Info
    w3wp.6 SimpleAuth..ctor
    Initializing SimpleAuth WebService ProcessID = 5184, Process Start Time = 1/14/2014 2:42:50 PM, Product Version = 3.2.7600.251
    2014-01-14 19:43:18.608 UTC Info
    w3wp.6 AuthorizationManager.GetUpstreamServerUriHeader
    Found config says USS is MU site
    2014-01-14 19:43:18.733 UTC Info
    w3wp.15 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:18.733 UTC Info
    w3wp.15 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 19:43:18.764 UTC Info
    w3wp.15 AuthorizationManager.GetUpstreamServerUriHeader
    Found config says USS is MU site
    2014-01-14 19:43:18.764 UTC Info
    w3wp.16 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:18.764 UTC Info
    w3wp.16 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2014-01-14 19:43:18.780 UTC Info
    w3wp.17 ThreadEntry
    ThreadHelper.ThreadStart
    2014-01-14 19:43:18.780 UTC Info
    w3wp.17 SusEventDispatcher.DispatchManagerWorkerThreadProc
    DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2014-01-14 19:43:18.780 UTC Info
    w3wp.15 SusEventDispatcher.RegisterEventHandler
    RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2014-01-14 19:43:18.780 UTC Info
    w3wp.16 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2014-01-14 19:43:18.780 UTC Info
    w3wp.16 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2014-01-14 19:43:18.780 UTC Info
    w3wp.16 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2014-01-14 19:43:18.796 UTC Info
    w3wp.16 SusEventDispatcher.TriggerEvent
    TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2014-01-14 19:43:18.796 UTC Info
    w3wp.15 AuthorizationManager.GetUpstreamServerUriHeader
    Found config says USS is MU site
    2014-01-14 19:43:19.295 UTC Info
    w3wp.6 ThreadEntry
    PipelineRuntime.ProcessRequestNotification
    2014-01-14 19:43:19.295 UTC Info
    w3wp.6 DssAuthWebServiceImplementation..ctor
    Initializing DssAuthWebService ProcessID = 5184, Process Start Time = 1/14/2014 2:42:50 PM, Product Version = 3.2.7600.251

  • INNER JOIN PROBLEM IN Microsoft SQL Server 2008 R2 Report Builder 3.0

    SELECT
    ,maximo_tbl_matrectrans.ponum
    ,maximo_tbl_po.description AS [maximo_tbl_po description]
    ,maximo_tbl_matrectrans.polinenum
    ,maximo_tbl_matrectrans.itemnum
    ,maximo_tbl_item.description AS [maximo_tbl_item description]
    FROM
    maximo_tbl_matrectran
    INNER JOIN maximo_tbl_po
    ON maximo_tbl_matrectrans.ponum = maximo_tbl_po.ponum
    INNER JOIN maximo_tbl_item
    ON maximo_tbl_matrectrans.itemnum = maximo_tbl_item.itemnum
    can you advise below picture in itemnum in show one value more time
    ponum polinenum maximo_tbl_a_po_description itemnum maximo_tbl_a_item_description
    D33-1021425 5 ASL REORDER HAZMAT 91G8110000071 DRUM, PLASTIC
    D33-1021425 5 ASL REORDER HAZMAT 91G8110000071 DRUM, PLASTIC
    D33-1020817 2 ASL REPLENISHMENT, D 91G6685000371 THERMOSTAT
    D33-1020817 2 ASL REPLENISHMENT, D 91G6685000371 THERMOSTAT
    D33-1020817 2 ASL REPLENISHMENT, D 91G6685000371 THERMOSTAT
    D33-1021365 2 ASL - D33DFAC STOCK 91G3920000081 CART, BIG WHEEL
    D33-1021365 2 ASL - D33DFAC STOCK 91G3920000081 CART, BIG WHEEL
    D33-1021425 5 ASL REORDER HAZMAT 91G8110000071 DRUM, PLASTIC
    D33-1020817 1 ASL REPLENISHMENT, D 91G5330002011 SEAL, THERMOSTAT
    D33-1022346 2 ASL STOCK REORDER E 92G6145000998 CABLE, POWER,
    D33-1022346 2 ASL STOCK REORDER E 92G6145000998 CABLE, POWER,
    D33-1020817 1 ASL REPLENISHMENT, D 91G5330002011 SEAL, THERMOSTAT
    D33-1020817 1 ASL REPLENISHMENT, D 91G5330002011 SEAL, THERMOSTAT
    D33-1022346 2 ASL STOCK REORDER E 92G6145000998 CABLE, POWER,
    but original we need..
    ponum polinenum maximo_tbl_a_po_description itemnum maximo_tbl_a_item_description
    D33-1021425 5 ASL REORDER HAZMAT 91G8110000071 DRUM, PLASTIC
    D33-1020817 2 ASL REPLENISHMENT, D 91G6685000371 THERMOSTAT
    D33-1021365 2 ASL - D33DFAC STOCK 91G3920000081 CART, BIG WHEEL
    D33-1020817 1 ASL REPLENISHMENT, D 91G5330002011 SEAL, THERMOSTAT
    D33-1022346 2 ASL STOCK REORDER E 92G6145000998 CABLE, POWER,

    Try below:
    SELECT DISTINCT
    maximo_tbl_matrectrans.ponum
    ,maximo_tbl_po.description AS [maximo_tbl_po description]
    ,maximo_tbl_matrectrans.polinenum
    ,maximo_tbl_matrectrans.itemnum
    ,maximo_tbl_item.description AS [maximo_tbl_item description]
    FROM
    maximo_tbl_matrectran
    INNER JOIN maximo_tbl_po
    ON maximo_tbl_matrectrans.ponum = maximo_tbl_po.ponum
    INNER JOIN maximo_tbl_item
    ON maximo_tbl_matrectrans.itemnum = maximo_tbl_item.itemnum
    -Vaibhav Chaudhari

  • Server 2008 R2 with WSUS need to specify location for Feature install for Server 2012 and Windows 8

    Having a problem where we need to add .net 3.5, amongst other things, in server 2012 and windows 8.1.  We're using WSUS on server 2008 R2, so when I go to add roles or features, I'm not able to as it tries to use Windows Update but it's set to use WSUS.
    I'm aware in server 2012 gpo's that you enable the policy 'specify settings for optional component installation and component repair' in Administrative Templates>System, however that setting is not available in Server 2008 R2.
    I've downloaded the templates from http://www.microsoft.com/en-us/download/details.aspx?id=36991 but the setting is still not there.
    Any suggestions on how to do this/allow feature install with Server 2008 R2?

    Hi,
    To upgrade the Administrative Templates, please run the downloaded msi file, then copy the needed admx files and adml files to the PolicyDefinitions folder.
    For detailed information, please refer to the link below,
    Managing Group Policy ADMX Files Step-by-Step Guide
    http://technet.microsoft.com/en-us/library/cc709647(v=WS.10).aspx
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • HELP ME!!! I have a problem regarding SQL Server 2008 R2 Replication! :((((

    Good day!
    I'm having a big problem in my SQL Server 2008 R2... I can't see the "Local Publication" under the Replication...
    About not installing it, I guess that's not true because I checked all the features to install.
    Is this a bug? Do I need to re-install my SQL Server 2008 R2? Or simply, do I need to do something simple without re-installing it?
    PLEASE HELP....
    See Link below:
    http://oi59.tinypic.com/4jx3y1.jpg

    None. This is a freshly installed SQL Server 2008 R2. After installing, All I did was create a database.
    If you want to know how I did it, simply:
    1. Open SSMS, connect to local server
    2. Open Object Explorer
    3. Expand your local server
    4. Right+Click on the Database then clicked on to "New Database..."
    5. Entered my database name then clicked "OK"

  • Windows Server 2008 R2 - Won't load certain web pages - Happens in all browers - Won't do windows updates

    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.

  • Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

    Hi!
    The setup process fails with this error:
      Configuration error code:     
    0x1C2074D8@1216@1
      Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'.  Error: Value does not fall within the expected range.
    I have found some hints by google, but nothing really helpfull.
    Has anyone had a simular problem when installing SQL server 2008 R2?
    All posts I found are about sql server 2008 (no R2!).
    The cluster itself is working (storage, network, msdtc, quorum...).
    Any hints?
    Andreas
    Here is the complete log:
    Overall summary:
      Final result:                  Failed: see details below
      Exit code (Decimal):           -2067791871
      Exit facility code:            1216
      Exit error code:               1
      Exit message:                  Failed: see details below
      Start time:                    2012-04-06 11:23:57
      End time:                      2012-04-06 12:01:21
      Requested action:              InstallFailoverCluster
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
    Cluster properties:
      Machine name: OC-SQLCL02ND01
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Machine name: OC-SQLCL02ND02
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
    Machine Properties:
      Machine name:                  OC-SQLCL02ND01
      Machine processor count:       32
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  Yes
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         G:\x64\setup\
      Installation edition:          STANDARD
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        InstallFailoverCluster
      AGTDOMAINGROUP:                <empty>
      AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
      AGTSVCPASSWORD:                *****
      ASBACKUPDIR:                   S:\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   S:\OLAP\Config
      ASDATADIR:                     S:\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      S:\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  MANAGEMENT\sqladmin
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
      ASTEMPDIR:                     S:\OLAP\Temp
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
      CUSOURCE:                     
      ENU:                           True
      ERRORREPORTING:                False
      FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
      FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
      FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
      FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             S:\
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      PASSPHRASE:                    *****
      PCUSOURCE:                     d:\install\mssql\sp1
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  MANAGEMENT\sqladmin
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  SQL
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLDOMAINGROUP:                <empty>
      SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
      SQLSVCPASSWORD:                *****
      SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
      SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
      SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
      SQMREPORTING:                  False
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:     
    0x1C2074D8@1216@1
      Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'.  Error: Value does not fall within the expected range.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:     
    0x1C2074D8@1216@1
      Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'.  Error: Value does not fall within the expected range.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Failed: see details below
      Configuration error code:     
    0x1C2074D8@1216@1
      Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'.  Error: Value does not fall within the expected range.
      Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
      Feature:                       Analysis Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Integration Services
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Passed
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

    Hi Andreas Plachy,
    Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
    SQL Server, and try again.
    Stephanie Lv
    TechNet Community Support

  • Installation issue : sql server 2008 r2 some services failed to installed on windows 7

    I have been facing this problem while installing sql server 2008 r2.. i tried so many times but same result .. it shows sql server installed with some errors
    database engine service : failed
    SQL Server Replication : failed
    Full-Text Search : failed
    Analysis Services : failed
    Reporting Services : failed
    And my Log file (or) summary file is (it is in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log):
    Overall summary:
      Final result:                  User cancelled
      Exit code (Decimal):           -2068380094
      Exit facility code:            1207
      Exit error code:               1602
      Exit message:                  User has cancelled.
      Start time:                    2014-08-14 21:15:26
      End time:                      2014-08-14 21:23:58
      Requested action:              AddNode
    Machine Properties:
      Machine name:                  MANJU-PC
      Machine processor count:       4
      OS version:                    Windows Vista
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Developer Edition   
    10.0.1600.22    No        
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No      
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Developer Edition    10.0.1600.22    No        
      Sql Server 2008                                                         
    Integration Services                     1033                 Developer Edition   
    10.0.1600.22    No        
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\x86\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        AddNode
      AGTSVCACCOUNT:                 <empty>
      AGTSVCPASSWORD:                *****
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      CONFIGURATIONFILE:             
      FAILOVERCLUSTERGROUP:          
      FAILOVERCLUSTERNETWORKNAME:    <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTANCENAME:                  <empty>
      MEDIASOURCE:                   D:\Softwares\JAVA & .NET SW\SQL Server 2008\SQL Server 2008\
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      SQLSVCACCOUNT:                 <empty>
      SQLSVCPASSWORD:                *****
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\ConfigurationFile.ini
    Detailed results:
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140814_210558\SystemConfigurationCheck_Report.htm
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
        Message:
            User has cancelled.
        Stack:
            at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
            at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
            at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

      Requested action:              AddNode
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                                      10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Developer Edition   
    10.0.1600.22    No        
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Developer Edition    10.0.1600.22   
    No        
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Developer Edition    10.0.1600.22    No      
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Developer Edition    10.0.1600.22    No        
      Sql Server 2008                                                         
    Integration Services                     1033                 Developer Edition   
    10.0.1600.22    No        
    Instead of installing SQL server instance you selected add node which is to be selected when SQL server installation is to be made on Node which is being added to cluster. Since your OS is not clustered I am sure you selected worng option.
    Please right click on setup file and select run as administrator. Now installation window which pops up on that on left hand side select
    installation and then on page that appears select 'New server standalone installation or add feature to existing installation'.
    You already have SQL server 2008 installed on your machine as per feature discovery report
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

Maybe you are looking for