When should I use High-Density Robots?

Build
#1

In which situation do I have to switch to “High-Density Robots”?

As I know on a windows server there could be 2 persons connected on same time. For me it makes sens to start with “High-Density Robots” in the case more than 2 Robots are running on the same time?

(The bad thing about enabling the “Remote Desktop Session Host” feature is the additional costs for windows server)

#2

Hi,

Please refer the below link, it clearly explains about High-Density Robots.

https://forum.uipath.com/t/question-regarding-high-density-robots/73057

1 Like
#3

Hi Anil,

Is it possible to install RPA orchestrator from community edition for learning purpose or do we need licence for it.

if we can use orchestrator from community edition please let me know step wise process

1 Like
#4

Hi,

Yes you can use Orchestrator by going to the link : https://platform.uipath.com

and follow the process in this link: https://orchestrator.uipath.com/docs/managing-tenants

#5

If by learning you mean learning the Orchestrator installation process (infrastructure), I will need to request a trial of the Enterprise Edition (Left option after accessing the link bellow)

Cheers

#6

Yes Orchestrator installation process, This information helps. Thank you…
Let me try that

#7

I downloaded Enterprise edition trial version and tried to install UiPath Orchestrator. After following all steps when i load URL getting below error. Please let me know if any fix can be applied.

HTTP Error 500.21 - Internal Server Error

Handler “ExtensionlessUrlHandler-Integrated-4.0” has a bad module “ManagedPipelineHandler” in its module list

Most likely causes:

  • Managed handler is used; however, ASP.NET is not installed or is not installed completely.
  • There is a typographical error in the configuration for the handler module list.
  • During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.

Things you can try:

  • Install ASP.NET if you are using managed handler.
  • Ensure that the handler module’s name is specified correctly. Module names are case-sensitive and use the format modules=“StaticFileModule,DefaultDocumentModule,DirectoryListingModule”.
  • Ensure that any application initialization rewrite rules set SKIP_MANAGED_MODULE=0 when setting a URL that maps to a managed handler (such as .aspx, for example.)
  • As an alternative, ensure that application initialization rewrite rules map the request to an unmanaged handler (for example, to an .htm file, which is mapped to the StaticFileHandler.)

Detailed Error Information:

Module IIS Web Core
Notification ExecuteRequestHandler
Handler ExtensionlessUrlHandler-Integrated-4.0
Error Code 0x8007000d
Requested URL https://opt-pc-0025.opteamix.com:443/
Physical Path C:\Program Files (x86)\UiPath\Orchestrator
Logon Method Anonymous
Logon User Anonymous
#8

Have you ran through the prerequisites?

Cheers

#9

.net version doesn’t meet prerequisites. let me add .net features.

#10

All prerequisites have been taken care but still getting below error.

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

Detailed Error Information:

Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=“Deny”), or set explicitly by a location tag with overrideMode=“Deny” or the legacy allowOverride=“false”.
Config File \?\C:\Program Files (x86)\UiPath\Orchestrator\web.config
Requested URL https://optwebser-12.opteamix.com:443/
Physical Path C:\Program Files (x86)\UiPath\Orchestrator
Logon Method Not yet determined
Logon User Not yet determined

Config Source:

  602:     </staticContent>
  603:     <handlers>
  604:       <remove name="ExtensionlessUrlHandler-Integrated-4.0" />

More Information:

This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.

View more information »