Thomson Reuters software may run slowly because of workstation limitations, network design, server resource contention, antivirus scanning, incorrect data paths, permissions or remote-access conditions. The application itself is not always the source. First determine whether the issue affects one user, one application, every workstation or only busy periods.
This guide covers performance problems across desktop and server-based Thomson Reuters CS Professional Suite applications, including UltraTax CS, Practice CS, Accounting CS, FileCabinet CS and Fixed Assets CS.
- Slow Thomson Reuters software may result from workstation, network, server, storage, antivirus, data-path, or remote-access issues.
- First determine whether the slowdown affects one user, one application, remote employees, or the entire firm.
- Wireless connections, unsupported storage configurations, and antivirus scanning of active application files can affect CS Professional Suite performance.
- Meeting minimum system requirements may not provide sufficient capacity for multiple applications, concurrent users, and busy-season workloads.
- Managed hosting can address infrastructure and remote-access bottlenecks, but application settings, permissions, and data issues must still be corrected.
Quick Thomson Reuters Performance Diagnosis
| Performance symptom | Most likely area to investigate | First test |
|---|---|---|
| Only one user is affected | Workstation, local profile or background processes | Test another workstation using the same user account |
| All users are affected | Server, network, storage or shared configuration | Check server CPU, RAM, disk activity and network utilization |
| Only one CS application is slow | Application settings, data path or integration | Compare the affected application with other CS applications |
| Performance drops during busy hours | Resource contention or concurrent-user load | Compare performance during peak and non-peak periods |
| Only remote staff experience lag | Internet path, session host or remote-access design | Compare remote performance with office or local access |
| Slowness began after a server migration | Paths, permissions or workstation components | Verify mapped drives, data locations and application components |
| Practice CS shows high SQL utilization | Integration backlog or folder permissions | Check the ClientStatusEvent folder and user permissions |
| File opening is slow but calculations are normal | Storage, data path or file scanning | Review storage activity and antivirus exclusions |
The purpose of this table is to identify the affected layer before changing software, purchasing hardware or migrating the environment.
Start by Determining Where the Slowdown Occurs
Thomson Reuters recommends identifying the scope of the problem before applying fixes. Determine:
- Which process is slow: application startup, opening a client, moving between screens, calculations, printing or closing the application?
- Does the problem affect every workstation?
- Does it affect every user?
- Is the application still slow when it runs locally rather than over the network?
- Does it happen continuously or only when more employees are working?
These questions separate workstation-specific issues from application, network and server-wide problems.
Create a simple incident record containing the application, user, workstation, date, time, action performed and delay experienced. A pattern usually becomes visible after several documented occurrences.
1. The Computer Meets Minimum Requirements but Not the Real Workload
Thomson Reuters currently lists a 2 GHz 64-bit processor and 4 GB of RAM as minimum UltraTax CS hardware requirements, while recommending a multi-core processor and at least 8 GB of RAM. It also recommends a persistent, high-speed internet connection for installations, updates, licensing and return processing.
Minimum requirements establish basic supportability. They do not necessarily represent sufficient capacity for:
- Multiple CS applications running together
- Large or complex client files
- Several historical tax years
- Microsoft 365, PDF tools and document-management software
- Endpoint security and monitoring applications
- Multiple concurrent remote users
Check Task Manager or an appropriate monitoring platform while the slowdown is occurring. Historical averages may hide short CPU, memory or disk-utilization spikes that appear only during calculations, print jobs or busy-season workloads.
2. Network or Storage Design Is Delaying File Access
CS Professional Suite applications frequently interact with shared files and network locations. Slow or unstable access between the workstation, application server and data location can make the software appear unresponsive even when processor utilization is normal.
Thomson Reuters does not recommend wireless networks for CS Professional Suite applications. It also warns that unsupported NAS devices may not handle file locking correctly and may create performance or data-integrity issues.
Review:
- Whether affected workstations use wired or wireless connectivity
- The location of application and client-data folders
- Network-switch errors or saturated links
- Mapped-drive consistency
- Storage capacity and disk response during busy periods
- Whether application data is being accessed across a slow site-to-site connection
- Whether the storage platform is supported for the application
Do not evaluate network speed only with a public internet speed test. The relevant measurement is the complete route between the user session, application and data.
3. One Server Is Performing Too Many Roles
A server may simultaneously operate as a file server, application server, print server, remote desktop host, database server, backup target and security-monitoring endpoint.
Each role consumes processor time, memory, storage operations and network capacity. Thomson Reuters advises firms to consider the number of responsibilities assigned to a server and notes that additional server tasks can slow processing. Its network guidance also recommends considering a dedicated server rather than relying on a workstation or basic peer-to-peer configuration for heavier workloads.
Monitor the server during the exact period when users experience delays. Review:
- CPU utilization
- Available memory
- Disk queue or storage latency
- Network throughput
- Active user sessions
- Backup or security jobs
- Database utilization
- Print and PDF processes
A server that appears healthy overnight may still be undersized during peak concurrency.
4. Antivirus or Endpoint Security Is Scanning Application Files
Security software is essential, but an incorrect scanning configuration can repeatedly inspect active application and data files.
Thomson Reuters specifically states that antivirus scanning of the WinCSI directory may interfere with UltraTax CS performance. Its broader network guidance also recommends scheduling resource-intensive scans outside business hours and avoiding unnecessary workstation scanning of server drives.
Do not disable security tools permanently. Ask the firm’s IT or security administrator to:
- Review the current Thomson Reuters exclusion requirements.
- Confirm exclusions are narrow and application-specific.
- Check whether both the workstation and server are scanning the same network files.
- Review scan schedules and endpoint-security logs.
- Test changes under controlled conditions.
Security exclusions should be approved by a qualified administrator and documented within the firm’s security policies.
5. Offline Files or Client-Side Caching Is Enabled
Windows Offline Files, also called Client Side Caching, may create delays or synchronization conflicts when applications rely on active network data.
Thomson Reuters identifies Client Side Caching as a potential cause of slower CS Professional Suite performance. It also identifies opportunistic locking as a setting that may affect UltraTax CS performance in certain environments.
These settings should not be changed without technical review because they may affect other applications and file-sharing processes.
6. Application Paths or Permissions Are Incorrect
Performance problems may begin after a server replacement, data migration, drive remapping or software reinstallation.
Examples include:
- FileCabinet CS pointing to an incorrect data location
- Fixed Assets CS workstation components not being reinstalled after migration
- Different users using inconsistent mapped drives
- Missing read, write or modify permissions
- Integration files accumulating because the application cannot process or delete them
Thomson Reuters documents a Practice CS scenario in which missing permissions can allow Client Status integration files to accumulate, resulting in high SQL Server CPU utilization and slow performance.
When slowness begins immediately after an infrastructure change, verify paths and permissions before purchasing additional server capacity.
7. UltraTax CS Is Not Using the Local Performance Option
For network installations of UltraTax CS, Thomson Reuters provides an “Improve performance using local drive” option under:
Setup → User Preferences → Miscellaneous
The option must be enabled on each applicable workstation, followed by an application restart. Thomson Reuters recommends monitoring performance afterward to determine whether the change helps.
This is an UltraTax-specific configuration step. It should not be treated as a universal fix for Practice CS, Accounting CS or other applications.
For detailed UltraTax-only steps, link to the separate UltraTax CS running slow troubleshooting guide rather than duplicating that procedure throughout this article.
8. Temporary Files and Background Processes Are Consuming Resources
Temporary files, unnecessary startup processes, screen savers, synchronization utilities and other background applications can consume workstation or server resources.
Thomson Reuters includes background processes, temporary files and screen savers in its UltraTax performance troubleshooting recommendations.
A controlled test can help:
- Restart the affected workstation.
- Open only the required Thomson Reuters application.
- Repeat the slow action.
- Compare the result with normal operation.
- Review startup applications and background tasks with the IT administrator.
Avoid deleting application folders or client data as part of general cleanup.
A Safe Troubleshooting Sequence
Use this order to reduce unnecessary changes:
Step 1: Define the symptom
Record the application, user, workstation, time and exact slow action.
Step 2: Determine the scope
Establish whether the issue affects one user, one application, remote users or the entire firm.
Step 3: Compare local and network behavior
Where licensing and configuration permit, determine whether the same operation remains slow outside the shared network path.
Step 4: Measure the affected infrastructure
Check workstation and server CPU, memory, storage and network activity while the slowdown is happening.
Step 5: Review supported architecture
Confirm operating-system support, network configuration, data locations and storage compatibility.
Step 6: Review security scanning
Verify current Thomson Reuters antivirus exclusions and scan schedules without weakening the firm’s security controls.
Step 7: Check application settings, paths and permissions
Review UltraTax local-drive settings, FileCabinet locations, mapped drives, integration folders and user rights.
Step 8: Escalate with evidence
Provide Thomson Reuters support or the firm’s IT provider with timestamps, affected users, resource metrics, event logs and reproduction steps.
Will Moving Thomson Reuters Software to Cloud Hosting Make It Faster?
Thomson Reuters on Cloud can improve performance when the recurring bottleneck is caused by:
- Aging or undersized local servers
- Fixed processor or memory capacity
- Slow storage
- Several applications competing for the same resources
- Poorly designed remote access
- Multiple office locations accessing one local environment
- Limited internal IT capacity to monitor and maintain infrastructure
However, cloud hosting is not an automatic fix for every issue. It will not independently correct:
- Damaged application or data files
- Incorrect permissions
- Wrong data paths
- Unsupported software configurations
- Misconfigured endpoint security
- A vendor-side service interruption
- Poor internet connectivity at the user’s location
The correct decision should follow diagnosis. When the underlying issue is infrastructure capacity, remote-session architecture or server management, a properly sized managed environment can remove those specific constraints. If the problem is application configuration, that configuration must still be corrected.
When a Managed Thomson Reuters Environment Makes Sense
A firm should evaluate managed Thomson Reuters hosting when:
- Slowdowns affect several users repeatedly
- The server reaches resource limits during peak periods
- Remote employees depend on unstable VPN access
- The existing server is approaching replacement
- The firm needs UltraTax CS, Practice CS, Accounting CS, QuickBooks and Microsoft applications in one environment
- Internal staff spend excessive time maintaining servers, backups and remote access
- Recovery processes have not been tested against filing-season requirements
OneUp Networks hosts properly licensed Thomson Reuters applications in managed environments designed around the firm’s user count, application mix, workflow and busy-season concurrency. Software licensing remains separate: the client must own or obtain the appropriate licenses from the original software vendor.
The process should begin with a performance assessment—not an immediate migration. OneUp Networks can review application dependencies, users, server utilization, data locations and remote-access requirements before recommending an architecture.
Frequently Asked Questions
When only one employee is affected, investigate the workstation, user profile, background applications, network connection and local application settings before changing the server.
Yes. Thomson Reuters states that antivirus scanning of the WinCSI directory may interfere with UltraTax CS performance. Any exclusion should be configured by the firm’s IT or security administrator.
When several applications and users slow down at the same time, the likely areas to measure are server CPU, available memory, storage performance, network utilization and concurrent remote sessions.
No. Hosting Thomson Reuters can address infrastructure, capacity and remote-access bottlenecks, but it will not automatically repair incorrect paths, permissions, damaged files or unsupported configurations.
Compare the cost and operational impact of new hardware, server management, security, backups, disaster recovery, remote access and future scaling. Managed hosting is more relevant when the firm wants to transfer ongoing infrastructure responsibility rather than continue managing a local server.
Diagnose the Bottleneck Before the Next Filing Deadline
Slow Thomson Reuters UltraTax CS performance should be treated as an infrastructure and application-diagnosis problem, not immediately as a software failure. Determine who is affected, identify the slow process, measure the environment and review supported configuration requirements before selecting a solution.
When the findings point to server capacity, storage, remote-access design or recurring infrastructure management problems, OneUp Networks can assess your Thomson Reuters environment and recommend a managed hosting configuration based on your actual applications, users and workflow.
Related Blogs:
