Root element is missing - Response from a WCF service - WCF-Custom adapter

hi BizTalk experts,
In the production environment, as soon as the response is getting subscribed by the orchestration, the orchestration instance is getting suspended and the error that shows up in console is
"Root element is missing".
I have checked the actual response message in the console it is a well formed xml. This is happening only for a few responses from the WCF services. A majority of them are getting processed successfully. I have tried getting the parsing the response in a
pipeline (using custom pipeline component, the production one uses xml receive) and pass it to the orchestration, but it fails giving the same error.
Thanks in advance.

Do you have any mapping done on the response message from the WCF service . ?
If so Better to copy the suspended message coming from the WCF service and validate against the custom response Schema you have created.
Note : You can try running fiddler tool to check the response from from the web service incase of failure.
Also try logging the message in the event viewer or any debug tool.
Thanks
Abhishek

Similar Messages

Document root element is missing: migrating spring app from tomcat

Hi!
can anybody help me with this issue?
I have ported my tomcat spring application to netweaver(6.40, SP 17, Windows 2k SP4) and i get the following error:
Error occured in invoking event "contextInitialized()" on listener clas
s com.webapp.listener.StartupListener. The error is: org.springfram
ework.beans.factory.BeanCreationException: Error creating bean with nam
e 'sessionFactory' defined in ServletContext resource [/WEB-INF/applica
tionContext-hibernate.xml]: Initialization of bean failed; nested excep
tion is org.hibernate.MappingException: Could not parse mapping documen
t in input stream
org.hibernate.MappingException: Could not parse mapp
ing document in input stream
     at org.hibernate.cfg.Configuration.addIn
putStream(Configuration.java:430)
     at org.springframework.orm.hibernat
e3.LocalSessionFactoryBean.afterPropertiesSet(LocalSessionFactoryBean.j
ava:654)
     at org.springframework.beans.factory.support.AbstractAutowir
eCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactor
y.java:1059)
     at org.springframework.beans.factory.support.AbstractAut
owireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.j
ava:363)
     at org.springframework.beans.factory.support.AbstractBeanFac
tory.getBean(AbstractBeanFactory.java:226)
     at org.springframework.bea
ns.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java
:147)
     at org.springframework.beans.factory.support.DefaultListableBea
nFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:269)
     at org.springframework.context.support.AbstractApplicationContext.ref
resh(AbstractApplicationContext.java:320)
     at org.springframework.web.
context.support.AbstractRefreshableWebApplicationContext.refresh(Abstra
ctRefreshableWebApplicationContext.java:134)
     at org.springframework.w
eb.context.ContextLoader.createWebApplicationContext(ContextLoader.java
:246)
     at org.springframework.web.context.ContextLoader.initWebApplica
tionContext(ContextLoader.java:184)
     at org.springframework.web.contex
t.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:4
9)
     at com.ifx.webapp.listener.StartupListener.contextInitialized(Star
tupListener.java:42)
     at com.sap.engine.services.servlets_jsp.server.r
untime.context.WebEvents.contextInitialized(WebEvents.java:45)
     at com
.sap.engine.services.servlets_jsp.server.container.ApplicationThreadIni
tializer.run(ApplicationThreadInitializer.java:112)
     at com.sap.engine
.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.sec
urity.AccessController.doPrivileged(Native Method)
     at com.sap.engine.
core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.
sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
C
aused by: org.dom4j.DocumentException: Error on line 1 of document : D
ocument root element is missing. Nested exception: Document root elemen
t is missing.
     at org.dom4j.io.SAXReader.read(SAXReader.java:482)
     at
org.hibernate.cfg.Configuration.addInputStream(Configuration.java:421)
     ... 18 more
And yes, the xml files are valid xml files at least in anything i've used to look at them (eclipse, ultraedit, notepad, ie) :).....
Thank you!
ps. the file:
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN"
    "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
    
    <bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
        <property name="dataSource" ref="dataSource"/>
        <property name="mappingResources">
            <list>
                <value>package/ModelObj1.hbm.xml</value>
                <value>package/ModelObj2.hbm.xml</value>
            </list>
        </property>
        <property name="hibernateProperties">
            <props>
                <prop key="hibernate.dialect">org.hibernate.dialect.Oracle9Dialect</prop>
            </props>
        </property>
    </bean>
    
    <bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager">
        <property name="sessionFactory" ref="sessionFactory"/>
    </bean>
    
    <bean id="dao" class="com.dao.hibernate.BaseDAOHibernate">
        <property name="sessionFactory" ref="sessionFactory"/>
    </bean>
</beans>

hi istvan,
we are also migrating from websphere to netweaver.
But in spring framework we r facing problems.
We hav spring-beans.jar file in lib dir of Web Application. But When we are creating BeanFactory from xml as,
BeanFactory beanFactory = new ClassPathXmlApplicationContext ("client-config.xml");
clent-config.xml file contains :
[code<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
     <bean id="propertyConfigurer" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" >
          <property name="location">
               <value>conf/service-client/client.properties</value>
          </property>
     </bean></beans>
[/code]
But code is giving exception: ClassNotFoundException -org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.
Wat is the problem ?
Kindly help.
We are also using JAAS for authentication.We are refering above code from our LoginModules login() method.
Regards,
sagar.

Org.xml.sax.SAXParseException: Document root element is missing.

Hi,
I am trying to get the portal login id from a weblogic server based application from iplaet portal server.
I get this follwoing error
org.xml.sax.SAXParseException: Document root element is missing.
at com.sun.xml.parser.Parser.fatal(Parser.java:2817)
at com.sun.xml.parser.Parser.fatal(Parser.java:2805)
at com.sun.xml.parser.Parser.parseInternal(Parser.java:493)
at com.sun.xml.parser.Parser.parse(Parser.java:284)
at com.sun.xml.tree.XmlDocument.createXmlDocument(XmlDocument.java:226)
at com.iplanet.portalserver.util.XMLParser.<init>(XMLParser.java:70)
at com.iplanet.portalserver.naming.share.NamingResponseParser.<init>(NamingResponseParser.java:33)
at com.iplanet.portalserver.naming.share.NamingResponse.parseXML(NamingResponse.java:74)
at com.iplanet.portalserver.naming.WebtopNaming.updateNamingTable(WebtopNaming.java:174)
at com.iplanet.portalserver.naming.WebtopNaming.getNamingProfile(WebtopNaming.java:155)
at com.iplanet.portalserver.naming.WebtopNaming.getServiceURL(WebtopNaming.java:57)
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:534)
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
<May 19, 2004 9:01:12 AM EDT> <Error> <HTTP> <101017> <[ServletContext(id=4873279,name=ematrix,context-path=/ematrix)] Root cause of ServletException
com.iplanet.portalserver.session.SessionException
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:539)
at com.iplanet.portalserver.session.Session.getSessionServiceURL(Session.java:520)
at com.iplanet.portalserver.session.Session.getSession(Session.java:414)
at jsp_servlet.__eatonPortalLogin._jspService(__eatonPortalLogin.java:155)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:462)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
Any help/pointers will be appreciated.
Ashish

Just for anyone else who hits this problem: I encountered the same issue with an XML document that XMLSpy claims is quite well formed. I opened the document in a hex editor, and there at the from was a three-byte byte order marker - the marker that I believe the UTF-8 standard says is optional. I removed these three bytes, and the file was parsed correctly.
In this case, the XML file was created using a Microsft DOM (save).
My solution is to make the java parser - as I use it - a tad more robust: Open the file and create an input stream - a pushback input stream. Read the first three bytes; if they are NOT a BOM, then push those bytes back. Now - in any case - give the stream to the parser to read.
try {
// Open file for reading.
f = new File(path);
FileInputStream fis = new FileInputStream(f);
PushbackInputStream pis = new PushbackInputStream(fis);
byte[] buf = new byte[3];
pis.read(buf, 0, 3);
if (! (buf[0] == 0x00EF) && (buf[1] == 0x00BB) && (buf[2] == 0x00BF) ) {
pis.unread(buf, 0, 3);
builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
doc = builder.parse(pis);
catch (Exception x) {
x.printStackTrace();
}

XML "Document root element is missing"

i have made a research in the forums but i have no definite solution about the error.
my flash client sends XML stream to my ServerSocket. and i want to parse these XML datas.
Document XMLDoc;
DocumentBuilderFactory Factory = DocumentBuilderFactory.newInstance();
DocumentBuilder Builder = Factory.newDocumentBuilder() ;
InputSource Is = new InputSource(new BufferedReader(new InputStreamReader(Sock.getInputStream(),"UTF-16LE")));
XMLDoc = Builder.parse(Is);
But now i have problem called "Document root element is missing". My XML stream comming from flash client :
// Actionscript code :
XDoc = new XML("<?XML version=\"1\"?><LOGIN><USERNAME>KHARON</USERNAME><PASSWORD>485009</PASSWORD></LOGIN>");
----- The XML data i want to sent to ...
<?XML version="1"?>
<LOGIN>
<USERNAME>KHARON</USERNAME>
<PASSWORD>485009</PASSWORD>
</LOGIN>
What is the problem ?

now ?
// Actionscript
XSock = new XMLSocket();
XSock.connect("127.0.0.1",6667);
XDoc = new XML("<?xml version=\"1.0\"?><LOGIN><USERNAME>KHARON</USERNAME><PASSWORD>ew2345dfs</PASSWORD></LOGIN>");
// Java
public void run() {
try {
Document XMLDoc;
DocumentBuilderFactory Factory = DocumentBuilderFactory.newInstance();
DocumentBuilder Builder = Factory.newDocumentBuilder() ;
InputSource Is = new InputSource(new BufferedReader(new InputStreamReader(Sock.getInputStream(),"UTF-16LE")));
XMLDoc = Builder.parse(Is);
org.w3c.dom.Node Node = XMLDoc.getFirstChild();
System.out.print(Node.getNodeValue());
/* Incomming data test code
System.out.print("Listening to incomming messeges");
char in ;
while ( (in = (char)Reader.read()) != -1 ) {
System.out.print( in );
but the result
parser exception ( Document root element is missing )
ihave made a research ( i am newbee in XML) and i have made some declerations like <!DOCTYPE LOGIN <!Element ...
i have declared root element with DOC type decleration. but the same error. :|
since 2 days i am working over these, but solution = null

"Root element is missing." - While using Sharepoint List Source in SSIS.

Hi Team,
We are trying to import data from sharepoint list using sharepointlist source in SSIS. But the following error pops-up.
[SP_SRC_SharePointList [67]] Error: System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlReader.MoveToContent()
   at System.Xml.Linq.XElement.Load(XmlReader reader, LoadOptions options)
   at System.Xml.Linq.XElement.Parse(String text, LoadOptions options)
   at System.Xml.Linq.XElement.Parse(String text)
   at Microsoft.Samples.SqlServer.SSIS.SharePointListAdapters.SharePointListSource.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers)
   at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper100 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer100[] buffers, IntPtr ppBufferWirePacket)
We are unable to debug / move any further. Request your help.
Thank you.
Best Regards,
Gayathri

It appears that the XML you trying to load does indeed not have the root element.
E.g.
<?xml version="1.0" encoding="UTF-8"?>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>has nonemust be<?xml version="1.0" encoding="UTF-8"?>
<Root><iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii>
<iii>
<kkk>test</kkk>
<ppp>000</ppp>
</iii></Root>
Arthur My Blog

"root element is missing" - UTF-8

I have 2 identical files, except they are stored in ISO-8859-1 and UTF-8.
"Test ansii.xml":
<?xml version="1.0" encoding="ISO-8859-1"?><e></e>
"Test utf8.xml":
<?xml version="1.0" encoding="UTF-8"?><e></e>
When I look at them in Internet Explorer they show correctly. But when I parse them with SAX in java I get an error when I parse the file stored in UTF-8.
import java.io.*;
import javax.xml.parsers.*;
import org.xml.sax.*;
import org.xml.sax.helpers.*;
public static void testXML(){
    try{
      File ansiiFile=new File("Test ansii.xml");
      File utf8File=new File("Test utf8.xml");
      SAXParserFactory factory = SAXParserFactory.newInstance();
      SAXParser saxParser = factory.newSAXParser();
      //try ISO-8859-1
      InputSource in = new InputSource(new InputStreamReader(new FileInputStream(ansiiFile),"ISO-8859-1"));
      saxParser.parse(in,new DefaultHandler());
      //try UTF-8
      in = new InputSource(new InputStreamReader(new FileInputStream(utf8File),"UTF-8"));
      saxParser.parse(in,new DefaultHandler());
    }catch(Exception e){
      e.printStackTrace();
}The first file parses well, but when I parse the file encoded in UTF-8 I get this error:
org.xml.sax.SAXParseException: The Document root element is missing.
     at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
     at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3170)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:501)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
     at test.Test.testXML(Test.java:44)
     at test.Test.main(Test.java:25)
Gil

Sigh, I found the answer.
http://www.i18ngurus.com/encyclopedia/byte_order_mark.html
byte order mark
Also known as BOM.
Name given to the Unicode character U+FEFF when used at the beginning of a Unicode byte stream. This invisible character generally know as ZERO WIDTH NO-BREAK SPACE (ZWNBSP) serves to identify unambiguously the Unicode transformation form used (and especially the byte order) for the stream. Indeed U+FFFE is a noncharacter so there is no risk of misinterpretation.
The following represents the byte signature of the character U+FEFF with the various Unicode Transformation Forms:
Bytes Encoding
00 00 FE FF UTF-32, big-endian
FF FE 00 00 UTF-32, little-endian
FE FF UTF-16, big-endian
FF FE UTF-16, little-endian
EF BB BF UTF-8
Historically the ZWNBSP was also used to indicate non-breaking but this use is now deprecated and replaced by the character U+2060 for that purpose.
http://p2p.wrox.com/archive/xslt/2002-11/79.asp
I suspect you edited the stylesheet using a text editor that inserts the
BOM at the start of the file. For example, I think Windows Notepad does
this.
Some XML parsers accept a BOM at the start of a UTF-8 file, others
don't. For example, the Crimson parser that comes with JDK 1.4 doesn't.
You basically need to find a text editor and an XML parser that agree
with each other about whether or not to use a byte order mark.
Alternatively, use a different encoding for the stylesheet, e.g.
iso-8859-1.
The code above found these strange bytes while expecting '<', and crashed of course.
Gil

DSDP 3.0 - CM 2012 R2 CU3 - Import Driver Packages Fail - Root element is missing

I realize that the Dell Server Deployment Pack 3.0 plug in is a vendor plugin to CM 2012 R2 but they (dell) are clueless. So I am hoping that there is some knowledge here.
I've opened a case with Dell and have used the Dell forums to document my issue here:
http://en.community.dell.com/techcenter/systems-management/f/4469/t/19613996
(there are some pics that might help.)
I have a ConfigMan 2012 R2 environment where I have integrated the Dell Server Deployment Pack 3.0. The installation succeeded and I have been able to also run the Dell System Integration using the DTK 4.4. I am doing all of this work directly
on the CM 2012 primary site server.
However, when I try to Import Dell Drivers, I get an error in the wizard:
I have tried multiple OM DVD's each one produces the same results:
OM_SMTD_801_A00.iso
OM_SMTD_802_A00.iso
OM_SMTD_740_A00.iso
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Xml.XmlException: Root element is missing.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.Load(String filename)
   at Microsoft.ConfigurationManagement.OemDeployment.DellDriverPackageImport.PackageSelection.GetPackageListXml(String dellCatalogXml)
   at Microsoft.ConfigurationManagement.OemDeployment.DellDriverPackageImport.PackageSelection.PackageSelection_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
Microsoft.ConfigurationManagement
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1401
    CodeBase: file:///D:/Program%20Files/Microsoft%20Configuration%20Manager/AdminConsole/bin/Microsoft.ConfigurationManagement.exe
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
.... (log continues)....
Any ideas?
My CM 2012 R2 is running on Windows 2012 R2.

Thanks for your comment. I thought that Microsoft might have had some involvement with the writing of this tool:
http://en.community.dell.com/techcenter/systems-management/w/wiki/4125.dell-server-deployment-pack-dsdp-for-configuration-manager

Parsing xml file error: Document root element is missing.

Hi,
When I try to parse an xml file with SAX parser, the SAXParseException message I got is: "Document root element is missing." Anybody knows what it is? How should I fix it? Thanks a lot in advance!
J.H.

An XML document has only a single root element. So after the XML header, your document must look something like this:
<tag>
</tag>
If you have more than one element like this, for example:
<tag>
</tag>
<anothertag>
</anothertag>
then you don't have a root element and your parser will give the message you referred to.

Server 2012 R2 - No response from the UmRdpService service and more...

Hi!
We have a Remote Desktop Services Deployment with the following:
LIC01 – Windows 2012 R2 - Licensing
RDCB01 – Windows 2012 – Connection Broker
RDWA02 – Windows 2012 R2 – Web Access
RDG01 – Windows 2012 R2 - Gateway
RDG02 – Windows 2012 R2 - Gateway
RDG03 – Windows 2012 R2 – Gateway
RDSH01 – Windows 2012 R2 - Session Host
RDSH02 – Windows 2012 - Session Host
RDSH03 – Windows 2012 R2 - Session Host
RDSH04 – Windows 2012 R2 - Session Host
RDSH05 – Windows 2012 R2 - Session Host
RDSH06 – Windows 2012 R2 - Session Host
RDSH07 – Windows 2012 R2 - Session Host
RDSH08 – Windows 2012 R2 - Session Host
RDSH09 – Windows 2012 R2 - Session Host
RDSH10 – Windows 2012 R2 - Session Host
We have two Session Collections:
Office-R2 (All Server 2012 R2 RDSHs)
"Office (RDSH02, Closed for users)"
User Profile Disk are enabled to a SOFS Share (Server 2012).
Client Settings: Everything except "Plug and play Devices" are enabled
Problem:
Suddenly, one or more of RDSH
servers (in the Office-R2 Collection) get the following error:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
After this, we get similar error messages
to other services, such as:
AudioEndpointBuilder, NcbService, ScDeviceEnum, WPDBusEnum, Netman
Users logged into the server, looses Redirection
services as local drives and local
printers, and they also have problem signing out of the server. (Hangs on signing out)
New Users that tries to sign in to that server are also having trouble (Hangs on signing in).
After using the logoff tool to sign out every user on that server, I end up With the following:
It
appears that there are no users logged on,
yet there are many Disconnected sessions...
Looking at the SOFS file share I still see that RDSH04 has read/Write to the .VHDX file that hold the User Profile.. And If the user try to log on to another server in that Collection, it get a temporary profile.
If I kill the Conncetion to the VHDX files, Users can then sign in normally to another node it that Collection.
Trying to restart the server With "Shutdown -r -t 0 -f" does not work, It just hangs on Shutdown (waited 3 days), so All I can do is Press and Hold.We
have also seen BSoD on these nodes, but I'm sure if they are related to this error:
WinDBG is saying:
BugCheck 3B, {c0000005, fffff803538fa84e, ffffd0002711cb00, 0}
Probably caused by : dfsc.sys ( dfsc!DfscCacheStore+6f )
I found https://support.microsoft.com/kb/2925981 and
http://support.microsoft.com/kb/2525246, but they are not for Windows Server 2012 R2.
Any Idea?
Thanks
Anders

Hi,
Firstly, dfsc.sys indicates the DFS clients. It means that your systems use DFS service to access the file share.
Please let us know if you configured the DFS service on your file server.
Also, what is the format of file path you configured for UPD?
\\FileServer\FileShare
Or
\\Domain.com\DFS NameSpace\File Share
Thanks.
Jeremy Wu
TechNet Community Support

Erro while recieving a signed response from a web service

i'm not sure whether this is the right forum to post this topic, but anyways i'm going fwd as i was not able to find a rite one, if any body knows, plz redirect me to that, anyways below is my issue.
i'm using axis as a web service engine on my client side and getting a signed response from a web service.
But while recieving the response im gettng the following error.
Verification failed for URI "#id-13753285"
org.apache.ws.security.WSSecurityException: The signature verification failed
     at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:332)
     at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:79)
     at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:279)
     at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:201)
     at org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllReceiver.java:159)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:190)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.sterlingcommerce.www.mesa.GISBindingStub.executeLightweightJDBCAdapterQuery(GISBindingStub.java:210)
     at client.MyClient.makeRequest(MyClient.java:105)
     at client.MyClient.main(MyClient.java:134)
failed becoz of remote exception: org.apache.ws.security.WSSecurityException: The signature verification failed
Exception in thread "main" org.apache.ws.security.WSSecurityException: The signature verification failed
     at org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:332)
     at org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:79)
     at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:279)
     at org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:201)
     at org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllReceiver.java:159)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:190)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
     at org.apache.axis.client.Call.invoke(Call.java:2767)
     at org.apache.axis.client.Call.invoke(Call.java:2443)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.sterlingcommerce.www.mesa.GISBindingStub.executeLightweightJDBCAdapterQuery(GISBindingStub.java:210)
     at client.MyClient.makeRequest(MyClient.java:105)
     at client.MyClient.main(MyClient.java:134)
below are my hadler configurations and properties file
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver" >
                    <parameter name="action" value="Signature"/>
                    <parameter name="user" value="signverf"/>
                    <parameter name="passwordCallbackClass" value="client.PWCallback"/>
                    <parameter name="passwordType" value="PasswordDigest"/>
                    <parameter name="signaturePropFile" value = "signatureVerifyCrypto.properties"/>
                    <parameter name="signatureKeyIdentifier" value="DirectReference"/>
               </handler>properties file
org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin
org.apache.ws.security.crypto.merlin.keystore.type=jks
org.apache.ws.security.crypto.merlin.keystore.password=password
org.apache.ws.security.crypto.merlin.keystore.alias=signverf
org.apache.ws.security.crypto.merlin.alias.password=password
org.apache.ws.security.crypto.merlin.file=certs/signverf/signverf_pubkeystore
commands i used to generate keystore:
keytool -import -alias signverf -file privCert4Sign.cer -keystore signverf_pubkeystore -storepass password
keytool -list -alias signverf -keystore signverf_pubkeystore
i tried goggling for this error,in one thread i got this is because of some issue in axis 1.4 which i'm using and if i try using axis 1.2, this will not come,
for the time i'm not able to download axis 1.2 from any of the apache mirrors :( ,
if some one can provide me the link,it will be really helpful.
also if anyone as faced similar issue or can see whats going wrong here, please reply.
also below is my soap response capture using tcpmon
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><ds:Signature Id="Signature-18290758" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/>
<ds:Reference URI="#id-13753285" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:Transforms xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/>
</ds:Transforms>
<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/>
<ds:DigestValue xmlns:ds="http://www.w3.org/2000/09/xmldsig#">jAaM4xp/2ZOch7iqyyLynojMpV0=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
JiOjIFgJ2qMvzJsirbjgV7AeDWfsS0Ak3xzue1nK+LXELM3tZ/h/eFyxCLZfLk+553vJbmnlU423
8NgjgngYcYa+bB6yTovZJKB66LdQEHLpmTX4WNteLrcVOBfHyZcJCKemF2XyaF4yX03XGAIdNnFV
1d8wZQcBgakPIrjJGAZtwo94bYBlL/MJedBP819Ecf/N6hEmafFxHD46Xapi+HdcDjQmCqxaol/I
bQuM3ikJJ2v+46bQNKEWavdG7lIicjUsvH3xpyzZthj26nAHV6nAOEe8tybKhKLga6KDM+3eAJNq
3s52yZTz68n7z5AijdmhMkc7ivCxELBx5TQYsw==
</ds:SignatureValue>
<ds:KeyInfo Id="KeyId-20631690" xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<wsse:SecurityTokenReference wsu:Id="STRId-5317380" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"><wsse:KeyIdentifier EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3">MIIDLDCCAhSgAwIBAgICBNIwDQYJKoZIhvcNAQEFBQAwTzEWMBQGA1UEAwwNcHJpdkNlcnQ0U2lnbjEMMAoGA1UECgwDYWJzMQswCQYDVQQGEwJVUzEaMBgGCSqGSIb3DQEJARYLeHl6QGFiYy5jb20wHhcNMDcwOTA0MDQzNzMxWhcNMDgwMzAyMDQzNzMxWjBPMRYwFAYDVQQDDA1wcml2Q2VydDRTaWduMQwwCgYDVQQKDANhYnMxCzAJBgNVBAYTAlVTMRowGAYJKoZIhvcNAQkBFgt4eXpAYWJjLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJSG2UR8nMAxctBlR5YSnEVeuHNFMM7t8YQX6J8GRausKPXyDT4pIfPHRaeag62K4cUhBDYBLyUmZqYTZBHpKISgYkYsXqYHoB4gif664rZvpMKw+cTpD/3WzViOeHHWfQM5/XUatLBPXzRUB78PcM9RnCEeznKUEPoWxTfl2qsR0d4CxOVzH9dHn6JCEaQQWzntH61YCw4Qm6Kq78+sLfnv7CBrg/NYewFX9JozZk7UzlmPZWCm7pp2d4UDn1KB7nLnLFxD6aMgjAikWKAU4h15ihJxu6Appc+ggAdAV/jQiaIeAtokfe2Iw1bUh8SOOR8iUa9lK0Jf6C/N9ZTnxCcCAwEAAaMSMBAwDgYDVR0PAQH/BAQDAgTwMA0GCSqGSIb3DQEBBQUAA4IBAQCKfRu1cXkwwnNZ+0brwT4iI1q/Ti/OVMWpP15Ob7bDE5rUjwpNUJXXlqKdOh7pkk1gLTiebQrMkd0ozpbi/Xdmea1xf9diCc4IApg6K9G4KACR2sLeXcKy7d4hakYqMLeaPJwBcd3V6DGiJgfP2S8Ui8rQzDpslTBM1+YaBdUVIv1/VCFO/K5I4lkPkjGDp/qDm4lXn3Mup9HG9INgklA02hPnYHWunVZm/5MZpEn4BYks+B3VqCXSAkRVD9aAuM3Tv4atblHDs3oKTV1awoVQbKkw+Eonnc/+Mex8A5sJ/8eUnQ3UPdT77U0+WcrvwFxoFP2e0J8xHW8N8b2fIr8H</wsse:KeyIdentifier></wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature></wsse:Security></soapenv:Header>
<soapenv:Body wsu:Id="id-13753285" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<mesa:processData xmlns:mesa="http://www.sterlingcommerce.com/mesa" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProcessData>
<service>Test_Web2</service>
<b2b-protocol>http</b2b-protocol>
<transport-instance-id>MESAHttpServerAdapter_HttpServerAdapter_node1</transport-instance-id>
<SyncModeBP>false</SyncModeBP>
<http-request-uri>/soap-new</http-request-uri>
<transport-session-id>Fri Aug 31 14:04:57 IST 2007:110</transport-session-id>
<incomingSOAPTransportMode>http</incomingSOAPTransportMode>
<VERIFICATION_KEY/>
<DECRYPTION_KEY/>
<SECURITY_TOKEN_NAME>ST1</SECURITY_TOKEN_NAME>
<SIGNING_CERTIFICATE>blrgislin13:10.11.23.37:114bb0fb841:12328</SIGNING_CERTIFICATE>
<SIGNING_ALGO>http://www.w3.org/2000/09/xmldsig#rsa-sha1</SIGNING_ALGO>
<SIGNING_KEY_IDENTIFIER_TYPE>3</SIGNING_KEY_IDENTIFIER_TYPE>
<CANONICALIZATION_ALGO>http://www.w3.org/TR/2001/REC-xml-c14n-20010315</CANONICALIZATION_ALGO>
<SIGNATURE_ENCRYPTION_ORDER>-1</SIGNATURE_ENCRYPTION_ORDER>
<SOAP_URI>/soap-new</SOAP_URI>
<SOAPEnvNSPrefix>soapenv</SOAPEnvNSPrefix>
<SOAPEnvNSURI>http://schemas.xmlsoap.org/soap/envelope/</SOAPEnvNSURI>
<messageMode>1</messageMode>
<query_type>SELECT</query_type>
<result_name>result</result_name>
<pool>mysqlPool</pool>
<row_name>row</row_name>
<sql>SELECT * FROM MBX_MAILBOX</sql>
<serviceMode>1</serviceMode>
<typeName>LightweightJDBCAdapterQuery</typeName>
<PrimaryDocument SCIObjectID="blrgislin13:10.11.23.37:114bb0fb841:19200"/>
<ADD_SOAP_ENVELOPING>false</ADD_SOAP_ENVELOPING>
<INSERT_SECURITY_HEADER>false</INSERT_SECURITY_HEADER>
</ProcessData>
</mesa:processData>
</soapenv:Body>
</soapenv:Envelope>
sorry for this long mail, but we are really stuck and need to move forward,
looking for your help.

Hi,
The Service Control Manager will generate an event if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds). You could modify the registry to increase the default time-out value for the service control
manager.
For more detailed information, please see:
Event ID 7011: Service Timeout
http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx
The Event 12362 indicates that a destination LUN could not be located or could not be restarted. You could refer to the article below to troubleshoot the issue:
Event ID 12362 — VSS Shadow Copy Provider Operations
http://technet.microsoft.com/en-us/library/ee264223(v=ws.10).aspx
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Getting response from a Web Service

Hello, everyone,
I want MII to show the response from a Web Service it is calling through the Web Service action.
But when this Web Service return an error (as a Soap Fault response), MII simply does not show the response. It show it truncated, such as
"<?xml version="1.0" encoding="UTF-8"?>
<ReceiveMessageFromMESResponse xmlns="http://tempuri.org/"/>"
It prevents me from showing the error message to the user.
What can I do to have MII show me the complete response received from the called Web Servce?
Thanks in advance!

Hi, SB!
Yes, this would solve the problem, but it would require changes on already-implemented, working external Web Services, which should be avoided by all means.
SOAP Fault responses are part of the SOAP protocol. I expected MII to understand it.
Thanks a lot for your answer!

App testing phase: Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered

We are testing an app at work and Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered to these tow devices.
PUSH notification were delivered to some of the other iOS devices: (iPhone5 / iOS 6.1.4 and iPhone5 / iOS 7.0.3)

Sounds like you have a battry issue but don't want to believe it.
If a car was running fine on one tank of gas, then you filled it up with another tank of gas and it began to run funny, one might suspect that tank of gas. But let's just say coincidence blew a valve-- would you think the new tank of gas was the culprit?
BUT WAIT!! It just might have been! The gas could have been of higher octane and put more more strain on the valves; you know, like going from 87 octane (OS6) to 93 octane (OS7) and showing you the engine was on the edge of compromise.
Sometimes you have to go with common sense. If everything else is ruled out, it must be the battery. And if it runs fine one moment in OS6 but immediately ***** in OS7, I'd believe my battery was suspect-- though comfy-- in OS6 but the OS7 showed its true power.
Moreover, if you had the answer-- or didn't want to believe someone's more competent advice-- why did you even call? You've already shown that you don't know much when you asked if you could go backwards after setting up the new OS as a new phone.
Additonally, if you're such the know-it-all, but yourself the $29 battery and put it in yourself. It's a piece of cake.
<Edited By Host>

Error for Photoshop Elements 3 & Horrible Response From Support

I own Adobe Photoshop Elements 3. It was installed on my Macbookpro and my G5 desktop.
The G5 died. I tried to install the software on my new iMac. It let me get all the way through installation then gave me this error message:
Could not complete your request because of missing or invalid personalization information.
So I got online via chat. After an excruciating hour of communicating with someone who put me through a series of unnecessary steps I was told to contact techncial support and complete a technical case. It took awhile to find the form. Finally I sentit off and got this reply:
At the outset, please accept our sincere gratitude for the time taken and efforts made by you in sharing your concerns with us.
I would like to inform you that your product Adobe Photoshop Element 3 is now out of product support lifecycle and hence is not supported by Adobe anymore. Currently Adobe support is available only for Adobe Photoshop Element 8 and 9, which are the most recent versions of the product.
In the first place I am not looking for product support. I am just trying to load the software. Does Adobe really need another $60 or so from me? I don't need a later version. The software works perfectly.
And I'd probably be happy to buy new software if I hadn't had to go through all these steps to get this recommendation. Why aren't the guys on the chat post advised to send the Elements 3 people off to buy new software?
When I googled this error message, I discovered it happens to a LOT of people. Why doesn't Adobe have a standard, easy automated fix instead of involving one-to-one interactions that take up their time and mine?

Please try downloading the trial of PSE 9 from link https://www.adobe.com/cfusion/tdrc/index.cfm?product=photoshop_elements&loc=en_us&crosssel l=selected.
You can first review the features in PSE 9 http://www.adobe.com/products/photoshopel/features/?view=topnew.
Thanks,
Garry

Does anyone know this message: "Document root element is missing"

I'm getting this message by loading an XML File from my server into an DocumentBuilder. The only strange thing, if I'm doing that from my local machine (linux) it works, but executing by Java WebStart I get the message above !?!
Does anyone know why?

That was the first idea i had, but InputStream.available() on the given File means something about 3500 signs.
Somewhere I read, that a Classpath, or Path may be missing, but I'm not using any special imports!
package com.msgis.XML;
import java.io.*;
import org.xml.sax.*;
import org.xml.sax.helpers.DefaultHandler;
//API
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
//Exceptions
import org.xml.sax.SAXException;
import org.xml.sax.SAXParseException;
//Reading XML File
import java.io.File;
import java.io.IOException;
//DOM definition and Exceptions
import org.w3c.dom.Document;
import org.w3c.dom.DOMException;
//URL
import java.net.URL;
import java.net.*;
Ideas?
That is the only idea left, because, in the IDE (Sun ONE Studio 5 Update 1, Standard Edition) it works, and from other projects I know that the IDE is linking its own classes.
java pgm does not work. It delivers the same Exception.
SAXParseException Document blablabla .......

Request/Response From Long running Service to BPEL

Hi,
I have long running web service which I plan to implement as a EJB30 Webservice.
I need to add support for Async callback Repsonse to the BPEL process calling this ejb service.
Since jax-ws is not supported by the current version of Oracle I cannot use that.
Can I use the Java concurrent api in side the EJB and implement the EJB as a stateful EJB with support for WS-Addressing?
I do not want to use the JMS, becuse of the additional coding of multiple Message beans to send and receive the message.
What other options do I have here?

<con:fault xmlns:con="http://www.bea.com/wli/sb/context"> is an osb internal fault and not a soap:Fault
BPEL process will fault if it receives either a soap:fault or a custom fault defined in the wsdl. so change your proxy service error handling to replace $body to one of these.
If you don't have reply with failure action, osb will return a soap:Fault ( generated by the system error handler) and bpel will fault , but the error info in $fault will be lost..
One way to address this is to define a Fault message for the service in the wsdl ( port type will have input, output and fault elements for the operation) and in the osb error handler transform $ fault to the fault message format and do a reply.

Root element is missing - Response from a WCF service - WCF-Custom adapter

Similar Messages

Maybe you are looking for