Compare Server Names in Excel sheet from column1 with column 2 and exact matched server names should be saved in column 3 in same Excel sheet

Hi Guys,
First of all thanks in advance any help much appriciated.
I am new in scripting and excel, i am looking for below solution as my job requires daily work of this kind and i came to know by automating this work lots of time can be saved.
Compare Server Names in Excel sheet from column1  with column 2 and exact matched server names should be saved in column 3 in same Excel sheet.
Looking solutions first using excel i.e.vlookup itself so that it will not require any approval in my job else using powersell ,vbscript.
Once again Thanks for you guys.
/Regards
Nitesh24in

Hi Edward,
Thanks once again
I have only changed excel file path and after that this is saved as below , i am not sure which three lines should be together in one line. Please advise.
$excel = New-Object -ComObject Excel.Application
$Workbook = $excel.Workbooks.Add("F:\NewDocsToReadNitesh26-May2013\Excel\test.xls")
$WorkSheet = $Workbook.Worksheets.Item(1)
$WorkSheet.Activate() | Out-Null
For ($i=1;$i -le $worksheet.UsedRange.Rows.Count;$i++) {
   If ($worksheet.cells.item($i,1).value2 -eq $worksheet.cells.item($i,2).value2) {
      $worksheet.cells.item($i,3).value2 = $worksheet.cells.item($i,1).value2
}$Workbook.Save()$excel.Quit()[System.Runtime.InteropServices.Marshal]::ReleaseComObject([System.__ComObject]$excel) | Out-Null
Thanks and Regards
Nitesh24in

Similar Messages

  • There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site "Mailserver"

    Good day Guys
    First of all I am not an Exchange Expert, and I might be asking a very stupid question, but please bare with me. :) 
    While I was on leave our Mail server fell over and The company got a Specialist to help out for the time being.
    We where\are on Microsoft Exchange 2007 , which Fell over, and the specialist was able to recover as much data as he could.
    They then installed Exchange 2013 and tried to migrate everything from 2007 to 2013 and not everything migrated over.
    But the problem is, Outlook Anywhere was enable on 2007 and worked a 100% (before the disaster)
    With Exchange 2013 I get the following error message when trying to connect With Outlook 2013, using an external connection:
    "There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site "Mailserver"
    Outlook is unable to connect to the Proxy server. (Error Code 0)"
    Has anyone had the Similar when migrating over from 2007 to 2013 or is this an Issue on IIS and nothing to do with Exchange migration?
    Your assistance will be greatly appreciated.

    Hi,
    Firstly, I would suggest we use Exchange 2013 FE as the Outlook Anywhere proxy server.
    For the certificate issue, it mostly occurs because the host name that Outlook are trying to access does not match the certificate SAN. Please check with this point. If they do not match, you
    can change the host name by referring to the following article:
    https://support.microsoft.com/kb/940726/en-us?wa=wsignin1.0
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

    I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of.  I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
    clients get prompted for a security warning.  I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine.  My Outlook 2013 client doesn't prompt me with the message but I have other users who are
    still getting the "The name of the security certificate is invalid or does not match the name of the site" error.  The domain on the cert error show up as server.mydomain.local.  I've gone through all the virtual directories and pointed
    all of my internal and external URL's to https://mail.mydomain.com.   This made one of the two warnings go away but not the second.  I've dug around on google and gone through everything I could find here and as far as I can tell my internal
    and external url's are configured properly and I can't figure out where this error is originating from.  Any ideas on where I should look outside of the virtual directories? 
    I'm including a good link I found that contains all of the virtual directories I updated.  I've checked them through both CLI and GUI and everything looks good.
    http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
    http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

    Hi,
    When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
    Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
    Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
    Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
    Regards,
    Winnie Liang
    TechNet Community Support

  • The name of the security certificate is invalid or does not match the name of the site error?

    I am looking for some help folks. We are in a Outlook 2007/Exchange2010/Windows2008R2 environment.
    When users open Outlook off the network, and occasionally on the network, they get the error
    The name of the security certificate is invalid or does not match the name of the site error
    The CAS hostname is HRECAS.XXX.ORG. The URL that is listed on the SSL certificate (issued by VeriSign) is WEB.XXX.ORG. WEB.XXX.ORG is what users use to get to OWA and such.
    When I use testexchangeconnectivity.com, under certificate name validation I see an error that reads:
    Host name autodiscover.xxx.org doesn't match any name found on the server certificate CN=web.xxx.org.
    Does this mean somehow we have to add autodiscover.xxx.org on the certificate?
    I tried to add AutoDiscoverExternalUri using
    http://support.microsoft.com/?kbid=940726 &
    http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/2d0c0f5f-e4ec-4f33-a37d-b94fd7a2319f on the CAS server.
    Set-ClientAccessServer -identity HRECAS -AutodiscoverServiceExternalUri
     https://autodiscover.xxx.org/Autodiscover/Autodiscover.xml 
    I get an error that says
    "a positional parameter cannot be found that accepts argument '-AutoDiscoverExternalUri'.
    Can someone point to me what I am doing wrong with the command and whether I should be concerning myself with adding that line? By the way the
    InternalUrl information is already configured on the system. Also should I edit the certificate to add autodiscover.xxx.org?
    Thank in advance for your support.
    TD
    TD

    Hi Tapera,
    Thanks for the question.
    SRV record is a good idea. You can set the SRV to
    https://web.abc.com/autodiscover/autodiscover.xml but you must make sure the
    url can be resolved from External clients.
    In addition, there is still a issue. It is hard coded that Outlook will find the autodiscover by the orders below:
    1. Access autodiscover via SCP in AD.
    https://web.abc.com/autodiscover/autodiscover.xml
    2. If SCP access fails, it will try:
    https://abc.com/autodiscover/autodiscover.xml
    3. Then
    https://autodiscover.abc.com/autodiscover/autodiscover.xml
    4. Local XML file
    5. SRV record
    As you can see, Outlook will try SRV record at last. Therefore, it will still try to access
    https://autodiscover.abc.com/autodiscover/autodiscover.xml each time you run Outlook. Then the certificate warning will still persists.
    I have a workaround solution. You can do a local policy to disable the autodiscover to access the
    https://autodiscover.abc.ocom/autodiscover/autodiscover.xml by:
    1.   
    On the Outlook client machine, open regedit and add the following key:
    HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Autodiscover
             "ExcludeHttpsAutodiscoverDomain"
             "ExcludeHttpsRootDomain"
    2.   
    Then set the value to “1” on the above two keys.
    Thanks,
    Simon  

  • Outlook Security Alert - "the name on the security certificate is invalid or does not match the name of the site"

    Due to our company changing names, we recently moved to a new domain. All users were at first getting a certificate error when opening Outlook "the name on the security certificate is invalid or does not match the name of the site." After our network
    admin made some changes, nobody receives this error anymore except one user. The URL at the top of the security alert is the old domain, mail.olddomain.com. I checked the users Exchange Proxy Settings in Outlook, everything is showing the URL's of the new
    domain so I'm not sure where this is coming from. I'm assuming it has to be something on her local machine since she is the only one who still gets the error.
    Thanks in advance for any help.
    Exchange server 2008
    Outlook 2010

    Hi,
    Please follow all above suggestions to confirm whether the issue happens in OWA. And run Test E-mail AutoConfiguration in Outlook to check whether there is any URL settings using the old domain.
    If the issue doesn’t happen in OWA and your URL configurations are all same as others and set correctly, please create a new Outlook profile to have a try.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Ask the Expert: Cisco UCS Troubleshooting Boot from SAN with FC and iSCSI

    Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about Cisco UCS Troubleshooting Boot from SAN with FC and iSCSI with Vishal Mehta and Manuel Velasco.
    The current industry trend is to use SAN (FC/FCoE/iSCSI) for booting operating systems instead of using local storage.
    Boot from SAN offers many benefits, including:
    Server without local storage can run cooler and use the extra space for other components.
    Redeployment of servers caused by hardware failures becomes easier with boot from SAN servers.
    SAN storage allows the administrator to use storage more efficiently.
    Boot from SAN offers reliability because the user can access the boot disk through multiple paths, which protects the disk from being a single point of failure.
    Cisco UCS takes away much of the complexity with its service profiles and associated boot policies to make boot from SAN deployment an easy task.
    Vishal Mehta is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past three years with a primary focus on data center technologies such as Cisco Nexus 5000, Cisco UCS, Cisco Nexus 1000v, and virtualization. He has presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE certification (number 37139) in routing and switching and service provider.
    Manuel Velasco is a customer support engineer for Cisco’s Data Center Server Virtualization TAC team based in San Jose, California. He has been working in the TAC for the past three years with a primary focus on data center technologies such as Cisco UCS, Cisco Nexus 1000v, and virtualization. Manuel holds a master’s degree in electrical engineering from California Polytechnic State University (Cal Poly) and VMware VCP and CCNA certifications.
    Remember to use the rating system to let Vishal and Manuel know if you have received an adequate response. 
    Because of the volume expected during this event, our experts might not be able to answer every question. Remember that you can continue the conversation in the Data Center community, under subcommunity Unified Computing, shortly after the event. This event lasts through April 25, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hello Evan
    Thank you for asking this question. Most common TAC cases that we have seen on Boot-from-SAN failures are due to misconfiguration.
    So our methodology is to verify configuration and troubleshoot from server to storage switches to storage array.
    Before diving into troubleshooting, make sure there is clear understanding of this topology. This is very vital with any troubleshooting scenario. Know what devices you have and how they are connected, how many paths are connected, Switch/NPV mode and so on.
    Always try to troubleshoot one path at a time and verify that the setup is in complaint with the SW/HW interop matrix tested by Cisco.
    Step 1: Check at server
    a. make sure to have uniform firmware version across all components of UCS
    b. Verify if VSAN is created and FC uplinks are configured correctly. VSANs/FCoE-vlan should be unique per fabric
    c. Verify at service profile level for configuration of vHBAs - vHBA per Fabric should have unique VSAN number
    Note down the WWPN of your vhba. This will be needed in step 2 for zoning on the SAN switch and step 3 for LUN masking on the storage array.
    d. verify if Boot Policy of the service profile is configured to Boot From SAN - the Boot Order and its parameters such as Lun ID and WWN are extremely important
    e. finally at UCS CLI - verify the flogi of vHBAs (for NPV mode, command is (from nxos) – show npv flogi-table)
    Step 2: Check at Storage Switch
    a. Verify the mode (by default UCS is in FC end-host mode, so storage switch has to be in NPIV mode; unless UCS is in FC Switch mode)
    b. Verify the switch port connecting to UCS is UP as an F-Port and is configured for correct VSAN
    c. Check if both the initiator (Server) and the target (Storage) are logged into the fabric switch (command for MDS/N5k - show flogi database vsan X)
    d. Once confirmed that initiator and target devices are logged into the fabric, query the name server to see if they have registered themselves correctly. (command - show fcns database vsan X)
    e. Most important configuration to check on Storage Switch is the zoning
    Zoning is basically access control for our initiator to  targets. Most common design is to configure one zone per initiator and target.
    Zoning will require you to configure a zone, put that zone into your current zonset, then ACTIVATE it. (command - show zoneset active vsan X)
    Step 3: Check at Storage Array
    When the Storage array logs into the SAN fabric, it queries the name server to see which devices it can communicate.
    LUN masking is crucial step on Storage Array which gives particular host (server) access to specific LUN
    Assuming that both the storage and initiator have FLOGI’d into the fabric and the zoning is correct (as per Step 1 & 2)
    Following needs to be verified at Storage Array level
    a. Are the wwpn of the initiators (vhba of the hosts) visible on the storage array?
    b. If above is yes then Is LUN Masking applied?
    c. What LUN number is presented to the host - this is the number that we see in Lun ID on the 'Boot Order' of Step 1
    Below document has details and troubleshooting outputs:
    http://www.cisco.com/c/en/us/support/docs/servers-unified-computing/ucs-b-series-blade-servers/115764-ucs-san-tshoot-00.html
    Hope this answers your question.
    Thanks,
    Vishal 

  • Exchange 2010 - The name on the security certificate is invalid or does not match the name of the site

    Scenario - Two Domains in different forests in production
    Domain ABC.com - Contains Exchange Server 2010 + Windows 2008 R2 AD Domain controllers
    Domain XYZ.com - Windows 2008 R2 Domain controllers + Contains all users + Desktop compuer accounts.
    User logs in to the domain XYZ.com from a desktop and he configures outlook using the user ID in  domain ABC.com.
    When he opens Outlook it is getting connected and he gets an error message pop -up saying 'The name on the security 
    certificate is invalid or does not match the name of the site'
    I am using an external certificate from Thawte for autodiscover.ABC.com & webmail.ABC.com
    I read about one solution provided in MS KB article - http://support.microsoft.com/kb/2772058 
    But in my scenarion there are two domain involved. Pls guide how to clear this.
     

    Hi,
    How about logon [email protected] on ABC domain via OWA?
    If OWA works well, it seems and issue on the Autodiscover side.
    Please run "Test E-mail AutoConfiguration" on Outlook to check whether this issue caused by Certificate Mismatch.
    1.
    Firstly make sure how many host name in your certificate the certificate. Run “Get-ExchangeCertificate | select certificatedomain”.
    2.
    Secondly, check the web services URLs which Outlook are trying to connect to. Run “Test Email AutoConfiguration”.
    3.
    In this scenario, you need to check the host name for the following services:
    Autodiscover, EWS, OAB, ECP, UM
    4.
    If any of the urls above does not match the one in the certificate, refer to the following article to change it via EMS:
    http://support.microsoft.com/kb/940726 
    More details to see following FAQ on "Checklist for Exchange Certificate issues":
    http://social.technet.microsoft.com/Forums/en-US/fa78799b-5c55-4c71-973b-0e186612ff6f/checklist-for-exchange-certificate-issues?forum=exchangesvrgeneral
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

    In the midst of Exchange 2013/2007 coexistence configuration. 
    Currently:
    Exchange 2007:
    2 CAS\HUB
    1 Mailbox server
    Exchange 2013 (2 sites):
    LA:
    1 CAS
    2 MBX servers
    MKE:
    1 CAS 
    2 MBX servers.
    We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
    2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com". 
    Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
    "The name of the security certificate is invalid or does not match the name of the site" for
    "LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

    Hi,
    Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
    Get-ExchangeCertificate | FL
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Upgraded to 5.4 when opening lightroom get a message "encountered an error when reading from its preview cache and need to quite" tried this several time but get the same eror message

    Upgraded to 5.4 when opening lightroom get a message "encountered an error when reading from its preview cache and need to quite" tried this several time but get the same error message.  Says Lightroom will attempt to fix the problem the next time it launches but that is not happening.  How do it fix this?

    Delete the preview cache using your operating system. It is a folder whose name ends with Previews.LRDATA. Do not delete the Lightroom catalog, which ends with .LRCAT

  • I have messed my MacBook Pro attempting to customize it. I am far from savvy with technology and I would like to erase and reset it to out of the box brand new and start over

    I have messed my MacBook Pro attempting to customize it. I am far from savvy with technology and I would like to erase and reset it to out of the box brand new and start over

    Polly,
    usually there are multiple models of MacBook Pro per model number, but in the case of your model number (A1502), there’s currently only one model for that model number: 13-inch Late 2013.
    To reset your MacBook Pro, you’ll need to boot into Recovery mode by holding down a Command key and the R key as you start it up. When the Mac OS X Utilities menu appears, select Disk Utility. On the left-hand side of the Disk Utility window, select your internal disk (most likely the top item of the list). On the right-hand side, select the Erase tab. For the Format dropdown, select “Mac OS Extended (Journaled)”. For the Name input box, “Macintosh HD” has traditionally been the default name — I don’t know if that’s still the case for the Late 2013 models. After that, press the Erase… button, and erase its entire internal disk. When it’s finished with the erasure, exit Disk Utility, and select Shut Down from the Apple menu. When you start it up again, OS X Internet Recovery will redownload Mavericks from Apple’s servers and reïnstall it on your internal disk. Once it has reïnstalled, run Software Update to get it up to date, and adjust the System Preferences to your taste.

  • Exchange 2013 - The name of the security certificate is invalid or does not match the name of the site

    Hi,
    I know this question has been asked a ton of times, but I haven't found any instance of this question asked for exchange 2013.  Yes, I've seen Exchange 2010, Exchange 2007, but not Exchange 2013.  The symptoms are all similar.  Here is a description:
    1 Exchange 2013 server, all roles installed.
    External domain name:  associates.com
    Internal AD domain name:  associates.local
    Client installed a third party SSL certificate, but did not purchase a SAN or UC certificate, so there is one namespace on the SSL cert, and that represents the external OWA name:  mail.associates.com
    Now, when internal OUtlook 2010 clients start, they get the "The name of the security certificate is invalid or does not match the name of the site."
    I'm just wondering if http://support.microsoft.com/kb/940726 still applies to Exchange 2013 to fix this issue.  Does this article apply to Exchange 2013?  If so, I will follow the above
    article.  If not, please direct me to any articles for Exchange 2013 that addresses this.
    the autodiscoverserviceuri points to: 
    https://netbiosnameofmailserver.associates.local/Autodiscover/Autodiscover.xml
    Thanks!
    A

    Yes, the http://support.microsoft.com/kb/940726 still applies to Exchange2013.
    As per my understanding on this post;
    - Poster's Exchange2013 has no SAN certificate.. (usually used for local address like; NETBIOS.Domain.lan).  Be reminded that SSL providers will no longer accepts .LAN or .LOCAL in very near future.
    - By default it uses local url for EWS, Autodiscover, etc.. (if you don't have SAN certificate installed in your CAS server, you would see the certi warning)
    Anyway, I just want to share my case after applying the said work around long time ago (maybe some of you might encounter it as well): my Outlook still showed the certificate warning (I was just keep clicking the YES button).. I was wondering
    that time what was wrong with my virtual directory settings.. until I decided to click "NO" for an answer to that certificate warning message, then voila! it didn't bug me anymore.  Oh by the way, the certificate warning usually give you a hint
    what triggers it like; "autodiscover.Domain.lan" on the first line of message, but in my case it just "NETBIOS.Domain.lan" (didn't make any sense, did it?).. Well, unfortunately I didn't have the chance to figure out what triggered that event.. 

  • The name on the security certificate is invalid or does not match the name of the site exchange 2010

    We did an update to SP1 to SP3 for Exchange 2010 over the weekend and now I am seeing the following errors.
    "The name on the security certificate is invalid or does not match the name of the site"
    Any ideas why an update would effect this. I have looked at the names and everything seems to match up.

    Hi,
    Does the issue happen to all users? If it is, please run the following command to check your certificate configuration:
    Get-ExchangeCertificate | fl
    Generally, the certificate mismatch issue is caused by the name in URLs doesn't match the certificate names with IIS service. Please make sure all URLs that used to connect Exchange from internal and external should match the certificate names with proper
    services.
    http://support.microsoft.com/kb/940726
    Best Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook: The name of the security certificate is invalid or does not match the name of the site

    Hey guys,
    We have setup autodiscover redirection properly (I guessed) by:
    Creating a CNAME from
    AliasName: autodiscover.tenant-domain.com TO
    PrimaryName: autodiscoverredirection.hostname.com.
    Then doing a re-direction to https autodiscover service.
    All seems to be working properly, however, when I open Outlook, it still shows the pop out saying "autodiscover.tenant-domain.com - The name of the security certificate is invalid or does not match the name of the site".
    The autodiscover redirection is indeed working properly, that's why the autodiscover is working, however it is still trying to match autodiscover.tenant-domain.com to the certitifcate instead of matching the re-directed url, which is autodiscover.hostname.com.
    Could anyone advise what is wrong? Or anyone who knows how to correct it can contact me? :)
    Jackson Yap APC Hosting http://www.apc.sg/

    Hi Jason, Well, if it is doing that, it is most likely beccause your autodiscoverredirection.hostname.com also respond to port 443/SSL. So, what you need to do is to make sure that specific IP isn't responding to 443. The reason is this, 1. You first hit
    https://autodiscover.tenant-domain.com, which this is a CNAME to autodiscoverredirection.hostname.com. So, if autodiscoverredirection.hostname.com respond to 443, it will then give you an error. If it doesn, it will then move on to perform redirection right
    away and you will not get that prompt.Regards, Kip Ng - http://blogs.technet.com/b/provtest/

  • The name on the security certificate is invalid or does not match the name of the site

    Hi Guys,
    Every time when we login to SAP Business One, we are getting two identical security Alerts, that we needs to click "Yes" twice.
    Text of error: “The name on the security certificate is invalid or does not match the name of the site”
    We tried to install certificate, but it is not solved this certificate issue and the alert still pops up on login.
    I guess, something wrong with dashboard settings, but don't really know what exact and how to fix it.
    Thanks,
    Sergey

    Hi,
    Please check SAP note:
    1810486 - Dashboard Certificate Sercurity Alert appears on every
    logon to Business One
    Thanks & Regards,
    Nagarajan

  • The name on the security certificate is invalid or does not match the name of the site" : IE

    Hi All,
    All clients are getting “the name on the security certificate is invalid or does not match the name of the
    site” when its reboot and try to access website.
    I don’t have idea about certificate authority. Can anyone help on how I start troubleshooting this.
    Is there any group policy setting which resolve this issue.
    Please suggest what parameter I have to check. 

    > All clients are getting “the name on the security certificate is invalid
    > or does not match the name of the site” when its reboot and try to access website.
    "View Certificate" should tell you.
    Greetings/Grüße,
    Martin
    Mal ein
    gutes Buch über GPOs lesen?
    Good or bad GPOs? - my blog…
    And if IT bothers me -
    coke bottle design refreshment (-:

Maybe you are looking for

  • Redundancy not forming with wlc

    Hi, We have two wlc 5508 running vers 7.4.100.60. They are not forming redundancy pair & are in maintenance mode. Both RP's are connected physically direct. Few outputs are given here:- (WLC01) >show redundancy summary Redundancy Mode = SSO ENABLED  

  • Weblogic Startup Issues

    I've been searching through this board and through other sources to find some answers..... I recently tried to update fusion middleware (Fusion Middleware 11g Release 1 (11.1.1.5)) on top of an existing copy we had installed due to a forms error we k

  • I cannot find 3d on Photoshop cs6 extended yes it is extended

    I cannot find 3d on Photoshop cs6 extended Yes it is extended

  • How to define onSelect action in code?

    I created a dropdownbykey using dynamic way like below. IWDDropDownByKey myDropDown = (IWDDropDownByKey) view.createElement(IWDDropDownByKey.class, "myDropDown "); myContainer.addChild(myDropDown); Now I want to add the code to set the onSelect actio

  • Why I can not send correct content in webserver?

    hi,All: I write some to send a email that have attachment, and it look ok when I run it in IDE, but when I run it in the webserver(jetty), I get a email like this: ------=_Part_2_26331059.1232704896093Content-Type: text/plain; charset=us-asciiContent