I get the below error when I run my xaction file in PUC (Pentaho User Console)
The Pentaho BI Platform reported an error while running an action sequence
Possible Causes:
ActionValidationException: RuntimeContext.ERROR_0035 - Action validation failed.
Action Sequence:farzan.xaction
Execution Stack:
EXECUTING ACTION: looking for the current user (KettleComponent)
Loop Index:N/A
I have attached xaction, ktr and database at:
https://drive.google.com/folderview?id=0BxjJ_gZ-RT2EemMtLTlYR1R3TUk&usp=sharing
It seems that your xaction file is throwing errors. Best way to find out your errors is to go search the log files. The path would be inside the BA Server: /pentaho/server/biserver-ee/pentaho-solutions/logs/.. There you will find log file. Check the error that is written in the logs.
[Also to note, from version 5 onwards, xaction support has been removed from the Pentaho releases.]
Hope this helps:)
Related
I have configured a machine with windows server 2016 and pentaho CE 7.0
I have already developed several Jobs and Transformations with their respective .BAT.
My problem occurs when I run the Jobs from the Windows Task Scheduler, which indicates the following error in the log:
Error opening new file 2020/07/08 13:43:36 - Microsoft Excel Writer.0
ERROR (version 7.0.0.0-25, build 1 from 2016-11-05 15.35.36 by buildguy) : java.io.IOException: Error creating output file! Parent
directory [file:///W:/Prueba] does not exist.
I already confirmed that the route exists and the most frustrating thing is that if I run the .BAT with a double click I get to the route.
Check for permissions ! it seems probably your script dont have correct permission to write in that folder.
I am using Loadrunner 2020 community edition. I have created a script in TruClient and when trying to replay in develop script mode, getting 'replay failed to start see vugen log for more details' error.
'logfile.log' was empty and 'mdrv.log' file had last replay log details when checked. Are those the files vugen referring to? What is the solution for this?
I faced the same issue, but was able to fix it as follows.
When I compiled the script, I did not see any errors in the output, so I checked the "Output -> Chromium(IE) - Interactive Replay" log which had several errors related to parameter files. When I fixed those, I was able to replay the script.
Output Log Path
I have an SSIS job that contains a script task.
There is also a connection to another server within the package that can only be executed accessed by a specific user and the agent cannot be given read rights to the other server.
So the solution to this is have the SQL job be run as the required user.
The problem with this is this user does not have full control over the folder/file where the script task will be temporarily located while the code runs so I get a failure on the script task but if I run it in visual studio or with the normal agent account the script task executes successfully.
I have tried giving the user access to all major drives on the server but this has not solved the problem
Is the script doing something on the folder?
Or does it just need permission to execute script?
I would anyway advise you to implement error handling in script:
https://learn.microsoft.com/en-us/sql/integration-services/extending-packages-scripting/task/logging-in-the-script-task?view=sql-server-2017
Make sure it works in visual studio, so that when you get that error you are sure that the error is caused by permissions/environment.
You could also take a look at this article:
article
I'm trying out SonarQube using the new MSBuild SonarQube Runner v1.0. If I install a fresh SonarQube server locally, the following command works fine, and I can build my solution directly afterward, call the 'end' command, and have the results published in SonarQube:
MSBuild.SonarQube.Runner.exe begin /key:TestKey /name:TestName /version:1.0.0.0
However, if I run this against an existing SonarQube server that exists on the internal network, it always returns with exit code 1:
15:32:40 Creating config and output folders...
15:32:40 Creating directory: c:\Test\MSBuild.SonarQube.Runner-1.0.itsonar\.sonarqube\conf
15:32:40 Creating directory: c:\Test\MSBuild.SonarQube.Runner-1.0.itsonar\.sonarqube\out
15:32:41 Generating the FxCop ruleset: c:\Test\MSBuild.SonarQube.Runner-1.0.itsonar\.sonarqube\conf\SonarQubeFxCop-cs.ruleset
Process returned exit code 1
It seems to download a lot of the dependencies into /.sonarqube, so communication with the server isn't an issue
Things I've tried:
checked the access.log, server.log and event logs
upgraded the existing server to v5.1.2 (clean install using the guide)
upgraded the sonar-csharp-plugin to v4.1
right-clicked all .jar files on the server and ensured they are unblocked
tried the runner directly on the server
(ongoing) tried debugging the source code (happening somewhere in the pre-process step: success comes back as true, but the error code is 1)
disabled UAC on the server an rebooted
re-installed JRE on both server and client, ensure JAVA_HOME in both PATH and registry are set correctly
Any help or pointers greatly accepted. I've been stuck on this for 2 days and can't think of anything else to try except continue trawling through source code. Thank you.
This is a tricky one! Looking at the code, I see only one path that can yield this output:
It fails while generating the FxCop ruleset for C#, as the VB.NET FxCop ruleset message is not logged - see TeamBuildPreProcessor.cs#L149 and TeamBuildPreProcessor.cs#L185
The GenerateFxCopRuleset() call for C# threw a WebException, leading to the call of Utilities.HandleHostUrlWebException() - which has to return true for the exception to be silently swallowed - see Utilities.cs#L153
The only path returning true without logging any message is if a HttpStatusCode.NotFound was received - see Utilities.cs#L158
The control flow goes back to FetchArgumentsAndRulesets(), which returns false, then goes back to Execute() which returns false as well - see TeamBuildPreProcessor.cs#L106
The MSBuild SonarQube Runner "begin" phase (called "preprocessor" in the code) fails - see Program.cs#L42
So, at some point, some SonarQube web service required for the C# FxCop ruleset generation is return a HTTP 404 error.
Could you monitor your network traffic and listen for the failing HTTP call? [I will keep on updating this answer afterwards]
EDIT: Indeed the error is caused by the quality profile name containing special characters. Such characters are currently badly URL-escaped, which leads to a 404.
I've created the following ticket to fix this issue in the upcoming release: http://jira.sonarsource.com/browse/SONARMSBRU-125
I'm trouble shooting an SSIS package that is failing. When I execute the package it runs 1st step but fails at the second step with the message "Execution of the job "XXXX" failed. See history log for details, history log has very little information there. Is there a way to see an exact error or generate log file with meaningful information?
Thanks!
You should modify Logging in the package so that it logs all possible things and rerun the package to see where it is failing.
But before that, you should back up the package so that you can recover from mishaps.