BEA-090513 -- ServerIdentity failed validation, downgrading to anonymous

I'm getting this error when starting up my instance. I only have one domain, so the information in the error message list about enabling trust between domains should not apply here.
I get the error mentioned in the topic with BEA code BEA-090513
What other ways are there to fix this error?

I think, if you only have a single domain, the only thing that could be causing this is a misconfiguration. Can you recreate the domain? Can you confirm that the config.xml files on all servers are identical?

Similar Messages

Server Crash : ServerIdentity failed validation, downgrading to anonymous

All,
Setup is as follows:
Domain has got an admin server and 2 managed servers.
Managed Server 1 on Machine 1
Managed Server 2 on Machine 2
Following error is continuously thrown in the logs :
<22-Jul-2010 09:54:45 o'clock> <Error> <Security> <managed1> <ExecuteThread: '2' for queue: 'weblogic.
socket.Muxer'> <<WLS Kernel>> <> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
Can this 090513 error on JMS queue lead to a server crash ?
I also get the below error
<ExecuteThread: '2' for queue: 'weblogic.adm
in.RMI' : Executing(weblogic.management.internal.MBeanHomeImpl)> <<WLS Kernel>> <> <BEA-080003> <RuntimeException thrown by r
mi server: weblogic.management.internal.MBeanHomeImpl.getMBean(Ljavax.management.ObjectName;)
java.lang.NullPointerException.
java.lang.NullPointerException
at weblogic.management.internal.MBeanHomeImpl.getMBean(MBeanHomeImpl.java:109)
Regards,
Rashi

Does this domain have rmi communication with another weblogic domain? If so this error would normally occur if you have not enabled domain trust between the domains. You can enable domain trust by following the steps in the below link :
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/domain.html#wp1176064
Not sure is this alone will crash a server. Is there any other errors in the logs ?

BEA-090513 "ServerIdentity failed validation" on single domain single server

Hi!
I'm getting loads of
<Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading
to anonymous.>
errors though I'm running a single server in a single domain - so the information
in
http://e-docs.bea.com/wls/docs81/messages/Security.html
isn't very helpful. What can I do to remove this problem?
Thanks so much,
Hans-Peter Stoerr

Hi I get the similar error
<Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
<Sep 12, 2007 4:04:51 PM CDT> <Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
####<Sep 12, 2007 2:47:32 PM CDT> <Error> <Security>sb1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defau
lt (self-tuning)'> <<WLS Kernel>> <> <> <1189626452736> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
####<Sep 12, 2007 2:47:32 PM CDT> <Error> <Security> > <sb1> <ExecuteThread: '8' for queue: 'weblogic.socket.Muxer'> <<WLS
Kernel>> <> <> <1189626452759> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
####<Sep 12, 2007 2:47:32 PM CDT> <Error> <Security> < <sb1> <ExecuteThread: '8' for queue: 'weblogic.socket.Muxer'> <<WLS
Kernel>> <> <> <1189626452760> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
I tried the bea method to change the credentials that the domain is interacting with (trust certificate) but no help.The errors keep coming still.
iN order to rule out some possiblity i shutdown the other domain completley and i could still see same errors in my managed server logs.i would really appreciate anyones tips to fix this issue.

ServerIdentity failed validation, downgrading to anonymous

I'm getting this error when trying to run one of the application
deployed in my domain. I only have one domain, so the information in the
error message list about enabling trust between domains should not apply
here.
I get the error mentioned in the topic with BEA code BEA-090513
What other ways are there to fix this error?

Here's a more complete stack trace from the server log:
####<Nov 18, 2003 10:12:10 AM EST> <Error> <Security> <ORLEX1090> <demoServer>
<ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-090513>
<ServerIdentity failed validation, downgrading to anonymous.>
####<Nov 18, 2003 10:12:10 AM EST> <Error> <Security> <ORLEX1090> <demoServer>
<ExecuteThread: '0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-090513>
<ServerIdentity failed validation, downgrading to anonymous.>
####<Nov 18, 2003 10:12:10 AM EST> <Warning> <RMI> <ORLEX1090> <demoServer> <ExecuteThread:
'0' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080003> <RuntimeException
thrown by rmi server: weblogic.management.internal.RemoteMBeanServerImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;[Ljava.lang.Object;[Ljava.lang.String;)
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime.
weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
principals=[], on ResourceType: ServerConfig Action: execute, Target: lookupServerRuntime
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.wlsRun(SecurityHelper.java:557)
     at weblogic.management.internal.SecurityHelper$IsAccessAllowedPrivilegeAction.run(SecurityHelper.java:453)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.management.internal.SecurityHelper.isAccessAllowed(SecurityHelper.java:347)
     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:764)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:466)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:409)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:404)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Steven Ostrowski <[email protected]> wrote:
I'm getting this error when trying to run one of the application
deployed in my domain. I only have one domain, so the information in
the
error message list about enabling trust between domains should not apply
here.
I get the error mentioned in the topic with BEA code BEA-090513
What other ways are there to fix this error?

ServerIdentity failed validation

I am porting over some code from WebLogic 6.1 to 8.1 and getting the following
errors. Any clue as to what these might be? Thanks.
<Error> <Security> <BEA-090513> <ServerIdentity failed validation, downgrading
to anonymous.>
<Error> <JTA> <BEA-110200> <User [<anonymous>] is not authorized to invoke startCommit
on a transaction branch.>

The problem went away after I established trust between the two domains. Thanks
so much for your help.
Naresh
"Peter" <PeterB> wrote:
>
"Naresh Bhatia" <[email protected]> wrote in message
news:[email protected]..
I am porting over some code from WebLogic 6.1 to 8.1 and getting thefollowing
errors. Any clue as to what these might be? Thanks.
<Error> <Security> <BEA-090513> <ServerIdentity failed validation,downgrading
to anonymous.><messagedetail>
The ServerIdentity failed validation. Within this domain, the server
identity is downgraded to Anonymous.
</messagedetail>
<cause>
Trust has not been properly established between two domains.
</cause>
<action>
See the documentation on Enabling Trust Between WebLogic Domains at
http://e-docs.bea.com.
</action>

JAAS between WLS (untrusted) domains - ServerIdentity failed validation

I'm trying to create a proxy/delegate class that can be used by clients to
transparently access a server.
The class should be usable from clients within WLS containers and from
regular java apps.
Using JNDI authentication everything works fine.
Using JAAS I'm having a problem when my client is a EJB app in an untrusted
WLS domain. When the login is requested the following error is occuring:
<ServerIdentity failed validation, downgrading to anonymous.>
I want to be able to do a JAAS login to a non-trusted domain. I'm assuming
that the server is trying to pass the subject who is logged into the current
container, and my call to LoginContext.login()
Any thoughts?
//Example of code
loginContext = new LoginContext("ServiceSecurity", new
FW_SimpleCallbackHandler(pUser, pPassword, pUrl));
loginContext.login();
Subject subject = loginContext.getSubject();
serviceHome = (ServiceHome)weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//JNDI lookup
//Create session bean instance
weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//do operation on instance

Then I'd start talking to BEA support to see if they even know how to do
this.
Without the trust relationship I'm not sure if you can achieve what you
want.
Dejan
Mark Fine wrote:
This is exactly what I am doing.
Implicitly there is a security context within the session bean (the user
logs in via the web app and context is propagated). I obtain a LoginContext
to the other server and call the method within that context.
It doesn't work because it is implicitly passing the security context of the
session bean and failing due to lack of trust.
//Example of code
loginContext = new LoginContext("ServiceSecurity", new
FW_SimpleCallbackHandler(pUser, pPassword, pUrl));
loginContext.login();
Subject subject = loginContext.getSubject();
serviceHome = (ServiceHome)weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//JNDI lookup
//Create session bean instance
weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//do operation on instance
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
In that case you should be able to get the two different Subjects from
the two different domains (return a different url from the URLCallback
when you login with JAAS), and afterwards use
weblogic.security.Security.doAs(...);
with the correct Subject for the appropriate server when you access the
servers.
HTH,
--dejan
Mark Fine wrote:
Thanks, but i think the content was miscommunicated. Everything works
fine
when the domains are "trusted". I want to know how to have "untrusted"
domains talk to each other through explicit logins.
ie. imagine an application on a domain in a finance department. What if
they are trusted against other domains and can't / don't want to
establish
trust with your domain. They just need access to one particular service
you
expose.
Thanks,
m
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Hi Mark,
You should first establish a trust relationship between your Weblogic
servers:
http://e-docs.bea.com/wls/docs70/secmanage/domain.html#1171534
Then you can use JAAS to authenticate and get valid Subjects for the two
users.
--dejan
Mark Fine wrote:
I'm trying to create a proxy/delegate class that can be used by clients
to
transparently access a server.
The class should be usable from clients within WLS containers and from
regular java apps.
Using JNDI authentication everything works fine.
Using JAAS I'm having a problem when my client is a EJB app in an
untrusted
WLS domain. When the login is requested the following error is
occuring:
<ServerIdentity failed validation, downgrading to anonymous.>
I want to be able to do a JAAS login to a non-trusted domain. I'm
assuming
that the server is trying to pass the subject who is logged into the
current
container, and my call to LoginContext.login()
Any thoughts?
//Example of code
loginContext = new LoginContext("ServiceSecurity", new
FW_SimpleCallbackHandler(pUser, pPassword, pUrl));
loginContext.login();
Subject subject = loginContext.getSubject();
serviceHome = (ServiceHome)weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//JNDI lookup
//Create session bean instance
weblogic.security.Security.runAs( subject,
new PrivilegedExceptionAction() {
public Object run() throws Exception{
//do operation on instance

BEA-090513

I do see this asked in quite a few topics but I still have questions:
          BEA WLS 8.1.4
          App (MDB's) on Domain A is trying to connect to Domain B' JMS (subscribe to Topics on Domain B).
          The domain B's log is full of messages like this though the MDB's on Domain A's App do get the messages published to the Topics.
          ####<May 17, 2007 1:12:12 PM GMT> <Error> <Security> <server1.corp.com> <App1> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <BEA-090513> <ServerIdentity failed validation, downgrading to anonymous.>
          From what I have read, looks like we need to establish Domain Trust between the 2.
          My questions:
          1. Is this just a nuisance of a message which can be suppressed somehow ?
          2. What are the other ramifications of this (enabling Domain Trust) ? I don't want to open up some kind of security hole etc.
          3. An other way (apart from establishing Domain Trust) this can be fixed.
          Thanx,

And also the admin shows Health status of others OK very slowly it may take more than 30mins for all servers(13) to show the Heath state as OK untill then it shows Not reachable..

Server Identity error downgrading to anonymous

I have to applications
Appl 1 is the real application Entitys, Statefull, and Stateless
Appl 2 (connector) is a wrapper over the Stateless methods, that let users
use arguments of type simple (Strings, int, double, etc...)
When both applications are on the same server they work fine.
When I deploy de connector application on a server in a different machine I obtain
<Error> <Security> <aquiles.melo> <desa> <ExecuteThread: '0' for queue: 'default'>
<kernel identity> <> <090473> <ServerIdentity failed validation, downgrading to
anonymous.>
and then
<Error> <JTA> <aquiles.melo> <desa> <ExecuteThread: '6' for queue: 'default'>
<kernel identity> <> <110201> <User [<anonymous>] is not authorized to invoke
startRollback on a transaction branch.>
I suppose I must configure the servers to recognize each other, and I really
could not find the way to do it.
(I must say I'm a newbie in J2EE security issues)
Any help will be welcomed.
Hope it is clear enough.
Thanks in advance
[email protected]

I found the way to solve this issue in e-docs.bea.com,
sorry for bothering you.
Look for "Enabling Trust Between WebLogic Domains" and you will
find the answer.
Bye
"Tonio Caputo" <[email protected]> wrote:
>
I have two (2) applications
Appl 1 is the real application Entitys, Statefull, and Stateless
Appl 2 (connector) is a wrapper over the Stateless methods, that let
users
use arguments of type simple (Strings, int, double, etc...)
When both applications are on the same server they work fine.
When I deploy de connector application on a server in a different machine
I obtain
<Error> <Security> <aquiles.melo> <desa> <ExecuteThread: '0' for queue:
'default'>
<kernel identity> <> <090473> <ServerIdentity failed validation, downgrading
to
anonymous.>
and then
<Error> <JTA> <aquiles.melo> <desa> <ExecuteThread: '6' for queue: 'default'>
<kernel identity> <> <110201> <User [<anonymous>] is not authorized to
invoke
startRollback on a transaction branch.>
I suppose I must configure the servers to recognize each other, and I
really
could not find the way to do it.
(I must say I'm a newbie in J2EE security issues)
Any help will be welcomed.
Hope it is clear enough.
Thanks in advance
[email protected]

OSB Validate action failed validation

Hi All,
I'm trying to convert non-xml to xml by using XqueryTransformation source as an HL7 and target as an CCD schema.When validating the against the schema I got the following exception.
Please provide any suggestions.
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382505</con:errorCode>
<con:reason>OSB Validate action failed validation</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
string value '' does not match pattern for cs in namespace urn:hl7-org:v3
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
<con1:message>
Element 'title@urn:hl7-org:v3' with empty content type cannot have text or element content.
</con1:message>
<con1:xmlLocation>
<ns0:title xmlns:ns0="urn:hl7-org:v3">XXX</ns0:title>
</con1:xmlLocation>
</con1:ValidationFailureDetail>
</con:details>
Thanks
Mani

Hi Anuj,
I tried doing that but in Response, it is echoing back the request after the statement:
The invocation resulted in an error: .
And now it shows:
Stage Error Handler
$fault: <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382505</con:errorCode>
<con:reason>OSB Validate action failed validation</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
string value '2' is not a valid enumeration value for VersionType in namespace http://www.example.org/abcd_Request_Schema
</con1:message>
<con1:xmlLocation>
<abcd:Version xmlns:abcd="http://www.example.org/abcd_Request_Schema">2</abcd:Version>
</con1:xmlLocation>
</con1:ValidationFailureDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>request xml validation</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
System Error Handler
$fault: <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>402</con:errorCode>
<con:reason>
Validation Failed. Please enter proper values.
</con:reason>
<con:details>
<con1:ValidationFailureDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:message>
string value '2' is not a valid enumeration value for VersionType in namespace http://www.example.org/abcd_Request_Schema
</con1:message>
<con1:xmlLocation>
<abcd:Version xmlns:abcd="http://www.example.org/abcd_Request_Schema">2</abcd:Version>
</con1:xmlLocation>
</con1:ValidationFailureDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>request xml validation</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
Is there any way by which only the customized error can be seen & not the OSB errors?

Dimension 'Years' failed validation

Hi All,
I am getting this error while deploying the application.
Error : Dimension 'Years' failed validation 'YearMembersSequential' for the following reason(s): Year members must be sequential.
I am seeing my Year dimension is sequential only.
I am not able to figure out the reason for this error . Can anyone please help me understand this.

Not to open a new thread as I have an issue with dimension Year as well, I will post my problem here (hope the author won't mind).
I created a simple EPMA application in version 11.1.2.2 with all mandatory and 2 generic dimensions. One of mandatory dimension is, of course, Year (dimension type: Year) with following members: FY11, FY12, FY13. Initial deployment against both, Planning and Essbase went well. After that I wanted to extend dimension Year for member FY14 and to redeploy the application. Validation was successful, but deployment message was "Completed/With Errors" (100%). Deployment was done with selecting "Refresh outline" and "Full deploy". In deployment log file I have the following entry:
"Consolidation operators for years must be set to Ignore for all plan types."
"Rejecting Member FY14."
This message is clear enough, but the problem is that members that belong to dimension type Year don't even have consolidation operators in properties area.
What else comes to my mind is that (maybe) with version 11.1.2.2 it is not allowed to add new members for dimension Year once application is deployed for the very first time. But in that case, the above error message is quite misleading. Under version 11.1.1.3 it is possible to add new members to dimension Year and to redeploy it without errors.
Is this a bug or a feature?
Has anyone had such problem?
Thanks,
Damir

Apple's Audio Units Fail Validation in Yosemite

Why do Apple's audio units fail validation in Yosemite
Anyone else having this problem ?
What's the fix ?
Even Logic Pro X 10.0.7 can't validate Apple's AU plugs.
[Rant: i have never been so disappointed with a Mac OS as i am with YO. Most of my midi/audio/video programs will not work because of the validation of AU/VST plugs. I am this close to trashing Yosemite . It reminds me of my OS 9 days: if you even looked in the wrong direction the system stop working.]

are there any AU plugs here, in the components folder...?

File Browse is emptied after failed validation

Why does the file browse text box get emptied after a failed validation? Is there any way to prevent this?
To further explain, create a form on a page with two page items, a text box and a file browse item, then put a not null validation on the text box. When you submit the page with a null text box, but with a file selected for the browse button, then validation catches and throws the error message back to the user when the page refreshes. However, the file browse text box is emptied, and the user has to reselect the file before resubmitting the page.
Is this a bug, or just the way it is supposed to work? Any way around it?
Thanks,
Kris
Edited by: kshenn on Oct 31, 2008 7:06 AM

Hello,
>> Is this a bug, or just the way it is supposed to work?
This is not a bug. Actually, it has nothing to do with APEX. The behavior of the file browse item is controlled by the HTML standard, which clears the field for security reasons.
If you pay close attention to Denes example, you’ll see that even when the validation error page is displayed, the file browse item itself is being cleared. The JavaScript generated file path is the one that retain its value. I don’t have access to Denes code, but I’m assuming that in his uploading procedure he’s using the JavaScript generated path.
>> Any way around it?
Where the file browse item is concern, no workaround.
In your specific case, where the validation you need is “not null”, you can create a JavaScript validation, and fire it before submitting the page (as part of the submit button). That way, the browser will not clear the file browse item, because the page will not be submitted without proper values in your items.
Regards,
Arie.

Critical WebLogicServer BEA-000362 Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException

Friends,
Getting below error when i restart the server.
<Dec 31, 2014 5:33:58 AM EST> <Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>
<Dec 31, 2014 5:34:07 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException>
<Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 31, 2014 5:34:07 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
I have changed the jar files path in build.properties file as its required to import new jars as part of Documentum server upgradation. But getting above errors.. Do i have to update Config.xml file or any other file.. Please suggest.

You've got a problem with a corrupted config.xml file.
Since you did not make any changes you can copy the config.xml.booted file over the corrupted config.xml.
The other option is to walk though the config.xml file and look for the problem...

Failed validation as a non-ragged hierarchy

After I define a TIME dimension and try to Maintain Dimension (Loading data at first time), it encounters error as below:
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01714: "TIME_TEST_HA.TIME_TEST_HA" failed validation as a non-ragged hierarchy, Generic at TxsOqStdFormCommand::execute
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.callGeneric(Unknown Source)
at oracle.olapi.data.source.DataProvider.executeBuild(Unknown Source)
at oracle.olap.awm.wizard.awbuild.UBuildWizardHelper$1.construct(Unknown Source)
at oracle.olap.awm.ui.SwingWorker$2.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Here is the data from related table TIME_TEST:
SELECT * FROM TIME_TEST;
YEAR QUARTER MONTH DAY
2008 4 11 5
2008 1 2 6
2008 4 10 7
2009 1 1 1
2009 1 1 5
Any help will be appreciate!
Thanks,
Satine

Hi Stuart,
My OLAP version is 11.1.0.7, upgrading from 11.1.0.6.
Here is the XML file for the dimension.
<!DOCTYPE Metadata [
<!ENTITY % BIND_VALUES PUBLIC "OLAP BIND VALUES" "OLAP METADATA">
%BIND_VALUES;
]>
<Metadata
Version="1.1">
<TimeDimension
Name="DAD"
ETViewName="DAD_VIEW"
ETKeyColumnName="DIM_KEY"
ETLevelColumnName="LEVEL_NAME"
ETDimensionOrderColumnName="DIM_ORDER"
ETHierarchyOrderColumnName="HIER_ORDER">
<Hierarchy>
<LevelHierarchy
IsSkipLevel="False"
IsRagged="False"
Name="SAD"
ETParentColumnName="PARENT"
ETDepthColumnName="DEPTH"
ETViewName="DAD_SAD_VIEW">
<HierarchyLevel
DimensionLevel="YEAR">
<HierarchyLevelMap
KeyExpression="TEST_TEST."YEAR""
Query="TEST_TEST">
<AttributeMap
Name="DAD_YEAR_ID"
Expression="TEST_TEST."YEAR"">
<Attribute
Name="DAD_YEAR_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="YEAR_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="YEAR_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="YEAR_TIME_SPAN"
Expression="200">
<Attribute
Name="YEAR_TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="QUARTER">
<HierarchyLevelMap
KeyExpression="TEST_TEST."QUARTER""
Query="TEST_TEST">
<AttributeMap
Name="DAD_QUARTER_ID"
Expression="TEST_TEST."QUARTER"">
<Attribute
Name="DAD_QUARTER_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="QUARTER_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="QUARTER_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="QUARTER_TIME_SPAN"
Expression="200">
<Attribute
Name="QUARTER_TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<HierarchyLevel
DimensionLevel="MONTH">
<HierarchyLevelMap
KeyExpression="TEST_TEST."MONTH""
Query="TEST_TEST">
<AttributeMap
Name="DAD_MONTH_ID"
Expression="TEST_TEST."MONTH"">
<Attribute
Name="DAD_MONTH_ID"/>
</AttributeMap>
<AttributeMap
Name="END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="END_DATE"/>
</AttributeMap>
<AttributeMap
Name="MONTH_END_DATE"
Expression="TO_DATE('2009-10-10', 'yyyy-mm-dd')">
<Attribute
Name="MONTH_END_DATE"/>
</AttributeMap>
<AttributeMap
Name="MONTH_TIME_SPAN"
Expression="200">
<Attribute
Name="MONTH_TIME_SPAN"/>
</AttributeMap>
<AttributeMap
Name="TIME_SPAN"
Expression="200">
<Attribute
Name="TIME_SPAN"/>
</AttributeMap>
</HierarchyLevelMap>
</HierarchyLevel>
<Description
Type="Description"
Language="ENGLISH"
Value="Sad">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Sad">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Sad">
</Description>
</LevelHierarchy>
</Hierarchy>
<DimensionLevel
Name="YEAR"
ETKeyColumnName="YEAR">
<Description
Type="Description"
Language="ENGLISH"
Value="Year">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year">
</Description>
<UniqueKeyAttribute
Name="DAD_YEAR_ID"/>
<VisibleAttribute
Name="YEAR_END_DATE"/>
<VisibleAttribute
Name="YEAR_TIME_SPAN"/>
<VisibleAttribute
Name="YEAR_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="YEAR_SHORT_DESCRIPTION"/>
</DimensionLevel>
<DimensionLevel
Name="QUARTER"
ETKeyColumnName="QUARTER">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter">
</Description>
<UniqueKeyAttribute
Name="DAD_QUARTER_ID"/>
<VisibleAttribute
Name="QUARTER_END_DATE"/>
<VisibleAttribute
Name="QUARTER_TIME_SPAN"/>
<VisibleAttribute
Name="QUARTER_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="QUARTER_SHORT_DESCRIPTION"/>
</DimensionLevel>
<DimensionLevel
Name="MONTH"
ETKeyColumnName="MONTH">
<Description
Type="Description"
Language="ENGLISH"
Value="Month">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month">
</Description>
<UniqueKeyAttribute
Name="DAD_MONTH_ID"/>
<VisibleAttribute
Name="MONTH_END_DATE"/>
<VisibleAttribute
Name="MONTH_TIME_SPAN"/>
<VisibleAttribute
Name="MONTH_LONG_DESCRIPTION"/>
<VisibleAttribute
Name="MONTH_SHORT_DESCRIPTION"/>
</DimensionLevel>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="END_DATE"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="END_DATE">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="TIME_SPAN">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="LONG_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="True"
Name="SHORT_DESCRIPTION">
<Classification
Value="STAR"/>
<Description
Type="Description"
Language="ENGLISH"
Value="Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="YEAR_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="YEAR_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Year End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="YEAR_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="YEAR_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="YEAR_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="YEAR_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="YEAR_SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="YEAR_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Year Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Year Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Year Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="QUARTER_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="QUARTER_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="QUARTER_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="QUARTER_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="QUARTER_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="QUARTER_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="QUARTER_SHORT_DESCRIPTIO"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="QUARTER_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Quarter Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="DATE"
ETAttributeColumnName="MONTH_END_DATE"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="END_DATE"
IsVisibleForAll="False"
Name="MONTH_END_DATE">
<Description
Type="Description"
Language="ENGLISH"
Value="Month End Date">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month End Date">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month End Date">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="NUMBER"
ETAttributeColumnName="MONTH_TIME_SPAN"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="TIME_SPAN"
IsVisibleForAll="False"
Name="MONTH_TIME_SPAN">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Time Span">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Time Span">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Time Span">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="MONTH_LONG_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="LONG_DESCRIPTION"
IsVisibleForAll="False"
Name="MONTH_LONG_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Long Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Long Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Long Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(60)"
ETAttributeColumnName="MONTH_SHORT_DESCRIPTION"
IsMultiLingual="False"
PopulateLineage="True"
AttributeGroupName="SHORT_DESCRIPTION"
IsVisibleForAll="False"
Name="MONTH_SHORT_DESCRIPTION">
<Description
Type="Description"
Language="ENGLISH"
Value="Month Short Description">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Month Short Description">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Month Short Description">
</Description>
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(8)"
ETAttributeColumnName="DAD_YEAR_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_YEAR_ID">
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(8)"
ETAttributeColumnName="DAD_QUARTER_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_QUARTER_ID">
</BaseAttribute>
</Attribute>
<Attribute>
<BaseAttribute
SQLDataType="VARCHAR2(6)"
ETAttributeColumnName="DAD_MONTH_ID"
IsMultiLingual="False"
PopulateLineage="False"
IsVisibleForAll="False"
Name="DAD_MONTH_ID">
</BaseAttribute>
</Attribute>
<Organization>
<AWPrimaryDimensionOrganization
MVOption="NONE"
HierarchyConsistencyRule="STAR_CONSISTENT"
AddUniqueKeyPrefix="True">
<MVCreationOptions
RefreshOn="DEMAND"
RefreshType="COMPLETE"
EnableRewriteMV="False"
UsingConstraintsClause="ENFORCED">
</MVCreationOptions>
<AttributeOrganization
CreateIndex="False"
Attribute="END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="YEAR_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="QUARTER_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_END_DATE">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_TIME_SPAN">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_LONG_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="MONTH_SHORT_DESCRIPTION">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_YEAR_ID">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_QUARTER_ID">
</AttributeOrganization>
<AttributeOrganization
CreateIndex="False"
Attribute="DAD_MONTH_ID">
</AttributeOrganization>
<AW
Name="&AW_NAME;"/>
<DefaultBuild>
<![CDATA[BUILD SPEC SYS_DEFAULT
LOAD,
COMPILE
)]]>
</DefaultBuild>
</AWPrimaryDimensionOrganization>
</Organization>
<Description
Type="Description"
Language="ENGLISH"
Value="Dad">
</Description>
<Description
Type="LongDescription"
Language="ENGLISH"
Value="Dad">
</Description>
<Description
Type="ShortDescription"
Language="ENGLISH"
Value="Dad">
</Description>
<TimeSpanAttribute
Name="TIME_SPAN"/>
<EndDateAttribute
Name="END_DATE"/>
<DefaultHierarchy
Name="SAD"/>
<ValueDescriptionAttribute
Name="LONG_DESCRIPTION"/>
<ShortValueDescriptionAttribute
Name="SHORT_DESCRIPTION"/>
</TimeDimension>
</Metadata>
You may want to have a test to change IsRagged="False" to IsRagged="True", then it woks well but the result is very stange.
And I find if the hierarchy is only with levels: YEAR and Quarter, then you can maintain it, but, for sure, the YEAR2009,QUARTER1 will overwrite YEAR2008,QUARTER1. If defining the hierarchy with levels:YEAR,QUARTER,MONTH, then you can't maintain it. On my opinion, it may because the data in third level MONTH can't identified the right routine to the higher level QUARTER.
Thanks,
Satine

40222 Disabled item failed validation.

When I run a Forms app, I receive this error message after I click one of its buttons:
41012 Invalid value for field Renewal_Type
40222 Disabled item RB.Renewal_Type failed validation.
There is a radio group by that name in one of the blocks, although it has not been assigned to a canvas. I think the developer of this app may have intended it for another form that he was going to build, but never got to it; thus it's disabled. Is that what causes this error message or is it something else? How can I fix this? Thanks.
Edited by: Prohan on Sep 10, 2010 9:42 AM

I found the answer here:
FRM - 40212 / FRM - 40222 error on a radio group during query
I can't say I understood the explanation for why it worked, but it did.

BEA-090513 -- ServerIdentity failed validation, downgrading to anonymous

Similar Messages

Maybe you are looking for