This topic covers issues you may encounter using QuarkXPress within Q++Studio (scanning a template or generating a diary, for example) or simply using QuarkXPress manually (independently of Q++Studio).
Using QuarkXPress within Q++Studio
The suggested solutions are when you are no longer able to use QuarkXPress within Q++Studio to scan templates or generate diaries, for example.
This can happen:
A.After you have installed a new version of QuarkXPress.
B.After you have updated QuarkXPress on your workstation.
C.After you have repaired or re-installed QuarkXPress on your workstation.
D.When QuarkXPress preferences get corrupted (QuarkXPress stops working for no obvious reason).
Solution to Cases A and B
The solutions to try in cases A or B are the following:
1.Restart your workstation.
2.Follow the instructions at Installing or Upgrading QuarkXPress.
Solution to Cases C and D
The solutions to try in cases C or D are the following:
3.Restart your workstation.
4.Try to purge the QuarkXPress preferences.
5.Try to synchronize the internal version of QuarkXPress.
If the above fail, please contact technical support.
Using QuarkXPress manually (independently of Q++Studio)
As usual, the first thing to try, when experiencing QuarkXPress problems, is to purge the QuarkXPress preferences.
➢The discussion below assumes that purging QuarkXPress preferences did not resolve the problem.
An optional QuarkXPress XTension can sometimes cause QuarkXPress to freeze or crash when you try to open a document with it. This problem can occur even when scanning and diary generation work normally.
Symptoms
The following combination of symptoms can indicate this problem:
•Opening a document from Q++Studio launches QuarkXPress, but QuarkXPress then stops responding. The document may appear before a busy cursor remains displayed indefinitely.
•Double-clicking the same document in Windows Explorer produces the same result.
•Starting QuarkXPress first, waiting for it to finish launching, and then opening the document works normally.
•The above can occur while scanning and diary generation complete successfully.
The cause for the above is often one of the more recent optional QuarkXPress XTensions.
Solution
An Xtension that causes a crash on one system might work fine on another system.
To locate the Xtension that is causing the problem, locate the most recent QuarkXPress crash report of the form QuarkXPress.crash_*.log and look near the beginning of the report, in the call stack (the sequence of function calls leading to the crash), for filenames ending in .xnt. Some past examples of Xtensions causing crashes are StockImagesUI.xnt and Quarky.xnt.
➢If you are unsure how to interpret the report, send it to technical support.
Once you have identified the Xtension which is potentially the cause of the crash, you can try to deactivate it as follows:
1.Start QuarkXPress directly from its normal shortcut, without opening a document.
2.Select Utilities > XTensions Manager.
3.Note the current settings, then clear the Enable checkbox for the Xtension that you think is causing the problem.
4.Confirm the changes and quit QuarkXPress completely. Changes to the enabled XTensions take effect the next time QuarkXPress starts.
5.With QuarkXPress closed, double-click a test document in Windows Explorer.
6.If the document opens successfully, quit QuarkXPress again and test opening a document from Q++Studio.
If this fails, please contact technical support.
See also: QuarkXPress Tools and Utilities and other QuarkXPress topics.
Topic 190075, last updated on 23-Oct-2026
