VSphere Client SSL error build 10041

So I'm seeing an odd error after upgrading to build 10041 (from 9926). The vSphere client (both 5.1 and 5.5) will no longer connect to my vCenter instance. I receive the following error
"vSphere Client could not connect to "<server>" An unknown connection error occured. (The request failed due to an SSL error. (The request was aborted: Could not create SSL/TLS secure channel.))"
Checking the event log I see Schannel 36888 errors with the following message: "A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 40. The Windows
SChannel error state is 813."
I managed to find out that error 40 means "handshake_failure". The error state (813) I haven't been able to find additional information on.
When I look at the vpxd.log file I see the following log lines which seems to confirm its a handshake error.
2015-04-02T13:26:08.442-05:00 [07548 error 'Default'] SSLStreamImpl::DoServerHandshake for SSL(TCPStreamWin32(socket=TCP(fd=38244) local=xxx:443,  peer=yyy:64839)): SSL_accept failed with BIO Error
2015-04-02T13:26:08.442-05:00 [07548 warning 'ProxySvc'] SSL Handshake failed for stream TCPStreamWin32(socket=TCP(fd=38244) local=xxx:443,  peer=yyy:64839), error: class Vmacore::Ssl::SSLException(SSL Exception: BIO Error)
Does anyone know if there were any changes around Schannel that would be causing a handshake error? I can't seem to find any additional information. It looks like vCenter accepts TLS 1.0, which in IE at least is enabled.

Hi Jeff,
I think we'd better involve the VMware side to further look at this issue.
For Windows 10 build 10049, you might need to notice the information below:
No access to Internet Protocol (v4 or v6) in 10049
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

  • Shutdown Error Build 10041

    Whenever I select shutdown from the start menu my computer goes into the process of shutting down but then it has issues closing Microsoft .NET Framework and it brings my computer back to my desktop. I am not entirely sure how to resolve the issue. I provided
    the error message I receive after it sends me back to desktop.
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
    Server stack trace:
    at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
    at System.Runtime.Remoting.Channels.SocketStream.Read(Byte[] buffer, Int32 offset, Int32 size)
    at System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
    at System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
    at System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
    at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
    at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
    at System.Runtime.Remoting.Channels.Tcp.TcpClientSocketHandler.ReadHeaders()
    at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
    at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
    Exception rethrown at [0]:
    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
    at AlienLabs.CommandCenter.RemotingService.Domain.ApplicationLaunchWatcher.remove_ApplicationLaunched(ApplicationLaunchedEventHandler value)
    at AlienLabs.CommandCenter.RemotingService.Domain.Classes.ApplicationLaunchWatcherHolder.unregisterApplicationLaunchedEvent(ApplicationLaunchedEventHandler eventHandler)
    at AlienLabs.CommandCenter.RemotingService.Domain.Classes.ApplicationLaunchWatcherHolder.ReleaseWatcher(ApplicationLaunchedEventHandler eventHandler)
    at AlienLabs.AlienFX.Controller.ControllerMainForm.closingApplication()
    at AlienLabs.AlienFX.Controller.ControllerMainForm.formClosing(Object sender, FormClosingEventArgs e)
    at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
    at System.Windows.Forms.Form.WmClose(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at AlienLabs.AlienFX.Controller.ControllerMainForm.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
    AlienwareAlienFXController
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/Program%20Files/Alienware/Command%20Center/AlienwareAlienFXController.exe
    AlienLabsTools
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabsTools/v4.0_2.8.8.0__bebb3c8816410241/AlienLabsTools.dll
    AlienwareAlienFXTools
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienwareAlienFXTools/v4.0_2.8.8.0__bebb3c8816410241/AlienwareAlienFXTools.dll
    Alienlabs.CommandCenter.Tools
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Alienlabs.CommandCenter.Tools/v4.0_2.8.8.0__bebb3c8816410241/Alienlabs.CommandCenter.Tools.dll
    System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    WindowsBase
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
    PresentationFramework
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll
    PresentationCore
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
    System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
    Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    AlienLabs.MasterIOBoard.Communication
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabs.MasterIOBoard.Communication/v4.0_2.8.8.0__bebb3c8816410241/AlienLabs.MasterIOBoard.Communication.dll
    AlienFX.DeviceDiscovery
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.DeviceDiscovery/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.DeviceDiscovery.dll
    AlienLabs.MasterIOBoard.Communication.Core
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabs.MasterIOBoard.Communication.Core/v4.0_2.8.8.0__bebb3c8816410241/AlienLabs.MasterIOBoard.Communication.Core.dll
    AlienFX.Communication
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.dll
    AlienFX.Communication.XPS
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.XPS/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.XPS.dll
    AlienFX.Communication.Andromeda
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.Andromeda/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.Andromeda.dll
    AlienFX.Communication.PID0x522
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x522/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x522.dll
    AlienFX.Communication.PID0x521
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x521/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x521.dll
    AlienFX.Communication.PID0x520
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x520/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x520.dll
    AlienFX.Communication.PID0x518
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x518/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x518.dll
    AlienFX.Communication.PID0x516
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x516/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x516.dll
    AlienFX.Communication.PID0x515
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x515/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x515.dll
    AlienFX.Communication.PID0x514
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x514/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x514.dll
    AlienFX.Communication.PID0x513
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x513/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x513.dll
    AlienFX.Communication.PID0x512
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x512/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x512.dll
    AlienFX.Communication.PID0x511
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.PID0x511/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.PID0x511.dll
    AlienFX.Communication.Core
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienFX.Communication.Core/v4.0_2.8.8.0__bebb3c8816410241/AlienFX.Communication.Core.dll
    LightFX
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/LightFX/v4.0_2.8.8.0__bebb3c8816410241/LightFX.dll
    AlienwareAlienFXModelResources
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienwareAlienFXModelResources/v4.0_2.8.8.0__bebb3c8816410241/AlienwareAlienFXModelResources.dll
    Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    System.Xaml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll
    Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    AlienLabs.CommandCenter.RemotingService.Domain
    Assembly Version: 2.8.8.0
    Win32 Version: 2.8.8.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/AlienLabs.CommandCenter.RemotingService.Domain/v4.0_2.8.8.0__bebb3c8816410241/AlienLabs.CommandCenter.RemotingService.Domain.dll
    System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
    System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
    System.Data.DataSetExtensions
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Data.DataSetExtensions/v4.0_4.0.0.0__b77a5c561934e089/System.Data.DataSetExtensions.dll
    System.Numerics
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.42.0 built by: NETFXREL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Hi Arbla,
    Were you running any application or third party service in 10041 build?
    For a clean installation, I do not receive any similar error information, I suggest your perform a Diagnostic startup which starts Windows with basic services and drivers only,
     to check if this issue would be reproduced.
    You can open Msconfig.exe to access System Configuration.
    For your reference which works in Windows 10 as well:
    http://windows.microsoft.com/en-in/windows/using-system-configuration#1TC=windows-8
    regards,
    Alex Zhao
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Update Operation Fatal Error when installing Technical Preview Build 10041 Upgrade

    I posted this in the Microsoft Community forums and was redirected here.
    Below is the original post (URL: http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/update-operation-fatal-error-when-installing/6eaff1b9-0223-4357-afc8-884382590e82 )
    Hello,
    In trying to perform an upgrade install of the Windows 10 Technical Preview Build 10041 (as is the latest available for direct download as of my writing), I am running into a problem I cannot find mention of anywhere else on the web.
    I fall into two categories with regards to this build: A) Product tester who actually needs to test application performance under Windows 10 on bare metal, B) Semi-crazy techie who loves using (usable) beta software as his primary environment ;)
    so it is rather important to me that I get this working on my machine in some non-virtualized respect. I am reluctant to do a full/fresh install if installation problems are happening, because my Windows 8 product key has been f***ed up from the
    start (likely some random database corruption) and I've had to utilize phone support to get around an "unknown error" the last two times I've had to use it. So, for fear of that key completely crapping out on me, I don't want to move to Win10 unless
    I'm confident it will install and I can stick with it (for better or worse) through the end. Problems within the Preview after I install it I can deal with.
    So, I first tried to install the Preview through the standard Windows Update method. The installer took about 7 hours (but from reading lots of internet discussions, stupidly long install times in that range seem to be a common problem with
    this builds separate from it actually failing). During the reboot between the "Setting up Devices" (Or is it Setting up Drivers? I forget) and "Taking Care of a Few More Things" (Again, possibly paraphrased), for about a split second, underneath
    the Windows logo and throbber, some error like this appeared:
    Fatal Error Performing Update Operation # of ##: ERROR CODE
    It only appeared for a fraction of a second, and I had no chance of reading the precise numbers or error.
    However, the installer then seemed to continue, and went until the main circle was at 100%. As soon as 100% hit, however, the screen went black for something like 30min. Then, I briefly saw "Attempting to recover installation" before "Restoring
    your previous version of Windows." And I was, quite impressively considering how far along that installer was, back in Windows 8.1 completely unharmed.
    I tried again by burning an ISO and doing a disc upgrade install. I let that one run overnight and was asleep for the error, but I was back in Win8.1 in the morning, so I can only assume a similar thing happened there.
    As for my system specs, I'm running on a MacBook Pro 9,1 under Boot Camp. I am upgrading from Windows 8.1.2 Pro with Media Center. I have found other online accounts of people quite successfully installing Windows 10 on Macs, so that isn't the issue.
    Does anyone have any clue as to what this error might have been/be, and how I might fix it? Or at least have it on good authority that a fresh installation would be unaffected (meaning it's software-related)? If not, I can try installing to a VHD,
    which would at least let me product test on bare metal, but wouldn't have the harddrive space to be my daily driver and would probably only get used occasionally.
    Thanks in advance to anyone who can help!
    So far, I have the yet-to-be-tried idea of a clean boot prior to installation.
    If anyone here has any more specific ideas, lemme hear 'em.
    Thanks!

    To the individual who proposed this as an answer to my problem: It's not even applicable. I specifically stated that I was trying to avoid doing a clean installation (at least without knowing more about the problem at hand). An answer saying to do the thing
    you're trying to avoid doing is not an answer. You can see my last reply for the current status of this issue. 6-8 hour blocks of time in which I can't use my computer (as is required to install build 10041) aren't super common for me, but I haven't abandoned
    this thread. There have simply been no more updates. If your motivation as a mod was that you simply don't like there being unanswered threads on this forum, then perhaps you could attempt to contribute rather than arbitrarily marking the first reply as an
    answer.
    I will continue to update this thread as I try new things and get more information.
    Thank you.

  • Errors "A media driver your computer needs is missing." or "Windows cannot install required files" upon attempting to install Windows 10 TP build 10041 64-bit

    I'm attempting to install Windows 10 TP build 10041 [64-bit]
    I am currently being prevented from installing by a "A media driver your computer needs is missing." error, which occurs fairly early in the process. I've interpreted further text in the message as a suggestion that it's a DVD, USB or some other
    similar driver issue. However, as I've been able to attempt each install through booting from DVD and USB, I'm not convinced this is the issue.
    I'm currently installing to a 128Gb SSD drive. I have installed Windows 10 TP on my laptop's SSD with no issues.
    On a few occasions the installation has continue with the installation, and then failed at about 6% with the following error:
    "Windows cannot install required files. Make sure all files required for installation are available, and restart the installation. Error code 0x8007045D". I have not removed the installation USB or DVD.
    I did not have this issue when installing build 9841, so am currently assuming this is an issue with build 10041.
    Apologies if this query has been posed before, a search did not show up this issue.
    Any advice would be greatly appreciated.

    Hi Michael,
    Thanks for trying to assist!
    I attempted removing/deleting partitions and formatting the SSD as part of the install process. I have also tried installing via USB and DVD with the same issues.
    As part of the troubleshooting, I attempted to install a different OS. I was able to successfully install Linux Mint 17.1 with no issues. This further solidifies my impression this is an issue with Windows.
    I will try a different USB port, appreciate the suggestion, didn't think it would make a different given the various methods already attempted.

  • SSL Error while Consuming Java build SOAP services using Dotnet Console App

    Hi, I want to consume a SOAP service developed in JAVA. I don't have any control on Service side. I have to just consume the SOAP service using my client Application which is in DotNet Console Application using C#. Here is the detail about the service:
    1. The service has SSL configured.
    2. End point looks like: https://xyz.com:443
    3. I am able to connect the service using SOAP UI Tool by configuring the Tool with the certs given by Java developer.
    4. Basically there are two certs used, one for "client authentication" purpose and the second cert is for "WS security" purpose.
    5. When i add the WSDL to my client app as a service Reference, the generated App.config file looks as shown below:
    <configuration>
    system.serviceModel>
    <bindings>
    <basicHttpBinding>
    <binding name="Hello_HTTPBinding">
    </binding>
    </basicHttpBinding>
    </bindings>
    <client>
    <endpoint address="http://localhost:8080/" binding="basicHttpBinding"
    bindingConfiguration="Hello_HTTPBinding"
    contract="Proxy_Hello" name="Hello_HTTPPort" />
    </client>
    </system.serviceModel>
    </configuration>
    6. Basically I need to pass two certs, one cert used for "client authentication" purpose and the second cert is used for "WS security purpose".
    7. I have changed the above client configuration as below marked in RED color text:
    <configuration>
    system.serviceModel>
    <bindings>
    <basicHttpBinding>
    <binding name="Hello_HTTPBinding">
    <security mode="TransportWithMessageCredential" >
    <transport clientCredentialType="Certificate" proxyCredentialType="Basic" realm="" />
    <message clientCredentialType="Certificate" algorithmSuite="Basic128" />
    </security>
    </binding>
    </basicHttpBinding>
    </bindings>
    <client>
    <endpoint address="https://xyz.com:443"
    binding="basicHttpBinding"
    bindingConfiguration="Hello_HTTPBinding"
    contract="Proxy_Hello" name="Hello_HTTPPort" behaviorConfiguration="NewBehavior"/>
    </client>
    <behaviors>
    <endpointBehaviors>
    <behavior name="NewBehavior">
    <clientCredentials >
    <clientCertificate findValue="clientxyz.com" storeLocation="CurrentUser" storeName="My" x509FindType="FindBySubjectName" />
    <serviceCertificate>
    <defaultCertificate findValue="helloabc.com" storeLocation="CurrentUser" storeName="My" x509FindType="FindBySubjectName"/>
    </serviceCertificate>
    </clientCredentials>
    </behavior>
    </endpointBehaviors>
    </behaviors>
    </system.serviceModel>
    </configuration>
    8. I am assuming the cert required for WS security  will be passed using in<serviceCertificate> element, but not fully sure....correct me if I am wrong.
    9. By creating proxy object of the service when I am trying to call the required method I am getting this Error: "Could not establish
    secure channel for SSL/TLS with authority "******xyz.com."
    10. Its working perfect in SOAP UI Tool, generating the Raw XML as shown below in ORANGE color Text:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:gw-headers-100" xmlns:urn1="urn:gw-util-100">
    <soapenv:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
    wsu:Id="X509-35309F239B754D9BA414230227616161">
    aaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbbbccccccccccccccccccccc********dddddddddddd*****eeeeeeeeee
    </wsse:BinarySecurityToken>
    <ds:Signature Id="SIG-2" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
    <ds:SignedInfo>
    <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
    <ec:InclusiveNamespaces PrefixList="soapenv urn urn1" xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    </ds:CanonicalizationMethod>
    <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
    <ds:Reference URI="#id-1">
    <ds:Transforms>
    <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
    <ec:InclusiveNamespaces PrefixList="urn urn1" xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"/>
    </ds:Transform>
    </ds:Transforms>
    <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
    <ds:DigestValue>
    abcabcabcabc******gggggg
    </ds:DigestValue>
    </ds:Reference>
    </ds:SignedInfo>
    <ds:SignatureValue>gggggg888******8sdsdsdss</ds:SignatureValue>
    <ds:KeyInfo Id="KI-38488AAAA222">
    <wsse:SecurityTokenReference wsu:Id="STR-ggggjj57557575">
    <wsse:Reference URI="#X509-74747477" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/>
    </wsse:SecurityTokenReference>
    </ds:KeyInfo>
    </ds:Signature>
    </wsse:Security>
    </soapenv:Header>
    <soapenv:Body wsu:Id="id-1" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <urn1:xxxxxxx>
    </urn1:xxxxxx>
    </soapenv:Body>
    </soapenv:Envelope>
    11. Using Dotnet Tracing I am able to see the Request XML generated from the console Application as shown below in BLUE color text: But getting the SSL error as: Could not establish secure channel
    for SSL/TLS with authority "******xyz.com.
    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
    <s:Header>
    <o:Security s:mustUnderstand="1" xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <u:Timestamp u:Id="_0" xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <u:Created>2015-02-04T04:19:29.825Z</u:Created>
    <u:Expires>2015-02-04T04:24:29.825Z</u:Expires>
    </u:Timestamp>
    <o:BinarySecurityToken>
    <!-- Removed-->
    </o:BinarySecurityToken>
    <Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
    <SignedInfo>
    <CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod>
    <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod>
    <Reference URI="#_0">
    <Transforms>
    <Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform>
    </Transforms>
    <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></DigestMethod>
    <DigestValue>aaaaaa****dddddd=</DigestValue>
    </Reference>
    </SignedInfo>
    <SignatureValue>ssssddddd888fffff****=</SignatureValue>
    <KeyInfo>
    <o:SecurityTokenReference>
    <o:Reference ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" URI="#uuid-93e09c54-aee8-4f45-a8a4-d63d8a2d63fb-1"></o:Reference>
    </o:SecurityTokenReference>
    </KeyInfo>
    </Signature>
    </o:Security>
    </s:Header>
    </s:Envelope>
    12. I want to Generate the Request XML from my Dotnet console Application simiar to the SOAP UI generated XML(refer #10).. Also want to get rid of SSL error....Appreciate your Suggestion..

    Hi tksdotnet,
    This forum is used to discuss the questions about the WCF web service, for java web services questions, it will be better to post in this forum:
    #WCF, ASMX and other Web Services:
    http://forums.asp.net/28.aspx/1?WCF+ASMX+and+other+Web+Services .
    Thanks for your understanding.
    Best Regards,
    Amy Peng
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Windows 10 TP Build 10041: fbl-impressive 10041 Enterprise is not be installed Error 0x80070241

    I have running Win 10 Enterprise TP build 10041 and downloaded Windows Update fbl_impressive 10041 Enterprise.
    The installation failed with the error message 0x80070241.
    What is to do?
    xb9$EF,3

    Czer
    Try updating from the ISO.  Instructions for making one here
    Wanikiya and Dyami--Team Zigzag

  • Cisco AnyConnect Secure Mobility Client doesn't work with Windows 10 Enterprise build 10041

    Just updated the Windows 10 OS to the latest build (10041) and this has prompted the VPN client to stop working. I've been using the 3.1.5187.0 version of the Cisco client. Any help greatly appreciated.

    Have you tried uninstalling the cisco vpn client software and then
    reinstalling it?
    Bob Comer

  • VSphere Client VERSION 5 - error parsing clients.xml file

    hi
    i'm trying to connect my server via vsphere client VERSION 5! but i get that stupid error that was common in vsphere 4 "Error parsing the server "SERVER
    IP" "clients.xml" file. Login will continue, contact your system administrator"
    this error was in vsphere 4 but i get it in vsphere client 5 , any ideas?

    Hello Ali Salehi,
    Thank you for posting in the TechNet forum.
    Have you made any changes before this issue?
    As this issue is related to VMware, to receive better support, it is recommended to contact the VMware support.
    Additionally, if the program is Vista compatible, you can try Vista compatibility mode. If this isn’t Vista compatible, and you meet the hardware requirements, you can try using the XP Mode. You can find more information at the following link:
    http://www.microsoft.com/windows/virtual-pc/get-started.aspx
    Best regards,
    Fangzhou CHEN
    Fangzhou CHEN
    TechNet Community Support

  • SSL Client Binding Error (does not support directory connections encryp....

    So I'm getting the dreaded "does not support directory connections encrypted with ssl" error when attempting to bind clients (10.5) to the server (10.5).
    I followed the Apple KB article, but it did not help...double-checked permissions and the config files.
    Binding works fine w/o SSL...but evidently SSL does not.
    Any news on this?
    Thanks.
    j

    Hmmm...still running into the same issue...do I need to give the cert reference text file certain permissions in order to work?
    I have followed the advice on afp548, and have a self-rolled CA with a self-assigned cert for the server, which is also the dns name of the server. I copied the CA hash and pointed to that instead of the self-signed cert hash, but still...no dice.
    -j

  • Window 10 build 10041 does not work with Intel 82579V Gigabit Ethernet on ASUS motherboard

          
    I originally posted this question here:
    answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/window-10-build-10041-does-not-work-with-intel/6729892f-83aa-4822-b20a-ea84f4fd06c7
    and was asked to post it on this forum...
    I updated a computer I have which is a quad core i7 that I built and includes an ASUS motherboard with Intel 82579V Gigabit Ethernet built in. Windows 10 preview 9926 worked fine with this network adapter. Window 10 build 10041 does not, and I have tried
    it twice so far. I even went as far as buying a Thunderbolt-Gigabit Ethernet Adapter (Broadcom, sold by Apple)... and while it installed the driver automatically, it did not work either. Each time you try to view the properties of either of them, it locks
    up or give an error. In fact, doing much of anything with the Intel adapter icon assures you of not being able to do a clean reboot... have to kill power.  I have finally gone back the previous version 9926, which has its issues but no where near as bad
    as not having any network connectivity!  Does anyone have this issue and a workaround? 
    Note, there are two images on the windows 10 preview forum that I posted this question on. I could not post the full link as I was getting a message here that links and graphics are not allowed.

    Thanks Roger, I posted the following yesterday in the other thread (thinking it was this thread - confusing after they moved it here)... It may be that the new driver fixes the issue that 10041 has with it, but I have not tried that yet. If I do I will update
    this... Thanks!
    I have more information about this, which basically exonerates any issue with the Intel 82579V Gigabit Ethernet hardware or software. I have 3 computers with Windows 10 preview so I have multiple angles to see issues from. With this I have found a culprit
    (but I suspect not just the only culprit) in this above mentioned problem...
    10041 build combined with installing (or attempting to install) CISCO VPN Windows 7 64bit 5.0.07.0440-k9 client causes the issue mentioned above. I confirmed this on a completely different machine with a totally different Ethernet adapter. First machine
    is an ASUS motherboard in a tower system I built, with the Intel 82579V Gigabit Ethernet hardware built in. Second machine is a Gateway Laptop from 2008 which has a Marvell Yukon 88E8057 PCI-E Gigabit adapter built in. Build 10041 will work fine with my 2008
    laptop, including the MS VPN client (which I have tested). However, if you attempt to install or even uninstall the Cisco client you will have to do a recovery to a restore point (as I have done twice) in order to get your network working again. Installing
    or attempting to install (because it never even does install properly and times out), CISCO VPN client will render your entire network unusable. Going back to a restore point saved me and I am still running 10041 but I can't use CISCO VPN client any longer.
    I could with build 9926, including on all 3 machines. I now have 9926 on two machines and 10041 on only the 2008 laptop. 
    Hopefully this above information helps someone resolve the issue. I will also mention, even though my network is working on the 2008 laptop, I still can't go into the Control Panel\Network and Internet\Network Connections and right mouse click on the Marvell
    Yukon 88E8057 PCI-E Gigabit adapter icon. I get an error when clicking on Properties menu popup : "An unexpected error has occurred". So something is still up with my network adapter driver or windows software, but it could be a side effect of all
    that has happened with the Cisco software install attempts under 10041.
    Another note: CISCO Anyconnect also has the issue.

  • Unable to install SCCM 2012 client in Win10 (build 10061)

    Hi,
    I am trying to install SCCM client version 5.00.7845.1000 on a Windows 10 (build 10061) and get these errors.
    -- File 'C:\WINDOWS\ccmsetup\WindowsUpdateAgent30-x64.exe' returned failure exit code 775. Fail the installation.
    -- InstallFromManifest failed 0x80070307
    -- CcmSetup failed with error code 0x80070307
    Both 0x80070307 and error 775 translate to :
    The implementation is not capable of performing the request.
    I am wondering if it's even possible to install the client on this build?
    Thanks
    Chanderjeet
    VISTA / XP Support Trainer

    I figured out a workaround for OSD. Essentially I create a fake ccmsetup.exe which then executes the normal ccmsetup command line OSD needs but with the /skipprereq:WindowsUpdateAgent30-x64.exe parameter included.
    1. Create a copy of your client install package. Move all the install files/folders into a new subfolder named client.
    2. Add the new client package and make note of the package ID assigned.
    3. Using VS Express 2013, create a new c# console project and name it ccmexec. Paste this code in, replace 10000A53 with the package ID of your new client package, and compile.
    using System;
    using System.Collections.Generic;
    using System.Diagnostics;
    using System.Linq;
    using System.Text;
    using System.Threading;
    using System.Threading.Tasks;
    namespace ccmsetup
        class Program
            static void Main(string[] args)
                var process = Process.Start("c:\\_SMSTaskSequence\\OSD\\10000A53\\client\\ccmsetup.exe", "/skipprereq:WindowsUpdateAgent30-x64.exe /useronly /source:C:\\_SMSTaskSequence\\OSD\\10000A53\\client
    /config:C:\\_SMSTaskSequence\\OSD\\10000A53\\MobileClient.TCF");
                while (!process.HasExited)
                    Thread.Sleep(1000);
    4. Take the fake ccmexec.exe and add it to the root (the root only - don't overwrite the normal ccmsetup.exe located in the client folder) of your new client source folder and update your new client package.
    5. Modify your Windows 10 task sequence(s) and switch the SCCM client package to your new one.
    This works for me under SCCM 2012 R2 CU1 w/ WIndows 10 x64 build 10041. This should work for the 10061 build as well. Yeah I know I this could be better (extract package ID from command line, etc.) but I was in a hurry just to make sure this workaround fundamentally
    works.

  • Problem with System Metrics SM_CXSIZEFRAME + SM_CXPADDEDBORDER in Windows 10 Preview (Build 10041)

    Maybe this forum is the wrong place to ask something about Windows 10 Preview, but I did not find a dedicated place to report
    programming problems as opposed to user problems:
    I program/maintain a 32-bit desktop (WIN32 API) application and try it now on Windows 10 Preview build 10041. I calculate the size of a window border with the help of the GetSystemMetrics function, using the constants SM_CXSIZEFRAME and SM_CXPADDEDBORDER.
    Originally, I only used SM_CXSIZEFRAME. This returned 4 pixels instead of the expected 8 pixels that I got on all previous windows versions up to Windows 8.1. Then I learned that already since Windows Vista one is expected to add the value of SM_CXPADDEDBORDER
    to get the full border size. (SM_CXSIZEFRAME alone only continued to work on Vista and beyond thanks to a little compatibility hack by Microsoft, with SM_CXSIZEFRAME still returning the full border size and SM_CXPADDEDBORDER returning
    yet 0, at least for 32-bit programs like mine.)
    Assuming that Microsoft finally switched off that compatibility measure on Windows 10 I query and add SM_CXPADDEDBORDER now as well. Unfortunately this does not solve my problem, as that system metric returns 0.
    Just to be on the sure side, I declared my program to support Windows 10 by using an embedded manifest and using the corresponding <compatibility> / <supportedOS> line with the Windows 10 GUID - this did not help either.
    As querying and adding those two system metric values is rather trivial (no need to include code in this question, I think), I don't have the slightest idea what
    I could do wrong here, this looks like Preview bug affecting 32-bit programs to me...

    I regret to inform you, that you have to live with this error for ever. Microsoft won't fix it... we reported an error of the Windows Error Reporting system (exists since Windows 8) and provided a reproduction (an application with one printed page of code,
    so very small and easy). It has never been fixed. 3 developers at Microsoft are involved and they confirmed, that it's a bug ... but... no chance. It's a strange company... I don't know what they mean with "we listen to our customers".
    PS: ja, nöd grad hilfriich mini Kommentär, aber die Type triibed eim eifach in Wahnsinn!! ... schinbar nöd nur öschtlich vo Bade, sondern au weschtlich
    Rudolf

  • EJB Client giving error

    Hi All,
    I am new to EJB programming. I am trying to use EJB3 and Weblogic12c.
    and would like to know why I am getting this error:
    run:
    [echo] Executing client class
    [java] java.lang.NoClassDefFoundError: com/saurabh/demo/HelloWorldClient
    [java] Caused by: java.lang.ClassNotFoundException: com.saurabh.demo.HelloW
    orldClient
    [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    [java] at java.security.AccessController.doPrivileged(Native Method)
    [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
    [java] Could not find the main class: com.saurabh.demo.HelloWorldClient. P
    rogram will exit.
    [java] Exception in thread "main"
    [java] Java Result: 1
    I am posting my code so that its more easy to debug...
    1. HelloWorld.java -
    package com.saurabh.demo;
    import javax.ejb.Remote;
    @Remote
    public interface HelloWorld
         public void sayHello(String name);
    2. HelloWorldBean.java
    package com.saurabh.demo;
    import javax.ejb.Stateless;
    @Stateless(mappedName="HelloWorld")
    public class HelloWorldBean implements HelloWorld
         public void sayHello(String name)
              System.out.println("Hello "+name+ " Its Working");
    3.
    package com.saurabh.demo;
    import java.util.Hashtable;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    public class HelloWorldClient{
         private static HelloWorld helloworld;
         public static void main(String[] args)
         try{
              Hashtable<String, String> env = new Hashtable<String,String>();
              env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
              env.put(Context.SECURITY_PRINCIPAL,"username of my weblogic");
              env.put(Context.SECURITY_CREDENTIALS,"password of my weblogic");
              env.put(Context.PROVIDER_URL,"t3://localhost:7001");
              Context ctx=new InitialContext(env);
              System.out.println("Initial Context created");
              helloworld =(HelloWorld)ctx.lookup("HelloWorld#com.saurabh.demo.HelloWorld");
              System.out.println("lookup Successful");
              System.out.println("Calling EJB method...");
              helloworld.sayHello("Saurabh");
              System.out.println("Output will be in Managed Server Console");
         catch(Exception e)
              e.printStackTrace();
    4. build.xml
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="Ejb_HelloWorld" basedir="." default="buildEar">
    <property file="${basedir}/developer.properties"/>
    <property name="jarname" value="HelloWorld-ejb"/>
    <property name="appname" value="HelloWorld"/>
    <property name="src" value="${basedir}/src"/>
    <property name="build" value="${basedir}/build"/>
    <property name="dist" value="${basedir}/dist"/>
    <property name="lib" value="${basedir}/lib"/>
    <property name="src.server" value="${src}/server"/>
    <property name="src.client" value="${src}/client"/>
    <property name="build.server" value="${build}/server"/>
    <property name="build.client" value="${build}/client"/>
    <property name="dist.server" value="${dist}/server"/>
    <property name="dist.client" value="${dist}/client"/>
    <path id="dependencies">
         <pathelement location="${lib}/javax.ejb_3.1.0.jar"/>
         <pathelement location="${lib}/weblogic.jar"/>
    </path>
    <target name="clean">
         <echo>"Cleaning the directories"</echo>
         <delete dir="${build}"/>
         <delete dir="${dist}"/>
    </target>
    <target name="compile" depends="clean">
         <echo>"Compiling EJB"</echo>
         <echo message="BEA_HOME:${BEA_HOME}"/>
         <echo message="WLS_HOME:${WLS_HOME}"/>
         <mkdir dir="${build}/server/classes"/>
         <echo message="Source directory : ${src.server}"/>
         <javac includeantruntime="false" srcdir="${src.server}" destdir="${build.server}/classes" debug="on">
         <classpath refid="dependencies"/>
         </javac>
    </target>
    <target name="compileClient">
         <echo>"Compiling Client class"</echo>
         <mkdir dir="${build.client}/classes"/>
         <javac includeantruntime="false" srcdir="${src.client}" destdir="${build.client}/classes" debug="on">
         <classpath refid="dependencies"/>
         <classpath location="${build.server}/classes"/>
         </javac>
    </target>
    <target name="buildEar" depends="compile">
         <echo>"Building EJB EAR"</echo>
         <mkdir dir="${dist.server}"/>
         <jar jarfile="${dist.server}/${jarname}.jar" basedir="${build}/server/classes"/>
         <jar jarfile="${dist.server}/${appname}.ear" basedir="${dist.server}"/>
    </target>
    <target name="run" depends="compileClient">
         <echo message="Executing client class"></echo>
         <java classname="com.saurabh.demo.HelloWorldClient" fork="yes">
         <classpath>
         <pathelement location="{build.client}/classes"/>
         <pathelement location="{dist.server}/HelloWorld-ejb.jar"/>
         <pathelement location="{lib}/wlfullclient.jar"/>
         </classpath>
         </java>
    </target>
    </project>
    5. developer.properties- This property file is being used to set the needed paths.
    BEA_HOME=C:\SG_Installs\wls1211_dev
    JAVA_HOME=C:\SG_Installs\Java
    WLS_HOME=C:\SG_Installs\wls1211_dev\wlserver
    project.home=C:\Saurabh Data\WebDev\EJB-HelloWorld
    wls.domain.path=C:\SG_Installs\BEA_Domain\BEA_Domain
    wls.application.path=C:\SG_Installs\BEA_Domain\BEA_Domain\applications
    There is no deployment descriptors since there is no need for that in EJB3 as I know.
    I have been trying to resolve this issue but with no luck... Please help....
    Edited by: 919201 on Mar 6, 2012 4:31 PM
    Edited by: 919201 on Mar 6, 2012 5:54 PM
    Edited by: Passionate on Mar 8, 2012 9:35 PM

    java.lang.NoClassDefFoundError: com/saurabh/demo/HelloWorldClient
    +[java] Caused by: java.lang.ClassNotFoundException: com.saurabh.demo.HelloW+
    orldClient
    Does {build.client}/classes include the com/saurabh/demo/HelloWorldClient class?

  • SSL error: ... SSLCipherUtility.getCompatabilityKeySize()

    Hi all:
    I am using WLS 8.1SP3 to do 2-Way SSL with client, and I am seeing the following SSL error. I have the SSL/Domestic BEA license. Pretty sure that the client uses 128-bit SSL.
    Anyone seen this before? Your help would be appreciated.
    Thanks
    ================
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 770107>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLSocket will be Muxing>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 SSL Version 2 with no padding>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 SSL3/TLS MAC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 received SSL_20_RECORD>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ClientHelloV2>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 58>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 2027>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 4>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 SSL3/TLS MAC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 received HANDSHAKE>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: ClientKeyExchange RSA>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 SSL3/TLS MAC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 received CHANGE_CIPHER_SPEC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 SSL3/TLS MAC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 received HANDSHAKE>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: Finished>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <write HANDSHAKE, offset = 0, length = 16>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.findContext(sock): 5177735>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <activateNoRegister()>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <avalable(): 15551322 : 0 + 0 = 0>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.activate(): activated: 24734398 21629812>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read(offset=0, length=4080)>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <hasSSLRecord()>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <hasSSLRecord returns true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 SSL3/TLS MAC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 received APPLICATION_DATA: databufferLen 0, contentLength 318>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read databufferLen 318>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read A returns 318>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read(offset=318, length=3762)>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <hasSSLRecord()>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <hasSSLRecord returns false 1>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 Rethrowing InterruptedIOException>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.findContext(sock): 5177735>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <activateNoRegister()>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <avalable(): 15551322 : 0 + 501 = 501>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.activate(): activated: 24734398 9126243>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read(offset=318, length=3762)>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: true>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <hasSSLRecord()>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <hasSSLRecord returns false 1>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 Rethrowing InterruptedIOException>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <Socket> <BEA-000430> <hasException
    java.lang.NullPointerException
    java.lang.NullPointerException
    at weblogic.security.utils.SSLCipherUtility.getCompatabilityKeySize(SSLCipherUtility.java:80)
    at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTTP.java:619)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:281)
    at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:285)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:281)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:702)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:648)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:53:58 PM EST> <Error> <HTTP> <BEA-101083> <Connection failure.
    java.lang.NullPointerException
    at weblogic.security.utils.SSLCipherUtility.getCompatabilityKeySize(SSLCipherUtility.java:80)
    at weblogic.servlet.internal.MuxableSocketHTTP.dispatch(MuxableSocketHTTP.java:619)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:281)
    at weblogic.socket.MuxableSocketDiscriminator.dispatch(MuxableSocketDiscriminator.java:285)
    at weblogic.socket.SSLFilter.dispatch(SSLFilter.java:281)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:702)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:648)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:123)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)
    at weblogic.socket.SocketMuxer.closeSocket(SocketMuxer.java:287)
    at weblogic.socket.SocketMuxer.cleanupSocket(SocketMuxer.java:625)
    at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:589)
    at weblogic.socket.SocketMuxer.deliverHasException(SocketMuxer.java:541)
    at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:125)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <avalable(): 15551322 : 0 + 501 = 501>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read(offset=0, length=501)>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 SSL3/TLS MAC>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15607581 received APPLICATION_DATA: databufferLen 0, contentLength 460>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read databufferLen 460>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <15551322 read A returns 460>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <write ALERT, offset = 0, length = 2>
    <Dec 5, 2005 8:53:58 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.removeContext(ctx): 770107>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 7470368>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLSocket will be Muxing>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <1759783 SSL3/TLS MAC>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <1759783 received ALERT>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
    at com.bea.sslplus.CerticomSSLContext.forceHandshakeOnAcceptedSocket(Unknown Source)
    at weblogic.security.utils.SSLContextWrapper.forceHandshakeOnAcceptedSocket(SSLContextWrapper.java:128)
    at weblogic.t3.srvr.SSLListenThread$1.execute(SSLListenThread.java:484)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <Alert received from peer, notifying peer we received it: com.certicom.tls.record.alert.Alert@e83a99>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <CLOSE_NOTIFY received from peer, closing connection: >
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <close(): 6234268>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
    at com.bea.sslplus.CerticomSSLContext.forceHandshakeOnAcceptedSocket(Unknown Source)
    at weblogic.security.utils.SSLContextWrapper.forceHandshakeOnAcceptedSocket(SSLContextWrapper.java:128)
    at weblogic.t3.srvr.SSLListenThread$1.execute(SSLListenThread.java:484)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <write ALERT, offset = 0, length = 2>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.removeContext(ctx): 7470368>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:02 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.removeContext(ctx): 7470368>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <Filtering JSSE SSLSocket>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.addContext(ctx): 22406146>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLSocket will be Muxing>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <24113997 SSL3/TLS MAC>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <24113997 received ALERT>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
    at com.bea.sslplus.CerticomSSLContext.forceHandshakeOnAcceptedSocket(Unknown Source)
    at weblogic.security.utils.SSLContextWrapper.forceHandshakeOnAcceptedSocket(SSLContextWrapper.java:128)
    at weblogic.t3.srvr.SSLListenThread$1.execute(SSLListenThread.java:484)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <Alert received from peer, notifying peer we received it: com.certicom.tls.record.alert.Alert@ce4f39>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <CLOSE_NOTIFY received from peer, closing connection: >
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <close(): 11754736>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <NEW ALERT with Severity: WARNING, Type: 0
    java.lang.Exception: New alert stack
    at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handle(Unknown Source)
    at com.certicom.tls.record.alert.AlertHandler.handleAlertMessages(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
    at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
    at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
    at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
    at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
    at javax.net.ssl.impl.SSLSocketImpl.startHandshake(Unknown Source)
    at com.bea.sslplus.CerticomSSLContext.forceHandshakeOnAcceptedSocket(Unknown Source)
    at weblogic.security.utils.SSLContextWrapper.forceHandshakeOnAcceptedSocket(SSLContextWrapper.java:128)
    at weblogic.t3.srvr.SSLListenThread$1.execute(SSLListenThread.java:484)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <write ALERT, offset = 0, length = 2>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.removeContext(ctx): 22406146>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <isMuxerActivated: false>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLFilter.isActivated: false>
    <Dec 5, 2005 8:54:10 PM EST> <Debug> <TLS> <000000> <SSLIOContextTable.removeContext(ctx): 22406146>
    ================

    The problem was due to the fact that the client application was using the new AES128 SSL ciphersuites, which are not supported in SP3/SP4. Here's BEA support's response:
    The following are the ssl cipher suite supported by weblogic server 8.1 sp4
    TLS_RSA_WITH_RC4_128_SHA
    TLS_RSA_WITH_RC4_128_MD5
    TLS_RSA_WITH_DES_CBC_SHA
    TLS_RSA_EXPORT_WITH_RC4_40_MD5
    TLS_RSA_EXPORT_WITH_DES40_CBC_SHA
    TLS_RSA_WITH_3DES_EDE_CBC_SHA
    TLS_RSA_WITH_NULL_SHA
    TLS_RSA_WITH_NULL_MD5
    TLS_RSA_WITH_NULL_MD5
    TLS_RSA_EXPORT124_WITH_RC4_56_SHA
    Support has been added for the following two AES cipher suites in WLS 8.1 SP5
    TLS_RSA_WITH_AES_128_CBC_SHA
    TLS_RSA_WITH_AES_256_CBC_SHA
    In order to use TLS_RSA_WITH_ AES_ 256_CBC_SHA cipher suite, you need you install JCE unlimited strength jurisdiction policy files instead of the policy files that are shipped with the JDK by default The jurisdiction files can be found at <http://java.sun.com/products/jce/index-14.html>
    Only TLS_RSA_WITH_AES_256_CBC_SHA requires the judisdiction files. TLS_RSA_WITH_AES_128_CBC_SHA does not
    --------

  • Agentry: SSL Error - broken pipe

    Hi,
    We have a work manager 5.2 modified version running on our production environment and lately we are experiencing some weird errors when the users try to synchronize.
    Sometimes (maybe 50% of the attempts...) the synchronization process is stuck and the client doesn't show any error at all. It's just waiting while loading a complex table, replacing definitions or anything, but never finishing. Inspecting the server logs I've seen that the error that seems to cause this issue is the following:
    2014/04/10 14:22:57.203:       + ANGEL Connection=XXX.XX.XXX.XXX:XXXXX
    2014/04/10 14:22:57.203:         + ANGEL Vine=1848370469
    2014/04/10 14:22:57.203:           + User=XXXXX
    2014/04/10 14:22:57.203:             + Server=Agentry
    2014/04/10 14:22:57.203:               + Complex Table=ctmaterialstoragelocation
    2014/04/10 14:22:57.203:                 + User=XXXXX
    2014/04/10 14:22:57.203:                   + ANGEL Vine=1848370469
    2014/04/10 14:22:57.203:                     + ANGEL Connection=XXX.XX.XXX.XXX:XXXXX
    2014/04/10 14:22:57.203:                       + Data Chunk=0
    2014/04/10 14:22:57.203:                         SSL error: error:2007107C:BIO routines:BIO_write:broken pipe
    This time it happened while loading the complex table ctmaterialstoragelocation but it's just an example. It can happen in any other step.
    Do you think that this error is really related to SSL? I think it's not and my guess is that something is wrong with the network and the connection is broken but I don't know how to be sure about the root cause of the issue. Any clues that could help me?
    Thank you.
    Tags edited by: Michael Appleby

    Hi,
    I'm going to close this thread since I discovered that the issue is due to my company network problem.
    We haven't found the root cause, but after many attempts testing from my home wifi I don't face the problem, so it is not caused by the Agentry Server.

Maybe you are looking for