Skip to content

Tosca Extractor Setup — Customer Guide

Configure analytiQa to automatically extract test automation data from your Tricentis Tosca workspace.

Unlike Jira and qTest, the Tosca extractor runs on a Windows machine in your own network, because it opens your Tosca workspace through the Tosca Commander API. It has two parts, installed together on the same machine:

Component What it does
Tosca extractor (data-streamer-tosca.exe) Reads test cases, execution lists and execution logs from your workspace and writes them as JSON files to a local export folder. Runs as a Windows service on a schedule, and you can also run it by hand
Fluentd (log shipper) Watches the export folder and sends new files securely over HTTPS to your analytiQa environment. Its installer is included in the extractor package

Your Qualtiva technical contact will usually go through this setup with you in a session. This page lists every step so you can prepare, or follow along. An install script sets up the service and Fluentd in one go (Step 5).


Prerequisites

  • A Windows machine with Tosca Commander installed. Note which Tosca release it runs (2026.x or 2025.x): you download the extractor that matches it (see Step 1)
  • The .NET Desktop Runtime the extractor needs: .NET 10 for the Tosca 2026.x extractor, .NET 8 for the Tosca 2025.x extractor. Run dotnet --list-runtimes and look for Microsoft.WindowsDesktop.App 10.x (or 8.x). If it's missing, install it from Microsoft's .NET download page
  • Your Tosca workspace (.tws file) on that machine. To log in with a Client ID + Secret or a Personal Access Token, the workspace must be created with the Tosca Server connection type
  • The workspace must be closed in Tosca Commander whenever the extractor runs. The extractor needs exclusive access to it.
  • Tosca credentials with read access to the workspace. Which ones depends on the workspace's connection type (see Step 2):
    • Tosca Server connection type: a Client ID + Client Secret (recommended) or a Personal Access Token
    • Direct repository connection: a Tosca username and password
  • The Windows account the extractor service runs as. By default it's the built-in NetworkService account: there's no password to manage and nothing to set up. That works with Tosca Server login (Client ID + Secret or token). With a direct repository login, opening the workspace can depend on a user's Tosca settings or licence, or on Windows authentication to the repository database. In that case use a dedicated local or domain account that can open the workspace in Tosca Commander instead: you need its password during the install, and the install script gives it the Log on as a service right. Either account needs read and write access to the workspace folder
  • Administrator rights on the machine, to run the install script
  • Outbound HTTPS from the machine to your analytiQa instance (https://<your-instance>.analytiqa.cloud)
  • Your analytiQa send-data URL, username and password. Ask your technical contact for a view link. They're the same credentials used for Publishing Test Results Directly.

Your Tosca credentials stay on your machine

Tosca isn't part of the secure credential intake link. Your Tosca login is entered directly into the extractor's appsettings.json on your own machine, during the setup session, and never needs to be sent to us. Don't email Tosca passwords, client secrets or tokens.


Step 1: Download and Unzip the Extractor

  1. Open the setup checklist for your analytiQa environment, https://<your-instance>.analytiqa.cloud/credentials/checklist. In the Tosca section, click the download that matches the Tosca release on the machine:

    Your Tosca release Download Extractor version Needs
    Tosca 2026.x Download the Tosca extractor for Tosca 2026.x (data-streamer-tosca-26-latest.zip) 26.x .NET 10 Desktop Runtime
    Tosca 2025.x Download the Tosca extractor for Tosca 2025.x (data-streamer-tosca-latest.zip) 25.x .NET 8 Desktop Runtime

    Each link always points at the newest release for that Tosca version, so it also works for later installs. If you don't know your instance address, ask your Qualtiva technical contact or email support@qualtiva.solutions.

  2. Unblock the downloaded zip, so Windows lets you run the scripts inside it: right-click it, choose Properties, tick Unblock and click OK (or run Unblock-File .\data-streamer-tosca-26-latest.zip in PowerShell).

  3. Unzip the package to a folder on the Tosca machine, for example C:\analytiqa\data-streamer-tosca.

The extractor must match your Tosca release

The first number of the extractor version is the Tosca release it works with: 26.x for Tosca 2026.x, 25.x for Tosca 2025.x. Tosca changes its programming interface between releases, so an extractor for the wrong release stops at startup with Unable to instantiate the TCAPI. This can look like a login problem, but it isn't one. When you upgrade Tosca, also install the matching extractor (see Upgrading Tosca).

The package contains data-streamer-tosca.exe, a README.md, one example settings file per login mode, a Scripts folder with the install scripts and the Fluentd configuration template, and a Tools folder with the Fluentd installer and its HTTP plugin. There's nothing else to download.


Step 2: Choose Your Login Mode

The extractor supports three ways of logging in to Tosca. Each has its own example file in the package. Copy the one that matches your setup to appsettings.json in the same folder as data-streamer-tosca.exe, then fill in the login values:

Start from appsettings-example.tosca-server-client.json.

"tosca_server_login": true,
"use_pat": false,
"tosca_cr_username": "<Tosca Server Client ID>",
"tosca_cr_password": "<Tosca Server Client Secret>",
  • tosca_cr_username is the Client ID, not a user's email address.
  • tosca_cr_password is the matching Client Secret.
  • Requires a workspace created with the Tosca Server connection type.

Start from appsettings-example.tosca-server-pat.json.

"tosca_server_login": true,
"use_pat": true,
"tosca_cr_username": "",
"tosca_cr_password": "<Personal Access Token>",
  • Put the full base64 Personal Access Token exported from Tosca Server in tosca_cr_password. Paste the whole string, unchanged.
  • tosca_cr_username is not used and can stay empty.
  • Requires a workspace created with the Tosca Server connection type.

Start from appsettings-example.direct-db.json.

"tosca_server_login": false,
"use_pat": false,
"tosca_cr_username": "<Tosca workspace username>",
"tosca_cr_password": "<Tosca workspace user password>",
  • The classic login for a workspace with a direct repository (database) connection, with no Tosca Server.
  • Use the same Tosca username and password you'd use to open the workspace in Tosca Commander.

Which mode should I use?

If your workspace is connected to Tosca Server, use a Client ID and Secret. If you're not sure how your workspace logs in, or where to create the Client ID/Secret or token in Tosca Server, ask your Tosca Server administrator.

The setting is use_pat, not use_pac

Older guides spelled this setting use_pac. The extractor ignores that spelling, so a token login configured with use_pac silently falls back to Client ID + Secret login and fails. If you're updating an older appsettings.json, rename it to use_pat.


Step 3: Complete appsettings.json

Set the rest of the values in appsettings.json. The example files already contain sensible defaults, so most installs only change the first few rows:

Setting What to set
workspace Full path to your .tws workspace file, e.g. C:\Tosca_Projects\Tosca_Workspaces\MyProject\MyProject.tws
dataOutPath Export folder. Default D:\analytiqa\export-assets\. Created automatically if it doesn't exist. If the machine has no D: drive, change it here; the install script (Step 5) points Fluentd at the same folder.
Product, Country, CustomerCode Tags stamped on every exported record. Your technical contact gives you the values to use.
startFromNodes Which part of the repository to search. / means the whole project; or give a semicolon-separated list of node paths.
objectSearchLastNHours How far back each run looks for modified objects (the examples use 72). See Historical Data below.
CleanUpOldFilesDays Export files older than this many days are deleted from the export folder on each run (the examples use 100). Set 0 or remove it to keep files forever.
runAssetExtract true (default) extracts your test assets. false runs only the diagnostic reports, without extracting assets. Leave it true unless support asks otherwise.
EnableAutoUpdate, AutoUpdateSas, AutoUpdateManifestFileName Automatic updates. Leave as shipped; see Keeping the Extractor Up to Date.
Service When the service runs exports. See Step 6.

Leave baseSearchString and objectSearchPtrnMatchType as shipped unless Qualtiva support asks you to change them.

Upgrading from a release before 25.0.1.23

CleanUpOldFilesDays used to be applied as hours. It now really means days, so an existing install keeps export files much longer than before. Check the value still makes sense for your disk space.

Historical Data

Set how far back to look:

  • Last N hours (default): objectSearchLastNHours (e.g. 24 or 72) in the extractor's configuration. Each run picks up only objects modified in that window, so extraction is incremental. A run that finds nothing new is normal, for example overnight or at weekends.
  • Custom absolute window: set both objectSearchStartDate and objectSearchEndDate (e.g. "2025-01-01" / "2025-01-31", inclusive of both end dates) to bound extraction to a specific historical range instead — both must be set together. These take precedence over objectSearchLastNHours when set. Since Tosca isn't part of the self-service portal, ask your analytiQa contact to configure this during onboarding.

Step 4: Run It Manually

Run the extractor once by hand before installing the service, to check your settings and login:

  1. Make sure the workspace is closed in Tosca Commander.
  2. Open a command prompt (or PowerShell) in the extractor folder and run data-streamer-tosca.exe.
  3. Check the console output:
    • The startup line Version: <version> shows which release is installed.
    • When the run finishes, the export folder (dataOutPath) contains export-*.json files and the application log, applog-tosca-data-streamer*.json.

Started from a command window like this, the extractor always does one export run and exits, also after the service is installed. You can use it any time for an extra run. If the service is running an export at that moment, the manual run is skipped (exit code 3) rather than competing for the workspace. data-streamer-tosca.exe --help lists the other options.

If the export folder can't be created (for example the path points at a drive that doesn't exist), the extractor prints Cannot create export folder ... and exits straight away. Fix dataOutPath and run it again.

If there's no appsettings.json at all, the first run writes a default one and exits. Replace it with the example file for your login mode (Step 2).

The service account

A manual run uses your Windows account. The service runs as NetworkService unless you give it a dedicated account in Step 5. NetworkService has no user profile, so a run under the service can't use anything from yours: Tosca settings, a licence, or environment variables. With Tosca Server login that's fine. If the workspace needs any of these, use a dedicated account: sign in to Windows once as that account, open Tosca Commander, complete any first-start, licence or Tosca Server sign-in prompts, then close it. A manual run as that account (runas /user:<account> cmd, then data-streamer-tosca.exe) shows that the service will be able to do the same.


Step 5: Install the Service and the Log Shipper

From an elevated PowerShell prompt (right-click PowerShell, Run as administrator) in the extractor folder:

cd C:\analytiqa\data-streamer-tosca
.\Scripts\Install-Analytiqa.ps1 -EndpointUrl https://<your-instance>.analytiqa.cloud/in-http -Username <your send-data username>

The script asks for:

  1. Your send-data password. It's stored as the machine environment variable LOGSTASH_HTTP_PASSWORD, not in a file.
  2. Whether to disable an existing Task Scheduler task that runs the extractor (see Upgrading from the scheduled task).

The extractor service runs as NetworkService, so there's no account or password to enter. To run it as a dedicated account instead (see Prerequisites), add -Credential (Get-Credential): the script then asks for that account's user name (DOMAIN\user, or .\user for a local account) and password. If appsettings.json uses a direct repository login, the script warns that NetworkService may not be able to open the workspace.

It then does everything from the package, without downloading anything:

Part What the script does
Fluentd Installs the bundled fluent-package 6 (C:\opt\fluent, Windows service fluentdwinsvc) if it's missing or older, and its HTTP output plugin. Writes C:\opt\fluent\etc\fluent\fluentd.conf with your send-data URL and username, reading the export folder from dataOutPath, with a disk buffer next to it (D:\analytiqa\fluentd-buffer by default). Checks the configuration, sets Fluentd to restart itself after a failure, and restarts it
Extractor service Creates the Windows service analytiQa Tosca Extractor (analytiqa-tosca-extractor): runs as NetworkService (or your dedicated account), starts automatically (delayed start) and restarts itself after a failure. Gives the account write access to the extractor and export folders, and a dedicated account the Log on as a service right
Check Shows the service status, the schedule and the Fluentd checks, each marked PASS, WARN or FAIL

The service runs its first export about a minute after it starts. To wait for it and see the result:

.\Scripts\Test-AnalytiqaInstall.ps1 -WaitForRunMinutes 30

Useful options for Install-Analytiqa.ps1:

Option Use it to
-Credential (Get-Credential) Run the extractor service as a dedicated Windows account instead of NetworkService
-LicenseUsageFolder <folder> Also send your Tosca license usage CSV exports from that folder
-AddDefenderExclusions Exclude the export and buffer folders from Microsoft Defender scanning (recommended by Fluentd). With other antivirus products, add the exclusions there
-DisableScheduledTask / -KeepScheduledTask Decide about an old scheduled task without being asked
-NoStart Install the service without starting it
-WhatIf Show what would be done, without changing anything

The script is safe to run again, for example after unzipping a new release. An already configured fluentd.conf and password are kept unless you pass new values. The parts can also be run on their own: Scripts\Install-Fluentd.ps1, Scripts\Install-ToscaExtractorService.ps1, and Scripts\Uninstall-ToscaExtractorService.ps1 to remove the service.

Where to look

The service logs to Event Viewer > Windows Logs > Application (source analytiqa-tosca-extractor): one entry when each export starts and one when it finishes or fails, with the error. The full detail is in the application log, applog-tosca-data-streamer*.json, in the export folder.

Re-sending files from the start

Fluentd remembers how far it has read each file. After changing paths or tags in fluentd.conf, or if your technical contact asks you to re-send data, reset it with the script in the package:

.\Scripts\fluentd-reset.ps1 -ExportFolder 'D:\analytiqa\export-assets'
Start-Service fluentdwinsvc

The script stops the service and clears its position files, so every file in the export folder is sent again from the start. Use your own dataOutPath for -ExportFolder if you changed it.

Manual setup (without the install script)

Install Fluentd and schedule the extractor by hand

Use this only if you can't run the install scripts. Run the steps from an elevated PowerShell prompt. Everything comes from the package's Tools folder, so no internet access is needed.

  1. Install fluent-package 6 LTS. Run Tools\fluent-package-6.0.5-x64.msi from the package. It installs to C:\opt\fluent and creates the fluentdwinsvc service. From fluent-package 5, uninstall version 5 first.
  2. Install the HTTP output plugin, again after every fluent-package install or upgrade:

    C:\opt\fluent\bin\fluent-gem install --local .\Tools\fluent-plugin-out-http-1.3.4.gem
    
  3. Copy Scripts\fluentd.conf.template to C:\opt\fluent\etc\fluent\fluentd.conf and fill in endpoint_url https://<CUSTOMER_HOSTNAME>/in-http (your send-data URL), username <SEND_DATA_USER>, <PATH_TO_LICENSE_USAGE_EXPORT_FOLDER> (or delete those license usage <source> blocks), and the D:/analytiqa/... folders if you changed dataOutPath (forward slashes). Don't save it with Set-Content -Encoding UTF8: the byte-order mark breaks Fluentd (unmatched end tag).

  4. Set the password: [Environment]::SetEnvironmentVariable('LOGSTASH_HTTP_PASSWORD', '<your send-data password>', 'Machine')
  5. Check with C:\opt\fluent\bin\fluentd --dry-run -c C:\opt\fluent\etc\fluent\fluentd.conf (it should end with finished dry run mode), then Restart-Service fluentdwinsvc. Also set it to restart itself after a failure: sc.exe failure fluentdwinsvc reset= 172800 actions= restart/60000/restart/60000/restart/300000.
  6. Schedule the extractor in Task Scheduler: import Scripts\SchedTask-Tosca Data Streamer.xml, then set its program to data-streamer-tosca.exe in your extractor folder (also as the working folder), the run-as account (Run whether user is logged on or not) and the trigger.

Step 6: Choose Your Schedule

Tosca extraction runs against your workspace directly, so timing is agreed with your analytiQa contact during onboarding. By default the service runs an export when it starts (a minute after Windows starts, for example) and then every 12 hours. To change that, edit the Service section of appsettings.json (the example files contain it with the defaults):

"Service": {
  "RunOnStart": true,
  "StartDelaySeconds": 60,
  "IntervalMinutes": 720,
  "DailyRunTimes": [],
  "DaysOfWeek": [],
  "MaxRunMinutes": 240,
  "StopGraceSeconds": 90
}
Setting What it does
RunOnStart true: run when the service starts, after StartDelaySeconds
IntervalMinutes Minutes between runs, from the start of one to the start of the next. 0 turns the interval off
DailyRunTimes Times of day to run, 24-hour "HH:mm", e.g. ["06:00", "21:00"], for example after your nightly test runs. Can be combined with an interval: whichever is due first runs
DaysOfWeek Only run on these days, e.g. ["Mon", "Tue", "Wed", "Thu", "Fri"]. Empty means every day
MaxRunMinutes A run still going after this many minutes is stopped and reported as an error. 0 means no limit
StopGraceSeconds When the service is stopped during a run, how long the run gets to finish its current step and close the workspace

For example, weekdays at 09:00 and 21:00 only: "IntervalMinutes": 0, "DailyRunTimes": ["09:00", "21:00"], "DaysOfWeek": ["Mon", "Tue", "Wed", "Thu", "Fri"].

The service picks up a changed schedule within a minute, without a restart. Run data-streamer-tosca.exe --schedule to check a schedule: it lists the next run times. Runs never overlap: if a run is still going when the next one is due, that one is skipped.

Keep the schedule in line with objectSearchLastNHours: each run should look back at least as far as the time since the previous run.

Tip

If you run Tosca automation from a CI/CD pipeline, you can also push execution results straight to analytiQa as each run completes — see Publishing Test Results Directly.


Keeping the Extractor Up to Date

Automatic updates are on by default. Before each run, the service checks for a newer release. If there is one, it downloads it, finishes the run on the current version, then restarts itself on the new version about a minute later (Event Viewer shows event 1200 from analytiqa-tosca-extractor). A manual run does the same check and switches to the new version after it finishes. Your appsettings.json is never overwritten. If the check fails (for example, no internet access), it's logged and the run continues on the current version.

Setting Purpose
EnableAutoUpdate true (default). Set false to keep this machine on its installed version.
AutoUpdateSas The read-only access key for the update check. It's already filled in in the example files; leave it as shipped. If it's empty, no update check happens.
AutoUpdateManifestFileName Advanced. Leave it out or as shipped unless Qualtiva support gives you a different release channel. By default each extractor checks the channel for its own Tosca release (for example data-streamer-tosca-26-latest.json for 26.x).

Automatic updates only replace the extractor itself. They don't change your Fluentd installation or your C:\opt\fluent\etc\fluent\fluentd.conf. Running Scripts\Install-Analytiqa.ps1 again after an update installs a newer bundled Fluentd, if the package has one.

Automatic updates also stay within the same Tosca release. A 25.x extractor never updates itself to 26.x, because 26.x wouldn't work against Tosca 2025.x.

Upgrading Tosca

When you upgrade Tosca to a new release (for example from 2025.x to 2026.x), install the matching extractor by hand:

  1. Upgrade Tosca, then make sure the .NET Desktop Runtime for the new extractor is installed.
  2. Stop the service (Stop-Service analytiqa-tosca-extractor) if it's installed, and back up the extractor folder, or at least your appsettings.json.
  3. Download the extractor for your new Tosca release (Step 1) and unzip it over the existing folder. The package doesn't contain appsettings.json, so your settings are kept.
  4. Run it manually once and check that the Version: line shows the new release number.
  5. Run .\Scripts\Install-Analytiqa.ps1 again (elevated). It keeps your Fluentd configuration and password, updates the service and starts it.

Your login settings don't need any changes.

Upgrading from the scheduled task

If the extractor already runs from Task Scheduler:

  1. Unzip the new Tosca 2026.x package over your extractor folder (your settings are kept), and run it manually once.
  2. Run .\Scripts\Install-Analytiqa.ps1 from an elevated PowerShell prompt. Your existing fluentd.conf and password are kept, so you don't need -EndpointUrl or -Username. Let it disable the scheduled task. The service runs as NetworkService. If the workspace only opens as the account your scheduled task used (for example a direct repository login), add -Credential (Get-Credential) and give it that account.
  3. Set the Service schedule to match your old task's timing (Step 6).

To go back to the scheduled task, run .\Scripts\Uninstall-ToscaExtractorService.ps1 -EnableScheduledTask. It removes the service and re-enables the task; your files, settings and Fluentd stay as they are.


Step 7: Review Your Configuration

Before confirming, check:

  • ✓ The extractor matches your Tosca release (26.x for Tosca 2026.x, 25.x for Tosca 2025.x), and its .NET Desktop Runtime is installed
  • ✓ appsettings.json was created from the example file for your login mode
  • ✓ For Tosca Server login, tosca_cr_username is the Client ID (not an email address), or use_pat is true with the full token in tosca_cr_password
  • ✓ The workspace path is correct, and the workspace is closed when the extractor runs
  • ✓ A manual run (data-streamer-tosca.exe) completes and writes export-*.json files
  • ✓ Scripts\Test-AnalytiqaInstall.ps1 shows no FAIL: the service is running (as NetworkService, or your dedicated account), Fluentd reads the same folder as dataOutPath, and its dry run passes
  • ✓ The old scheduled task, if any, is disabled
  • ✓ The Service schedule and objectSearchLastNHours cover each other

What Happens Next

  1. First run (5–60 minutes depending on size): about a minute after the service starts, the extractor exports objects in its search window to the export folder
  2. Delivery: Fluentd picks up new files, usually within a minute, and sends them to your analytiQa environment
  3. Ongoing runs: on the service's schedule, new and modified objects are exported and sent. The service starts again by itself after a Windows restart
  4. Dashboard ready: Log in to analytiQa dashboard → Tosca tab

What Gets Extracted

From your Tosca workspace, analytiQa captures:

  • Test Cases: Name, folder location and properties
  • Execution Lists and Execution Entries
  • Execution Logs and Test Case Logs: Pass/fail results, execution date and duration
  • Metadata: Creation and modification dates, project and workspace details
  • Diagnostics: Workspace health-check results, per-type item counts, and information about the extractor machine
  • License usage (optional): Tosca license usage CSV exports, if you point Fluentd at them

Example Dashboards

Once data is ingested, see Common Queries & Reports for pre-built examples:

  • Total test cases and test steps breakdown
  • Execution success rate over time
  • Test cases by priority and type
  • Automation coverage trends

Network & Access FAQ

Q: Does analytiQa need access to my network or workspace?
A: No. The extractor runs on your machine and only makes outbound HTTPS connections: Fluentd sends data to your analytiQa instance, and the update check downloads new releases. The install itself downloads nothing: Fluentd and its plugin come from the package.

Q: Can I use Tosca Server instead of a direct repository login?
A: Yes, and it's the recommended option for workspaces created with the Tosca Server connection type. Use a Client ID and Secret, or a Personal Access Token. See Step 2.

Q: What if my workspace is too large and extraction takes too long?
A: Tell analytiQa to extract a subset — specify a date range, or specific folders with startFromNodes, to reduce volume.


Troubleshooting

Issue Solution
"Unable to instantiate the TCAPI" (often with TypeLoadException), usually right after a Tosca upgrade The extractor doesn't match the installed Tosca release. It stops before logging in, so your credentials aren't the problem. Install the extractor for your Tosca release (Upgrading Tosca).
The extractor doesn't start, or asks for .NET The .NET Desktop Runtime is missing: .NET 10 for the 26.x extractor, .NET 8 for 25.x. See Prerequisites.
"Cannot create export folder" dataOutPath points at a drive or folder that doesn't exist on this machine (for example no D: drive). Change dataOutPath, and the matching paths in fluentd.conf.
"Error opening workspace ... Workspace is required to be closed" Close the workspace in Tosca Commander, on this and any other machine. The same message also appears when the login fails, so check the error logged straight after it and your login settings (Step 2).
Tosca Server login fails Check tosca_cr_username is the Client ID, not an email address. For a token, check the setting is use_pat (not use_pac) and the full token is pasted.
"Empty results" Normal when nothing changed in the search window. Otherwise check objectSearchLastNHours (or your date range) covers real activity, and startFromNodes points at a non-empty part of the repository.
Files exported but no data in dashboards Run Scripts\Test-AnalytiqaInstall.ps1: it checks that fluentdwinsvc is running, the HTTP plugin is installed, fluentd.conf reads your export folder, the LOGSTASH_HTTP_PASSWORD variable is set and the dry run passes. Running Scripts\Install-Fluentd.ps1 again fixes most of these. If C:\opt\fluent\fluentd.log shows 401 Unauthorized right after the password was set, restart Windows: some Windows versions only pass a new machine environment variable to services after a restart.
"Install-Analytiqa.ps1 cannot be loaded" / "not digitally signed" Windows blocks scripts from a downloaded zip. Unblock the zip before unzipping (Step 1), or run Get-ChildItem -Recurse \| Unblock-File in the extractor folder. Alternatively start it with powershell -ExecutionPolicy Bypass -File .\Scripts\Install-Analytiqa.ps1 ....
The service doesn't start: error 1069 (logon failure) Only with a dedicated account: its password is wrong or has changed, or the account lost Log on as a service (a domain Group Policy can remove it; ask your Windows/AD team to include the account). Run Scripts\Install-ToscaExtractorService.ps1 -Credential (Get-Credential) again.
The service runs, but exports fail while manual runs work The service runs in the background as NetworkService (or your dedicated account), without your Windows profile. With NetworkService and a direct repository login, the workspace may need something from a user's profile or Windows authentication: re-install the service with a dedicated account, Scripts\Install-ToscaExtractorService.ps1 -Credential (Get-Credential). With a dedicated account, sign in once as that account and open Tosca Commander to finish any first-start, licence or sign-in prompts. Either way, make sure the account can write to the workspace folder and dataOutPath. Event Viewer > Windows Logs > Application (source analytiqa-tosca-extractor) shows each run's error.
"Export run skipped: another extractor run was already in progress" The old scheduled task is still enabled, or the extractor was started by hand during a scheduled run. Disable the task (Upgrading from the scheduled task).
"Export run was still going after Service:MaxRunMinutes" Large workspaces can take longer than 4 hours on the first run. Raise MaxRunMinutes in the Service section, or narrow startFromNodes or the search window.
"Extraction takes too long" Large workspaces take time (1–60 min). Narrow startFromNodes or the search window.

Where to look: Event Viewer > Windows Logs > Application, source analytiqa-tosca-extractor, for each run's result, and applog-tosca-data-streamer*.json in the export folder for the details. Scripts\Test-AnalytiqaInstall.ps1 checks the whole install without changing anything.

More help? See Support & Troubleshooting.


Next Steps