Supplied XML is not valid

Hi All,
While refreshing a Webi report, I am getting following error:
"A database error occured. The database error text is: The supplied XML is not valid. [Measures].[0701FBYSYG9KJQ47GRMMAVZ89]. (WIS 10901) ".
Could you please let me know how to resolve it?
Regards,

definition of one of your measure objects selected in the webi query is not correct in the universe. Parse the objects in the universe and find the objects with incorrect definition. This may be due to deletion of a key figure from BEx query. You can refresh the universe structure for updating it.

Similar Messages

Parse failed: Exception DBD, The supplied XML is not valid[Measures].[SAP_OBJECT_NAME] State:N/A error for hidden KFs when migrated to HANA

Hi All
Please help me with the following query. We are migrating SAP BW 7.4 on Oracle to HANA. We have few WEBI report's universes built on BEx queries. In one of those reports there are some hidden RKFs, these works perfectly fine in reports based on oracle. Now we migrated to HANA in development system and when i refresh the universe structure they started giving errors like "Parse failed: Exception DBD, The supplied XML is not valid[Measures].[SAP_OBJECT_NAME] State:N/A". The object giving this error is in hidden state. I tried to unhide it and run the report then it runs fine but that not the client want as there might be so many hidden KFs in other reports also. BO version is 4.1 SP 2. We are on SAPKW74006 support package on BW side. Is there any notes to correct this error. Please pass me the relevant links. Highly appreciate your help.
Thanks
Dwaraka

DCA-40012: The Web Service call failed. A connection to the target Web Service could not be created.
First of all test the web service you have created in model project. Right click the web service name and select "Test WebService". If you see any issue(s) while testing fix it first before you run the jspx page.
Check the port number in the URL and connections.xml, it have to be same.

SAP BW query to BOBJ Universe: The supplied XML is not valid.

Help!
The Business Objects Sever XI is giving us messages like the below, on some but not all BOBJ Universes based on SAP BW queries.
A database error occurred. The database error text is: The supplied XML is not valid. [various InfoObjects] [LEVEL01] (WIS 10901)
These queries were executing 1 working day, 3 calendar days ago. No transports to SAP BW or promotions to BOBJ were made.
Any ideas?
Thanks,
John Hawk
When we refresh the Universe, we get this mesdage
Error getting hierarchies for dimension 0INFOPROV (Cube FIGL_M10/FIGL_M10_Q001): Exception condition "HIERARCHY_NOT_FOUND" raised
Edited by: John Hawk on Jun 1, 2010 9:15 PM

Hi John,
I'm also getting same error 'Error getting hierarchies for dimension 0INFOPROV (Cube ZLE_M10/YBO_FREIGHT_ZLE_M10_UNIV_MPT1): Unknown error' when tried to create universe on top of query which is based on multi provider. Could you please send me copy of program ZZ_REPAIR_HIEDIR?
Thanks,
Milind

Parse failed: Exception: DBD, The supplied XML is not valid?

Hi,
I have created a OLAP Universe on top of SAP BEx Query which is having Filters. Below is code generated by Universe Designer Tool ...
<FILTER KEY="[!V000002]"><CONDITION OPERATORCONDITION="Between"><CONSTANT TECH_NAME="@Prompt('Calendar Month Interval From','A','Calendar Year/Month\LovCalendar Month IntervalBase',mono,primary_key)"/><CONSTANT TECH_NAME="@Prompt('Calendar Month Interval To','A','Calendar Year/Month\LovCalendar Month IntervalBase',mono,primary_key)"/></CONDITION></FILTER>
Can anyone suggest me how to solve this.
Regards,
Ramana.

Hi all,
Just refresh the universe structure and parse it and export it.
Actually the issue is, SAP BEx Query and its filters was changed after i have created Universe so what i have done is , created a new universe and named tat universe with the actual universe name.
So the filters parsing got success.

DPM 2012 R2 install fail - Reporting services "definition contains XML that is not well-formed or the XML is not valid"

Hi Everyone,
I've been battling with this for a while and I'm getting nowhere. I'm attempting to install DPM 2012R2 onto a fresh VM with a local SQL installation. The setup is as follows:
Server OS: 2008R2 SP1
SQL: 2008 R2 standard with SP3(tried SP2 before this)
Collation: SQL_Latin1_General_CP1_CI_AS
Reporting services installed: Yes(ticked do not configure during the installation)
Enabled reporting servics on port 80 with the default URL
DPM Installation does not throw any errors during the preinstall stage(The server passes all the checks)
Basically, when Installing. I get this error(extract):
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployFileInServer(Boolean recreate, ReportDBInfo rptInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployReports(String sourceFolderPath, Boolean recreate, Boolean calledFromSetup)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean calledFromSetup, String sourceFolderPath, String sqlServerName, String sqlInstanceName, String dbConnectionString)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteReporting, String sqlMachineName, String sqlInstanceName, String rsMachineName, String rsInstanceName, String installerPath)
[10/12/2014 2:35:25 p.m.] * Exception : => Report configuration failed.Verify that SQL Server Reporting Services is installed properly and that it is running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception
---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException: exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.ReportingException:
exception ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The report definition is not valid or supported by this version of Reporting Services. This could be the result of publishing a report definition of
a later version of Reporting Services, or that the report definition contains XML that is not well-formed or the XML is not valid based on the Report Definition schema. Details: Root element is missing.
at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings)
at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings)
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 Microsoft.Internal.EnterpriseStorage.Dls.UI.Reporting.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReport(String pathOfReport, ReportDBInfo rptInfo)
--- End of inner exception stack trace ---
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.CreateReport(String pathOfReport, ReportDBInfo rptInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployFileInServer(Boolean recreate, ReportDBInfo rptInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.DeployReports(String sourceFolderPath, Boolean recreate, Boolean calledFromSetup)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.Library.Reporting.Reporter.InstallReports(Boolean calledFromSetup, String sourceFolderPath, String sqlServerName, String sqlInstanceName, String dbConnectionString)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteReporting, String sqlMachineName, String sqlInstanceName, String rsMachineName, String rsInstanceName, String installerPath)
--- End of inner exception stack trace ---
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ReportingConfiguration.DeployReports(Boolean isRemoteReporting, String sqlMachineName, String sqlInstanceName, String rsMachineName, String rsInstanceName, String installerPath)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.DeployReports(String reportserverConfigFilePath, Boolean isOemSetup, String sqlMachineName, String sqlInstanceName, Boolean isRemoteReporting, String reportingServerMachineName, String
reportingInstanceName)
--- End of inner exception stack trace ---
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.BackEnd.DeployReports(String reportserverConfigFilePath, Boolean isOemSetup, String sqlMachineName, String sqlInstanceName, Boolean isRemoteReporting, String reportingServerMachineName, String
reportingInstanceName)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.DpmInstaller.DeployReports(Boolean isRemoteReporting, Boolean isUpgrade)
at Microsoft.Internal.EnterpriseStorage.Dls.Setup.Wizard.ProgressPage.InstallerThreadEntry()
*** Mojito error was: ReportDeploymentFailed; 0; None
[10/12/2014 2:35:25 p.m.] *** Error : Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running.
ID: 812
[10/12/2014 2:35:25 p.m.] Information : Data Protection Manager installation has failed. All the items that were copied during the installation process have been removed.
For details, click the Error tab.
Any ideas?
I've managed to get it to this stage. Originally I didn't have encryption keys or a listening port(which I fixed).

Can you try following steps:
If there are SSL certificates on your computer, by default SQL 2008
installation configures HTTPS for reporting websites. When DPM tries to
deploy reports on these websites it may fail if the reporting websites
are not accessible (might be due to invalid/expired certificates). To
workaround this, provided you do not require HTTPS for reporting websites do
the following:
1. Edit C:\Program Files\Microsoft DPM\SQL\MSRS10.MSDPMV3BETA1EVAL\Reporting
Services\ReportServer\rsreportserver.config
2. Set the SecureConnectionLevel to 0 if the current value is 2 (A value to
2 means secure connection is required)
3. Connect to SQL reporting service configuration manager and connect to the
instance MSDPMV3BETA1EVAL
4. Click on Web Service URL, click advanced and remove SSL identities
5. Repeat the above for Report Manager URL
6. Make sure report manager URL and web service URL are accessible with out
any errors.
6. Restart report server
If that doesn't solve the problem, please try following steps:
1. Open Start-> All programs->SQL server 2008->Configuration Tools->Report
Server Configuration Manager
2. Connect to the instance which the DPM is using to install.
3. Browse Report Manager URL and web service url
4. If report manager URL or web service url throws any error say 500 or 404
fix the error. (Try also replacing machine name with localhost in url)
5. Otherwise delete DPMReports folder (if present) using below instructions
6. Restart reporting services
7. Try DPM setup again.
Deleting DPM reports:
1. Open report manager URL in IE
2. Click show details on right hand side
3. Put a tick against DPMReports folder
4. Click Delete button.
Regards, Trinadh [MSFT] This posting is provided AS IS with no warranties, and confers no rights. If you found the reply helpful, please MARK IT AS ANSWER. Looking for source of information for DPM? http://blogs.technet.com/b/dpm/ http://technet.microsoft.com/en-in/library/hh758173.aspx

XML Document not Valid

Hi Techies,
I m making a xml document and that is validated on xml schema. But it is giving error that document is not valid because it is not deg\fining DOCTYPE element. Is it necessary to define it

It is not nesessary, but you have probably made your parser validating. In Java validating parsers use DTD to validate, and while schema validation is possibly those parsers are non-validating.

Orion-ejb-jar.xml is not valid

I am trying to parse orion-ejb-jar.xml as follows:
package test;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import org.apache.xml.serialize.*;
import org.xml.sax.*;
import java.io.*;
public class GetFieldSize {
String filePath = null;
Document document = null;
public GetFieldSize(String filePath) {
this.filePath = filePath;
public void constructDocument() {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
DocumentBuilder builder = factory.newDocumentBuilder();
builder.parse(new InputSource(new FileReader(filePath)));
} catch (FactoryConfigurationError fce) {
fce.printStackTrace();
} catch (ParserConfigurationException pce) {
pce.printStackTrace();
} catch (SAXException se) {
se.printStackTrace();
} catch (IOException ie) {
ie.printStackTrace();
public static void main(String[] args) {
GetFieldSize getFieldSize = new GetFieldSize("Z:\\nosqms\\ProcessTools\\qTools\\qTools\\qTools\\src\\META-INF\\orion-ejb-jar.xml");
getFieldSize.constructDocument();
I got the following parse error.
oracle.xml.parser.v2.XMLParseException: Expected '>'.
void oracle.xml.parser.v2.XMLError.flushErrors()
void oracle.xml.parser.v2.NonValidatingParser.parseMarkupDecl()
void oracle.xml.parser.v2.NonValidatingParser.parseDoctypeDecl()
void oracle.xml.parser.v2.NonValidatingParser.parseProlog()
void oracle.xml.parser.v2.NonValidatingParser.parseDocument()
void oracle.xml.parser.v2.XMLParser.parse(org.xml.sax.InputSource)
org.w3c.dom.Document oracle.xml.jaxp.JXDocumentBuilder.parse(org.xml.sax.InputSource)
void test.GetFieldSize.constructDocument()
void test.GetFieldSize.main(java.lang.String[])
When I opened the orion-ejb-jar.xml in IE, I got the following error:
A string literal was expected, but no opening quote character was found. Line 87, Position 1
CDATA #IMPLIED
Seems like problem with http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd.
How to rectify it?

1: Replace
isolation (committed | serializable | uncommitted | repeatable_reads)
CDATA #IMPLIED
locking-mode (pessimistic | optimistic | read-only | old_pessimistic)
by
isolation (committed | serializable | uncommitted | repeatable_reads) #IMPLIED
locking-mode (pessimistic | optimistic | read-only | old_pessimistic) #IMPLIED
2: in
<!ELEMENT ior-security-config (transport-config?, as-context?
sas-context?) >
add the final comma:
<!ELEMENT ior-security-config (transport-config?, as-context?, sas-context?) >

XML SAX dtd Validation Problem

Hi,
 I’m having problems getting an xml document to validate within Weblogic 8.1. I am trying to parse a document that references both a dtd and xsd. Both the schema and dtd reference need to be substituted so they use local paths. I specify the schema the parser should use and have created an entityResolver to change the dtd reference.
 When this runs as a standalone app from eclipse the file parses and validates without a problem. When deployed to the app server the process seems to be unable read the contents of the dtd. Its not that it cannot find the file (no FileNotFoundException is thrown but this can be created if I delete the dtd) rather it seems to find no declared elements.
 Initial thought was that the code didn’t have access to read the dtd from its location on disk, to check I moved the dtd to within the deployed war and reference as a resource. The problem still persists.
 Code Snippet:
 boolean isValid = false;
 try {
 // Create and configure factory
 SAXParserFactory factory = SAXParserFactoryImpl.newInstance();
 factory.setValidating(true);
 factory.setNamespaceAware(true);
 // To be notified of validation errors in the XML document,
 // add a custom error handler to the document builder
 PIMSFeedFileValidationHandler handler
 = new PIMSFeedFileValidationHandler();
 // Create and Configure Parser
 SAXParser parser = factory.newSAXParser();
 parser.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
 parser.setProperty(NAMESPACE_PROPERTY_KEY, getSchemaFilePath());
 // Set reader with entityResolver for dtd
 XMLReader xmlReader = parser.getXMLReader();
 xmlReader.setEntityResolver(new SAXEntityResolver(this.dtdPath));
 // convert file to URL, as it is a remote file
 URL url = super.getFile().toURL();
 // Open an input stream and parse
 InputStream is = url.openStream();
 xmlReader.setErrorHandler(handler);
 xmlReader.parse(new InputSource(is));
 is.close();
 // get the result of parsing the document by checking the
 // errorhandler's isValid property
 isValid = handler.isValid();
 if (!isValid) {
 LOGGER.warn(handler.getMessage());
 LOGGER.debug("XML file is valid XML? " + isValid);
 } catch (ParserConfigurationException e) {
 LOGGER.error("Error parsing file", e);
 } catch (SAXException e) {
 LOGGER.error("Error parsing file", e);
 } catch (IOException e) {
 throw new FeedException(e);
 return isValid;
 See stack trace below for a little more info.
 2005-01-28 10:24:09,217 [DEBUG] [file] - Attempting validation of file 'cw501205.wa1.xml' with schema at 'C:/pims-feeds/hansard/schema/hansard-v1-9.xsd'
 2005-01-28 10:24:09,217 [DEBUG] [file] - Entity Resolver is using DTD path file:C:/Vignette/runtime_services/8.1/install/common/nodemanager/
 VgnVCMServer/stage/pims-hansard/pims-hansard.war/WEB-INF/classes/com/morse/pims/cms/feed/sax/ISO-Entities.dtd
 2005-01-28 10:24:09,227 [DEBUG] [file] - Creating InputSource at: file:C:/Vignette/runtime_services/8.1/install/common/nodemanager/VgnVCMServer/stage/pims-hansard/pims-hansard.war/WEB-INF/classes/com/morse/pims/cms/feed/sax/ISO-Entities.dtd
 2005-01-28 10:24:09,718 [WARN ] [file] - org.xml.sax.SAXParseException: Element type "Hansard" must be declared.
 org.xml.sax.SAXParseException: Element type "Session" must be declared.
 org.xml.sax.SAXParseException: Element type "DailyRecord" must be declared.
 org.xml.sax.SAXParseException: Element type "Volume" must be declared.
 org.xml.sax.SAXParseException: Element type "Written" must be declared.
 org.xml.sax.SAXParseException: Element type "WrittenHeading" must be declared.
 org.xml.sax.SAXParseException: Element type "Introduction" must be declared.
 … continues for all the elements in the doc
 2005-01-28 10:24:10,519 [DEBUG] [file] - XML file is valid XML? false
 2005-01-28 10:24:10,519 [WARN ] [file] - Daily Part file 'cw501205.wa1.xml' was not valid XML and was not processed.
 Has anybody seen this behavior before with weblogic and if so how have you resolved the issue.
 Thanks in Advance
 Adam

It looks like you clicked on "Post" before you got around to explaining your problem. I don't see any error messages or any description of what was supposed to happen and what happened instead.
Now, I don't know anything about XML Schema, but just guessing at how that unique name feature might be designed, and just guessing that your unique name is actually in the <userId> element, I would suggest that this:
<xsd:unique name="un_name">
<xsd:selector xpath="USER"/>
<xsd:field xpath="."/>
</xsd:unique> is at fault because it doesn't mention the <userId> element anywhere.

Validating xml in pipeline - if not valid drop file in invalid folder

My goal is to receive an xml file through a customized pipeline so I can validate it. If it's valid I drop it in 'valid' folder. Then my orchestration will pick it from that location and do whatever it will do with it. This works fine.
But if the xml file is NOT valid I want to drop it in a an 'INVALID' folder and have a different orchestration pick it up and send an email to me. Is this possible? In my pipeline I don't have a dissambler, just an XMLValidator with the appropriate
schema in the document schemas collection. When I do drop in an 'invalid' xml file according to the schema, the pipeline is suspended. How can I drop that invalid xml file into a folder?
I've been learning/working with BizTalk for about 3 months. I'm trying to keep this simple and avoid doing any custom c# code until I'm more comfortable with BizTalk.
thank you in advance for your expert advice.
Jean Stiles

Hi Jean,
Your validation pipeline should promote the "MessageType" property of the message (if the orchestration doesn't have any other filters and if the orchestration's receive shape has a message type pointing to specific message). Its seems that when your validation
component validate any incoming message, after its process it shall promote the message type property of the message. Other wise you would not have any subscriber for the message published. The error "The published message could not be routed because no subscribers
were found" is due to this issue. i.e your orchestration subscription doesn't match to the message outputted by your custom vaidation component.
Not sure what is the full functionality of your custom validation component. if its simply validating the message, you can still get this functionality by using XML-Receive pipeline and set the property "Validate Document" to "True" and by specifying the
"DocumentSpecNames" to the schema which you want to validate the incoming message against.
If you're using custom pipeline to do standard validation, then follow like this:
Receive Port (with Enable routing for Failed Messages enabled) Receive Location with XML-Receive pipeline (Validate Document" to "True" and by specifying the "DocumentSpecNames" to the schema which you want to validate )
Bind the Receive Port to Orchestration - Do your process as normal
Create a send port with above filter for ErrorReport and configure this send port to send the invalid message to your invalid folder.
If you're using custom pipeline to something more than standard validation of XML-Receive pipeline , then follow like this:
Receive Port (with Enable routing for Failed Messages enabled) Receive Location with Your custom validation pipeline component.
Ensure your custom pipeline component promotes the message type property as
string systemPropertyNS = @”http://schemas.microsoft.com/BizTalk/2003/system-properties”;
outboundMsg.Context.Promote(“MessageType”, systemPropertyNS, “http://NameSpace#RootNode”);
replace the outboundMsg to the outbound message you output in your custom validation component. And message type to relevant value as yours. Or by some means ensure your custom pipeline output the message with matces to subcription expected by your Orchestration.
Bind the Receive Port to Orchestration - Do your process as normal
Create a send port with above filter for ErrorReport and configure this send port to send the invalid message to your invalid folder.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured

Today I tried to configure JAVA APM on a CentOS 6.4 server with tomcat6 installed through the normal RPM package. Adding this server to SCOM was no problem and it shows itself as a 'Deep Monitored Configuration'. The last part of enabling
JAVA APM fails. I have followed the following process:
1. Imported the JAVA APM MP's
2. Extracted the JAVA APM Files
3. Copied those files to my CentOS server
4. Added the JAVA_OPTS to my tomcat configuration file
5. Restarted Tomcat
When I look for the log file which needs to be created through the installation of the APM agent it cannot be find. When I look into my Catalina.out file I see the following errors:
Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
com.microsoft.ManagementServices.APMAgent.Exception.ApmException: SEAgent.config.xml does not have a valid event sender configured
 at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
 at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
 at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
 ... 15 more
Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
 at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.AgentThreadManager.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
 at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
 at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
Caused by: java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
 ... 15 more
Caused by: com.microsoft.ManagementServices.APMAgent.Exception.ApmException: Error registering MBean: com.microsoft.ManagementServices.APMAgent:type=COUNTER
 at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.registerMetricMBeans(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.EventSender.MBeanEventLog.<init>(Unknown Source)
 ... 19 more
Mar 05, 2014 7:05:16 PM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
 at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
 at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
 at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
 at com.microsoft.ManagementServices.APMAgent.Agent.Startup.AgentContextLoader.loadContext(Unknown Source)
 at com.microsoft.ManagementServices.APMAgent.Agent.Startup.Agent.premain(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:601)
 at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:382)
 at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:397)
Caused by: java.lang.InstantiationException: Monitor initialization failed: SEAgent.config.xml does not have a valid event sender configured
 at com.microsoft.ManagementServices.APMAgent.Agent.Monitor.AgentContext.<init>(Unknown Source)
 ... 12 more
Does anyone have seen this error before? Can someone help me with this one?
Thnx,

I'm running tomcat on a CentOS release 6.4 (Final) server. I installed Tomcat 6 through an RPM from the CentOS sources. I have installed Apache Tomcat/6.0.24 wit JVM version 1.7.0_09-icedtea-mockbuild_2013_01_16_18_52-b00, the JVM Vendor is Oracle Corporation.
My tomcat configuration needs to be done in '/etc/tomcat6/tomcat6.conf'
I installed the APM Agent in the path '/opt/apm/' with the rights 40755 (root/root). The files have the following rights:
-rw-rw-r-- 1 root tomcat 32046 Mar 3 15:38 apm_facade.jar
-rw-rw-r-- 1 root tomcat 244819 Mar 3 15:38 apm_monitor.jar
-rw-rw-r-- 1 root tomcat 38110 Mar 3 15:38 apm_producers.jar
-rw-rw-r-- 1 root tomcat 207006 Mar 3 15:38 asm-all-3.3.1.jar
-rw-rw-r-- 1 root tomcat 4157 Mar 3 15:38 ASM_Third_Party_Notices.txt
-rw-rw-r-- 1 root tomcat 241368 Mar 3 15:38 DispatcherStub.dll
-rw-rw-r-- 1 root tomcat 36880 Mar 3 15:38 pmonitor.config.xml
-rw-rw-r-- 1 root tomcat 2625 Mar 3 15:38 SEAgent.config.xml
-rw-rw-r-- 1 root tomcat 830 Mar 5 15:19 Starter.properties
The above rights are equal to the /etc/tomcat6 directory with the tomcat configuration files.
In the tomcat6.conf I have added the following entries:
#Microsoft SCOM APM
JAVA_OPTS="${JAVA_OPTS} -Djava.library.path=/opt/apm"
JAVA_OPTS="${JAVA_OPTS} -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar"
When I look into the running tomcat process I see the following:
tomcat 17401 1 0 Mar05 ? 00:00:39 /usr/lib/jvm/jre/bin/java -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar
-Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -Djava.library.path=/opt/apm -javaagent:/opt/apm/apm_facade.jar -Xbootclasspath/p:/opt/apm/apm_producers.jar -Xbootclasspath/p:/opt/apm/apm_facade.jar -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory
-classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat6/temp
-Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start
My Starter.Properties looks like this:
# Jars to load by inner classloader.
# Use semicolons to separate the JAR entries
ClassPath=apm_monitor.jar;asm-all-3.3.1.jar;apm_producers.jar
# Path to pmonitor.config
MonitorConfigFileName=pmonitor.config.xml
# Path to SEAgent.config
AgentConfigFileName=SEAgent.config.xml
# Log file name
# Example for full-path location:
# LogFileName=c:\\tracelog\\apm-java-agent.log
# Example for relative path (to agent jar files):
# LogFileName=apm-java-agent.log
LogFileName=apm-java-agent.log
# Log level (SEVERE, WARNING, INFO, CONFIG, FINE, FINER, FINEST)
# A level of FINER or FINEST may expose Personally identifiable
# information (PII) in the log file. The levels below INFO are
# intended for debugging and diagnostic use only.
LogLevel=FINEST
The 'apm-java-agent.log' is not created on the system. The only logging is done in the catalina.out. When restarting tomcat I see the following entries in te log file:
INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
INFO: Java APM Agent loading succeeded (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
INFO: Initializing Java APM Agent (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger warning
WARNING: Failed registering the COUNTER MBean
Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger error
SEVERE: Java APM Agent initialization failed: SEAgent.config.xml does not have a valid event sender configured
Mar 06, 2014 9:35:21 AM com.microsoft.ManagementServices.APMAgent.Log.SystemLogger info
INFO: Java APM Agent loading failed (Build: 1.10.100.15, Label: NotFromLabel, BuildDate: 20131112)
Hope this gives your some more background around my problem, I double checked the permissions..

XML Parser Message: Element series is not valid for the content model

Hello,
I work with FrameMaker 8 and DITA.
I change the element prodinfo in the topic.edd from:
General rule: (prodname), (vrmlist), (brand | series | platform | prognum | featnum | component)*
to:
General rule: (brand | series | platform | component)*
When I import the element definition to the template everything is okay.
When I insert the elements metadata, prodinfo, brand, series, platform and component into a topic I get the XML Parser Message that the element brand is not valid for the content model (prodname,vrmlist, ((brand|series|platform|prognum|featnum|component))*).
When I delete the element brand in the topic I get the XML Parser Message that the element series is not valid for the content model (prodname,vrmlist, ((brand|series|platform|prognum|featnum|component))*).
I change the element prodinfo in the topic.edd to:
General rule: (brand)?, (series)?, (platform)?, (component)?
...and get the same Parser Message.
I do not understand that. Is not it allowed to change the EDD this way without changing the DTD?
With kind regards
Nina

Hi Nina... In general, the EDD and DTD need to sync up. You can remove elements from an EDD element definition's general rule, as long as the resulting elements are still valid to the DTD. But if changing a general rule creates an invalid structure, you'll need to also change the DTD to allow the revised structure. With DITA, it is common to remove inline elements from block-level elements. For example, you might want to remove the <msgblock>, <msgnum>, and <msgph> elements from the general rule of the element .. this can be done easily in the EDD and the resulting structure remains valid with the DTD. However, what you're doing leaves the <brand> element as a child of <prodinfo> .. which is invalid. You'll get these errors when saving a file, since this is when the file is validated against the DTD. I do not recommend modifying the structure in such a way that requires you to modify the DTD. If you really need to do this, then you should consider making a specialization to support your revised model. I hope this helps. Cheers and Happy New Year! ...scott

The parameters supplied for the batch are not valid.

Error:The parameters supplied for the batch are not valid
Stored Procedure is as follows
CREATE PROCEDURE [dbo].[Usp_TrackVehicleDetails]
@reg_Number NVARCHAR(25)
AS
BEGIN
SET NOCOUNT ON;
DECLARE @Imei_Number NVARCHAR(25),
@Imei_Table
NVARCHAR(MAX),
@Latitude_Val
NVARCHAR(MAX),
@Longitude_Val NVARCHAR(MAX),
@Imei_PK
NVARCHAR(MAX),
@result INT
-- Tracking Device by means of Latitude and Longitude
SELECT @Imei_Number=Imei_No FROM MapDevice_Vehicle WHERE Vehicle_No=@reg_Number;
SELECT @Imei_Table='Imei_'+@Imei_Number
SET @Imei_PK='SELECT(MAX(CAST(Imei_Id AS NVARCHAR(MAX)))) FROM dbo.'+@Imei_Table;
SET @Latitude_Val='SELECT Latitude FROM dbo.' +@Imei_Table+' WHERE CAST(Imei_Id AS NVARCHAR(MAX))='+'('+@Imei_PK+')';
SET @Longitude_Val='SELECT Longitude FROM dbo.' +@Imei_Table+' WHERE CAST(Imei_Id AS NVARCHAR(MAX))='+'('+@Imei_PK+')';
EXEC @result= sp_executesql @Imei_PK,@Latitude_Val,@Longitude_Val
SELECT @result
--RETURN @result
BEGIN TRY
BEGIN TRANSACTION T1
-- Returning Values based on Vehicle_Number
SELECT ISNULL(@Latitude_Val,'')[latitude],
ISNULL(@Longitude_Val,'')[longitude]
IF @@ERROR!=0
BEGIN
ROLLBACK TRANSACTION T1
END
ELSE
COMMIT TRANSACTION T1
END TRY
BEGIN CATCH
SELECT ERROR_MESSAGE() AS ErrMsg, ERROR_LINE() AS ErrLine,ERROR_PROCEDURE() AS ErrProc
END CATCH
END

Your construct is not correct....
EXEC @result= sp_executesql @Imei_PK,@Latitude_Val,@Longitude_Val --These
should be parameters/....
Please try the below(The longitude and latitude to be included...)
/*Test script*/create table MapDevice_Vehicle(vehicle_no nvarchar(25),imei_no nvarchar(25))
Insert into MapDevice_Vehicle Select 'KL8P8234','KL'
create table Imei_KL(Imei_Id nvarchar(25))
Insert into Imei_KL Select 'KL8P8234'
exec [Usp_TrackVehicleDetails] 'KL8P8234'/*Test script*/
CREATE PROCEDURE [dbo].[Usp_TrackVehicleDetails]
@reg_Number NVARCHAR(25)
AS
BEGIN
SET NOCOUNT ON;
DECLARE @Imei_Number NVARCHAR(25),
@Imei_Table NVARCHAR(MAX),
@Latitude_Val NVARCHAR(MAX),
@Longitude_Val NVARCHAR(MAX),
@Imei_PK NVARCHAR(MAX),@paramdefs nvarchar(MAX),@result INT
-- Tracking Device by means of Latitude and Longitude
SELECT @Imei_Number=Imei_No FROM MapDevice_Vehicle WHERE Vehicle_No=@reg_Number;
SELECT @Imei_Table='Imei_'+@Imei_Number
SET @Imei_PK='SELECT(MAX(CAST(Imei_Id AS NVARCHAR(MAX)))) FROM dbo.+@Imei_Table';
SET @paramdefs = N'@Imei_Table nvarchar(255)';
--SET @Latitude_Val='SELECT Latitude FROM dbo.' +@Imei_Table+' WHERE CAST(Imei_Id AS NVARCHAR(MAX))='+'('+@Imei_PK+')';
--SET @Longitude_Val='SELECT Longitude FROM dbo.' +@Imei_Table+' WHERE CAST(Imei_Id AS NVARCHAR(MAX))='+'('+@Imei_PK+')';
EXEC @result= sp_executesql @Imei_PK,@paramdefs,@Imei_Table = @Imei_Table
SELECT @result
--RETURN @result
BEGIN TRY
BEGIN TRANSACTION T1
-- Returning Values based on Vehicle_Number
SELECT ISNULL(@Latitude_Val,'')[latitude],
ISNULL(@Longitude_Val,'')[longitude]
IF @@ERROR!=0
BEGIN
ROLLBACK TRANSACTION T1
END
ELSE
COMMIT TRANSACTION T1
END TRY
BEGIN CATCH
SELECT ERROR_MESSAGE() AS ErrMsg, ERROR_LINE() AS ErrLine,ERROR_PROCEDURE() AS ErrProc
END CATCH
END

Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state

we have developed packages to do the followings
Extract data from DB2 Source and put it in MS Sql Server 2008 database (Lets Say DatabaseA).From MS Sql Server 2008 (DatabaseA)
we will process the data and place it in another database MS Sql Server 2008 (DatabaseB)
We have created packages in BIDS..We created datasource connection in Datasource folder in BIDS..Which has DB2 Connection and both Ms Sql Server connection (Windows authentication-Let
say its pointing to the server -ServerA which has DatabaseA and DatabaseB).The datasource connections will be used in packages during development.
For deployment we have created Package Configuration which will have both DB2 Connection and MS SqlServer connection in the config
We deployed the packages in different MS SqlServer by changing the connectionstring in the config for DB2 and MS SqlServer...
While runing the package we are getting the following error message
Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for
use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.
ilikemicrosoft

Hi Surendiran,
This is because the package has been created by somebody else and the package is being deployed under sombody else's account. e.g. If you are the creator then the package is encryption set according to your account and the package setup in SQL server is
under a different user account.
This happens because the package protection level is set to EncryptSensitiveWithUserKey which encrypts
sensitive information using creator's account name.
As a solution:
Either you have to set up the package in SQL server under your account (which some infrastructures do not allow).
OR
Set the package property Protection Level to "DontSaveSensitive" and add a configuration file
to the package and set the initial values for all the variables and all the connection manager in that configuration file (which might be tedious of-course).
OR
The third options (which I like do) is to open the package file and delete the password encryption entries from the package. Do note that this is not supported by designer and every time you make changes to the connection managers these encryption entries come
back.
Hope this helps.
Please mark the post as answered if it answers your question

FMLE3.5 Won't accept XML - Say it's not valid profile

FME won't accept my cutom profiles.
I use PHP to output a 100% identical copy of a already functional XML profile, but FME tells me that the profile is not valid.
Just to be sure I copy everything from a working XML, into notepad or editplus, and save it, then try to open it in FME it gives the same error? I've done no changes what so ever.
What kind of encoding does it use? Or what is wrong? Does it react on linespaces or linebreaks that a editor may apply?
When I open a XML profile from ustream, fmle3.5 or justiv.tv, the format is all messed up. Is this what I need to achieve?
Example of how I try to ouput it from PHP.
$data = "<?xml version=\"1.0\" encoding=\"UTF-16\"?>\n";
$data .= "<flashmedialiveencoder_profile>\n";
$data .= "<preset>\n";
$data .= "<name>Custom</name>\n";
$data .= "<description></description>\n";
............. and so on is what I use to output with PHP
Any suggestions?

Problem in your profile is solved after following steps:
1. I Opened the profile that you sent in notepad.
2. It shows me that you saved the profile using ANSI encoding.
3. I resaved the profile using Notepad in Unicode Big Indian encoding.
Then it worked fine in FMLE.
Hope this works fro you too.
I am attaching edited file also for your further reference.
Regards,
Neha

XML Schema dependencies is not valid in osb 11g version

Hi,
I'm working in osb 11.1.1.5 version.I have to import the 10g project in 11g server, but in my 10g project some schemas are included in another schemas.When i'm trying to export the resources in the 10g console and importing it in the 11g console i'm getting the errors. XML Schema dependencies is not valid in osb 11g version.Is there any alternative to import the 10g project in 11g in this case?Please suggest.
Thanks in advance!

while running the proxy in the eclipse i'm getting the error
servicebus:/XMLSchema/HistoricLoadService/Schemas/CCD/datatypes-base:998:2: error: derivation-ok-restriction.5.3a: A type with a mixed content model can only restrict another type with a mixed content model. at poc_ccd.xsd
When i'm trying to export the project from 10g console and importing it from osb 11g console I'm getting the conflicts like
servicebus:/XMLSchema/HistoricLoadService/Schemas/CCD/datatypes-base:289:2: error: derivation-ok-restriction.5.3: Must be a valid restriction.
Resource XMLSchema HistoricLoadService/Schemas/CCD/ poc_ccd forms a cyclic reference

Supplied XML is not valid

Similar Messages

Maybe you are looking for