Jpa query fail! :(

Hello! I have a simple problem (I think and hope!), I have the next query with subquery:
select pfs from Person pfs where ...... and pfs NOT IN (select dae.socisPersons.person from DadesAnualsEntitat dae where ......)
DadesAnualsEntitat have a Set<PersonaFisicaSoci> named "socisPersons" and PersonaFisicaSoci has a Person named "person".
I don't know how to do because the correct would be 'NOT IN (select dae.socisPersones from DadesAnualsEntitat dae where...)' but they're incompatible objects. There are too much navigations, I know. Some idea? sorry for my poor english, thanks a lot!

Try comparing on the Id instead of the object,
i.e.
pfs.id not in (select dae.socisPersons.person.id from...
James : http://www.eclipselink.org

Similar Messages

Getting Rest Query failed error.

Hi,
I have integrated my app with facebook. I am able to post my reviews and comments on FB but when I click on link in FB post, its redirectign me to the required url but not loading the review.
Can any body tell me why this happens.
here are logs:
2013-05-22 18:29:17,281 [http-bio-8090-exec-10] ERROR com.fatwire.wsdk.rest.WidgetSDKResource - Failed to execute method feed in widget wsdk.reviews
com.fatwire.cos.ex.CoSServerException: com.fatwire.cos.ex.CoSServerException: REST query failed
     at com.fatwire.cos.core.jpa.query.CoSJpaQuery.getSingleResult(CoSJpaQuery.java:161)
     at com.fatwire.cos.records.RecordManager.countRecords(RecordManager.java:462)
     at com.fatwire.wsdk.cos.records.processors.feed.RecordListReadProcessor.calculatePageNo(RecordListReadProcessor.java:229)
     at com.fatwire.wsdk.cos.records.processors.feed.RecordListReadProcessor.getPageNo(RecordListReadProcessor.java:186)
     at com.fatwire.wsdk.cos.records.processors.feed.RecordListReadProcessor.process(RecordListReadProcessor.java:62)
     at com.fatwire.cos.core.monitor.MonitoredMethodInterceptor.invoke(MonitoredMethodInterceptor.java:68)
     at com.fatwire.wsdk.pipeline.impl.PipelineImpl.execute(PipelineImpl.java:60)
     at com.fatwire.cos.core.monitor.MonitoredMethodInterceptor.invoke(MonitoredMethodInterceptor.java:68)
     at com.fatwire.wsdk.rest.WidgetSDKResource.executeWidgetMethod(WidgetSDKResource.java:183)
     at sun.reflect.GeneratedMethodAccessor255.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
     at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
     at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
     at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
     at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
     at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
     at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
     at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
     at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
     at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
     at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
     at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
     at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
     at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
     at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
     at com.google.inject.servlet.ServletDefinition.doService(ServletDefinition.java:263)
     at com.google.inject.servlet.ServletDefinition.service(ServletDefinition.java:178)
     at com.google.inject.servlet.ManagedServletPipeline.service(ManagedServletPipeline.java:91)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:62)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:168)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.fatwire.cos.comments.service.filters.RestFilter.doFilter(RestFilter.java:141)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.fatwire.cos.core.i18n.ResourceFilter.doFilter(ResourceFilter.java:45)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.fatwire.cos.core.sso.SSOContextFilter.doFilter(SSOContextFilter.java:64)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter(CASFilter.java:219)
     at com.fatwire.wem.sso.SSOFilter.doFilter(SSOFilter.java:51)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.fatwire.cos.core.sso.GeneralPreparationsFilter.doFilter(GeneralPreparationsFilter.java:68)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.fatwire.cos.core.util.web.StartupGuardFilter.doFilter(StartupGuardFilter.java:42)
     at com.google.inject.servlet.FilterDefinition.doFilter(FilterDefinition.java:163)
     at com.google.inject.servlet.FilterChainInvocation.doFilter(FilterChainInvocation.java:58)
     at com.google.inject.servlet.ManagedFilterPipeline.dispatch(ManagedFilterPipeline.java:118)
     at com.google.inject.servlet.GuiceFilter.doFilter(GuiceFilter.java:113)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
     at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
     at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
     at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused by: com.fatwire.cos.ex.CoSServerException: REST query failed
     at com.fatwire.cos.core.jpa.cmd.wem.WemCommandManager.execREST(WemCommandManager.java:356)
     at com.fatwire.cos.core.jpa.cmd.wem.WemCommandManager.execGET(WemCommandManager.java:192)
     at com.fatwire.cos.core.jpa.cmd.wem.WemCountQueryCommand.findResult(WemCountQueryCommand.java:79)
     at com.fatwire.cos.core.jpa.cmd.wem.WemCountQueryCommand.executeSingle(WemCountQueryCommand.java:68)
     at com.fatwire.cos.core.monitor.MonitoredMethodInterceptor.invoke(MonitoredMethodInterceptor.java:68)
     at com.fatwire.cos.core.jpa.query.CoSJpaQuery.getSingleResult(CoSJpaQuery.java:156)
     ... 104 more
Thanks in advance.
Thanks,
Nelash jindal

Hi There,
Please try the below steps and check if it helps :
Go to C:/programfiles/Adobe/Adobe Captivate(version)/AdobeCaptivate.ini
Open the file with notepad and add the line Use32BitJVMForPublish=1
Save it and Try to publish the project .
Regards,
Mayank

The following query failed: GetUserProfileByName - with the wrong username

I have 2 users (out of 800), who run into this issue on occasion. Their username is 'fccs\user1' in the profile db, and in every UserInfo table in the system. But when they try to go to certain sites or open an infopath form, this error gets thrown:
The following query failed: GetUserProfileByName (User: FCCS\[email protected], Form Name: Template, IP: , Connection Target: , Request: http://fccsteams/sites/DataManagement/Tasks/Lists/Tasks/Folders1.aspx?RootFolder=/sites/DataManagement/Tasks/Lists/Tasks/2013/11&, Form ID: urn:schemas-microsoft-com:office:infopath:list:-AutoGen-2013-08-05T23:14:53:458Z Type: DataAdapterException, Exception Message: The remote server returned an error: (500) Internal Server Error. Operation Failure ---> Access Denied: To create a user profile, you must be an administrator, or create your own profile and have personal features rights. UnauthorizedAccessAccess Denied: To create a user profile, you must be an administrator, or create your own profile and have personal features rights. The remote server returned an error: (500) Internal Server Error.)
Notice how the username is now the entire email address and not just the username. I have no idea why it thinks that that is their username. Any ideas?

Hi,
According to your post, my understanding is that you got query failed error.
Melick had written a blog said that the form access the user profile web service (Userprofileservice.asmx) using UDC
file.
You can check whether the UDC connection was still pointing to root site.
You can change this file to match with the sub site collection. Otherwise there may be a cross domain access issue.
There are similar threads for your reference.
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/9c2f7f4c-0fa9-43bd-94b1-1d7075e35841/5566-error-with-getuserprofilebyname-and-infopah-browser-forms-using-claims-based-authentication
http://social.msdn.microsoft.com/Forums/en-US/49753330-40c0-4327-9a9b-2c3304a74e67/sharepoint-infopath-and-populating-forms-with-ad-data?forum=sharepointcustomizationlegacy
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

General JPA query question

Hello world,
I'm new to JPA 2.0 and there are few things I don't understand.
BTW: I can't figure out the keywords to search for this question, so please pardon me if it's one of the most asked.
Using the Preview, I've seen that alignment went straight to Hell, so I tried to make this as readable as I could using pipes in place of white spaces in the result sets.
I have a couple of tables:
CUST table (for customers):
CUST_ID (pk, integer)
CUST_NAME (varchar)
ORD table (for orders):
ORD_ID (pk, integer)
ORD_STATUS (char) can be: N for new, S for shipped, D for delivered
CUST_ID (fk, integer)
The relationship is, of course, a "one to many" (every customer can place many orders).
Content of the tables:
CUST_ID|CUST_NAME
1|elcaro
2|tfosorcim
3|elppa
ORD_ID|ORD_STATUS|CUST_ID
2|N|1
3|N|1
4|N|1
5|S|1
6|S|1
7|D|1
8|D|1
9|D|1
10|D|2
11|N|2
12|S|3
13|S|3
Here's how I annotated my classes:
Customer.java:
@Entity(name = "Customer")
@Table(name = "CUST")
public class Customer implements Serializable
private static final long serialVersionUID = 1L;
@Id
@Column(name = "CUST_ID")
private Integer id;
@Column(name = "CUST_NAME")
private String name;
@OneToMany(mappedBy = "customer")
private List<Order> orders;
// Default constructor, getters and setters (no annotations on these)
Order.java:
@Entity(name = "Order")
@Table(name = "ORD")
public class Order implements Serializable
private static final long serialVersionUID = 1L;
@Id
@Column(name = "ORD_ID")
private Integer id;
@Column(name = "ORD_STATUS")
private Character status;
@ManyToOne
@JoinColumns
@JoinColumn(name = "CUST_ID", referencedColumnName = "CUST_ID")
private Customer customer;
// Default constructor, getters and setters (no annotations on these)
Everything works just fine, the following JPQL query yields the results I expected:
select c from Customer c
it returns three objects of type Customer, each of which contains the orders that belong to that customer.
But now, I want to extract the list of customers that have orders in status 'N', along with the associated orders (only the status 'N' orders, of course).
Back in the good ol' days I would have written an SQL query like this:
select c.cust_id, c.cust_name, o.ord_id, o.ord_status
from cust c
inner join ord o on (o.cust_id = c.cust_id)
where o.ord_status = 'N'
and it would have returned the following result set:
CUST_ID|CUST_NAME|ORD_ID|ORD_STATUS
1|elcaro|2|N
1|elcaro|3|N
1|elcaro|4|N
2|tfosorcim|11|N
The following JPQL query, however, doesn't yield the expected results:
select distinct c from Customer c join c.orders o where o.status = 'N'
it returns the correct set of customers (customer 'elppa' doesn't have any status 'N' order and is correctly excluded), but each customer contains the full set of orders, regardless of the status.
It seems that the 'where' clause is only evaluated to determine which set of customers has to be extracted and then the persistence provider starts to navigate the relationship to extract the full set of orders.
Thinking a little about it, I must admit that it makes sense.
I then tried out another JPQL query:
select c, o from Customer c join c.orders o where o.status = 'N'
this JPA query yields results that are similar to the ones produced by the previous SQL query: each result (4 results as expected) is a 2-object array, the first object is of type Customer and the second object is of type Order. But, again, the objects of type Customer contain the full set of related orders (as I expected, this time). Not to mention the fact that now the orders are not contained in the Customer objects, but are returned separately, just as in an SQL result set.
Now the question is:
Is it possible to write a JPA query that filters out, not only the customers that don't have an order in status 'N', but the related orders (fetched during relationship navigation) that are not in status 'N' as well?
What I'd like to be able to get is a 2-customer result where each customer contains only its status 'N' orders.
I read the Java EE 6 Tutorial and one of the examples (the Order Application) has a schema that is similar to mine, but I couldn't find a query like this (in the downloaded source code).
Although I think the above is standard behavior, I use an Oracle Weblogic 12c server (through its Eclipse adapter) and the persistence provider appears to be EclipseLink.
Thanks in advance.
Best regards,
Stefano
Edited by: user11265230 on 17-apr-2012 14.11

Hello,
When returning an entity from JPQL, it gives you the entity as it is in the database. Your "select distinct c from Customer c join c.orders o where o.status = 'N'" is asking for all customers that have an order with a status of 'N', so that is what it gives you. There is no condition to filter anything on the relationship when building the Customer object in JPA - doing so would mean returning a managed entity that does not reflect what is in the database. This would affect other queries, since JPA requires that queries return the same instance of an entity regardless of the query that is used to bring it back. So a query using your "where o.status = 'N'" would cause conflicting results when used with a query using "where o.status = 'Y'". And these queries would make the EntityManager unable to determine what has changed on the returned objects.
EclipseLink does have the ability to filter over relationships, it is just not available through standard JPA and I would strongly discourage it. Instead of querying for Customers, why not change the query to get Orders instead -
"select o from Customer c join c.orders o where o.status = 'N'". Assuming Orders have a ManyToOne back reference to their Customer, this will mean you do not need to travers the Customer-> order relationship. If using
"select c, o from Customer c join c.orders o where o.status = 'N'"
I am not sure why you would use the orders from the returned customers instead of the orders returned in the results though.
You could also return "select c.id, c.name, o.id, o.status from Customer c join c.orders o where o.status = 'N'" which is the equivalent of what you would get from the SQL you initially posted.
Regards,
Chris

WSA - Report Query Failed

Hi all,
Recently, I'm receiving these two alerts from one WSA S370:
Report Query Failed
 query_id: wsa_monitor_overview_web_proxy_summary
 data_source: WSASimpleTotalRDS
 error: <type 'type'> ('egg/command_client.py send_message|555', "<class 'Commandment.DaemonUnresponsiveError'>", 'S370B.NAME.net: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
AND
Report Query Failed
 query_id: wsa_monitor_overview_clients_by_blocked_transactions
 data_source: WSACommonRDS
 error: <type 'type'> ('egg/command_client.py call|238', "<class 'reporting.query.exceptions.DatabaseQueryFailure'>", '', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|251] [reportdatasource/CounterReportDataSource.py _run_api_query|482] [query/client.py time_merge_query|454] [query/client.py _call|235] [egg/command_client.py call|238]')
The code I'm using is 7.1.1-038
I started receiving the alerts only after upgrading to this code. Have you noticed something similar?
Thanks a lot for your help!!!
Fernando

Hello Everyone,
I am in Australia (Melbourne) and i am using ironport s160 web security appliance version: 7.1.2-80. Reecently i have started receiving the following warning from ironport proxy.
The Warning message is:
Report Query Failed
 query_id: wsa_monitor_overview_malware_categories
 data_source: WSACommonRDS
 error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
Report Query Failed
 query_id: wsa_monitor_overview_suspect_transactions_detected
 data_source: CounterReportDataSource
 error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|272] [reportdatasource/CounterReportDataSource.py _parse_api_results|506] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|525] [query/result.py next|112] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
Report Query Failed
 query_id: wsa_monitor_overview_suspect_transactions_summary
 data_source: WSASimpleTotalRDS
 error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
Report Query Failed
 query_id: wsa_monitor_overview_top_application_types
 data_source: CounterReportDataSource
 error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
Report Query Failed
 query_id: wsa_monitor_overview_top_url_categories
 data_source: CounterReportDataSource
 error: ('egg/command_client.py send_message|555', "", 'proxymel3.sportsbet.com.au: The daemon is not responding.', '[database/ReportCatalog.py run_report_queries|332] [reportdatasource/CounterReportDataSource.py query|265] [reportdatasource/CounterReportDataSource.py _parse_overall_interval|581] [query/merged_result.py range|85] [query/client.py _call|235] [egg/command_client.py call|233] [egg/command_client.py send_message|555]')
Product: IronPort S160 Web Security Appliance
Model: S160
Version: 7.1.2-080
Serial Number: 0025643CFD42-4GQYHL1
Timestamp: 14 Jun 2012 14:00:21 +1000
Thank you for your help.
Lovedeep

451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain

Hi,
I have two Exchange 2010 servers running on Windows 2008 Ent R2.
These mail servers have been running fine for a few years.
Today I noticed two things.
1. users were telling me they were having delays receiving emails from outside of our own domain. The mail gets sent out, but it takes about 15-30 mins for users outside our our domain to get their mail. Mail sent from inside our domain gets delivered right
away.
2. An error message that I see when I go to Tools->Queue Viewer in EMC. The error is: 451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain. This error shows up when you click on the "Queues" tab and then look at the
"hub version 14" under "next hop domain" column.
I'm assuming these two things are related. I don't understand why the problem is just showing up now. As I said, mail delivery has been fine for a while and I haven't done any major updates to the server in a few months.
Thanks for any ideas and suggestions as to what might be causing it and where I can look.
Mike

Hi,
1. I replaced my Cert with the same exact cert from GoDaddy, just an updated expire date.
2. We have two exchange servers.
3. The message I am seeing now, is under "Last Error" for every queue (not individual messages).
That error message is: 451 4.4.0 Primary Target IP address responded with 421 4.2.1 Unable to connect. Attempted failover to alternate host but that did not succeed.
OR
451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain. (This is the same error I mentioned earlier.
I ran some tests on mxmailbox.com for my domain name.I got the following alerts back when running a DNS check.
SOA Serial Number format is invalid. ns.rackspace.com Serial XXXXXXXX : Suggested serial format year was 1402 which is before 1970
AND
SOA Expire value out of recommended range. ns.rackspace reported Expire 604800. Expire is recommeded to be between 1209600 and 2419200
I use Rackspace DNS servers for External lookups.
Does this point my mail delay problem to Rackspace or something local on my own machine?
Thanks!
Mike

ERROR: Cannot create authcontext with null org-Naming query failed code:21

I use OpenSSO Enterprise 8.0 Update 1 Patch1 Build 6.1(2009-June-9 12:56)
I try to evaluate the Apache 2.2 web agent.
It's been installed without errors, and both the OpenSSO and Apache server restarted.
The agent profile's been created. Also, I use the default (OpenDS) configuration repository
for OpenSSO, but an external (DSEE) user data directory.
I think I did all the required steps with regards to both directories, since I don't see any error
in the LDAP logs, each entry seems to be found as expected, the BIND operations are all
successfull.
Also, I use a sub-realm rather than the default top realm, and thus, I've modified the agent configuration
(in the agent profile) so that the login URL is now ... /UI/Login?realm=myrealm
When I try to access the Apache homepage, I get an error 500. The most recent OpenSSO server log file
(...../opensso/debug/Authentication) contains the following message:
ERROR: Cannot create authcontext with null org
The most recent agent log file (....../apache22_agent/Agent_001/logs/debug/amAgent) has the following error:
2009-07-07 17:08:11.992 Error 10513:80149a50 PolicyEngine: am_policy_evaluate: InternalException in Service::update_policy with error message:Naming query failed. and code:21
I don't know what else I can do to debug this problem and find a solution. Any idea ?

Thank you Shubba,
With all available log details enabled, I now have the following messages on the agent side:
2009-07-09 10:14:51.731MaxDebug 5613:80149a50 all: No value specified for key com.sun.identity.agents.config.profile.attribute.mapping, using default value .
2009-07-09 10:14:51.731 Debug 5613:80149a50 NamingService: BaseService::doRequest(): Using server: http://portable.antibes.net:8080/opensso/namingservice.
2009-07-09 10:14:51.731MaxDebug 5613:80149a50 NamingService:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RequestSet vers="1.0" svcid="com.iplanet.am.naming" reqid="10">
<Request><![CDATA[
<NamingRequest vers="3.0" reqid="2" sessid=""AQIC5wM2LY4SfcyaGFgc5h9Y7/kpf4f//ml82oVfNlbWxQE=@AAJTSQACMDE=#""> <GetNamingProfile> </GetNamingProfile> </NamingRequest>]]> </Request>
</RequestSet>
2009-07-09 10:14:51.712MaxDebug 5613:80149a50 NamingService: BaseService::sendRequest Request line: POST /opensso/namingservice HTTP/1.0
2009-07-09 10:14:51.712 Debug 5613:80149a50 NamingService: BaseService::sendRequest Cookie and Headers =Host: portable.antibes.net
2009-07-09 10:14:51.712 Debug 5613:80149a50 NamingService: BaseService::sendRequest Content-Length =Content-Length: 334
2009-07-09 10:14:51.712 Debug 5613:80149a50 NamingService: BaseService::sendRequest Header Suffix =Accept: text/xml
Content-Type: text/xml; charset=UTF-8
2009-07-09 10:14:51.712MaxDebug 5613:80149a50 NamingService: BaseService::sendRequest(): Total chunks: 7.
2009-07-09 10:14:51.712MaxDebug 5613:80149a50 NamingService: BaseService::sendRequest(): Sent 7 chunks.
2009-07-09 10:14:51.728 Debug 5613:80149a50 NamingService: HTTP Status = 500 (Internal Server Error)
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Http::Response::readAndParse(): Reading headers.
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Server: Apache-Coyote/1.1
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Content-Type: text/html;charset=utf-8
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Date: Thu, 09 Jul 2009 08:14:51 GMT
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Connection: close
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Http::Response::readAndParse(): Reading body content of length: 13830487939496281954
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 all: Connection::waitForReply(): returns with status success.
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: Http::Response::readAndParse(): Completed processing the response with status: success
2009-07-09 10:14:51.729MaxDebug 5613:80149a50 NamingService: <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style></style> </head><body><h1>HTTP Status 500 - </h1><HR size="1" noshade="noshade">type Exception reportmessage description The server encountered an internal error () that prevented it from fulfilling this request.exception <pre>javax.servlet.ServletException: AMSetupFilter.doFilter
com.sun.identity.setup.AMSetupFilter.doFilter(AMSetupFilter.java:117)
</pre>root cause <pre>java.lang.NullPointerException
com.iplanet.services.naming.service.NamingService.processRequest(NamingService.java:361)
com.iplanet.services.naming.service.NamingService.process(NamingService.java:352)
com.iplanet.services.comm.server.PLLRequestServlet.handleRequest(PLLRequestServlet.java:180)
com.iplanet.services.comm.server.PLLRequestServlet.doPost(PLLRequestServlet.java:134)
javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
com.sun.identity.setup.AMSetupFilter.doFilter(AMSetupFilter.java:91)
</pre>note The full stack trace of the root cause is available in the Apache Tomcat/6.0.18 logs.<HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html>
2009-07-09 10:14:51.729 Warning 5613:80149a50 NamingService: BaseService::doHttpPost() failed, HTTP error = 500
2009-07-09 10:14:51.729 Debug 5613:80149a50 NamingService: NamingService()::getProfile() returning with error code HTTP error.
2009-07-09 10:14:51.729 Error 5613:80149a50 PolicyEngine: am_policy_evaluate: InternalException in Service::update_policy with error message:Naming query failed. and code:21
In my Tomcat server (OpenSSO server web container), I have the following errors:
Jul 9, 2009 10:12:35 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 22746 ms
[Fatal Error] :2:46: Element type "NamingRequest" must be followed by either attribute specifications, ">" or "/>".
java.lang.NullPointerException
at com.iplanet.services.naming.service.NamingService.processRequest(NamingService.java:361)
at com.iplanet.services.naming.service.NamingService.process(NamingService.java:352)
at com.iplanet.services.comm.server.PLLRequestServlet.handleRequest(PLLRequestServlet.java:180)
at ...
It seems like the problem comes from the couple of closing square brackets in the NamingRequest tag:
</NamingRequest>]]>
I don't know where it comes from, so if you've an idea I'd enjoy .
Cheers,

Database Query Failed

I got this error message instead of weekly report.
Anybody ever experienced this? How to fix it?
The Warning message is:
Report Query Failed
query_id: mga_overview_incoming_mail_over_time
data_source: CounterReportDataSource
error: <type 'type'> ('command_manager/command_client.py call|242', "<class 'reporting.query.exceptions.DatabaseQueryFailure'>", '', '[database/ReportCatalog.py run_report_queries|234] [reportdatasource/CounterReportDataSource.py query|131] [reportdatasource/CounterReportDataSource.py _parse_api_results|216] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|251] [reportdatasource/CounterReportDataSource.py _parse_interval_result|317] [reportdatasource/CounterReportDataSource.py _parse_standard_interval_result|326] [query/result.py next|239] [query/client.py _call|212] [command_manager/command_client.py call|242]')
Version: 5.5.1-011

Yes, I did. Instead of a graph, I got this error message:
Error while receiving data.
There may have been an intermittent timeout during the database query.
Have you tried going onto the GUI interface and going to "Monitor > Incoming Mail", switching the Time range to display a Week and then clicking on the Printable button on the right hand corner.
I got this error message instead of weekly report.
Anybody ever experienced this? How to fix it?
The Warning message is:
Report Query Failed
query_id: mga_overview_incoming_mail_over_time
data_source: CounterReportDataSource
error: ('command_manager/command_client.py call|242', "", '', '[database/ReportCatalog.py run_report_queries|234] [reportdatasource/CounterReportDataSource.py query|131] [reportdatasource/CounterReportDataSource.py _parse_api_results|216] [reportdatasource/CounterReportDataSource.py _parse_interval_result_set|251] [reportdatasource/CounterReportDataSource.py _parse_interval_result|317] [reportdatasource/CounterReportDataSource.py _parse_standard_interval_result|326] [query/result.py next|239] [query/client.py _call|212] [command_manager/command_client.py call|242]')
Version: 5.5.1-011

How to configure lazy/eager loading for each JPA query

Hi!
I have extensive EJB model (entities with many child entities, entities with association to other large (many fields, BLOBs including) entities, and so on) and I would like for each JPA query configure what properties or associated entities (actually - in arbitrary depth) of selected entities should be fetched.
E.g. for one query I would like to fetch only Order (and no data of associated entities), but for other queries I would like to fetch Order, Order.Customer, Order.ShippingAddress.ZipCode and nothing else ( e.g. if there is Ordere.Route, Order.Billing and other associations, then I would like not to waste resources for fetching them). In both case the select clause of query can include only Order, but the results should be different - i.e. - there is no associated data in the first case and there are some associated data the second case.
I know that one solution is to declare all associations as lazy and then - after reading the result of query - do some touching for retrieving the associated data:
String check = order.Customer.toString();
check = order.ShippingAddess.ZipCode.toString();
But I see 2 problems with this: 1) it is not nice (resources are wasted for simply touching associated entities); 2) I assume that each "touch" operation generates other query to database that could be executed together with the original query. So - it would be nice to configure JPA query somehow to let it know which associations will be required from the result and which not.
What is the best practice?
I found, that JBoss server has lazy-loading-group configuration, but - I guess - it is JBoss specific:
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.2/html/Server_Configuration_Guide/Loading_Process-Lazy_loading_Process.html
besides - it is XML and it would be more pretty if query configuration could be done with annotations!

JPQL has a "fetch" construct in which you can force a lazy element to be fetched using a query - I must note that I have had unexpected results with it in the past but that was using an old version of Hibernate and I wasn't very experienced with JPA yet.
http://docs.oracle.com/cd/E15051_01/wls/docs103/kodo/full/html/ejb3_langref.html#ejb3_langref_fetch_joins

Query Failed: [nQSError: 46036] Internal Assertion ( OBIEE error)

Hi Friends.
Did anyone faced this problem. I am using custom filters on reports. The reports work well for 5 filters but start giving error on last filter. As far as I can guess its an internal OBIEE optimizer error. Can anyone faced this problem and help
A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46036] Internal Assertion: Condition pCond, file server\Query\Optimizer\Request\Src\SQORRqList.cpp, line 2604.Please have your System Administrator look at the log for more details on this error. (HY000)

We faced same problem. There is no clear definition of error even we increase log trace level to 7.
Query Status: [nQSError: 46036] Internal Assertion: Condition pCond, file server\Query\Optimizer\Request\Src\SQORRqList.cpp, line 2716. [[
We will open a ticket to Oracle Support.

Data Synchronize from HFM FMDmeException Query Failed or invalid

I'm trying to create a Data Synchronization where HFM is the data source source.
I keep getting the following dme exception and don't know how to further diagnose the issue.
4/19/12 1:29 PM : Error submitting request to source connector - exception: com.hyperion.datasync.fmdme.exception.FMDmeException: Acknowledgement failure - status: 1, reason: Query Failure: The query failed or is invalid! (0)
4/19/12 1:29 PM : Translation failed - Source query failed to open - exception:; nested exception is:
com.hyperion.datasync.fmdme.exception.FMDmeException: Acknowledgement failure - status: 1, reason: Query Failure: The query failed or is invalid! (0)
The DME Listener service is running.
I've tried the simplest data sync -- just one member in each dimension, copying to same application (in a different scenario).
I have data synchronizations that do work where the source is a Planning application.
I was able -- a month ago -- to create a sync where HFM is the source on this development application so don't know if something has changed in the application itself.
Any suggestions appreciated.
Thanks,
Barb
Edited by: bg on Apr 19, 2012 1:31 PM

You're right. I should have put it in Financial Consolidation. I don't see that I can post a question directly to EPMA level.

451 4.4.0 DNS query failed - NonExistentDomain

I am in the process of migrating from Exch 2007 to 2013 for a small company. It is a very simple setup of just a single domain which has
1 server, 1 organization and 1 database. Here is what I have done so far:
1. Installed a physical server EX13 for Exchange 2013 with SP1. All updates have been applied.
2. Added a new Receive Connector of EX13 in addition to existing EX07.
3. Changed SMTP port forwarding on the firewall from EX07 to EX13.
4. Migrated a few mailboxes to the EX13.
Accounts on both servers have no issues with exchanging email both ways on the Internet. However, when accounts on the old server email to
migrated users, the new server does not always receive the messages promptly. There is a delay as much as 30 minutes that happens sporadically.
I checked the message header on the delayed messages and found that they had been stuck in EX07 for a long time before forwarding to EX13.
From Ex07 queue viewer, I found the following error:
451 4.4.0 DNS query failed. The error was: SMTPSEND.DNS.NonExistentDomain; nonexistent domain
Net Hop Domain: hub version 15
Delivery type: SMTP Relay in Active Directory
Message Source Name: FromLocal
Last Error: 451 4.4.0 DNS query failed. The error was: SMTPSEND.dns.NonExistentDomain;nonexistentdomain
The status showed "retry" and eventually the message would be delivered. Once it went through, I sent another one again from an EX07
account to EX13 account, the message was received instantly.
So far I have tried the following:
1. Added a host entry to point EX13.my_external_domain.com to the internal address of EX13
2. Added an 'A' record on the internal DNS server with the same entry.
3. Verified that EX13.my_external_domain.com was accessible from EX07 using this FQDN.
4. Removed EX07 and leaving only EX13 on the Receive Connector list
5. Removed EX13 and leaving only EX07 on the Receive Connector list
6. Put both connectors back
There is no change of status. Every morning our users are saying that they could not email users on the new server. Then after 30 minutes,
the problem disappeared but it will come back later in the day. On the other hand, users on the new server do not notice any delay when sending messages to the those on the new box. At this point, I don't feel comfortable migrating more users. Can someone
please shed some lights?

As suggested by Cara, I queried the message logs of both servers to track the delayed message. This time, it took an hour for a message to be delivered.
========================================
Message Log on Sending Server EXCH07
========================================
[PS] C:\Windows\system32>get-messagetrackinglog -messagesubject "exch07-user1 to
exch13-user1" | fl
Timestamp : 3/28/14 2:18:00 PM
ClientIp : fe80::a5d8:d604:af26:37a9
ClientHostname : EXCH07.contoso.local
ServerIp : fe80::a5d8:d604:af26:37a9%10
ServerHostname : EXCH07
SourceContext :
ConnectorId :
Source : STOREDRIVER
EventId : RECEIVE
InternalMessageId : 4106
MessageId : <CC47D79927E02645940E84883BD0D909F58F56E607@TO-EXCHAN
GE.contoso.local>
Recipients : {[email protected]}
RecipientStatus : {}
TotalBytes : 3897
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 04I:
Timestamp : 3/28/14 3:12:02 PM
ClientIp : 2002:960a:116::960a:116
ClientHostname : EXCH07
ServerIp : 2002:960a:125::960a:125
ServerHostname : EXCH13.contoso.local
SourceContext : 08D1189FA5E0283C
ConnectorId : Intra-Organization SMTP Send Connector
Source : SMTP
EventId : SEND
InternalMessageId : 4106
MessageId : <CC47D79927E02645940E84883BD0D909F58F56E607@TO-EXCHAN
GE.contoso.local>
Recipients : {[email protected]}
RecipientStatus : {250 2.1.5 Recipient OK}
TotalBytes : 4337
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 3/28/14 2:18:00 PM
Timestamp : 3/28/14 3:40:22 PM
ClientIp : fe80::a5d8:d604:af26:37a9
ClientHostname : EXCH07.contoso.local
ServerIp : fe80::a5d8:d604:af26:37a9%10
ServerHostname : EXCH07
SourceContext :
ConnectorId :
Source : STOREDRIVER
EventId : RECEIVE
InternalMessageId : 4685
MessageId : <CC47D79927E02645940E84883BD0D909F58F56E608@TO-EXCHAN
GE.contoso.local>
Recipients : {[email protected]}
RecipientStatus : {}
TotalBytes : 3905
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1-1
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 04I:
Timestamp : 3/28/14 4:34:27 PM
ClientIp : 2002:960a:116::960a:116
ClientHostname : EXCH07
ServerIp : 2002:960a:125::960a:125
ServerHostname : EXCH13.contoso.local
SourceContext : 08D1189FA5E0295D
ConnectorId : Intra-Organization SMTP Send Connector
Source : SMTP
EventId : SEND
InternalMessageId : 4685
MessageId : <CC47D79927E02645940E84883BD0D909F58F56E608@TO-EXCHAN
GE.contoso.local>
Recipients : {[email protected]}
RecipientStatus : {250 2.1.5 Recipient OK}
TotalBytes : 4345
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1-1
Sender : [email protected]
ReturnPath : [email protected]
MessageInfo : 3/28/14 3:40:22 PM
Timestamp : 3/28/14 2:18:00 PM
ClientIp : fe80::a5d8:d604:af26:37a9%10
ClientHostname : EXCH07
ServerIp :
ServerHostname : EXCH07
SourceContext : MDB:caef6319-6c43-4f5e-8b42-34b112a9f6a4, Mailbox:589
783a4-b411-45d8-b359-23095d3cd24d, Event:114759020, M
essageClass:IPM.Note, CreationTime:2014-03-28T18:17:5
9.653Z, ClientType:OWA
ConnectorId :
Source : STOREDRIVER
EventId : SUBMIT
InternalMessageId :
MessageId : <CC47D79927E02645940E84883BD0D909F58F56E607@TO-EXCHAN
GE.contoso.local>
Recipients : {}
RecipientStatus : {}
TotalBytes :
RecipientCount :
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath :
MessageInfo :
Timestamp : 3/28/14 3:40:22 PM
ClientIp : fe80::a5d8:d604:af26:37a9%10
ClientHostname : EXCH07
ServerIp :
ServerHostname : EXCH07
SourceContext : MDB:caef6319-6c43-4f5e-8b42-34b112a9f6a4, Mailbox:589
783a4-b411-45d8-b359-23095d3cd24d, Event:114778671, M
essageClass:IPM.Note, CreationTime:2014-03-28T19:40:2
1.777Z, ClientType:OWA
ConnectorId :
Source : STOREDRIVER
EventId : SUBMIT
InternalMessageId :
MessageId : <CC47D79927E02645940E84883BD0D909F58F56E608@TO-EXCHAN
GE.contoso.local>
Recipients : {}
RecipientStatus : {}
TotalBytes :
RecipientCount :
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1-1
Sender : [email protected]
ReturnPath :
MessageInfo :
========================================
Message Log on Sending Server EXCH07
========================================
[PS] C:\Users\administrator.contoso\Desktop>get-messagetrackinglog -messagesubject "exch07-user1 to exch13-user1" | fl
RunspaceId : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp : 3/28/2014 3:12:01 PM
ClientIp :
ClientHostname :
ServerIp :
ServerHostname : EXCH13
SourceContext : No suitable shadow servers
ConnectorId :
Source : SMTP
EventId : HAREDIRECTFAIL
InternalMessageId : 1236950581391
MessageId : <[email protected]>
Recipients : {[email protected]}
RecipientStatus : {}
TotalBytes : 5337
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
Directionality : Originating
TenantId :
OriginalClientIp :
MessageInfo :
MessageLatency :
MessageLatencyType : None
EventData : {[DeliveryPriority, Normal]}
RunspaceId : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp : 3/28/2014 3:12:02 PM
ClientIp : 2002:960a:125::960a:125
ClientHostname : EXCH13.contoso.local
ServerIp : 2002:960a:125::960a:125
ServerHostname : EXCH13
SourceContext : 08D1189F8F482FF4;2014-03-28T19:09:18.823Z;0
ConnectorId : EXCH13\Default EXCH13
Source : SMTP
EventId : RECEIVE
InternalMessageId : 1236950581391
MessageId : <[email protected]>
Recipients : {[email protected]}
RecipientStatus : {}
TotalBytes : 5337
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
Directionality : Originating
TenantId :
OriginalClientIp : 2002:960a:116::960a:116
MessageInfo : 0cI:
MessageLatency :
MessageLatencyType : None
EventData : {[FirstForestHop, EXCH13.contoso.local], [ProxiedClientIPAddress, 65.114.181.16],
[ProxiedClientHostname, qw01016.businesswatchnetwork.com], [ProxyHop1,
EXCH13.contoso.local(2002:960a:125::960a:125)], [DeliveryPriority, Normal]}
RunspaceId : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp : 3/28/2014 3:12:02 PM
ClientIp :
ClientHostname : EXCH13
ServerIp :
ServerHostname :
SourceContext :
ConnectorId :
Source : AGENT
EventId : AGENTINFO
InternalMessageId : 1236950581391
MessageId : <[email protected]>
Recipients : {[email protected]}
RecipientStatus : {}
TotalBytes : 5337
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
Directionality : Originating
TenantId :
OriginalClientIp : 2002:960a:116::960a:116
MessageInfo :
MessageLatency :
MessageLatencyType : None
EventData : {[CompCost, |ETR=0], [DeliveryPriority, Normal]}
RunspaceId : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp : 3/28/2014 3:12:38 PM
ClientIp : 2002:960a:125::960a:125
ClientHostname : EXCH13
ServerIp : 2002:960a:125::960a:125
ServerHostname : EXCH13.contoso.local
SourceContext : 08D1189F8F482FFC;250 2.0.0 OK;ClientSubmitTime:2014-03-28T18:17:59.590Z
ConnectorId : Intra-Organization SMTP Send Connector
Source : SMTP
EventId : SEND
InternalMessageId : 1236950581391
MessageId : <[email protected]>
Recipients : {[email protected]}
RecipientStatus : {250 2.1.5 Recipient OK}
TotalBytes : 6130
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
Directionality : Originating
TenantId :
OriginalClientIp :
MessageInfo : 2014-03-28T18:18:00.077Z;LSRV=EXCH13.contoso.local:TOTAL=36|QDM=35
MessageLatency : 00:54:38.1220000
MessageLatencyType : LocalServer
EventData : {[E2ELatency, 3278], [Microsoft.Exchange.Transport.MailRecipient.RequiredTlsAuthLevel,
Opportunistic], [DeliveryPriority, Normal]}
RunspaceId : 4ec43dbc-f727-4ac4-850e-ecac5e5e23ab
Timestamp : 3/28/2014 3:12:38 PM
ClientIp :
ClientHostname : EXCH13.contoso.local
ServerIp :
ServerHostname : EXCH13
SourceContext : 08D1189F97D8A52F;2014-03-28T19:12:38.090Z;ClientSubmitTime:2014-03-28T18:17:59.590Z
ConnectorId :
Source : STOREDRIVER
EventId : DELIVER
InternalMessageId : 1236950581391
MessageId : <[email protected]>
Recipients : {[email protected]}
RecipientStatus : {}
TotalBytes : 6130
RecipientCount : 1
RelatedRecipientAddress :
Reference :
MessageSubject : EXCH07-USER1 to EXCH13-USER1
Sender : [email protected]
ReturnPath : [email protected]
Directionality : Originating
TenantId :
OriginalClientIp : 2002:960a:116::960a:116
MessageInfo : 2014-03-28T18:18:00.077Z;SRV=EXCH13.contoso.local:TOTAL=0;SRV=EXCH13.contoso.lo
cal:TOTAL=35|QDM=35;SRV=EXCH13.contoso.local:TOTAL=0
MessageLatency : 00:54:38.1220000
MessageLatencyType : EndToEnd
EventData : {[MailboxDatabaseName, Mailbox Database 1497118588], [Mailboxes,
43a77dd2-c8bb-4b4c-804c-e761b15da654], [E2ELatency, 3278], [DeliveryPriority, Normal]}

CSCul66951 LDAP routing query fails when user name is the same (6 july 2014)

in the case CSCul66951 LDAP routing query fails when user name is the same it is mentionned that the version 8.0.2-055 correct this bug ? How come i don't see this version on my menu Available upgrades from my IronPort C370 ?
Is there someone on the support team that have try this LDAP query on a IronPort C370 with this version in the development lab ?
Do i have to open a support Case to have this version of AsyncOS ?
Best regards,
Benoit Belair
University of Quebec in Montreal

Yes - CSCul66951 - this was included w/ the 8.0.1-HP1, and is rolled into 8.5.6-074 GA release.
See release notes, resolved issues:
http://www.cisco.com/c/dam/en/us/td/docs/security/esa/esa8-0/release_notes/ESA_8-0-1_HP1_Release_Notes.pdf
CSCun02766 - 8.5.6-063, which was superseded by the 8.5.6-074 GA release.
See release notes, resolved issues:
http://www.cisco.com/c/dam/en/us/td/docs/security/esa/esa8-5-6/ESA_8-5-6_Release_Notes.pdf

Execute SQL Task Editor: The query failed to parse. Syntax error, permission violation, or other nonspecific error.

Environment: SQL Server 2008 R2
Code:
CREATE TABLE dbo.PkgAudit
PkgAuditID INT IDENTITY(1, 1),
PackageName VARCHAR(100),
LoadTime DATETIME ,
NumberofRecords VARCHAR(50),
Status1 VARCHAR(50),
Status2 VARCHAR(50),
The following code is inserted in the SQL Task Execute Editor
INSERT INTO dbo.PkgAudit(PackageName
,LoadTime
,NumberofRecords
,Status1
,Status2
) VALUES(?,?,?,?,?)
Screen Shot (Parameter Mapping):
Problem: an error Message occurred when I hit Parse Query Button in the Execute SQL Task Editor, "Execute SQL: Task Editor: The query failed to parse. Syntax error, permission violation, or other nonspecific error". How I could Solve this
problem

Different connection providers require different Parameter syntax. E.g. ADO @ParameterName notatoin, not just an offset of 0,1 etc.
Arthur My Blog

JPA query language syntax

My question is if JPA query language syntax allows full qualified class names in the SELECT clause of the query, e.g.:
SELECT * FROM com.abc.Person
This works well with Hibernate, but TopLink Essentials complains about the dots in com.abc.Person.
In the Java EE 5 Tutorial only partially qualified names ( SELECT * FROM Person) are used.
There are only examples with fully qualified names for constants in WHERE clauses.

my first guess:
SELECT t FROM tablename t WHERE t.timestamp>:somethingwhere :something
is handled with something like: (..).setParameter("something", someSQLDate);

Jpa query fail! :(

Similar Messages

Maybe you are looking for