I have had a scheduled UiPath job running each 2 minutes for the last few months without any issues. Today, the scheduler does not seem to work at all. I can't seem to find a reason why.
I have tried all of the following:
Restarted the machine
Disabled/enabled the scheduled job
Checked all robot and machine settings in orchestrator
Check to see that the license status is still OK
Upgrade studio from 18.3.2 to 19.2.0
We are using the Community Edition Orchestrator and version 18.3.2 community studio. I upgraded to 19.2.0 studio as well, but that did not seem to help. Running the robot from the server manually works when starting a process from the taskbar robot window, but the orchestrator schedules do not seem to be working at all.
Everything seems to set up right considering nothing was changed since this has been running fine for months. It ran well yesterday but simply does not run at all starting this morning. Am I missing something here?
Turns out this was a performance issue with UIPath Orchestrator Comunity Edition. There have been issues today according to a few posts on the UIPath forums...
https://forum.uipath.com/t/schedules-no-longer-executing/100553
https://forum.uipath.com/t/robot-isnt-running-as-i-scheduled-on-orchestrator-community-edition/100471/2
Related
Afternoon all,
I had been using the Visual Studio 2022 Preview. Recently I decided to switch to the Release version. I uninstalled VS2022 Preview and installed the 2022 Community Release.
The install runs fine and completes with no issues. However when trying to run VS2022 It comes up with the error attached below.
From my talks with MS found at https://developercommunity.visualstudio.com/t/Unable-to-launch-VS-Comunity-2022-after/1596301?entry=myfeedback&viewtype=all It appears VS2022 Community should be running version 17.0 of the .Threading DLL. However no matter what I have tried it refuses to load.
I have run the uninstaller with -F. Re-installed several times.
Attempted to install 17.0 to the GAC but this does not change the outcome
As per the post on the developer community pretty much everything short of re-installing windows (Which I am 100% trying to avoid)
I ran the FusionLog viewer (Attached) and it looks like there is something re-binding this to the 17.1 .threading version however I know very little about how this works and where I might find a solution, Hence, I am here :). Although my post on the DeveloperCommunity is still active I'm hoping a resolution here maybe faster!
Thank you!
I have this error too, and its becouse you dont have defined startup project.
Right click on your startup project and choose "set as startup project".
Actually the above is incorrect, you can't even get to the startup screen.
The correct answer is you need to remove the V15 version of the dll from the GAC. Instructions from MS can be found here.
Yesterday I updated SSMS from 16.3 to 16.4.1, rebooted and then installed the Window 10 Anniversary Update from Windows update. Everything on my PC seemed to be running fine.
However, trying to open SSMS today for the first time since the update and nothing happens. There is no error message and nothing is created in Event Viewer.
I have tried repairing the installation, which didn't fix the problem, and reinstalling the application which again did not fix the problem.
I can see in Process Monitor that the process exits with status 0 and it doesn't appear there is any effort made to write to a log file.
Has anyone encountered a similar issue with this release?
Edit: The problem is resolved by uninstalling 16.4.1 and reinstalling 16.3, which makes me think something is broken in the latest release.
It appears the solution, after rolling back to 16.3, was to install the Community edition of Visual Studio 2015 and then install 16.4.1 again.
I have a problem with Visual Studio 2015.
When I start the IDE, it hangs after a short while, and I need to kill the process in Task Manager. Sometimes, I can open a project before it freezes, but then it usually freezes some time after that.
My OS: Windows 7
VS version: 14.0.24720.00 Update 1
Screen shot from ProcessExplorer:
(red marks numbers that keep climbing, the rest are not increasing)
I have created a dump file, but can't debug it...
Can someone please help me?
EDIT: Feb 2017 :
New PC (Windows 10) and newer version (14.0.25431.01 Update 3) do NOT give the same problem.
I had the same issue a while ago.
First, I'd recommend you to disable all extensions you're not interested in using of.
Second, many of VS issues is because of Node.js Tools. Though latest version of which fixes many of them, I highly recommend you to uninstall it if you're not planning to develop node-based apps.
Finally, there's still a lot of performance issues with VS, so we can only hope that Microsoft will fix them in the future.
New PC (Windows 10) and newer version (14.0.25431.01 Update 3) do NOT give the same problem.
I'm using Microsoft Visual Studio Community Edition 2013. My trial ran out recently and I'm trying to renew it by logging in. A window pane comes up for me to sign in and I enter my credentials, however I get the following script error:
Line: 4
Char: 16405
Error: Object doesn't support this property or method
Code: 0
URL: https://app.vssps.visualstudio.com/_static/tfs/20150123T002517/_scripts/TFS/Loader.min.js
After some rudimentary searching, it seems as if I'm missing a library. Has anyone experienced the same problem and knows which part of the code it's referring to? I don't want to go on a mad updating rampage.
I have been running into this problem for months. I do development on Virtual Box machines running XP, because it is small and easy to copy, and I have gotten this problem on some of the machines and not others. I thought it had to do with window updates, but I have that turned off, and I am still getting the problem on machines that just worked a few days ago. Unfortunately with XP you can't update anything or even go back to a previous version of IE.
Actually, it was the virtualization software itself. I'm actually using vmware not virtualbox (mix-up in the comments). Incidentally, vmware just released an update today and after installing it, I was able to log in.
By the way, it could've been the log-in itself. After the update, microsoft visual studio didn't even ask me to validate the software, but went straight to the ide. I saw by my user id, an exclamation prompting me to sign in, whereupon I was able to validate my install.
I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.