What symptoms indicate Canix Suggests the Wrong Package Tag Prefix for a New York License?

- Canix suggests an incoming transfer tag instead of the next expected package tag. - The next package number does not match the facility’s received package-tag range. - Teams working across multiple licenses are unsure which tag range should be active.

What usually causes Canix Suggests the Wrong Package Tag Prefix for a New York License?

- Package tags were received in Metrc but the prefix was never updated in Canix facility management. - The wrong license or facility context is selected. - Staff are mixing plant-tag and package-tag workflows.

When should this issue be escalated to IT or security?

- Wrong tags were already printed or used on live inventory. - Multiple licenses share the same team and the tag assignment path is still unclear. - State traceability could be compromised by continuing package creation.

IT Support Portal

ServiceNow-style demo portal

Affiliate Disclosure

Some recommendations may include affiliate links. If you purchase through these links, the site may earn a commission at no additional cost to you. Recommendations are still selected for fit, safety, and support relevance.

Canix Suggests the Wrong Package Tag Prefix for a New York License

If you are seeing "the trust relationship between this workstation and the primary domain failed", use this IT support runbook to validate symptoms, isolate likely causes, apply safe resolution steps, and escalate correctly in Windows and macOS enterprise environments.

Estimated time

10-20 min

Overview

This troubleshooting guide is aligned to the exact query "the trust relationship between this workstation and the primary domain failed" and focuses on enterprise-safe remediation for Canix.

Severity: MediumAdmin RequiredEnv: BothCannabis Tech • Canix

Author & Verification

Tamem J

IT Solutions Engineer

Last reviewed: May 11, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

• Enterprise Microsoft 365 Administration
• Endpoint Management (Intune, Jamf, Kandji)
• Identity & Access (Entra ID, Okta)

Tested on Canix package tag prefix guidanceTested on Metrc package tag receipt workflows

Reviewed under Editorial Standards.

Trust Signals

No ratings yet

0 total helpfulness votes

• Enterprise Microsoft 365 Administration
• Endpoint Management (Intune, Jamf, Kandji)
• Identity & Access (Entra ID, Okta)

Reference This Page For

Best use cases

This page is designed to be the narrow, issue-specific reference when the support query, product, and environment closely match.

Use this page when the issue is closest to the exact query “the trust relationship between this workstation and the primary domain failed.”
Best for Cannabis Tech / Canix troubleshooting in managed Windows and macOS environments.
Prefer this ticket when you need enterprise-safe steps, escalation criteria, and commands tied to this specific issue.

Canonical URL

https://tamemj.com/support/tickets/canix-package-tag-prefix-is-wrong-for-new-york-license/

Editorial standards AI retrieval guide

Symptoms of the trust relationship between this workstation and the primary domain failed

Canix suggests an incoming transfer tag instead of the next expected package tag.
The next package number does not match the facility’s received package-tag range.
Teams working across multiple licenses are unsure which tag range should be active.

Likely Causes of the trust relationship between this workstation and the primary domain failed

Package tags were received in Metrc but the prefix was never updated in Canix facility management.
The wrong license or facility context is selected.
Staff are mixing plant-tag and package-tag workflows.

Interactive Decision Tree

ITIL-style triage path powered by state machine logic.

How to Fix: the trust relationship between this workstation and the primary domain failed

Accordion runbook sections

1
Confirm scope, user impact, and reproduction
Info
v
Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.
2
Validate prerequisites and application/session state
Info
v
Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.
3
Run safe diagnostics from the Commands section
Command
v
Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.
4
Apply safe remediation steps
Info
v
Confirm the facility has already received the correct package tags in Metrc before changing any Canix setting.
Update the package-tag prefix in Canix using the first digits from the correct package tag for that license.
Verify the active license or facility in Canix before creating new inventory.
Re-test with a single package creation workflow before releasing the process back to the broader team.
5
Escalate when access, policy, or security controls are involved
WarningAdmin required
v
Wrong tags were already printed or used on live inventory.
Multiple licenses share the same team and the tag assignment path is still unclear.
State traceability could be compromised by continuing package creation.

Commands

Copyable diagnostic or remediation commands (1 snippet).

Capture package tag context

CLI • Admin required

# Facility / license:
# Example tag Canix is suggesting:
# Example package tag actually received in Metrc:
# Admin > Facility Management screenshot:
# Whether any incorrect tags were already used on live packages:

When to Contact IT / Security

Wrong tags were already printed or used on live inventory.
Multiple licenses share the same team and the tag assignment path is still unclear.
State traceability could be compromised by continuing package creation.

Related Search Queries

Other common ways people describe this issue in search and ticket intake.

Was this helpful?

Your response is stored locally in this browser for demo analytics.

Continue With Related Resources

Move from the troubleshooting article into related downloads, broader fix libraries, and pillar guides without restarting your search.

Software Download

Audacity

Open-source, multi-track audio editor and recorder for cutting, mixing, and applying effects to audio files on any platform.

Media • Windows, macOS, Linux

Software Download

Notion

All-in-one workspace for notes, wikis, databases, and project management with a flexible block-based editor.

Productivity • Windows, macOS, iOS, Android, Web

IT Asset

Canix Audit Trail and Variance Review SOP

Runbook for reviewing Canix audit history, tracing package edits, and documenting same-day inventory variance investigations in New York cannabis operations.

Runbooks • DOCX

IT Asset

NY Cannabis Reconciliation and Variance Log

Editable daily log for package mismatches, variance investigations, same-day disposition, and compliance signoff across New York cannabis operations.

Templates • DOCX

Corporate Fix