No certificate appears on the list during the installation process
You need to install certificates on your computer.
To install a new certificate follow these steps:
On the Windows' Start menu, type Run and open the app. Alternatively you can press the Windows + R key.
Type inetmgr and then click OK.
On Connections, select your computer.
On the IIS window, look for the IIS section, and double-click Server Certificates.
On Actions, click Import to install a new certificate.
Select the .pfx file, type in the certificate's password, and select Personal.
Click OK.
The certificate should appear shortly on the setup wizard. If it doesn't, consider restarting the installer.
I don't need four databases and four connection strings
All database connection strings are required because, in addition to storing information about the platform, they also store information that facilitate IBM Robotic Process Automation Studio commands, such as Wait Lock (waitLock) for example.
This is what the databases do:
Automation
The main database that stores general information about the platform.
Knowledge base
The auxiliary database for commands and tools that use knowledge base algorithm version 1 in IBM Robotic Process Automation Studio such as Answer Question (answerQuestion)
and Machine Learning Model Builder.
Address
The auxiliary database for the Search Postal Code (zipCodeLookup) command that works similarly to the Zip Code query API but with some improvements.
Wordnet
The auxiliary database for querying synonyms used in commands and tools that use the knowledge base algorithm version 2.
I want to use another database management system
As stated in requirements, SQL Server is the only supported database management system. You can't use any other system.
I did not set up a port for Abbyy, but I want to use OCR
The server also has the Tesseract service embedded. If you don't want to use Abbyy, you can use Tesseract instead.
I have changed the value of the environment variable to another directory, but the files were not moved automatically
You can only change directories in the Web Client. For more information, see File storage.
One of the services is not responding
On the Windows Start menu, type Run and open the app. Alternatively you can press the Windows + R key.
Type inetmgr and then click OK.
On Connections, expand the applications, and select the service that is not responding.
On Actions, click Restart, located on the Manage Website section.
If the service still does not respond, click Stop and then Start.
The connection to the Web Client appears as not private
If you are using a self-signed certificate, the user's web browser is unable to recognize the certificate authority and displays this error message. To solve this issue, consider a few options:
Ask users to add the page to the browser exceptions.
Generate a Certificate Signing Request.
Replace current certificate with IBM RPA API certificate.
After installing the server, the IBM RPA API certificate should be installed by default. To replace the certificate with IBM RPA API, see General parameters.
Can I change the server schema?
Changing the server schema is not a supported action, and it is not recommended. IBM does not provide information on how to change the server schema, since this operation has several risks involved.
Where are the execution logs?
You can find them on the Web Client.
Log in to the Web Client.
Go to Scripts.
Select a script and click the vertical ellipsis ⋮ > Details.
Details contain the script log, and the following details:
Date and time when the script started executing.
Date and time when the script finished executing.
Script creation date.
Script version.
Computer where the execution occurred.
Execution status.
How do I know if Abbyy works?
You can try using IBM Robotic Process Automation Studio in the on-premises environment, and testing commands such as Click by OCR (ocrClick), Get Control Text by OCR (ocr) and Recognize Image Text or PDF (recognizeText) using Abbyy as the OCR provider.
How can I verify whether the email server is working properly?
To test the email server, try registering a new user or scheduling the execution of a script that will give an error message. These actions will send an email message.
The email server is configured correctly, however the emails are not being sent
Check the server's connection with the email server.
If you are still unable to send emails, contact IBM Support immediately.
I cannot see which ports are available to connect
To check the status of the connection ports, start the Windows Run application, and type NETSTAT -a. The list of all active ports with their respective status displays.
The list of port statuses:
Established
The port has an active connection.
Syn_sent
The connection to the port in question is constantly trying to be established.
Syn_sent
There is a connection request for the port in question.
Fin_wait1
The port is closed and the connection will be closed.
Fin_wait2
The connection is closed and the port is waiting for the remote connection to shut it down.
Time_wait
The port is waiting for packet processing to finish after being closed.
Close
The port is not being used.
Close_wait
The remote connection has been disconnected and the port is expected to be closed.
Last_ack
The remote connection has been disconnected and the port is closed. Completing operation.
Listen
The port is waiting for a connection request.
Closing
Both connection ports are closed, but data is still being sent.
Unknown
The connection status is unknown.
With this information, you can make decisions about which port to use on the on-premises services.
The Web Client does not start
Check whether IIS URL Rewrite 2.1 is installed. If not, install it, as it is a prerequisite for the platform to work properly.
This can also happen if the server cannot access the database. This only occurs if:
The user that created the database is not the same user defined in the connection string, or it does not have access to the database.
You are trying to connect to the database using Windows Authentication instead of SQL Server Authentication.
In that case, you will need to:
Create a new SQL Server user, with SQL Server Authentication and disabling User must change password at next log in.
Grant this user access to the databases.
Reinstall IBM Robotic Process Automation Server.
Enter the connection string with the new user in User Id and Password.
Scheduler does not work
This problem has several known causes:
MSMQ was not installed properly or is unavailable.
MSMQ ports are not enabled on the server.
The Client is unable to communicate with the server scheduler.
Enable MSMQ ports on the client-side as well, and grant access to the server's domain using MSMQ ports.
Example:203.0.113.25:1801
If you are still experiencing issues with the Scheduler and Message Queueing is installed but not available, try reinstalling Message Queueing. Follow these steps:
On the Windows Start menu, open Server Manager.
On the header bar, click Manage and select Remove Roles and Features.
A new window opens on the Before You Begin page, click Next to continue.
Select the Select a server from the pool option and select your server name and click Next to continue.
On Server Roles, click Next to continue.
On Features, clear the Message Queueing option and click Next.
Enable Restart the destination server automatically if required and click Remove.
The computer restarts automatically after removing the feature.
To reinstall the Message Queueing feature, follow these steps:
On the Windows Start menu, open Server Manager.
On the header bar, click Manage and select Add Roles and Features.
A new window opens on the Before You Begin page, click Next to continue.
On Installation Type, select Role-based or feature-based installation and click Next.
On Server Selection, select the Select a server from the server pool option and the server you want to use and click Next.
On Server Roles, click Next.
On Features, enable Message Queueing and click Next.
Enable Restart the destination server automatically if required and click Install to install the feature.
There was an error during the Windows features configuration process
The error occurs when the setup wizard tries to enable the MSMQ Windows Feature. Try to enable MSMQ in PowerShell:
Type PowerShell in the Windows search bar, and run PowerShell with administrator privileges.
You might see the following error over PowerShell:
To solve this issue, make sure your operating system is up to date and try to enable the Message Queueing feature using the "Turn Windows features on or off" window.
If you are still unable to install, consider reinstalling the operating system. If the problem persists, contact IBM Support immediately.
Incompatibility of IBM Robotic Process Automation certificates
The 20.12.0 release introduced a new IBM RPA CA certificate. If you are upgrading from a version prior to 20.12.x, you have to update your current certificate.
Fix server certificate
Stop the IBM Robotic Process Automation service on Windows Task Manager.
On the Windows Start menu, type Run and open the app. Alternatively you can press the Windows + R key.
Type inetmgr and then click OK.
Remove the Web Service, WDG Automation Broker and API certificates on IIS.
Restart the IBM Robotic Process Automation service on Windows Task Manager.
The certificates are recreated with the correct specifications.
Fix computer certificate
Navigate to the Computers page on the Web Client.
On the desired computer, click the vertical ellipsis ⋮ > Download certificate.
Run the certificate file to install the new certificate.
Note: In versions prior to 20.12, download the Legacy certificate.
I can't run scheduled executions
This issue occurs because the server is unable to find the computer in the network, either because the hostname has changed or it was incorrectly saved.
To solve this issue, follow these steps on the client computer:
Open Windows command prompt.
Type hostname. Save the returned hostname.
Log in to the Web Client.
Navigate to Computers and search for the computer's hostname.
If you are unable to find it, create a new computer with the obtained hostname and save it.
On the Computers page, click Actions > Download certificate on the computer with the fixed hostname.
Run the downloaded certificate file.
Try scheduling executions on the desired computer.
Contribute in GitHub:
Open doc issue
