Chapter 10
10. Troubleshooting
Read the message first. If a run started, inspect its History entry before trying again. A failed operation can leave completed CatDV changes.
10.1 Startup and installation
| Symptom | What to do |
|---|---|
| Startup names a folder, database, or temporary storage problem | Check your account's write permission for that location, then reopen |
| Another copy owns the database | Close the other copy. If it did not exit cleanly, sign out and back in |
| Windows installer requires WebView2 | Ask your administrator to install the Microsoft WebView2 Runtime for the machine, then retry |
| Installer shows an unexpected trust warning | Install only through Control Room. If the warning stays, email support@northshoreautomation.com |
| License is inactive, expired, or unknown | Open Control Room and check activation, expiration, and internet access |
10.2 Connection and staging
| Symptom | What to do |
|---|---|
| CatDV authentication failed | Correct the API address and credentials. Test, save, then stage again |
| CatDV user seat limit reached | Release an unused CatDV session or ask the administrator to check available seats |
| CatDV cannot be reached or times out | Check network access and the API address; ask the administrator to check the server |
| No search fields configured | Move at least one configured source card into Search By |
| Configured column is missing | Compare the file headers with active mappings. Import the correct headers or move unused cards to Unmapped |
| Target conflict | Remove the duplicate active instruction for that CatDV field |
| A file drop does nothing | Drop one CSV or TSV file onto the Run staging area |
| File is too large | Split it into files within 50 MB, each with the same header row |
| Run file is unavailable | Finish staging, resolve its error, or restage an expired or stale file. For License required or License expired, check the license in Control Room |
Testing a connection does not save it. Select Save settings after correcting the connection.
10.3 Results that need attention
| Symptom | What to do |
|---|---|
| No matching assets found | Check search values and field identifiers. Prefer an exact unique identifier |
| Several assets match | Narrow the search. Change duplicate handling only when those changes are intended |
| Search field has no value | Fill the source cell. Every configured search field needs a value |
| Existing metadata remains after an empty source cell | Blank write values are omitted. They do not clear CatDV fields |
| Path stays unchanged | Check Apply path rules, rule activation, pattern, and priority. Use Test rules |
| Failed row contains a created or updated asset | Inspect partial changes in CatDV before preparing another run |
| Session release is unconfirmed | Close Data Wrangler to retry release before starting another import |
| Progress stops updating | Use Reconnect when shown. Inspect History before starting any new job |
| Job is interrupted after reopening | Review the last recorded evidence and CatDV state, then prepare only the remaining work |
10.4 Ask for support
Email support@northshoreautomation.com with the Data Wrangler version, operating system, job ID, exact message, and the steps that caused it. Include the affected source header names and CatDV field identifiers when relevant.
Enable logging under Settings, then Logging, if North Shore Automation support asks for it. Review logs and example rows before sharing. Remove credentials, license codes, and private metadata.
Do not send the local database or complete data folder unless North Shore Automation support asks for it and gives you a secure way to send it.
Previous: Licensing and updates · Contents · Next: Reference