Skip to content

Troubleshooting

Spencer Hawkins edited this page Jan 24, 2019 · 13 revisions

Troubleshooting 101

Can't get MTGATracker to work? Do these steps first to get some info, then come get our attention in Discord#troubleshooting

1. Check if mtgatracker_backend.exe is running. This is the process that reads the log file and sends info to the UI.

  • 1.1. Open Task Manager and MTGATracker
  • 1.2. Find the MTGATracker drop down
  • 1.3. Note if mtgatracker_backend.exe is present.

In this screenshot, mtgatracker_backend.exe is present:

In this screenshot, mtgatracker_backend.exe is missing:

2. Put MTGATracker into debug mode. Check for any error output.

  • 2.1. Press the settings icon
  • 2.2. Turn on "Debug Mode" in the General tab.
  • 2.3. Restart MTGATracker
  • 2.4. Note any error messages or other output in the console tab of the dev tools window. (Best if you take a screenshot!)

Example:

3. (Only if mtgatracker_backend.exe not present in step 1) Check for error output when launching mtgatracker_backend.exe manually

  • 3.1. Open cmd.exe
  • 3.2. Type the following, line by line: (NOTE: make sure to replace <VERSION> with the version number you installed, e.g. 5.1.0. It is probably easier to type this by hand, using tab auto-completion, rather than copy/pasting!)
cd %APPDATA%\..\Local\mtgatracker\app-<VERSION>\resources\appdist\mtgatracker_backend\
mtgatracker_backend.exe -p 5678
  • 3.3. Note if the program crashes, or runs continuously. Note any output. (Screenshots are best!)

Example:

Once you've collected this data, messages us in the troubleshooting channel (or check below for solutions to issues we've seen before).

Stuff that worked for others and might work for you(?)

After troubleshooting sessions, these are the solutions that eventually worked. YMMV, each of these cases was unique in their own way.

MTGATracker launches, but doesn't ever do anything

In this case, you should see NO changes in the tracker, at all, ever. You will not see decklists, you will not get draft helper, etc.

Case 1: MTGA is installed on a different disk than MTGATracker

In this case, MTGATracker is looking on the wrong disk for the MTGA output log file. Fix this by installing version 4.2.2 or later, and using the settings panel to locate the log path manually.

Case 2: Wbem was (accidentally) removed from system path

In this case, launching MTGATracker from the command line yielded this error:

...
(node:540) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Command failed: WMIC path win32_process get Name,Processid,ParentProcessId,Commandline
'WMIC' is not recognized as an internal or external command,
operable program or batch file.
...

The most important part was 'WMIC' is not recognized as an internal or external command. If you see this, this may be your issue. To fix, add the directory C:\Windows\System32\wbem back onto your path, per superuser.

Case 3: Unknown WMIC Exception

In this case, launching MTGATracker from the command line yielded this error:

...
Error: Command failed: WMIC path win32_process get Name,Processid,ParentProcessid,CommandLine
Unknown WMIC Exception.
...

Thanks windows for that super helpful error message! /s. This occurred for one user with multiple graphics cards. The solution ended up being forcing MTGATracker to run on the integrated graphics card, not the dedicated card.