Client found response content type of 'text/html;charset=iso-8859-1', but expected 'text/xml'.

Hello All,
I am on BI 4.0 SP6.
I am login to Advance Analysis Office using sso with Authentication : Windows AD, but when i login errors occurs:
Client found response content type of 'text/html;charset=iso-8859-1', but expected 'text/xml'.
The request failed with the error message:
I have done all settings and configuration for SSO as per following notes:
http://service.sap.com/sap/support/notes/1631734
http://service.sap.com/sap/support/notes/1646920
http://service.sap.com/sap/support/notes/1794675
Earlier i was getting Login Exception Error WSE : 99999, i did some changes, after that the above error is coming
Does anybody knows the solution?
KR,
MD

refer the below note
1785270 - How to configure AD SSO for Advance Analysis for MS Office with Business Objects BI 4.0

Similar Messages

Client found response content type of 'text/plain', but expected 'text/xml'

Hi All
We have developed a J2EE- JAX-RPC web service using Weblogic's 'ServiceGenTask'.
Invoking web service via java client and SOAP UI works like charm but fails when the
service invoked via .NET client.
Below is the .NET sample code and the Stack Trace:
.NET CODE:
System.Net.ServicePointManager.ServerCertificateValidationCallback = new RemoteCertificateValidationCallback(delegate { return true; });
testwebservice.ESI est1 = new testwebservice.ESI();
esi_detail = est1.getDetails("someuserid", "password"<Details> <Id>" + txt_eino.Text +"</Id> </Details>");
Stack Trace:
System.InvalidOperationException was unhandled by user code
Message=Client found response content type of 'text/plain', but expected 'text/xml'.
The request failed with the error message:
HTTP/1.1 100 Continue
<env:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><env:Header/><env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><m:getCertificateDetailsForWSUResponse xmlns:m="http://mynamespace"><result xsi:type="xsd:string"><CertificateStatus>valid</CertificateStatus>
</m:getCertificateDetailsForWSUResponse></env:Body></env:Envelope>
Source=System.Web.Services
StackTrace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at shcilestamp.EstampIndia.getCertificateDetailsForWSU(String string, String string0, String string1) in c:\Users\Revenue\AppData\Local\Temp\Temporary ASP.NET Files\sra\6fd93bb3\8d227466\App_WebReferences.iojpamot.0.cs:line 105
at default_1.btn_verify_estamp_Click(Object sender, EventArgs e) in c:\Users\Revenue\Desktop\OFFICE\sra\default.aspx.cs:line 1006
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
InnerException:
Note: The same client code is able to access the service deployed in our DR site without any fault.
However it fails to invoke service deployed in Production site.
Is this anything to do with the Content-type settings at the web/app server layer?
Any help will be appreciated.
Thanks & Best Regards
Avinash

Make sure you're using the Reverse Proxy Plugin for Web Server, not the Application Server Connector (they are VERY similar, but not the same). The RPP knows how to handle 100 Continue, the Connector does not.
Or use Web Server 7 and its built-in reverse proxy feature.

Client found response content type of '', but expected 'text/xml', While Creating Subscription in SSRS2008 R2

I am trying to Create a Subscription from a windows service and provided all authentication as Anonymous. Added the Web Reference of reporting service 2008 as 'http://ServerName:Port(80)/ReportServer/ReportService2005.asmx' and execution service as
'http://ServerName:Port(80)/ReportServer/ReportExecution2005.asmx'. I was getting the following error while executing the below code statement:
rs.CreateSubscription(reportPath, extSettings, desc, eventType, matchData, parameters);
Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.
I am running Microsoft SQL Server 2008 R2. Please help.

Hi PrabhatY,
According to your description, the error "Client found response content type of '', but expected 'text/xml'.The request failed with an empty response." is thrown out when you create a subscription for a report with PowerShell.
In your scenario, please check if you could access the report server and create a subscription in report manager. Then you should make sure all parameters within CreateSubscription method are right. If issue persists, please try to use Fiddler to monitor
local request and received response message. Please refer to this document to use this tool:
Getting Started with Fiddler.
Reference:
ReportingService2005.CreateSubscription Method
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

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.

Not a valid SOAP Content-Type: text/html; charset=iso-8859-1

Friends
JDEV and SOA suite 10134
I have multiple domains on my BPEL Server. In one of the domain since I deployed the new process, all the processes of that domain are now failing on execution with following error in opmn/soa_instance/*.err log files. No errors in domain.log
+"Caused by: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; cha+
+rset=iso-8859-1"+
At the same time we get Internal Server Error on BPEL Console.
I have sync processes with 1 or two invokes, so I am generally losing the instances, cannot provide the details in the process execution. All BPEL processes are invoking Siebel Web Services, that is the common part.
When I restart my system, it may or may not work; even if it works then within few instances execution again starts giving the same error. I can see that after the errors the instance are going through and getting completed successfully few times. All these processes were working successfully earlier.
Any idea about this !!!!
Thanks

Thanks Anirudh,
I don't use compensation handlers. Moreover I have properly defined the scopes and sequences throughout the bpel process. My processes are sync in nature and I'm not able say at what step exactly the processes are failing and throwing the SOAP content Type error though the instances are getting completed with delay soemtimes.

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

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

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ágina</title>
<META HTTP-EQUIV="Content-Type" Content="text-html; charset=Windows-1252">
</head>
<script>
function Homepage(){

</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">No se puede mostrar la página</h1>
</td>
</tr>
<tr>
<td width="400" colspan="2"> <font style="COLOR:000000; FONT: 8pt/11pt verdana">No se puede mostrar la página que está buscando porque la dirección de la pá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ó la dirección de la página en la barra de direcciones, compruebe que la ha escrito correctamente.<br>
</li>
<li>Abra la página principal
<script>
     
     </script>
     y busque vínculos a la información que desee.</li>
</ul>
<h2 style="COLOR:000000; FONT: 8pt/11pt verdana">HTTP 405 – Resource not allowed<br> Servicios de Internet Information Server</h2>
     <hr color="#C0C0C0" noshade>
     <p>Información técnica (para personal de soporte)</p>
<ul>
<li>Más información:<br> Soporte té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.

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

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

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?

SOAP-Exception: unsupported response content type

Hi,
can anybody give me a little hint?.
I currently try to run the JDeveloper "Tutorial" web service examples. I could successfully implement and deploy the DateTime Web-Service example. But when executing "DateTimeClient.java" I get the error message listed below.
I'm using JDeveloper 9.0.2 and the OC4J- J2EE Container (standalone) shipped with JDeveloper
Thanks for your help
Thomas
D:\Programme\oracle\jdev\jdev9i902\jdk\bin\javaw.exe -ojvm -classpath D:\Programme\oracle\jdev\jdev9i902\jdev\mywork\WebService\DateTimeClient\classes;D:\Programme\oracle\jdev\jdev9i902\jdev\lib\jdev-rt.jar;D:\Programme\oracle\jdev\jdev9i902\soap\lib\soap.jar;D:\Programme\oracle\jdev\jdev9i902\lib\xmlparserv2.jar;D:\Programme\oracle\jdev\jdev9i902\jlib\javax-ssl-1_2.jar;D:\Programme\oracle\jdev\jdev9i902\jlib\jssl-1_2.jar;D:\Programme\oracle\jdev\jdev9i902\jdk\jre\lib\ext\activation.jar;D:\Programme\oracle\jdev\jdev9i902\jdk\jre\lib\ext\mail.jar;D:\Programme\oracle\jdev\jdev9i902\j2ee\home\lib\http_client.jar -Dhttp.proxyHost=http-proxy.danet.de -Dhttp.proxyPort=8080 datetimeclientpackage.DateTimeClient
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type "text/html", must be: "text/xml". Response was:
<HTML><HEAD><TITLE>Method Not Allowed</TITLE></HEAD>
<BODY><H1>Method Not Allowed</H1>
An error has occurred.
</BODY></HTML>
     java.lang.String org.apache.soap.rpc.Call.getEnvelopeString(org.apache.soap.transport.SOAPTransport)
     org.apache.soap.rpc.Response org.apache.soap.rpc.Call.invoke(java.net.URL, java.lang.String)
     java.lang.String datetimeclientpackage.DateTimeClientStub.getDate()
     void datetimeclientpackage.DateTimeClient.main(java.lang.String[])
Exception in thread main
Process exited with exit code 1.

I have just found the same/similar problem discussed some months ago. I have adopted the solution proposed by
Raghu Kodali (disabling usage of http-proxy-server). Now the samples runs well.
Thanks a lot.

Weblogic Portal - Disc API bug in response content type

Hi
While using WLP Disc APIs in the portal for AJAX calls, the response content type returned by the weblogic portal server is:
text/x-netuix-json-comment-filtered; charset=ISO-8859-1
This is not getting changed to 'application/json' inspite of setting this as the content type for a JSF JSP.
Probably, looks like a bug.
We have a JSF portlet in which we need to make an AJAX call.
Please refer to the weblogic whitepaper for the AJAX examples (weblogic-portal-jsf-whitepaper.pdf).
The example works fine in the dev/build environment. When the portal server is accepting calls through Sun One webserver,
the logs from the webserver show the response content type from the portal server as "text/x-netuix-json-comment-filtered; charset=ISO-8859-1"
- I tried changing the content type to "application/json" in the JSF JSP (as per the example from the pdf file). Still the content type does not change.
- The response from the portal server is suffixed with "\n\r\t". Because of the trailing space/carriage return chars in the portal server response, the sun one webserver is unable to parse (or) eliminate the "\r\n\d" chars to the browser. When the browser receives a response (with the trailing chars), the module.js (weblogic wrapper API for DISC calls) fails.
- The module.js tries to check whether the response from portal server ends with "**/" but unfortunately, the weblogic protal server returns
"/** %json response%**/\n\r\d"
I found a workaround to this issue by having a filter for the JSF JSP which sets the content type as "application/json" and does a flush() before it makes a call to the JSF JSP which responsds to an ajax call. This works as the content type is set and flushed first so any attempt by the portal server to set as "text/x-netuix-json-comment-filtered" does not get reflected in the http response.
Any support/fix from oracle regarding this will be helpful as most of the webserver integration with the portal server happens during the middle of the project build and might lead to a technical risk.
Server details: WLPS 10.3, Sun One 7.0
Thanks
Ananth Krishnan

Make sure you're using the Reverse Proxy Plugin for Web Server, not the Application Server Connector (they are VERY similar, but not the same). The RPP knows how to handle 100 Continue, the Connector does not.
Or use Web Server 7 and its built-in reverse proxy feature.

Response content type does get set.

Hi All,
I'm in the middle of converting an ISO-8859-1 web application to a UTF-8 encoded application. The application uses struts/tiles and runs on Sun One App server 7.0 and J2EE 1.3.
I have made the following changes to the existing application.
1. added acceptCharset="UTF-8" to struts forms.
2. added <controller contentType="text/html; charset=UTF-8" /> to struts-config.xml
3.have set the request.setCharacterEncoding("UTF-8"); on an abstract level of the all the actions.
4.Created a new ServletFilter and included, response.setContentType("text/html;charset=UTF-8");
5.Configured the database to work with Unicode characters.
Now I can successfully save Unicode characters do the database. (I have tested this) However the problem is when retrieving information back to the web tier, html page shows me garbage instead of the Unicode characters. The browser default encode type is still selected to ISO-8859-1, and when I manually change this to UTF-8 garbage properly turns into Unicode. My suspicion is response content type is not getting set properly. This explains browser selecting ISO-8859-1 by default.
Anyone have a clue? Point in the right direction would be highly appreciated.
Thanks,
Shaminda.

I am seeing similar results.
Amanda, did you find resolution?
Herschel

Client found response content type of 'text/html;charset=iso-8859-1', but expected 'text/xml'.

Similar Messages

Maybe you are looking for