- Release notes
- Before you begin
- Managing access
- Getting started
- Integrations
- Working with process apps
- Working with dashboards and charts
- Working with process graphs
- Working with Discover process models and Import BPMN models
- Showing or hiding the menu
- Context information
- Export
- Filters
- Sending automation ideas to UiPath® Automation Hub
- Tags
- Due dates
- Compare
- Conformance checking
- Process simulation
- Root cause analysis
- Simulating automation potential
- Starting a Task Mining project from Process Mining
- Triggering an automation from a process app
- Viewing Process data
- Creating apps
- Loading data
- Transforming data
- Structure of transformations
- Tips for writing SQL
- Exporting and importing transformations
- Viewing the data run logs
- Merging event logs
- Configuring Tags
- Configuring Due dates
- Configuring fields for Automation potential
- Activity Configuration: Defining activity order
- Making the transformations available in dashboards
- Data models
- Adding and editing processes
- Customizing process apps
- Publishing process apps
- App templates
- Notifications
- Additional resources
Process Mining
Possible cause
There is an issue with CData Sync connecting to SQL Server.
Solution
-
Open SQL Server Configuration Manager.
-
Check the TCP Port number.
-
Check if TCP/IP is set to Enabled for the Port. The following illustrations shows an example.
You may encounter errors while loading data using CData Sync. For example, when some of the tables have loaded successfully, but for the remaining tables an error message occurs indicating that the database or disk is full.
Possible cause
When CData loads data from your source system to Azure Blob, CData Sync temporarily stores the .csv for the task on the local disk on the server where CData is installed. This error might show up when there is is an issue with the local disk.
The location where the temporary .csv file is stored is located on C:\ drive. There is no option in CData Sync to configure or modify the storage location.
Possible solution
-
Check if the disk where CData Sync is installed has enough free space.
-
If the disk is (almost) full, check if the folder C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\cdata contains temporary folders with data.
Note:The location might be different for older versions of CData Sync.
-
In case you see temporary folders, you can delete those manually to free up disk space. In you CData Sync connections, you can add the following to your connection under Miscellaneous > Other
schemacacheduration=-1.
Possible solution
In case the steps above do not provide a solution to the problem, you could create a symbolic link from the CData Sync temporary directory to another disk with sufficient free disk space.
-
Open a command prompt on the server where CData Sync is installed.
-
Create the symbolic link using the following command:
mklink /J "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\cdata" "D:\cdata_tmp"mklink /J "C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\cdata" "D:\cdata_tmp"Replace the drive letter, in this example D, with a drive that has sufficient disk space.
When executing a task or job in CData with the source system set to SQL Server, you might encounter a timeout when running a query that produces a large volume of data.
Possible solution
- In the Source connection, go to the Advanced tab and locate the Miscellaneous section. Change the value for Timeout.
- This value is specified in seconds, you can increase this to 1800 (30 minutes).
- In the Job settings, go to the Advanced tab to edit the Replicate Options. Update the value for Command timeout.
- This value is specified in seconds, you can increase this to 1800 (30 minutes).
Note: Although the setting is described as controlling the timeout for destination connections, it also enforces a timeout on the source connection.
- This value is specified in seconds, you can increase this to 1800 (30 minutes).
