Skip to main content

​
Common deployment issues

Across enterprise rollouts, a handful of issues come up again and again. Getting ahead of these prevents most failed deployments.

​
App blocker prevents installation

If your organization uses an application blocker (such as AppLocker), it can stop the Jamie MSI from installing or updating. This is one of the most common blockers we see. To resolve it, your admins should:
  • Allow MSI files to be executed under your app blocker policy.
  • Whitelist either of the following:
    • the temporary Windows folder where MSIs are downloaded for execution, or
    • MSI installers signed by wespond UG (Jamie’s publisher).

​
Proxies must be configured system-wide

If you route traffic through a proxy, make sure it’s configured system-wide on Windows, not just at the user level. A user-level-only proxy is a frequent misconfiguration that stops Jamie from connecting at all.

​
Firewall ports

If Jamie installs but then fails to work, a firewall is the usual cause. Make sure the ports Jamie needs are open.

Firewall ports (PDF)

Reference sheet of the ports Jamie needs open.

​
Sending an installation log to support

If you hit an issue during deployment, generate an installation log and include it when you contact support — it gives the team something concrete to debug. Run the installer with logging enabled: 
msiexec /i Jamie_5.7.3_x64_en-US.msi /l*v install.log
Adjust the version in the filename (5.7.3) to match the MSI you actually downloaded.
This produces an install.log file in the current folder. Send it to support@meetjamie.ai.

​
Resources

Help Center

Step-by-step guides and answers to common questions.

Developer documentation

Build on top of Jamie with the API, webhooks, and MCP.

​
Support

​
Your Account Managers

You can always reach out to your Account Manager, who will help you with any questions: