BMC Synthetic Transaction Monitoring 10.5 - How to disable Accurancy check - synthetic

I need to disable the Accurancy check only on every execution plan configured.
The others check (Performance, Availability Errors, Execution Errors) must be active.
Could anyone help me?
Regards,
Ema

Below my solution
Guide: https://community.microfocus.com/borland/tm_art/w/knowledge_base/22848/classifying-tm-art-workbench-script-runtime-error-as-availability-or-accuracy-error-in-tm-art-central
Steps:
open file .ltz with Silk Performer
Settings -> Active Profile -> Replay -> Simulation -> Errors tab
Click the Add... button.
Select a module and a severity and the list of predefined error codes will appear in the table.
For example, select "BMC TM ART - HTTP" as module and "error" as Severity. In the list of error codes, you will find the code "500" and its error description "internal server error". Below is a screenshot of some error codes for the WinSock module.
Select the new severity
Save and reload file .ltz

Related

Magento 1.9 site where "SQL ERROR: SQLSTATE[42S22]" keeps showing up after daily reindex (and in other instances)

I own a Magento CE 1.7 based website where we keep getting variations of the following error, usually after the daily morning site reindex:
"SQL ERROR: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'main_table.data' in 'field list'
SQL QUERY: SELECT DISTINCT main_table.data, main_table.lifetime, main_table.expire, main_table.priority, additional_table.*, IFNULL(al.value, main_table.frontend_label) AS store_label FROM eav_attribute AS main_table
INNER JOIN catalog_eav_attribute AS additional_table ON additional_table.attribute_id = main_table.attribute_id
LEFT JOIN eav_attribute_label AS al ON al.attribute_id = main_table.attribute_id AND al.store_id = 1 WHERE (main_table.entity_type_id (...)"
I have a website down detector set up so that I can know immediately when the site is unavailable. However it obviously doesn't detect whenever the site is unusable due to errors such as “SQL ERROR: SQLSTATE[42S22]”. That means that my team must be constantly manually (!!!) monitoring if the site is indeed working properly (by clicking on product and category links)!
Usually we surpass the error by just cleaning the cache or performing a new reindex.
My questions are the following:
1 - Is there a way of automatically perform a detection of this type of errors in Magento so that - if it happens - a cache cleaning (or a site reindex) is immediately run and an alert is sent to the webmaster?
2 – If such an error is detected, is there a way of it not be shown to the person accessing the site? That is, if the error is detected, is it possible to immediately display a message (“We’ll be back soon”) while the cache is being cleaned or the site reindexed?
I will be grateful for any help you can provide.
Thank you!

How to Call package successfully

got error when calling package
error is
Error starting at line : 1 in command -
PKG_Generate_GRNo.GenerateGR(TO_NUMBER(:P164_APP_ID,
'9999999'),:APP_USER,:P164_FIRST_NAME,:P164_LAST_NAME,:P164_EMAIL,:P164_SKYPE_ID,:P164_COUNTRY,:P164_DATE_OF_BIRTH)
Error report - Unknown Command
PKG_Generate_GRNo.GenerateGR(TO_NUMBER(:P164_APP_ID,
'9999999'),:APP_USER,:P164_FIRST_NAME,:P164_LAST_NAME,:P164_EMAIL,
:P164_SKYPE_ID,:P164_COUNTRY,:P164_DATE_OF_BIRTH);
Session state protection violation is definitely an Apex error, relating to your page settings. It seems your package is trying to change the state of a read-only page. See this other question.
The item identifier in the error message P164_COURSECOUNT has the same prefix as the parameters you pass to the package (:P164_APP_ID) so presumably they relate to the same page. We know nothing about your application or its architecture, so it's hard to offer concrete advice. Maybe you need to change the page or item settings, maybe you need to change what the package does. Only you can tell the right course of action.
As you didn't post the whole command, a note: you have to enclose it into begin-end block, e.g.
BEGIN
PKG_Generate_GRNo.GenerateGR (TO_NUMBER ( :P164_APP_ID, '9999999'),
:APP_USER,
:P164_FIRST_NAME,
:P164_LAST_NAME,
:P164_EMAIL,
:P164_SKYPE_ID,
:P164_COUNTRY,
:P164_DATE_OF_BIRTH);
END;
/

Pentaho SolutionEngine.ERROR_0007 on Red Hat

I installed some days ago Pentaho BA (full install) on a Red Hat system. I installed version 5.0.7.1-x64 because the latest 5.1 version gave me problems just after the installation. The 5.0.7.1 version still have some problems (exceptions in logs) but it was working fine, until today. Today I logged in into the PUC and I found that there are some severe issues in the functionalities of the server: after logging in I get only the upper menu and not the content of the home page. I can access and see the "Browse Files" menu, but when I select a dashboard or a report it doesn't load: it just loads the upper bar like for the home page and the title but the dashboard is completely empty. Not even the "grid" for the various reports.
I copied the content of the log file catalina.out and you can find it here http://pastebin.com/hshXekFM
From line 33 there's the part where the server loads the login pageFrom line 51 it's after the login.
Here you can find the content of the catalina.2014-07-09.log http://pastebin.com/L7ReLdpt
and here the pentaho.log file:
2014-07-09 09:53:53,732 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] 2bc1b7a9-073e-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/Secure/global-department-list.xaction: SolutionEngine.ERROR_0007 - Action sequence execution failed
2014-07-09 10:20:56,969 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] f39bcc4a-0741-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Esecuzione dell'Action Sequence fallita
2014-07-09 10:20:57,185 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] f3be215b-0741-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Esecuzione dell'Action Sequence fallita
2014-07-09 10:20:57,224 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] f3c3035c-0741-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Esecuzione dell'Action Sequence fallita
2014-07-09 10:20:57,322 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] f3d2bacd-0741-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Esecuzione dell'Action Sequence fallita
2014-07-09 10:22:17,301 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] 23814d9e-0742-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Action sequence execution failed
2014-07-09 10:22:17,343 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] 238656af-0742-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Action sequence execution failed
2014-07-09 10:22:17,434 ERROR [org.pentaho.platform.engine.services.solution.SolutionEngine] 23941250-0742-11e4-8cb0-005056a82a08:SOLUTION-ENGINE:/public/bi-developers/rules/session-region-list.xaction: SolutionEngine.ERROR_0007 - Action sequence execution failed
2014-07-09 10:22:17,492 ERROR [org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob] ActionAdapterQuartzJob.ERROR_0004 - Action "org.pentaho.platform.plugin.action.builtin.ActionSequenceAction" failed to run as a quartz job
java.lang.Exception: java.io.FileNotFoundException
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.invokeAction(ActionAdapterQuartzJob.java:271)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.execute(ActionAdapterQuartzJob.java:133)
at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:38)
at org.quartz.core.JobRunShell.run(JobRunShell.java:199)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
Caused by: java.io.FileNotFoundException
at org.pentaho.platform.web.http.api.resources.RepositoryFileStreamProvider.getInputStream(RepositoryFileStreamProvider.java:118)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob$1.call(ActionAdapterQuartzJob.java:176)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob$1.call(ActionAdapterQuartzJob.java:166)
at org.pentaho.platform.engine.security.SecurityHelper.runAsUser(SecurityHelper.java:179)
at org.pentaho.platform.engine.security.SecurityHelper.runAsUser(SecurityHelper.java:168)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.invokeAction(ActionAdapterQuartzJob.java:250)
... 4 more
2014-07-09 10:22:17,502 ERROR [org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob] ActionAdapterQuartzJob.ERROR_0001 - Property "ActionAdapterQuartzJob-ActionClass" or "ActionAdapterQuartzJob-ActionId" must be set in the job data map
2014-07-09 10:22:17,502 ERROR [org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob] ActionAdapterQuartzJob.ERROR_0002 - Failed to create an instance of action "unknown"
org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob$LoggingJobExecutionException: ActionAdapterQuartzJob.ERROR_0001 - Property "ActionAdapterQuartzJob-ActionClass" or "ActionAdapterQuartzJob-ActionId" must be set in the job data map
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.resolveClass(ActionAdapterQuartzJob.java:79)
at org.pentaho.platform.scheduler2.quartz.ActionAdapterQuartzJob.execute(ActionAdapterQuartzJob.java:117)
at org.pentaho.platform.scheduler2.quartz.BlockingQuartzJob.execute(BlockingQuartzJob.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:199)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:546)
How can I solve this?
Thank you very much in advance
Just edit the file sessionStartupActions.xml and comment out the lines that are calling those .xaction files.
That happens when it tries to call the actions for the sample data that you probably didn't install.
This is very likely to be Quartz configuration issue.
I would suggest to re-check quartz configuration files - have they been modified by patch or manually since last job/transformation was successfully scheduled?
This may be a start point.
If this is not a solution don't hesistate to fire a bug - at least developers could provide more sophistaicated error message for this case.
For enterprise users pentaho provides official support - so don't waste time for forums and kick they directly.
Otherwise - quartz is widely used so at least there is some configurations where it is really works without this exception - so the question is to find what is the difference between this one and other.
Hope it will help a little bit. :(

Method 'add' in COM object of class 'Documents' returned error code 0x800A175D (<unknown>) which means: <unknown>

I am trying to open word Template from AX 2012 Reports. It works fine in the env I have developed but when I try to execute the same from different login I face the "COM error"
Please help.
You can always find help for these mysterious Office error codes by decoding the error code. COM error codes contain three major parts:
the top 4 bits indicate the severity of the error. 8 means "warning", one you can't ignore
the next 12 bits is the facility code, the origin of the error. 10 means "automation"
the lower 16 bits is the internal error code, the one that you really care about.
Switch your calculator to hex mode, 0x175d is error code 5981. Now turn to Google and query "word error 5981".
Lots of good hits, you can read them at your leisure. But clearly there's a problem with macros on that machine. Best left to the IT staff at your site, use superuser.com if you need more help with that.

Restart my delta loading after delete the infopackage in PSA by mistake

here i have got one issue.can some one please help me to resolve this.
i was trying to extract some data to DS 0FI_AP_6...
then in InfoPackage Monitor I can see like..
-->Requests (messages): Everything OK
-->Extraction (messages): Everything OK
-->Transfer (IDocs and TRFC): Missing messages or warnings
-->Info IDoc 2 : sent, not arrived ; IDoc ready for dispatch (ALE service)
Data Package 1 : 23752 Records arrived in BW
Data Package 2 : 15216 Records arrived in BW
Request IDoc : Application document posted
Info IDoc 1 : Application document posted
Info IDoc 3 : Application document posted
Info IDoc 4 : Application document posted
-->Processing (data packet): Everything OK
Data Package 1 ( 38672 Records ) : Everything OK
in Status Menu I am having message like...
Missing data packages for PSA Table
Diagnosis
Data packets are missing from PSA Table . BI processing does not
return any errors. The data transport from the source system to BI was
probably incorrect.
Procedure
Check the tRFC overview in the source system.
You access this log using the wizard or following the menu path
"Environment -> Transact. RFC -> Source System".
Error handling:
If the tRFC is incorrect, resolve the errors listed there.
Check that the source system is connected properly to BI. In
particular, check the remote user authorizations in BI.
Please suggest me how to resolve this issue...
thanks in advance for your help and quick reply is much appreciated.
But what the worst thing is I deleted the infopackage in PSA by mistake.
In the normal case, if I repeat the process again, the delta load would be OK, but now the delta load remains error.
so gurus,
1. how can I restart my delta loading correctly?
2. I want to modify the timestamp in the delta table, but how to do it ?
Go to T-Code RSA7 in the source system. This will tell you the date/timestamp that the delta is set to. If the date was changed to a range that no longer works then you will need to re-initialize the datasource in the BW system side. However, the Delta date may still be fine becauase it may have never been changed when you tried to first do your load because of the connection issues.
You can create a new infopackage and set the update to Initialize Datasource with Data Transfer. This will essentially run a full load from the datasource and then reset the delta pointer date/timestamp to when you ran it. This way you will capture all the data that you needed and anything that was already in the PSA should be overwritten.
Also note that you should delete or set the request status to red on the previous request that may contain bad data in the PSA.
From the original error it seems like you are having an RFC connection issue between the datasource and BW. Contact your BASIS support and have them check the connection to make sure it is good. To ensure that your datasource is extracting properly you can run t-code RSA3 on it in the source system. This will ensure that the extraction of data is working properly.