Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text

Hi I am in trouble with JAX-WS 2.1.2M1
I try to call my Webservice like this:
Service service = Service.create(serviceName);
        service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, "http://spblue.liberty:8084/SPBlue/GlobalLogoutService");
Dispatch<SOAPMessage> disp = service.createDispatch(portName, SOAPMessage.class, Service.Mode.MESSAGE);
        SOAPMessage message = XmlUtil.getSOAPMessageFromString(request);
        SOAPMessage response = disp.invoke(message);when my disp invokes I get following Exception which seems to as a little Problem, anyway I don�t know how to get rid of this Exception.
com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]
at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:116)
at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:280)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:158)
at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:74)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:559)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:518)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:503)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:400)
at com.sun.xml.ws.client.Stub.process(Stub.java:234)
at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:166)
at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:192)
at test.service.Logout.requestLogout(Logout.java:115)
at test.service.Logout.main(Logout.java:149)
ERROR: JDWP Unable to get JNI 1.2 environment, jvm->GetEnv() return code = -2
JDWP exit error AGENT_ERROR_NO_JNI_ENV(183): [../../../src/share/back/util.c:820]
my ServiceClass is:
@ServiceMode(value=Service.Mode.MESSAGE)
@WebServiceProvider( targetNamespace="http://spblue.liberty:8084/wsdl/globalLogout")
public class GlobalLogoutServiceImpl implements Provider<SOAPMessage> {
     * Web service operation
    public SOAPMessage invoke( SOAPMessage logoutRequest ){
        return logoutRequest;
}So how can I set the Charachter set before invokikng the service.
Or how can I change the Service to accept UTF-8.
Well, I don�t know.
Any help is welcome.

Hi,
I don't know if this can help you, but I had a similar problem while invoking a web service. Eventually, I found out that the server was returning an html error page, and not the expected xml answer.
That's why the client code raises such an error... It means that the MIME type of the anser is text/html (for the html page) and not the text/xml type of the 'nominal' web service answer.
You can verify this by using a proxy to intercept the http request and answer involved in this web service invocation (use Fiddler for instance). Then, you will see that the server responds by sending an html page saying that something is wrong.
Hope this helps...
Sam

Similar Messages

  • Unsupported Content-Type: text/html; charset=iso-8859-1

    Originally posted on JBI forum -
    It was helpfully suggested there that I check on JAX-WS forum whether this was an issue with utf-8/16 encodings...
    I have been experimenting with the openESB composite application described here
    http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
    This works fine as it appears on this webpage.
    I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
    To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
    This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
    Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
    Thanks
    Joss Armstrong
    HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
    BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
    com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
    BPCOR-6129:Line Number is 29
    BPCOR-6130:Activity Name is Invoke1
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
    at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    *Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
    at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    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 com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

    Jossarm/Jeff,
    The Cryptography forum is not the right forum for this question; have you tried posting to the Glassfish forum on java.net?
    But, here is what I think the problem might be:
    SOAP-based web-service security uses XML Signature and XML Encryption to secure the message - not SSL; as a result it uses text/xml at the start of its message (which is what SOAP messages are). SSL assumes that the secure session has been established and all messages thereafter, are expected to begin with text/html (as expected in HTTP). You cannot mix-and match this - unless the service is an HTTP-based service that expects a SOAP-based message embedded in the HTTPRequest.

  • Unsupported Content-Type: text/html in JAX-WS

    Hi All,
    I was trying to add new WS client proxy using jdeveloper but it gives me some error:
    Exception in thread "main" com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html Supported ones are: [text/xml]
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:303)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:135)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:277)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:124)
    at com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:121)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
    at com.sun.xml.ws.client.Stub.process(Stub.java:272)
    at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
    at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
    at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
    at $Proxy28.lovQueryPage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
    at $Proxy29.lovQueryPage(Unknown Source)
    at com.siebel.asi.LS_spcClinical_spcList_spcOf_spcValue_spcServiceClient.main(LS_spcClinical_spcList_spcOf_spcValue_spcServiceClient.java:51)
    Strange thing is that, it works properly when a new client proxy is created in a new Application but it fails when I try to add second proxy to the application where first proxy is already added. Any pointers?
    Thanks,
    Nikunj

    How Can I make this work in the single project. Is there some alternate way to do so ?

  • Unsupported Content-Type: text/plain

    Hi everyone,
    I am trying to invoke an aync Oracle BPEL process from WLI 8.1.6, without worrying about the response / callback. The web service control that is generated shows the operation stub as public void receive (java.lang.String input); which makes sense since I don't want any response. When I invoke BPEL though, I get the following error in WLI:
    <Error> <WLW> <000000> <Failure=com.bea.control.ServiceControlException: SERVICE FAULT:
    Code:javax.xml.soap.SOAPException
    String:Unsupported Content-Type: text/plain
    Detail:
    END SERVICE FAULT [ServiceException]>
    There shouldn't be any response though, so how can I tell WLI to ignore what (doesn't) come back? When I check BPEL, the request is successfully received and the BPEL process completes successfully.
    Thanks,
    Nicholas

    By default, getContent() will return decoded text. But,some mail server will put 8bits instead of 8bit. Javamail will throw exception when encoding is "8bits". In that case, you will have to decode the message by yourself, force using "8bit".
    Part 2 & 3 of the problem - it is not able to find the character set support.

  • Unsupported Content-Type

    I have been experimenting with the openESB composite application described here
    http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
    This works fine as it appears on this webpage.
    I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
    To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
    This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
    Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
    Thanks
    Joss Armstrong
    HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
    BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
    com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
    BPCOR-6129:Line Number is 29
    BPCOR-6130:Activity Name is Invoke1
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
    at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    *Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
    at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    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 com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    Edited by: jossarm on May 19, 2008 9:37 AM

    Hi,
    You may want to post this question on JAX-WS forum as well. If I remember it correctly, JAX-WS currently supports only utf-8 and urf-16 encodings.
    But checking with the JAX-WS team would definitely clear this up...
    Regards
    --Sherry                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Sharepoint error - Search Issue - The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1).

    i see this error everywhere - In ULS logs, on site. On the site > Site settings > search keywords; I see this - 
    The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>IIS 7.0 Detailed Error - 500.19 - Internal Server Error</title> <style type="text/css"> <!-- body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;} code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;} .config_source code{font-size:.8em;color:#000000;} pre{margin:0;font-size:1.4em;word-wrap:break-word;} ul,ol{margin:10px 0 10px 40px;} ul.first,ol.first{margin-top:5px;} fieldset{padding:0 15px 10px 15px;} .summary-container fieldset{padding-bottom:5px;margin-top:4px;} legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;} legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px; border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696; border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;'.
    I am facing issues in searching, my managed metadata service is not running, search results page throws internal error. Any Idea why this above error comes.
    P.S: We use windows authentication in our environment.

    Hi IMSunny,
    It seems you have solved this issue based on your another post.
    http://social.technet.microsoft.com/Forums/en-US/aa468ab0-1242-4ba8-97ea-1a3eb0c525c0/search-results-page-throws-internal-server-error?forum=sharepointgeneralprevious
    Thanks
    Daniel Yang
    TechNet Community Support

  • WCF returning "The content type text/html of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8)"

    I have a WCF service I am trying to run on a new installation of 64-bit Windows Server 2008 IIS. Although it runs fine on Windows 2003 IIS, it is throwing the error in the thread title, which appears to be a server config issue, but I am not sure. Googling and searching the MSDN forums did not turn up a solution. I tried running WCF Logging, but that didn't help either.
    Does anyone have any suggestions on how to solve this probelm?
    Here is the error:
    The content type text/html of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
    <title>500 - Internal server error.</title>
    <style type="text/css">

    I have the same issue on Windows 7 machine. The service works fine using a SoapUI client but a .Net client faisl to get a response.
    Hi,
    I have a WCF service which works perfectly when using SoapUI but throws error in my .Net client.
    {"The content type text/html; charset=UTF-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first
    1024 bytes of the response were: '<HTML><HEAD><link rel=\"alternate\" type=\"text/xml\" href=\"http://xyz.mysite.com/ysa/Broker.svc?disco\"/><STYLE type=\"text/css\">#content{ FONT-SIZE: 0.7em;
    PADDING-BOTTOM: 2em; MARGIN-LEFT: 30px}BODY{MARGIN-TOP: 0px; MARGIN-LEFT: 0px; COLOR: #000000; FONT-FAMILY: Verdana; BACKGROUND-COLOR: white}P{MARGIN-TOP: 0px; MARGIN-BOTTOM: 12px; COLOR: #000000; FONT-FAMILY: Verdana}PRE{BORDER-RIGHT: #f0f0e0 1px solid; PADDING-RIGHT:
    5px; BORDER-TOP: #f0f0e0 1px solid; MARGIN-TOP: -5px; PADDING-LEFT: 5px; FONT-SIZE: 1.2em; PADDING-BOTTOM: 5px; BORDER-LEFT: #f0f0e0 1px solid; PADDING-TOP: 5px; BORDER-BOTTOM: #f0f0e0 1px solid; FONT-FAMILY: Courier New; BACKGROUND-COLOR: #e5e5cc}.heading1{MARGIN-TOP:
    0px; PADDING-LEFT: 15px; FONT-WEIGHT: normal; FONT-SIZE: 26px; MARGIN-BOTTOM: 0px; PADDING-BOTTOM: 3px; MARGIN-LEFT: -30px; WIDTH: 100%; COLOR: #ffffff; PADDING-TOP: 10px; FONT-FAMILY: Tahoma; BACKGROUND-COLOR: #003366}.intro{MARGIN-LEFT: -15px}</STYLE><TITLE>Broker
    Service</TITLE></HEAD><BODY><DIV id=\"content\"><P class=\"head'."}
    I have the same service hosted on my local machine and when I point to the local service I can execute the operation with no issues. The message encoding is Soap11. I tried changing to Soap12 but I get exact same error. Any ideas greatly appreciated.
    I do have windows Activation Features installed and I am using .Net Framework 4.
    Thanks
    Sofia Khatoon

  • How to  get rid of "Content-type: text/html; charset=UTF-8 Set-Cookie..." ?

    Hi
    I have several applications and I am working on making some kind of APEX "SSO".
    An user is authentified in one application. Then he may go to another application. The cookie has the same name from one application to another. The session ID is preserved from one application to another : i use this kind of URL : "f?p=109:1:&SESSION.:"
    I have seen that I need to authentify automatically the user when he swap to another application. For that i have a process in the welcome page that authentify the user, using the :app_user and the password, a PL/SQL after header:
    wwv_flow_custom_auth_std.login(
        P_UNAME       => :APP_USER,
        P_PASSWORD    => :P1_PASSWORD,
        P_SESSION_ID  => v('APP_SESSION'),
        P_FLOW_PAGE   => :APP_ID||':1'
        );So far so good. User is authenticated. The problem I face is that this message appears :
    Content-type: text/html; charset=UTF-8 Set-Cookie: TELEGESTION_AUTH=-1; path=/; Location: /pls/apex/f?p=109:1How to get rid of this message ?
    Thank you for your kind help !
    Christian
    PS: My question has not been answered... I hope somebody could help me on this topic.
    Edited by: Christian from France on Mar 4, 2010 2:02 AM

    Hi
    Have you tried using "f?p=109:1:&APP_SESSION.:" instead of "f?p=109:1:&SESSION.:".
    I don't see why you need to reauthenticate if they're in the same workspace?
    Cheers
    Ben

  • "Content-type: text/html; charset=utf-8 cache-control: no-cache..." display

    "Content-type: text/html; charset=utf-8 cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache X-Frame-Options: DENY "
    is being displayed at the top of one of our pages now. I can see that line in the body section of the page using Firebug, but can't find what is creating it there.
    Does anyone have any tips on how I would go about finding something like this?
    The page was using a custom theme but that stopped working when we upgraded to 4.1. So, I copied the Simple Green template to start modifying.
    Mentioning that in case it's relevant...
    Thanks!

    LauraC wrote:
    "Content-type: text/html; charset=utf-8 cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache X-Frame-Options: DENY "Looks like an HTTP header...
    is being displayed at the top of one of our pages now. I can see that line in the body section of the page using Firebug, but can't find what is creating it there.
    Does anyone have any tips on how I would go about finding something like this?If it's included within the <tt>body</tt> element in the original page source then it's produced by something in APEX and the position in the source will give a clue as to where. You should also run the page in Debug mode and look at the trace to see if there's any clues there.
    If it's visible in the generated page source but not the original then it's produced by something dynamic in the page. Possibly some JS lingering from the previous theme?

  • Unsupported response content type "text/html", must be: "tex

    Hi Gurus,
    I'm trying to access a WebService (http://200.68.11.21/WebServices/RecibeMsgSoapISP.wsdl), but I've been facing the following problem below. Could anybody help me?
    //****************************** MY CODE
    FileInputStream file = new FileInputStream("c:\\EXE\\deuda2.xml");
    byte[] bytes = new byte[file.available()];
    file.read(bytes);
    String xml = new String(bytes);
    System.out.println("Xml:\n" + xml);
    URL endPoint =
    new URL(
    "http://200.68.11.21/WebServices/RecibeMsgSoapISP.wsdl");
    Call call = new Call();
    SOAPTransport m_httpConnection =
    new org.apache.soap.transport.http.SOAPHTTPConnection();
    call.setSOAPTransport(m_httpConnection);
    call.setTargetObjectURI("urn:RecibeMsgSoapIsp");
    call.setMethodName("RecibeM2TGR");
    call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
    //SOAPTransport st = new SOAPHTTPConnection();
    //call.setSOAPTransport(st);
    Vector params = new Vector();
    params.addElement(new Parameter("StrXml", String.class, xml, null));
    call.setParams(params);
    //call.setHeader();
    Response response = call.invoke(endPoint, "");
    Parameter result = response.getReturnValue();
    System.out.println("result:" + result);
    //****************************** MY EXCEPTION
    [SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type "text/html", must be: "text/xml". Response was:
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
    <html dir=ltr>
    <head>
    <style> a:link               {font:8pt/11pt verdana; color:FF0000} a:visited          {font:8pt/11pt verdana; color:#4e4e4e}
    </style>
    <META NAME="ROBOTS" CONTENT="NOINDEX">
    <title>No se puede mostrar la p&aacute;gina</title>
    <META HTTP-EQUIV="Content-Type" Content="text-html; charset=Windows-1252">
    </head>
    <script>
    function Homepage(){
    <!--
    // in real bits, urls get returned to our script like this:
    // res://shdocvw.dll/http_404.htm#http://www.DocURL.com/bar.htm
         //For testing use DocURL = "res://shdocvw.dll/http_404.htm#https://www.microsoft.com/bar.htm"
         DocURL=document.URL;
         //this is where the http or https will be, as found by searching for :// but skipping the res://
         protocolIndex=DocURL.indexOf("://",4);
         //this finds the ending slash for the domain server
         serverIndex=DocURL.indexOf("/",protocolIndex + 3);
         //for the href, we need a valid URL to the domain. We search for the # symbol to find the begining
         //of the true URL, and add 1 to skip it - this is the BeginURL value. We use serverIndex as the end marker.
         //urlresult=DocURL.substring(protocolIndex - 4,serverIndex);
         BeginURL=DocURL.indexOf("#",1) + 1;
         urlresult=DocURL.substring(BeginURL,serverIndex);
         //for display, we need to skip after http://, and go to the next slash
         displayresult=DocURL.substring(protocolIndex + 3 ,serverIndex);
         InsertElementAnchor(urlresult, displayresult);
    function HtmlEncode(text)
    return text.replace(/&/g, &apos;&amp&apos;).replace(/&apos;/g, &apos;&quot;&apos;).replace(/</g, &apos;&lt;&apos;).replace(/>/g, &apos;&gt;&apos;);
    function TagAttrib(name, value)
    return &apos; &apos;+name+&apos;="&apos;+HtmlEncode(value)+&apos;"&apos;;
    function PrintTag(tagName, needCloseTag, attrib, inner){
    document.write( &apos;<&apos; + tagName + attrib + &apos;>&apos; + HtmlEncode(inner) );
    if (needCloseTag) document.write( &apos;</&apos; + tagName +&apos;>&apos; );
    function URI(href)
    IEVer = window.navigator.appVersion;
    IEVer = IEVer.substr( IEVer.indexOf(&apos;MSIE&apos;) + 5, 3 );
    return (IEVer.charAt(1)==&apos;.&apos; && IEVer >= &apos;5.5&apos;) ?
    encodeURI(href) :
    escape(href).replace(/%3A/g, &apos;:&apos;).replace(/%3B/g, &apos;;&apos;);
    function InsertElementAnchor(href, text)
    PrintTag(&apos;A&apos;, true, TagAttrib(&apos;HREF&apos;, URI(href)), text);
    //-->
    </script>
    <body bgcolor="FFFFFF">
    <table width="410" cellpadding="3" cellspacing="5">
    <tr>
    <td align="left" valign="middle" width="360">
         <h1 style="COLOR:000000; FONT: 13pt/15pt verdana"><!--Problem-->No se puede mostrar la p&aacute;gina</h1>
    </td>
    </tr>
    <tr>
    <td width="400" colspan="2"> <font style="COLOR:000000; FONT: 8pt/11pt verdana">No se puede mostrar la p&aacute;gina que est&aacute; buscando porque la direcci&oacute;n de la p&aacute;gina es incorrecta.</font> </td>
    </tr>
    <tr>
    <td width="400" colspan="2"> <font style="COLOR:000000; FONT: 8pt/11pt verdana">
         <hr color="#C0C0C0" noshade>
    <p>Pruebe lo siguiente:</p>
         <ul>
    <li>Si escribi&oacute; la direcci&oacute;n de la p&aacute;gina en la barra de direcciones, compruebe que la ha escrito correctamente.<br>
    </li>
    <li>Abra la p&aacute;gina principal
    <script>
         <!--
         if (!((window.navigator.userAgent.indexOf("MSIE") > 0) && (window.navigator.appVersion.charAt(0) == "2")))
              Homepage();
         //-->
         </script>
         y busque v&iacute;nculos a la informaci&oacute;n que desee.</li>
    </ul>
    <h2 style="COLOR:000000; FONT: 8pt/11pt verdana">HTTP 405 &ndash; Resource not allowed<br> Servicios de Internet Information Server</h2>
         <hr color="#C0C0C0" noshade>
         <p>Informaci&oacute;n t&eacute;cnica (para personal de soporte)</p>
    <ul>
    <li>M&aacute;s informaci&oacute;n:<br> Soporte t&eacute;cnico de Microsoft
    </li>
    </ul>
    </font></td>
    </tr>
    </table>
    </body>
    </html>
         at org.apache.soap.rpc.Call.getEnvelopeString(Call.java:208)
         at org.apache.soap.rpc.Call.invoke(Call.java:255)
         at test.Test.main(Test.java:42)
    Best regards,
    George

    Is this statement that causes the exception? "Response response = call.invoke(endPoint, "");"
    If so you might be able to catch the SOAPException and interogate the response variable - surround the call with a try, catch block and within the catch you can get the MimeHeaders and check "Content-Type" If it's "text/html" then you know it not a SOAP message so don't use the SOAP api calls.
    It sounds like the web service is offline and the web server is trying to send you an HTML error page which of course is not a SOAP message and so a SOAPException is thrown.

  • HTTP/1.1 500 Internal Server Error.......content-type: text/html;charset=ut

    Hi
    I have created one web service... while i am testing in WSNAVIGATOR i am getting the following error.........
    <b>Request</b>
    POST /sap/bc/srt/rfc/sap/ZZ_BAPI_CUSTOMER_DISPLAY?sap-client=100 HTTP/1.1
    Host: SAPDEV:8000
    Content-Type: text/xml; charset="UTF-8"
    Connection: close
    Authorization: <value is hidden>
    Content-Length: 578
    SOAPAction: ""
    <?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Header><sapsess:Session xmlns:sapsess="http://www.sap.com/webas/630/soap/features/session/"><enableSession>true</enableSession></sapsess:Session></SOAP-ENV:Header><SOAP-ENV:Body><ns1:CustomerDisplay xmlns:ns1='urn:sap-com:document:sap:soap:functions:mc-style'><CustomerNo>0000040009</CustomerNo></ns1:CustomerDisplay></SOAP-ENV:Body></SOAP-ENV:Envelope>
    <b>Response</b>
    HTTP/1.1 500 Internal Server Error
    content-type: text/html;charset=utf-8
    content-length: 3175
    how to solve this problem.... please help me
    Regards
    Ravi Shankar B
    Message was edited by:
            RaviShankar B

    generally HTTP500 error would generate ABAP dumpt - check txn ST22.
    other thing i have noticed is SAPDEV:8000
    you have set up FQDN (fully qualified domain name) for web applications to work properly.
    for more on FQDN check this.
    https://wiki.sdn.sap.com/wiki/display/BSP/FullyQualifiedDomainName%28FQDN%29
    Regards
    Raja

  • Msg=Unsupported response content type "text/html; 400 Bad Request

    Hi All
    this is the excpetion that I get when I am tring to run the
    service MAnagerClient.
    whether it is a list or deploy command :
    can anybody help me?
    Exception in thread "main" [SOAPException: faultCode=SOAP-
    ENV:Protocol; msg=Unsupported response content type "text/html;
    charset=iso-8859-1", must be: "text/xml". Response was:
    <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
    <HTML><HEAD>
    <TITLE>400 Bad Request</TITLE>
    </HEAD><BODY>
    <H1>Bad Request</H1>
    Your browser sent a request that this server could not
    understand.<P>
    <HR>
    <ADDRESS>Oracle HTTP Server Powered by Apache/1.3.19 Server at
    ranaldb Port 1324</ADDRESS>
    </BODY></HTML>
    at org.apache.soap.rpc.Call.getEnvelopeString
    (Call.java:175)
    at org.apache.soap.rpc.Call.invoke(Call.java:212)
    at
    org.apache.soap.server.ServiceManagerClient.invokeMethod
    (ServiceManagerClient.java:129)
    at org.apache.soap.server.ServiceManagerClient.list
    (ServiceManagerClient.java:151)
    at org.apache.soap.server.ServiceManagerClient.main
    (ServiceManagerClient.java:237)

    Hello,
    Your message contains a an HTTP 404 error so the URL that you are trying to access is not valid.
    Can you check from a browser what is the response when you call the endpoint?
    http://server:port/wedanyservices-WedanyServicesPro-context-root/MyWebService2
    I believe that you do not have a service deployed at this URL this is why you have such response, and you cannot send another response.
    Regards
    Tugdual Grall

  • Error consuming Web service - content type text/xml;charset=utf-8 of the response message does not match the content type of the binding

    Hi all,
    We are trying to interact with Documentum server through DFS exposed WCF which communicates through port 9443 and we are provided with documentum issued Public Key certificates. We have successfully imported the certificates in client machine and configured
    the bindings as below in our .Net web application config file.
    <system.serviceModel>
    <bindings>
    <wsHttpBinding>       
    <binding
    name="ObjectServicePortBinding1">
    <security
    mode="Transport">
    <transport
    clientCredentialType="None"
    proxyCredentialType="None"
    realm=""
    />
    <message
    clientCredentialType="Certificate"
    algorithmSuite="Default"
    />
    </security>
    </binding>
    <binding
    name="QueryServicePortBinding">
    <security
    mode="Transport">
    <transport
    clientCredentialType="None"
    proxyCredentialType="None"
    realm=""
    />
    <message
    clientCredentialType="Certificate"
    algorithmSuite="Default"
    />
    </security>
    </binding>
    </wsHttpBinding>
    </bindings>
    Also, we set the message encoding as MTOM and the wcf client object initialization code snippet is as below,
    ObjectServicePortClient
    serviceClient = new
    ObjectServicePortClient(new
    WSHttpBinding("ObjectServicePortBinding1"),
    new
    EndpointAddress(UriUtil.ObjectServiceUri));
    if (serviceClient.Endpoint.Binding
    is
    WSHttpBinding)
       WSHttpBinding
    wsBinding = serviceClient.Endpoint.Binding as
    WSHttpBinding;
    wsBinding.MessageEncoding =
    "MTOM".Equals(transferMode) ?
    WSMessageEncoding.Mtom :
    WSMessageEncoding.Text;
    serviceClient.Endpoint.Behaviors.Add(new
    ServiceContextBehavior(Config.RepositoryName,
    Config.DocumentumUserName,
    Config.DocumentumPassword));
    When we execute the above code, we are getting error message as below,
    Exception: The content type text/xml;charset=utf-8 of the response message does not match the content type of the binding (multipart/related; type="application/xop+xml"). If using a custom encoder, be sure that the IsContentTypeSupported
    method is implemented properly. The first 407 bytes of the response were: '<?xml version="1.0" ?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode>S:VersionMismatch</faultcode><faultstring>Couldn't
    create SOAP message. Expecting Envelope in namespace http://schemas.xmlsoap.org/soap/envelope/, but got http://www.w3.org/2003/05/soap-envelope </faultstring></S:Fault></S:Body></S:Envelope>'
    Then, we changed the bindings as below
    <system.serviceModel>
    <bindings>
    <wsHttpBinding>       
    <binding
    name="ObjectServicePortBinding1">
    <security
    mode="Transport">
    <transport
    clientCredentialType="Certificate"
    proxyCredentialType="None"
    realm=""
    />
    <message
    clientCredentialType="Certificate"
    algorithmSuite="Default"
    />
    </security>
    </binding>
    <binding
    name="QueryServicePortBinding">
    <security
    mode="Transport">
    <transport
    clientCredentialType="
    Certificate"
    proxyCredentialType="None"
    realm=""
    />
    <message
    clientCredentialType="Certificate"
    algorithmSuite="Default"
    />
    </security>
    </binding>
    </wsHttpBinding>
    </bindings>
    We are getting another error message,
    Exception: The client certificate is not provided. Specify a client certificate in ClientCredentials.
    Any pointers on resolving this issue would be highly helpful.
    Thanks

    Hi Dhanasegaran,
      As per your case, the corresponding details which may guide you to resolve this issue:
    1. First of all, you can try to call the wcf service directly from the browser & check where it will point out the correct location.
    2. In config file ,Set IncludeExceptionDetailInFaults to true to enable exception information to flow to clients for debugging purposes .
    Set this to true only during development to troubleshoot a service like below :
    <serviceBehaviors>
      <behavior name="metadataAndDebugEnabled">
        <serviceDebug
          includeExceptionDetailInFaults="true"   
    />
        <serviceMetadata
          httpGetEnabled="true"
          httpGetUrl=""   
    />
      </behavior>
    </serviceBehaviors>
    3. I suggest you to change that <security mode ="TransportWithMessageCredential"> instead of <security mode ="Transport">
     for more information, refer the following link :
    https://msdn.microsoft.com/en-us/library/aa354508(v=vs.110).aspx

  • How to change content-type (text/xml;charset=utf-8)  in SOAP receiver?

    Hi,
    How can I change the content-type (text/xml;charset=utf-8) sent by the SOAP adapter to an external webservice?
    I need to sent text/xml  as content-type to the webservice, otherwise I get an error.
    I have tried with different adapter modules but so far no positive results.
    Thanks.
    Edited by: Roberto Viana on Mar 26, 2009 2:02 PM

    Hi Stefan, many thanks for your answer.
    According to your answer it is not possible to manipulate/change the way PI fills the content-Type.
    I was hoping to solve the issue with a custom built adapter module that sets the HTTP header content-type to text/xml without the charset entry, but I understand that's not the case.
    Regards,
    Roberto Viana

  • Running mac OS 10.5.8, Using Mail 3.5, Text encoding set to Automatic. messages arrive, but the message is 200  lines of alphanumerics. Top says Content-Type: text/plain;      charset=utf-8 Content-Transfer-Encoding: base64.

    I use Mail 3.6 and some incoming email messages start with
    Content-Type: text/plain;
        charset=utf-8
    Content-Transfer-Encoding: base64
    then go on to 200+ lines of alphanumerics (mostly upper and lower case letters). 
    What causes this problem, how can I fix it?
    Text encoding is set to Automatic, and  I'm not using any fancy fonts.  Senders are usually
    sending from PCS that may well use Outlook.
    Rosemary C.  Chicago

    Does it look something like this...
    JVBERi0xLjYNJeLjz9MNCjMyNCAwIG9iag08PC9GaWx0ZXIvRmxhdGVEZWNvZGUvRmlyc3QgNi9M
    ZW5ndGggMTU4L04gMS9UeXBlL09ialN0bT4+c3RyZWFtDQohx6hAp7lMT4WVkGpP6z3UpIQfO4eN
    QRbgjhTqX5mfaabWcvQk/hLnUX6MpKiXwist+RiaiGrzj8XGSNFXuvETWsnoPoV687Exvzo1KYV4
    jIuPmKXlRJvESTE/K2htJihPMS/o6fo3i+nHbTBRWpyrXSfmCPVEgsAzcyECvSU0Rz4MJsEXpdu6
    6u/hg1hlPkb2gpkUQJv50YtWhkD/Jg0KZW5kc3RyZWFtDWVuZG9iag0zMjUgMCBvYmoNPDwvRmls
    Check Mail>View>Message, does it say View Raw Source, Long Headers, or Default Headers?
    See if view Plaintext version helps.

Maybe you are looking for

  • How to print a report on local/network printer(Sample Code)

    Hi forms Gurus, I'm looking for sample code witch allow to print report on local/network printer from Forms builder. Plz help! it's very important. TYAG.

  • I can't burn a CD.  Error Code 4280 why is this?

    I just purchased a CD of itunes.  When I went to burn the cd onto a disc all it says is something about error 4280.  I do have the current updated version of itunes.

  • BAM / BPM integration (11.1.1.2.0)

    Hi all, I'm trying to integrate 'BPM instances with BAM Reports. I have done all the initial works (BAM credentials in application server, Clear DisableActions, Creating Business indicators, etc ) When I invoke the BPM incident from bpm/workspace it

  • External Hard Drive choice help

    I need to upgrade my equipment this year as CS5 and LR3 start getting real slow on my iMac 2.8 ghz intel dual with 4 GB RAM (maxed out) Even with LR set to 32bit. Even getting a new system, it may not be a bad idea to have a dedicated scratch disk. I

  • How can i find all global variable and parameters in a form?

    I don't know name of global variables and parameters,but i want get their name and value . how can i do? who can help me? Thank you. Daniel Liang 2007.1.19