Help ! Fatal Alert !

I own a Tungsten E2. My Operating system is Windows 2000.
This morning, my Tungsten would not start : total black-out.
I pressed the reset button, and got the following message, and everything is blocked :
Fatal Alert
MemoryMgr.c, Line:3732, NULL handle
Can anyone tell me how to restart ?
Thanks in adavance.
Xavier
Post relates to: Tungsten E2

Sounds like you're going to have to Hard Reset the unit. Unfortunately, this will erase all the data from it, and it will reinstall all the programs that it came with "out of the box".
Hopefully you have been doing regular HotSyncs to your computer and been backing up your data.
To perform a Hard Reset: (Palm Knowledgebase article #887)
While pressing and holding the Power button down, tap and release the Reset button in back and continue to hold the Power button down. When the grey Palm logo appears, you can release the Power button.
You should now see the warning page in about 5 languages. Press the UP direction on the 5-way pad to complete the task. Your Palm will reset itself several times as it re-installs the original programs and erases all your previous data.
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Similar Messages

HELP received a FATAL ALERT

I've just did a sync on my palm I was adding an excel file and first it came up as a locked file. I removed said filed and attempted to add a modified version of this said file. (was told some formula's were not supported)
So after doing the second sync. I went to my documents on my Palm Tungsten E2 and now I get a black boxs
Fatal Alert
MemoryMgr.c,Line:3751, Free handle
I've done a few soft reset. And will remove said warning but the minute I try to go into the documents it freezes.
Even now I dd yet another sync to remove all the files I added today, and still get the same warning.
Post relates to: Tungsten E2

Are you sync'ing the excel file over to the handheld again? This may be causing the error.
The next step is to hard reset and rename the backup folder on your PC.
Go to http://www.palm.com/cgi-bin/cso_kbURL.cgi?ID=887 and follow the directions to do a hard reset. Next before you hotsync your data back over you will need to rename your backup folder, to do that go here;
XP
C:\program files\palm or palm one\[hotsync username]\ and rename your backup
folder to backup.old
Vista
Start-->documents\Palm OS Desktop\[hotsync username]\ and rename your backup
folder to backup.old
Then hotsync to your current hotsync name and all your contacts, calendar,
tasks, and memos will come back over.
Show file extensions for XP or Vista
XP
If you can not view file extensions on your PC I would like you to open a
folder go to Tools-->Folder Options--> View (tab) and under show hidden
files and folders uncheck hide file extensions for known file types.
Vista
Open control Panel go to Folder Options--> View (tab) and under show hidden
files and folders uncheck hide file extensions for known file types.

Https Issue:SSLHandshakeException:Received fatal alert:bad_certificate

hi experts,
My scenario is Proxy to AS2. In AS2 receiver I have https protocol. I have put SSL Certificate(keystore) value.
Let say
View- x
Certificate name- cer
then I have given
TRUSTED\x\cer
in SSL Certificate(keystore) field of AS2 receiver channel.
Let me know weather it is correct.
Second field in Communication channel is "Private key for Client Authentication". I have kept it as blank.
I am getting an error in AS2 Receiver Channel saying:-
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIRecoverableException: SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate # , SEEBURGER AS2: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate #
My certificate has not expired yet.
Please help me in this matter.
Thanks
Jaideep

hi experts,
Please look into the below matter and help me to resolve it.
Thanks
Jaideep

SSL: Received fatal alert: certificate_unknown Problem

Hi all, first I read this thread http://forums.sun.com/thread.jspa?threadID=5385002 but I didnt help me so i startad a new one.
I´m doing a client, server and thread implementation with ssl, i copied certifcates and keystores on the directories and so on.
Here is the error on the server, just when a client conects:
javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown
     at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
     at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
     at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
     at com.sun.net.ssl.internal.ssl.AppInputStream.read(Unknown Source)
     at java.io.ObjectInputStream$PeekInputStream.read(Unknown Source)
     at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source)
     at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source)
     at java.io.ObjectInputStream.readStreamHeader(Unknown Source)
     at java.io.ObjectInputStream.<init>(Unknown Source)
     at org.tockit.comunication.ServerThread.run(ServerThread.java:55)
     at java.lang.Thread.run(Unknown Source)Here is the code of the client, server and server thread, i cant find the error as i follow some tutorials and it worked:
import java.io.BufferedReader;
import java.io.FileOutputStream;
import java.io.IOException;
import java.io.InputStreamReader;
import java.io.ObjectInputStream;
import java.io.ObjectOutputStream;
import java.net.Socket;
import java.net.UnknownHostException;
import java.util.ArrayList;
import javax.net.ssl.SSLSocket;
import javax.net.ssl.SSLSocketFactory;
import citic.android.remoteir.ComConstants;
import citic.android.remoteir.SendMessage;
public class Client {
         public static void main(String[] args)
             // Se crea el cliente y se le manda pedir el fichero.
             Client cf = new Client();
             BufferedReader in = null;
             BufferedReader stdIn = new BufferedReader(new InputStreamReader(System.in));
             String userInput;
             cf.pide("rup", "localhost", 27960, 0, 20);
         public void pide(String query, String servidor, int puerto, int startIndex, int count)
             try
                 // Se abre el socket.
                  SSLSocketFactory sslsocketfactory = (SSLSocketFactory)SSLSocketFactory.getDefault();
                    SSLSocket socket = (SSLSocket)sslsocketfactory.createSocket(servidor,puerto);
                 ObjectOutputStream oos = new ObjectOutputStream(socket
                         .getOutputStream());
                 SendMessage mensaje = new SendMessage();
                 mensaje.queryTerms = query;
                 mensaje.startIndex = startIndex;
                 mensaje.count = count;
                 oos.writeObject(mensaje);
                 ObjectInputStream ois = new ObjectInputStream(socket
                         .getInputStream());
                 ComConstants mensajeRecibido;
                 Object mensajeAux;
                 String mensa = null;
                 do
                     mensajeAux = ois.readObject();
                     // Si es del tipo esperado, se trata
                     if (mensajeAux instanceof ComConstants)
                         mensajeRecibido = (ComConstants) mensajeAux;
                         System.out.println("Client has Search Results");
                         String test;
                         test = new String(
                                 mensajeRecibido.fileContent, 0,
                                 mensajeRecibido.okBytes);
                         if (mensa == null) {
                              mensa = test;
                         else {
                                mensa += test;
                         System.out.println("client mierda" + test);
                     } else
                         System.err.println("Mensaje no esperado "
                                 + mensajeAux.getClass().getName());
                         break;
                 } while (!mensajeRecibido.lastMessage);
                 SaxParser sap = new SaxParser(mensa);
                 ois.close();
                 socket.close();
             } catch (Exception e)
                 e.printStackTrace();
package org.tockit.comunication;
import java.io.*;
import java.net.*;
import java.security.KeyStore;
import javax.net.ssl.KeyManager;
import javax.net.ssl.KeyManagerFactory;
import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLServerSocket;
import javax.net.ssl.SSLServerSocketFactory;
import javax.net.ssl.SSLSocket;
public class Server {
     public static void main(String[] args) throws IOException {
             ServerSocket serverSocket = null;
             boolean listening = true;
             System.out.println("Indroduzca valor del puerto");
             InputStreamReader isr = new InputStreamReader(System.in);
             BufferedReader br = new BufferedReader (isr);
             int port;
             try
                  String texto = br.readLine();
                  int valor = Integer.parseInt(texto);
                  port = valor;
                  try {
                       System.setProperty("javax.net.ssl.keyStore","C:\\Program Files\\Java\\jre6\\bin\\remoteir.ks");
                         System.setProperty("javax.net.ssl.keyStorePassword","aquabona");
                         SSLServerSocketFactory sslServerSocketfactory = (SSLServerSocketFactory)SSLServerSocketFactory.getDefault();
                         SSLServerSocket sslServerSocket = (SSLServerSocket)sslServerSocketfactory.createServerSocket(port);
                         System.out.println("Arracando servidor en " + port);
                      while (listening){
                              SSLSocket cliente = (SSLSocket)sslServerSocket.accept();
                           System.out.println("Aceptado cliente");
                            Runnable nuevoServer = new ServerThread(cliente);
                            Thread hilo = new Thread(nuevoServer);
                            hilo.start();
                  } catch (IOException e) {
                      System.err.println("Could not listen on port:" + port);
                      System.exit(-1);
             catch (Exception e)
                 e.printStackTrace();
}The line at at org.tockit.comunication.ServerThread.run(ServerThread.java:55) is marked with ERRRROOOOOORRRRR and serverThread cod is posted on the fisrt reply post.
All this code works in absence of SSL (regular sockets).
I have another question related to the SSLSockets in the method of the serverThread, will my SSLSockets in the serverThread´s methods work to comunicate with other servers as i try to do?
Thanks!

And this is a method like the ones i asked on #1, sorry about this but i cant post more than 7500 characters
    private void enviaFicheroMultiple(String query, ObjectOutputStream oos, int startIndex, int count, ArrayList<String> ips, ArrayList<String> ports, SearcherValue value)
        try
             String finalString = "";
            String tempFinal = "";
             QueryWithResult[] outputLine;
             QueryWithResult[] finalResults = new QueryWithResult[1];
             Operations op = new Operations();
            boolean enviadoUltimo=false;
            ComConstants mensaje = new ComConstants();
            mensaje.queryTerms = query;
            outputLine = op.processInput(query, value);
                   int i = 0;
                   boolean firstRun = true;
                   while (i < ips.size()) {
                        String ip = ips.get(i);
                        int port = Integer.parseInt(ports.get(i));
                   try
                   SSLSocketFactory sslsocketfactory = (SSLSocketFactory)SSLSocketFactory.getDefault();
               SSLSocket socket = (SSLSocket)sslsocketfactory.createSocket(ip,port);
                 ObjectOutputStream ooos = new ObjectOutputStream(socket
                         .getOutputStream());
                 SendMessage message = new SendMessage();
                 message.numDoc = value.numDoc;
                 message.docFreq = value.docFreq;
                 message.queryTerms = query;
                 message.startIndex = startIndex;
                 message.count = count;
                 message.multiple = false;
                 message.ips = null;
                 message.ports = null;
                 message.value = true;
                 message.docFreq = value.docFreq;
                 message.numDoc = value.numDoc;
                 ooos.writeObject(message);
                 ObjectInputStream ois = new ObjectInputStream(socket
                         .getInputStream());
                 QueryWithResult[] qwr = (QueryWithResult[]) ois.readObject();
                 int size = qwr.length;
                 int num=0;
                 boolean kk = true;
                 int pos = 0;
                 if(firstRun) {
                      finalResults = new QueryWithResult[size];
                    finalResults = qwr;
                    System.out.println("lenght" + finalResults.length);
                } else {
                     QueryWithResult[] old = finalResults;
                     finalResults = new QueryWithResult[old.length + size];
                     int y =0;
                     while(y < old.length){
                          finalResults[y] = old[y];
                          y++;
                     int l = old.length;
                     int k = qwr.length;
                     while(l < finalResults.length){
                          finalResults[l] = qwr[0];
                          l++;
                 firstRun = false;
                 ois.close();
                 socket.close();
             } catch (Exception e)
                 e.printStackTrace();
             i++;
             QueryWithResult[] old = finalResults;
          finalResults = new QueryWithResult[old.length + outputLine.length];
          int y =0;
          while(y < old.length){
               finalResults[y] = old[y];
               y++;
          int l = old.length;
          int k = outputLine.length;
          while(l < finalResults.length){
               finalResults[l] = outputLine[0];
               l++;
                   XmlConverter xce = new XmlConverter(finalResults, startIndex, count);
                String serialized = xce.runConverter();
                   finalString = serialized + tempFinal;
                   finalString = finalString.trim();
                   System.out.println("Final String " + finalString);
                   byte mybytearray[] = finalString.getBytes();
                   ByteArrayInputStream byteArrayInputStream = new ByteArrayInputStream(mybytearray);
                BufferedInputStream bis = new BufferedInputStream(byteArrayInputStream);
            int readed = bis.read(mensaje.fileContent,0,4000);
            while (readed > -1)
                mensaje.okBytes = readed;
                if (readed < ComConstants.MAX_LENGTH)
                    mensaje.lastMessage = true;
                    enviadoUltimo=true;
                else
                    mensaje.lastMessage = false;
                oos.writeObject(mensaje);
                if (mensaje.lastMessage)
                    break;
                mensaje = new ComConstants();
                mensaje.queryTerms = query;
                readed = bis.read(mensaje.fileContent);
            if (enviadoUltimo==false)
                mensaje.lastMessage=true;
                mensaje.okBytes=0;
                oos.writeObject(mensaje);
            oos.close();
        } catch (Exception e)
            e.printStackTrace();
    }

Why get "fatal alert: bad_certificate" but "certificate_expired"

Hi all,
I am testing 2 way SSL authentication now.
Expected Result:
When the client side provides a expired client cert to the server during handshaking, the server is supposed to return fatal alert: certificate_expired, which is exactly the client side wanna receive.
Acturally Result:
At first, I test server side with Tomcat, but the coming out result is that server will reject the connection with fatal alert: certificate_unknown.
Then, I try Weblogic. From Weblogic, I can see the warn:
<Nov 16, 2007 3:31:01 PM GMT+08:00>
<Warning><Security><BEA-090479>
<Certificate chain received from 206.225.50.35 - 206.225.50.35 failed date validity checks.>
But the client side will receive fatal alert : bad_certificate.
Any solution to get the expected response from server with fatal alert: certificate_expired?
Your help are appreciated!

Hi all,
I am testing 2 way SSL authentication now.
Expected Result:
When the client side provides a expired client cert to the server during handshaking, the server is supposed to return fatal alert: certificate_expired, which is exactly the client side wanna receive.
Acturally Result:
At first, I test server side with Tomcat, but the coming out result is that server will reject the connection with fatal alert: certificate_unknown.
Then, I try Weblogic. From Weblogic, I can see the warn:
<Nov 16, 2007 3:31:01 PM GMT+08:00>
<Warning><Security><BEA-090479>
<Certificate chain received from 206.225.50.35 - 206.225.50.35 failed date validity checks.>
But the client side will receive fatal alert : bad_certificate.
Any solution to get the expected response from server with fatal alert: certificate_expired?
Your help are appreciated!

Got SSLKeyException:FATAL Alert:BAD_CERTIFICATE using weblogic ws test tool

Hi,
Iam trying to test the webservices using the WebLogic Webservice standard testing home page. The services work fine without SSL, but if the server is setup to use SSL, I get a BAD CERTIFICATE exception using the testing home page.
Although, when I invoke the services through a different SOAP client they do work with SSL turned on provided I import the trusted ca (using my own certificate authority) to java cacerts file.
I set up the custom trust and identity keystores and Iam using my own trusted authority. Configured the SSL as detailed in
http://e-docs.bea.com/wls/docs81/secmanage/ssl.html
Is this a bug related to WebLogic Webservice testing home page or am I missing something. Any help will be greatly appreciated.
Thanks
Veena.
weblogic.webservice.tools.wsdlp.WSDLParseException: Failed to retrieve WSDL from https://raiders.fgm.com:7002/searchservice/SearchService?WSDL. Please check the URL and make sure that it is a valid XML file [javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.] at weblogic.webservice.tools.wsdlp.DefinitionFactory.createDefinition(Ljava.lang.String;)Lweblogic.xml.xmlnode.XMLNode;(DefinitionFactory.java:151) at weblogic.webservice.tools.wsdlp.WSDLParser.(Ljava.lang.String;)V(WSDLParser.java:76) at weblogic.webservice.WebServiceFactory.createFromWSDL(Ljava.lang.String;Ljava.lang.String;Ljavax.xml.rpc.encoding.TypeMappingRegistry;)Lweblogic.webservice.WebService;(WebServiceFactory.java:108) at weblogic.webservice.WebServiceFactory.createFromWSDL(Ljava.lang.String;Ljavax.xml.rpc.encoding.TypeMappingRegistry;)Lweblogic.webservice.WebService;(WebServiceFactory.java:84) at weblogic.webservice.server.servlet.ServletBase.invokeOperation(Ljava.lang.String;Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;Ljavax.xml.rpc.encoding.TypeMappingRegistry;Lweblogic.webservice.Operation;)V(ServletBase.java:295) at weblogic.webservice.server.servlet.WebServiceServlet.invokeOperation(Ljava.lang.String;Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;Ljavax.xml.rpc.encoding.TypeMappingRegistry;Lweblogic.webservice.Operation;)V(WebServiceServlet.java:343) at weblogic.webservice.server.servlet.ServletBase.handleGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;Lweblogic.webservice.WebService;)V(ServletBase.java:266) at weblogic.webservice.server.servlet.ServletBase.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ServletBase.java:158) at weblogic.webservice.server.servlet.WebServiceServlet.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(WebServiceServlet.java:254) at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3661) at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630) at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178) at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)

Thank You Prasanna for your response.
I converted the trusted CA cert to PEM format and copied it to the domain directory and restarted the weblogic server after setting the following properties weblogic.webservice.client.ssl.strictcertchecking=false
weblogic.security.SSL.ignoreHostnameVerification=true
But, Iam still getting the BAD certificate exception.
Thanks
Veena.

Getting error in OSB :: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received..

Hi There,
am getting error when invoking a webservice from OSB .
"The invocation resulted in an error: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received..".
certs were loaded to the trust store and could see certificates in Trust store.
surprisingly, same webservice works from SOA BPEL and even from soapUI.
I even made Host Name verification to NONE... none of those helped.
your suggestions are very much appreciated.
Thanks,
Karthik.

Enable -Dssl.debug=true java option and capture the logs.
You might find this userful
http://weblogic-wonders.com/weblogic/2010/01/28/troubleshooting-ssl-issues/

FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was receiv

I am trying to invoke a third part web-service (EDC RAVE) through the Oracle Service Bus/Weblogic Server. However whenever I try to use a business service to connect I get the following error message:
The invocation resulted in an error: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received..
I have tried to add the certificate to the set of trusted demo certificates but that doesn't seem to have solved the problem. Does anyone know how to resolve the problem?
The only solution I have found is:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/webserv/trouble.html#1071057
But I am using 10.3, not 8.1.

Hi,
I am getting the same error while invoking a Rave webservice from ALSB or from a web application hosted on weblogic 10.3.
I have tried first two of the options below, still got the same execption:
1) Disable host name verification ( never a pleasant thought )
2) Write your own custom hostname verification
3) Ask them to get a cert specific to their host ( with a CN of "someserver.mdsol.com, for instance ).
3rd one is not an option for us, as Medidata does not want to do any change in their setup or to obtain new certificate with CN specific to their host.
After troubleshooting for several days I am out of ideas. Would appreciate if someone helps me on this.
Some further details:
The Rave server presents a wildcard certificate with CN as *.mdsol.com. I have imported all the certificates in the chain to the trust store.
Configured the trust store in weblogic and disabled host name verification.
I have enabled the ssl debug, when i invoke Rave webservice, getting the following errors :
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Use Certicom SSL with Domestic strength>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.6 for algorithm HmacSHA1>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacSHA1>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.6 for algorithm HmacMD5>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacMD5>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE KeyAgreement: SunJCE version 1.6 for algorithm DiffieHellman>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Will use default KeyAgreement for algorithm DiffieHellman>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Will use default KeyAgreement for algorithm ECDH>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm DESede/CBC/NoPadding>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm DES/CBC/NoPadding>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm AES/CBC/NoPadding>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RC4>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSL Session TTL :90000>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSL enableUnencryptedNullCipher= false>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSLContextManager: loading server SSL identity>
<Aug 29, 2010 8:05:18 PM IST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias usadc-vsedc35.quintiles.
net from the JKS keystore file C:\eDC-ODM\Beta\ssl\wls\dev1\WLS1\keystore\edc_server.jks.>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Loaded public identity certificate chain:>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=usadc-vsedc35.quintiles.net, OU=Global Solutions, O=Quintiles, L=Morrisville, ST=NC, C=US; Issuer: CN=USKAN-SECSA01, DC=quintiles, DC=net>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=USKAN-SECSA01, DC=quintiles, DC=net; Issuer: CN=uskan-secs02, DC=quintiles, DC=net>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=uskan-secs02, DC=quintiles, DC=net; Issuer: CN=uskan-secs02, DC=quintiles, DC=net>
<Aug 29, 2010 8:05:18 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Aug 29, 2010 8:05:20 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the JKS keystore file C:\eDC-ODM\Beta\ssl\alsb\truststore\pftrust.jks.>
<Aug 29, 2010 8:05:20 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSLContextManager: loaded 4 trusted CAs from C:\eDC-ODM\Beta\ssl\alsb\truststore\pftrust.jks>
<Aug 29, 2010 8:05:20 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=ca.webcrf.net, OU=IAS Engineering, O=Phase Forward, L=Waltham, ST=Massachusetts, C=US; Issuer: CN=ca.webcrf.net, OU=IAS Engineering, O=Phase Forward, L=Waltham, ST=Massachusetts, C=US>
<Aug 29, 2010 8:05:20 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US; Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US>
<Aug 29, 2010 8:05:20 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: CN=*.mdsol.com, OU=Domain Control Validated, O=*.mdsol.com; Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US>
<Aug 29, 2010 8:05:20 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Subject: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale, ST=Arizona, C=US; Issuer: OU=Go Daddy Class 2 Certification Authority, O="The Go Daddy Group, Inc.", C=US>
<Aug 29, 2010 8:05:20 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Failed to load server trusted CAs
java.security.cert.CertificateParsingException: Could not set value for ASN.1 string object.
at com.certicom.security.cert.internal.x509.X509V3CertImpl.<init>(Unknown Source)
at com.certicom.tls.interfaceimpl.CertificateSupport.addTrustedCertificate(Unknown Source)
at com.certicom.net.ssl.SSLContext.addTrustedCertificate(Unknown Source)
at com.bea.sslplus.CerticomSSLContext.addTrustedCA(Unknown Source)
at weblogic.security.utils.SSLContextWrapper.addTrustedCA(SSLContextWrapper.java:62)
at weblogic.security.utils.SSLContextManager.createServerSSLContext(SSLContextManager.java:424)
at weblogic.security.utils.SSLContextManager.getDefaultServerSSLContext(SSLContextManager.java:318)
at weblogic.security.utils.SSLContextManager.getServerTrustedCAs(SSLContextManager.java:279)
at weblogic.security.utils.SSLSetup.getTrustedCAs(SSLSetup.java:438)
at weblogic.security.utils.SSLSetup.getSSLContext(SSLSetup.java:317)
at weblogic.security.SSL.SSLClientInfo.getSSLSocketFactory(SSLClientInfo.java:101)
at weblogic.security.SSL.SSLSocketFactory.setSSLClientInfo(SSLSocketFactory.java:218)
at weblogic.security.SSL.SSLSocketFactory.<init>(SSLSocketFactory.java:36)
at weblogic.security.SSL.SSLSocketFactory.getInstance(SSLSocketFactory.java:68)
at weblogic.net.http.HttpsClient.New(HttpsClient.java:561)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:242)
at com.sun.xml.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:133)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:140)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:86)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
at test.GetFromRWS.doGet(GetFromRWS.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3495)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Aug 29, 2010 8:05:22 PM IST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Aug 29, 2010 8:05:22 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 4106403>
<Aug 29, 2010 8:05:22 PM IST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Aug 29, 2010 8:05:22 PM IST> <Debug> <SecuritySSL> <BEA-000000> <write SSL_20_RECORD>
<Aug 29, 2010 8:05:22 PM IST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Aug 29, 2010 8:05:23 PM IST> <Debug> <SecuritySSL> <BEA-000000> <11680652 SSL3/TLS MAC>
<Aug 29, 2010 8:05:23 PM IST> <Debug> <SecuritySSL> <BEA-000000> <11680652 received HANDSHAKE>
<Aug 29, 2010 8:05:23 PM IST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Aug 29, 2010 8:05:23 PM IST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Aug 29, 2010 8:05:24 PM IST> <Debug> <SecuritySSL> <BEA-000000> <11680652 SSL3/TLS MAC>
<Aug 29, 2010 8:05:24 PM IST> <Debug> <SecuritySSL> <BEA-000000> <11680652 received HANDSHAKE>
<Aug 29, 2010 8:05:24 PM IST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Aug 29, 2010 8:05:24 PM IST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(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 com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:947)
at com.sun.xml.ws.transport.http.client.HttpClientTransport.checkResponseCode(HttpClientTransport.java:221)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:149)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:86)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.client.Stub.process(Stub.java:248)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
at test.GetFromRWS.doGet(GetFromRWS.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3495)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks 'n Regards,
Satya
Edited by: user10115986 on Aug 31, 2010 2:03 AM

SSLHandshakeException: Received fatal alert :handshake_failure

Hola forum,
I'm having a bit of a problem with ssl sockets currently. Please bear with me as this is my first run at using ssl sockets for anything and I've done a fair bit of searching on google already.
Here's the code I'm using:
(kindly ignore any typos as they are the result of having to manually type the code in - the code resides on a seperate system).
int port = 443;
String hostname = "hostname";
TrustManager[] trustAllCerts = new TrustManager[]{
   new X509TrustManager(){
      public void checkClientTrusted(X509Certificate[] arg0, String arg1) throws CertificateExcpetion{}
      public void checkServerTrusted(X509Certificate[] arg0, String arg1) throws CertificateException{}
      public X509Certificate[] getAcceptedIssuers(){
          return new X509Certificate[0];
SSLContext sslContext = SSLContext.getInstance("SSL");
sslContext.init(null, trustAllCerts, new SecureRandom());
SSLSocketFactory factory = sslContext.getSocketFactory();
SSLSocket socket = (SSLSocket)factory.getSocketFactory(hostname, port);
socket.setUseClientMode9true);
socket.startHandshake();
...this throws the following exception from startHandshake():
javax.net.ssl.SSLHandhakeException: Received fatal alert: handshake_failure
      at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
      at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(Unknown Source)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Uknown Source)
      at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
      at testcode.main(testcode.java 62)Any insight? I would be most appreciative. Thanks!

ejp thanks for the reply - unfortunately I have 0 control over the server that I am attempting to establish a connection to and I don't think I can get them to do much of anything (just getting their server certificate was some work).
Could this exception be caused by the server requiring client validation? I checked the various socket settings (forget the property names) but none of them indicated that client validation was required.
Let me know if just the debug on the client side would be helpful and I'll type it in.
--edit, alright here are what I think the relevant parts of the debugging info from the client side(bear with me as this has to be hand transcribed-). Please let me know if more is needed-
found key for : key alias
chain[0] = [
addiing as trusted cert:
adding as trusted cert:
trigger seeding of SecureRandom
done seeding SecureRandom
dexport control - checking the cipher suites
export control - no cached value available...
export control - storing legal entry into cache...
%% No cached client session
** ClientHello, TLSv1
RandomCookie:...
Session ID: {}
Cipher Suites: ...
Compression Methods: { 0 }
main, WRITE: TLSv1 Handshake. length = 73
main, WRITE: SSLv2 client hello message, length = 98
main, READ: TLSv1 Handshake, length = 74
***ServerHello, TSLv1
RandomCookie: ...
Cipher Suite: ...
COmpression Method: 0
%% Created: ...
**SSL_RSA_WITH_RC4_128_MD5
main, READ: TLSv1 Handshake, length = 2702
*** Certificate chain
chain [0] = ...
[2] : ...
[3] : ...
[4] : ...
[5] : ...
chain [1] = ...
[2] : ...
[3] : ...
[4] : ...
[5] : ...
chain[2] =...
[2]: ...
Found trusted certificate:
main, READ: TLSv1 Handshake, length = 278
*** CertificateRequest
Cert Types: RSA, DSS,
Cert Authorities:
*** ServerHelloDone
*** Certificate chain
*** ClientKeyExchange, RSA PreMasterSecret, TLSv1
Random Secret: ...
main, WRITE: TLSv! Handshake, length = 141
SESSION KEYGEN:
PreMaster Secret:
CONNECTION KEYGEN:
Client Nonce:
Server Nonce:
Master Secret:
Client MAC write Secret:
Server MAC write Secret:
Client write key:
Server write key:
...no IV for cipher
main, WRITe: TLSv1 Change Cipher spec, length = 1
*** Finished
verify_data: ...
main, WRITE: TLSv1 Handshake, length = 32
main, waiting for close_notify or alert: state 1
main, Exception while waiting for close java.net.SocketException: Software caused connection abort: recv failed main, handling exception: java.net.SocketException: Software caused connection abort: recv failed
java.net.SocketException: Software caused connection abort: recv failed
    at java.netSocketInputStream.socketRead0(Native Method)
    at java.net.SocketInputStream.read(Unknown Source)
    at com.sun.net.ssl.interal.ssl.InputRecord.readFully(Uknown Source)
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Unknown Source)
    at com.sun.net.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLCoketImpl.waitForClose(Unknown Source)
    at com.sun.net.ssl.internal.ssl.HanshakeOutStream.flush(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.sendChagneCipherSpec(Unknown Source)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.sendChangeCipherAndFInish(Unknown Source)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverHelloDone(Unknown Source)
    at com.sun.net.ssl.internal.ssl.CLientHandshaker.processMessage(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source)
    at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at com.sun.net.internal.ssl.SLSocketImpl.startHandshake(Unknown Source)
    at https.TestSSLSockets.main(TestSSLSockets.java:104)thanks again!
Message was edited by:
cjmose

Fatal Alert after Hard Reset

Hi,
I did a hard reset trying to eliminate a Fatal Error (MemoryMgr.c, Line3639, Non-word-align handle) on the Passwords Plus app..
After each Hard Reset Fatal Alert/Fatal Exception also appears when syncing with the Desktop or running BACK-UP MAN.
It seems that I need help!!
Tod
Post relates to: Tungsten T3

you could delete passwords plus from the backup folder (on desktop)
or you can do a selective restore in backupman
webosnation.com is another option for help.

SCHANNEL Fatal Alert:80 in Event Viewer

See a post in 2012 that tweaks the registry to set the alert to O thus eliminating the alert but it doesn't explain why it happens or whats causing it. On my machine it didn't start til Windows did the last .NET update leading me to believe that this is
the cause.
Hi,
Here’s workaround you can try:
Note: You’d better backup the registry before change it/
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]
"EventLogging"=dword:00000000
Value
Description
0x0000
          Do
not log
0x0001
          Log
error messages
0x0002
          Log
warnings
0x0004
          Log
informational and success events
There’s a similar website you can refer:
http://www.eventid.net/display-eventid-36887-source-Schannel-eventno-10676-phase-1.htm
Hope that helps.
It would be nice to see what is actually causing the error rather than 'toggling it off'. Searching Google there seems to be no definitive answer, just lists of different type
fatal errors
Here's the post that I've found relating to this on TechNet:-
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 80
BTW the Forum Selection doesn't list Windows7 and that is what I have. I choose one just to post

Windows Server 2012 R2 Hyper-V VM Fileserver.
Have these errors happening consistently in event viewer every 2 to 3 minutes.
Am not running web server, just a file server.
Any ideas on how to track this down?
Not seeing much info on 36887 with code "49"
Anyone else had/solved this problem?
This topic first appeared in the Spiceworks Community

Windows server 2008 R2: The following fatal alert was generated: 40. The internal error state is 1205.

On my app server which is win2008R2, no IIS installed, I kept getting these errors:
"The following fatal alert was generated: 40. The internal error state is 1205." - Event ID 36888
"An TLS 1.0 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed." - Event ID 36874
I did a few search on google but they mentioned about the SSL. However, my server has no SSL installed. We don't have a need to put SSL on the app server. Any help will very appreciated.
-vecon

Simply ignore the message then.
If you would like to investigate further, you will need to identify the source of the TLS connection. If this is not logged in event viewer then you could give a look to IIS logs or simply use a Network Sniffer like Wireshark to inspect the traffic.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Getting "Fatal Alert PUtils.h, Line 74, Invalid counter...

I have not clue what is going on. I have a Palm m515. I tried to contact the support over the phone but their accent is a lot worse than mine; I could not understand anything.
I have backed up the information, done a hard reset and still getting those messages.
I was planning to get another device, I would like to get the Palm Treo Pro, but I am very disappointed w/ the customer support that Palm has; probably the worse I ever seen.
I would very much appreciate any information you can give me about this. I heard there is a software that repairs corrupted files, or something like that. Let me know please. I really need my PDA!!
Thanks
Post relates to: Palm m515

I spent several hours today working on this deal. I did a hard reset. No problems.
Then I went to the address that you indicated. No back up folder.
I realized that the Palm folder stands alone as part of the "Presario" in the C: drive. After opening "Palm" several files opened:
PqiTemp, Add-on, components, helpnote, image Library, "Juan", etc., addcn30.dl, AlarmApp,e..., etc., Currency,ini....
There is one called "BAKCN20.DLL".. The last one on that group es zlib.dll
I opened each one, and in the "Juan" there are several others: address, archive, Backup, datebook, expense, install, mail, memopad, etc.
I opened the Backup, and has large number of files: Archimedes, Emer drugs, mathlib.prc, Med alert, etc.
Is this the one I have to rename? I want to make sure because there is another one in this group called "BackupBuddyVFS.PRC" I believed this is the one I bought following the recommendation of the company that produces one of the applications to back up all the files when I did the hard reset; so I would not lose any information...
I freaked out when I saw my empty Palm, so, I went to my external drive "E Book" that I bought also following recommendations of another software manufacturer and did not have problems in recovering the whole thing again, including the
ocassional "Fatal Alert PUtils., Line 74, invalid counter"... but at least I have all my bank accounts, and private information back on the PDA.
My questions are: Once I change the name of the back up folder to "backup.old". When I do a sync it will not recognize it any more?
I start downloading again all my programs one by one...the minute I get the Fatal Alert...that's it?
Can I delete the file that produced it, and the problem will be solved?
Worse case scenario? Do I have to get another PDA?
If I get a Palm Treo Pro, and I start loading my applications, how do I know I am not going to have the same problem? What do I do next?
I hope the questions are not to stupid but computers are not my thing. I really appreciate your help though!
Juan

Fatal Alert

We have been receiving this error message several times a day:
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 10. The Windows SChannel error state is 1203.
None of the Lync functionality seems to be effected it just looks to be an annoying error.
Has anyone seen this error and know how to stop it.

Sometimes the 1203s go hand in hand with 1205s.
Check out the following:
http://ucken.blogspot.com/2013/12/schannel-errors-on-lync-server.html
http://serverfault.com/questions/445426/lync-tls-event-36874-how-to-handle
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

ID: 36887; source: Schannel "fatal alert was recieved; 49"

at my eventlog i get only one error - the following error one:
"the following fatal alert was recieved; 49"
Log Name : System
Source: Schannel
Event ID: 36887
Level: Error
User: System
The notification comes irregularly over again
I did a some intensive research but I can't find hints for alert 49.
Anybody has a hint to solve the problem ?
_________________________________________________ assist others - and you can hope of help at self

Hi,
Thanks for posting in Microsoft TechNet forums.
I would appreciate if you can help clarify the following questions:
When did this issue begin to occur?
Have you experience any low performance since came across this event error?
Is this a client inside a domain?
Please refer to this thread,
it seems this issue have something to do with security software or exchange server related client.
At this point, I suggest we prepare
clean boot to test.
Best Regards
Magon Liu
TechNet Subscriber Support
in forum. If you have any feedback on our support, please contact
[email protected]
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Help ! Fatal Alert !

Similar Messages

Maybe you are looking for