I have a very strange problem:
We try to start CANape (14) with python (Version 3.8) via AzureDevops agent (Version 2.181.2) Therefore I use the following python code:
import win32com.client
CANape = win32com.client.Dispatch('CANape.Application')
CANape.Open1(args.CANapeConfig, 1, 50000, True)
CANape.RunScript(args.SciptToExecute)
...
This script works on my PC. I also tried this on the target PC - it also works.
But when I try to run this script via the agent of the AzureDevops, the application begins to execute but suddenly stops.
It appears in the task manager, but the application is not open / not running and ends after a couple of time.
Have anyone an idea?
Thank you very much.
Bastian
Related
I'm troubleshooting an Selenium script that runs through the Task Scheduler on a Windows Server. It's running in PowerShell using version 3.0.1 of the Selenium module (found here:https://www.powershellgallery.com/packages/Selenium/3.0.1) with the Edge browser (the one with Chromium).
The "The HTTP request to the remote WebDriver server for URL [localhost] timed out after 60 seconds." error has been quite persistent and only appears when run through the Task Scheduler. The script runs fine when running manually through ISE.
Also to note, there's another script that is more or less the same as the one having the issue, albeit using a slightly different url (same site). This second script runs without issue through the task scheduler. They're performing the same sequence of actions which is why I'm not entirely sure why it would fail for one script but not the other.
I haven't found a suitable solution while looking at other posters facing the same issue. Any help is much appreciated!
I had the same issue. I tried all kinds of code changes but the only step that worked for me was to change the Security Options in Task Scheduler.
Task (right-click) > Properties > General > Switch from Run whether user is logged on or not to Run only when the user is logged on.
I guess this would be a temporary solution. I'll keep looking and update this if I find a better solution.
Before explaining what my problem is, please know that I have looked up for solutions on similar topics but none of them seems to work nor even to corresponds to my problem.
What I am trying to do:
I have this python code on multiple files that I run with flask with the following command:
python -m flask run --host=0.0.0.0
So far, everything works, but I would like this code to automatically run everytime the computer boots. In the future this will be used on mini PCs without any graphical interface nor human intervention.
Since I need to do some configuration checks before running the web server, I've created a powershell script that ends with Flask running (using the previous command).
So far, everything works too. Now we're coming to the problem:
I'd like this script to run when I boot the machine. Specificity: Every things needs to work with Administrator privileges, on the local system without any interaction.
I've tried scheduled tasks but Flask won't run even if the rest of the script works (like creating folders or other things)
Ok, it's not a big deal I have other ways to do it, so I've created a Windows Service in C# to run the Script at startup on the local system.
The script works, I've checked the privileges too, everything's fine but arriving at the flask command line that is supposed to make it run, nothing works.
It's the same thing if I run flask using "pythonw" which is supposed to run python as a background process.
What the problem seems to be:
Well, as long as I run flask and I have either a command prompt or a powershell terminal, everything works greats. But if in a way or another I run the script as a background process, it won't work.
Normally it would take around 30 seconds for Flask to start-up. Here if I try to create a folder right after flask ended starting up (as a test) I can see the folder is created almost instantly, which means the process is immediately killed.
The problem doesn't seem to come from the service itself but really Windows that kills the process I don't know why
I'm running out of idea so if you guys have anything that I could try it would really help me.
I am using ROS Melodic in Ubuntu 16.04.
I am working with turtlebot 3 burger and trying out simulations on gazebo.
I have written a simple code to make the turtlebot move in a circle.
The code works perfectly as everything was working a couple of days ago.
Now when I try to launch it using
roslaunch assignment3_ws move.launch code:=circle
I get the following error:
ERROR: could not contact master [https://localhost:11311]
The traceback for the exception was written to the log file
I tried running it in every possible way.
With roscore, without roscore.
Even the network is setup properly in the bash file.
Can anyone provide a solution?
Have you changed the ROS_MASTER_URI environment variable to 192.168.1.162 ?
if you are using simulation and you need to set your ROS_MASTER_URI to localhost.
you only change ROS_MASTER_URI if you are trying to connect to remote ROS systems(Servers, other PCs, etc).
I'm trying to automate the deployment of the solution my team is working on through TFS Build server. One of the steps which executes a PowerShell script on the target machine fails with the following error:
Microsoft ODBC Driver 11 for SQL Server : Login failed for user 'sa'..
The PowerShell script I'm trying to execute does in fact connect to multiple databases using the sa credentials. When I try to execute the same script passing it the exact same arguments by hand (i.e: executing the script from the target machine VM itself) it works like a charm. But when it is being executed as part of the build steps it fails with the aforementioned error.
Is there a way to further debug the issue? It would be great if there is a way to output trace statements from the script so I could have some insight on what is actually going on.
Usually all the related error should reflect in TFS build log. To narrow your issue you can try to connect to the TFS build agent with the credentials used for the build service and manually run the ps script.
If you execute the ps script with your own account, which will not help to the issue. Usually this kind of problems is related to permissions. Your build service account are lack of related permission. Try to add it to Administrator or SQL Administrator group and execute the build again.
Everytime I try to run the local server on unity I get this error:
ArgumentException: Can't find process with ID 787
After this error, the button is disabled. I'm using a Mac, I'm running behind a proxy but my co-worker said that he can run it just fine. Maybe it's a bug? Once I click the error, it directs to this line of code in the LaunchAssetBundleServer script, which comes by default with the AssetBundleManager that you can download from unity.
var process = Process.GetProcessById (instance.m_ServerPID);