I have a Master-Detail Interactive Grid page in Oracle Application Express. Occasionally, users get the error message "Error Processing Request" when they attempt to save changes to the interactive grids. The users don't see any other detail on the error (including the code for the error). In those instances, there are no obvious problems with the data being entered (no mandatory fields missing, validations that would fail, etc). I am unable to reproduce these errors myself. I suspect that the errors may be caused by some sort of connectivity problem, but I have no way to verify this. Is anybody aware of the cause (or common causes) of this error?
Not an answer, but a tip to try to find more information on the "monitor activity".
1 - Go to "monitor activity"
2 - Click on "By View"
3 - Try to find in the report, filtering in the error column, some occurrence of this error.
4 - Check if is there a link in the "debug id" column; it will take you to more details about page execution; see if you find any error code or some other useful information ...
Related
I have a dataflow flow that appends to an existing bigquery table which has been working for the last few weeks. When i run it now it gives me the error "Cannot run job. Please reload the page and try again." and won't even start the job.
After trying a lot of things, i made a copy of the flow and when the publishing action is creating a new csv file, it works but when i try to
Add a publishing action to an existing big query table,it keeps giving me another bizarre error "SyntaxError: Unexpected token C in JSON at position 0".
I have no idea what is happening since everything used to work perfectly and i made no changes whatsoever.
I am not adding anything new, but I want to give you an answer.
It seems that one of your JSON inputs may be malformed. Try logging it to see what's the problem - and also try skipping malformed JSON strings.
As mentioned in past comments, I suggest to check your logs in StackDriver to find out why are you getting the:
"Cannot run job. Please reload the page and try again."
Also if you can retrieve more information about the error from those logs, It'd be useful to assist you further.
Besides the above, maybe we can solve this issue easier by only just checking the json format, here I put an easy third party json validator and here you can check where you have the error in your json.
I'm reviewing the Sitecore logs in my site and I'm getting a huge number of the following error:
ERROR Evaluation of condition failed. Rule item ID: Unknown, condition item ID: Unknown
Exception: System.InvalidOperationException
Message: Operation is not valid due to the current state of the object.
Source: Sitecore.ExperienceAnalytics
at Sitecore.ExperienceAnalytics.Aggregation.Rules.AggregationAdaptor.HistoricalVisitContextBase.GetPages()
at Sitecore.Analytics.Rules.Conditions.HasVisitedPageCondition1.Execute(T ruleContext)
at Sitecore.Rules.Conditions.WhenCondition1.Evaluate(T ruleContext.......
In the past week, this error has occurred >10,500 times
I don't know what to do to figure out what is causing the error or to resolve it. I don't know if it's affecting site performance or not, but I'd like to resolve this issue so I don't have >10k errors happening each week.
This helped me solve the issue: https://sitecoreart.martinrayenglish.com/2017/10/sitecore-xdb-mechanics-guide-to.html
The most common cause of the error is due to old tests that are still part of the content item's configuration, that are either not stopped correctly, inactive or have been removed.
Fixing the Issue
The fix is to remove the bad/old test references from the item in question's Final Renderings XML field.
-Determine what item is throwing the testing exception.
-Enable raw values and standard fields in the “View” section of the “View” tab.
-Copy the Final Renderings XML value of the item and format it so that it is easy to read. This site does a nice job: https://www.freeformatter.com/xml-formatter.html
-Paste you’re the XML into Visual Studio or another editor.
-Locate the attributes in the XML that have a s:pt and remove the attributes.
-Copy and paste the updated XML back into the item's Final Renderings field.
-Save and publish.
After this, the errors will stop appearing in your logs. You will however need to launch your test again.
When I click the view button next to an order (whether from the dashboard or orders page) I get an "error undefined" alert as the page is loading.
I also get the same error when I try and change the order status from the same page and it yields no results.
It also produces no errors in the error log.
I can however change the order status from the edit order page but this is very inconvenient.
If anyone knows a common solution or maybe pointers as to how to start diagnosing the issue please post them here. I've been hunting for answers most of the day and have had no luck with any solutions.
ty in advance.
if you are using SSL Tyr this at upload/admin/controller/sale/order.php
After
$data['store_name'] = $order_info['store_name'];
Remove
$data['store_url'] = $this->request->server['HTTPS'] ? preg_replace("/^http:\/\//", "https://", $order_info['store_url']) : $order_info['store_url'];
Add
$data['store_url'] = $this->request->server['HTTPS'] ? HTTPS_CATALOG : HTTP_CATALOG;
Unfortunately OpenCart 2.2.0.0 is known to be a bit buggy.
Best thing would be to start using 2.3.0.2 (avoid 2.3.0.0 and 2.3.0.1) if possible.
In our QA environment and prod environment we have the same deployment (But different server env.).
In PROD environment, when I log into Page editor, page editor ribbon keeps loading for 4 mins. Once it's loaded it works fine. But if I navigate to a different page again the ribbon gets loaded for 4mins.
In QA server things are fine, these deployments are identical to each other. Just wondering why it's slow in PROD env.
Any ideas?
Sitecore version 6.6
Logs says,
ManagedPoolThread #16 08:51:27 INFO Job ended: AllClassifieds.Web.Extensions.Agents.WebPublisher (units processed: )
1372 08:51:54 ERROR A potentially dangerous Request.Form value was detected from the client (leftpane_0$hdnFSClientState="<fsclientstate></fsc...").
Exception: System.Web.HttpRequestValidationException
Message: A potentially dangerous Request.Form value was detected from the client (leftpane_0$hdnFSClientState="<fsclientstate></fsc...").
Source: System.Web
at System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection)
at System.Web.HttpRequest.ValidateHttpValueCollection(HttpValueCollection collection, RequestValidationSource requestCollection)
at System.Web.HttpRequest.get_Form()
at Sitecore.Pipelines.PreprocessRequest.SuppressFormValidation.Process(PreprocessRequestArgs args)
This error repeats for several minutes until page editor gets loaded.
I don't think that the performance problem is related to the validation exception you've included in your question. I think (but it's only the guess) that the reason between the speed of QA and PROD environments is the number of items in the PROD environment.
From my experience I know that sometimes there are issues with My Items ribbon button in Page Editor. It displays the number of items locked to the current user and for every ribbon reload it makes another query to get all this items.
Maybe try to remove this button (log in to core database and look for /sitecore/content/Applications/WebEdit/Ribbons/WebEdit/Page Editor/Edit/My Items) and see if this helps.
If not, I do recommend using some profiling tool like dotTrace Performance (you can download 10-day free trial) and see if it can find the problematic place.
Yes, two years later and still relevant.
In Sc8 rev 4 at least.
WebEdit.ShowNumberOfLockedItemsOnButton isn't used anymore. It still exists in the code, but there are no usages of it. It doesn't affect this problem when set.
So another solution is to set amountOfLockedItems to 0 and comment out:
var amountOfLockedItems = context.app.canExecute("ExperienceEditor.MyItems.Count", context.currentContext);
In MyItems.js. Or as said, just hide/erase the button on the core database.
I guess Sitecore doesn't want to run this query on index as it would be too inaccurate for the users, but maybe they could optimize the database query a bit? We have over 9000, sorry 200000 items and it takes a whole minute to find all the locked items for the user.
I have a "DatabaseError: current transaction is aborted" that comes and goes (to be specific, 11 times out of 841) in a Django 1.3 project using Postgres. The project is a quiz site and the error occurs when a user submits the answer form in the view. From the database's perspective, the process involves a number of queries and looks like this:
Gather all of the correct answers for the question (they are multiple choice and may need more than one answer)*
Grab the user's profile
Save this answer
Query for the user's new point total
Save the total to their profile
Check to see if they qualify for a new reward
Award new reward if they do
Somewhere in that tortured process, this error crops up (I'm guessing because one query isn't waiting for the others). Is there a way for me, in production (i.e., DEBUG = False), to log the database errors just in this case? I'm on WebFaction and the Postgres error logs are not available to me. Could I steal something from this middleware example to fire in just this specific case?
Alternatively, is there a better way to find this error or should I be wrapping the individual queries in transactions (unfortunately they aren't all in the same place in the code, not sure if wrapping the view in a transaction decorator would help)?
*Just to confuse matters, the multiple right answers requirement was added in the middle of development and then dropped right before we went live, so I could simplify this process somewhat, basically skipping steps 1 and 4, but I'd like to know a general answer to this sort of mysterious issue.
You haven't said where in your 7 steps you have transactions that begin and end. That would be helpful to know.
One source of "transaction aborted" messages is due to deadlocks. More details would be in the PostgreSQL logs.
But the bottom line is that you will continue to have a painful and time-consuming experience debugging PostgreSQL if you can't get access to your PostgreSQL error messages. Take that up with WebFaction. If they can't helpful and your time is worth much, your bottom line costs will be lower by moving to an environment that provides this fundamental feature.
You have to enable autocommit for the transaction. In your DATABASES entry, include:
'OPTIONS': {'autocommit': True,},
By default, Django opens a transaction at the first query. By using this option, you manually have to start a transaction (e.g. using #commit_on_success). Since there is no transaction open anymore, you'll get the actual error that was previously masked by the transaction error.
The autocommit setting will be the new default for Django 1.6, see https://docs.djangoproject.com/en/dev/ref/databases/#postgresql-notes