I have rebooted my computer and when I try and run my UiPath Sudio project that was working fine yesterday, I get a Runtime execution error saying Orchestrator information is not available and to check if the robot service is started.
Any idea why my RPA application isn’t working?
I'd say there are three possible reasons why your UiPath Robot isn't starting:
The Windows UiPath Robot Service hasn't started
UiPath Assistant is not connected to UiPath Orchestrator
You are running the program on a different machine
UiPath Service
Windows configures the UiPath Robot service to initialize with a delayed start. If your computer has a large number of services, you may boot up Studio and run your UiPath App before it's actually initialized. In this case, you can solve the problem with patience and just wait. Or you can be more proactive and change the startup type to Automatic from Automatic(Delayed Start)
UiPath Assistant
You may simply not have UiPath Assistant configured or running. In order to connect to or publish to UiPath Orchestrator, the UiPath Assistant must be running. Check to make sure it's running and it's connected.
Wrong computer?
You said you rebooted, so this may not be your problem. But I once did a git clone of a project on another computer and when I tried to run the app I couldn't connect to UiPath Orchestrator and couldn't figure out why because is worked on my other laptop.
Of course, every laptop needs its own unique machine configuration in UiPath Orchestrator. It was an obvious error but so obvious it took me a long time to figure it out. So just remember each machine needs its own UiPath Orchestrator configuration and UiPath Assistant connection.
Related
Here is a situation:
An Azure Windows 10 VM is working through a day and is being used via RDP without a problem, while suddenly RDP drops and RDP is no longer a mean to connect. Looking at Azure portal, in an Activity Log, one can see that the VM is deallocated and the Entity that started the action is VS DevTest Lab.
While I've been using some Azure Fluent API for .Net to test start and stop of VM, those tests never came up as being triggered by VS DevTest Lab.
Can someone explain what VS DevTest Lab mean when it comes to practically determining who triggered a VM deallocation? Thank you in advance.
I believe this is because in DevTest Labs you can have the auto-shutdown configured to save on expenses. Check to see if that is configured in the portal
I installed TFSE on my computer. Now I want to stop it from auto running from when I boot the computer, but I rather not uninstall it. I've checked the startup list in Task Manager but it's not there. Is there any way of stopping it from auto-starting?
First, just as Daniel says:It's not recommend to hold TFS server on your own desktop PC. If you really want it, you can install it in your Virtual machine. Install Team Foundation Server
If you just need the service and process of TFS not running. You can stop the service manually follow Stop and start services, application pools, and websites
If you want to prevent Visual Studio from connecting to Team Foundation Server on startup. Please refer this smilar question.
I'm trying to follow a tutorial on Azure deployment. I'm stuck on one of the first steps creating the App Service. It seams that the form tries to find all App Service Plans but can't, so all of Visual Studio hangs. I had to kill it with Task Manager. Any clues on how I can fix this? Do I need to create something at the Azure management console?
Had the same issue, turned out I hadn't installed Azure SDK, you'd think there would be some kind of error message, but no. Installing the SDK fixed issue
I did the steps below to resolve the issue.
Login to your Azure account
Manually create an app service (use any dummy app service name). The service plan and resource group will be created while you're creating this app service
Once you see the dummy app service created on your Azure dashboard (it will take around 1-2 minutes), open your visual studio from your pc, create your web project and check api service
--- This time, the service plan and resource group will be brought in.---
Click "Create" to create your "real" web/api project in Azure
Now you can remove the dummy service from Azure
I had the same problem. It started to work after I logged into the Azure Dashboard and manually created an App Services Web App.
Ran into the same issue a few days ago and here is how I got it working.
I had yet to create any App Services in the Azure account I had tied to Visual Studio and when I got to the Create App Service window you posted, Visual Studio would freeze.
I logged into the Azure Portal, created an App Service with a different name than the project. Once it was created, I then deleted the newly created App Service.
After doing this had no problem freezing in Visual Studio. The fix appears to be to create at least one App Service in portal before it works in VS.
I did two things at once, not sure which one got through the lock up.
1) In Visual Studio, went to File -> Account Settings then under the "All Accounts" section of the Account Settings window I reentered my credentials for the Azure account I had linked the project to. This account had a notification raised saying "We need to refresh the credentials for this account."
2) As others have said, I created a new Web App. I'm not sure this was the problem, however - I had previously created a couple other web apps and these resources were still present in my dashboard.
I have to agree with the above comments, too - the error messages provided for this are really, really poor.
Check that there are no characters that it will not accept. For instance an underscore '_'
Azure built a dummy name for me to use including an underscore which it does not accept. It was trial and error for me to find this where a simple warning would have saved lots of time.
Login to Azure Portal and create necessary resources. VS screens do not seem to work properly.
I created Api App on azure portal and my problem solved.
Same problem, however I have 3 Azure subscriptions, but even after making sure all of'em has at least one App Service it still hangs on this step. No other option than to not check the option to host.
Updating Azure SDK on VS2015 fix the problem in my case
So, at work, we are trying to use NCover Desktop for code coverage on a cloud based azure web application.
We are using Azure SDK V1.8 and Visual Studio 2010.
I researched online for answer and found some article a little bit helpful in setting up environment and stuff. Following is the procedure I'm following for this.
Create new NCover project and select auto config
Reset IIS and detect w3wp.exe process
Start application and select/deselect executable.
Problem is, I think VS is running on localhost rather than IIS, that's why even after restarting IIS, I'm not able to detect w3wp.exe process to attach.
how can I fix this issue?
Any help is appreciated.
EDIT:
So, After pointing our site towards IIS - Following is the error messasge I am getting.
I also tried to change port so there is not conflicts.
All the sudden started getting the following error while trying to debug a worker role:
"Windows Azure Tools for Microsoft Visual Studio
There was an error attaching the debugger to the role instance 'deployment16(360)blah blah' with Process Id: '8780'. Unable to attach. The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
Restarting Visual Studio and the machine do not help.
As you start getting this problem all of sudden in your development machine something must have changed and it is mostly due to some of the OS auto-update and/or some application update you installed in your machine. There could be any random reason for this problem however if I would have hit the exact same problem here is what I would do to troubleshoot such issue:
To start, first thing is to just check it is not an application specific problem by creating a base app from web/worker template and see if that exhibit the problem.
If you have installed new release Windows Azure SDK 1.7 check with both SDK 1.6 and 1.7 to verify if both exhibit the problem.
Check if your could debug IIS based application as well outside Compute Emulator. This will isolate if the problem is specific to Windows Azure development Fabric or bind to your IIS itself.
If this is IIS specific issue, Check IIS configuration for all enabled functionalities, try resetting Application Pool configuration, running "ASPnet_regiis -i" etc to fix the issue.
If it is Windows Azure Computer Emulator specific, I know sometime OS updates may make application unstable so in that case, I will re-install .net 4.0 and VS2010 SP1 again respectively. (This does help so many time) then re-install Azure SDK 1.7 completely.
Such random problem mostly occur due to some change in your machine configuration, so restoring the VS2010 and the re-installing all other application does help to solve problems.
If you have an exception in the role's OnStart() or in Application_Start() that the debugger doesn't pick up, you may also receive this message. Application_Start() errors are especially pernicious because the debugger doesn't attach to the web process until after this method returns.
If you are wedded to cloud specific classes such as RoleEnvironment and cannot make the web role a startup project, you can use Ctrl-F5 to run the cloud project without debugging. With some luck you'll get a yellow screen of death to show you the true error.
Avkash covers the points.
I had the same issue recently. I set my web project as start-up rather than Azure and I discovered that that web project didn't actually run. Turned out somehow when of my projects was compiling for X64. I changed that and it worked.