none
Help getting the XPS writer working.

    Question

  • Win7 ... the MS XPS Document writer has never worked well.  Today I uninstalled the feature and reinstalled it (to no avail).

    If I try from Outlook, I get a simple message box ... "Printer not ready".

    From Notepad, a message box ... "The parameter is incorrect"

    From Excel, an elaborate message box starting with "... could not be printed in the MS XPS Doc Writer on e00 ..."

    From Winword, I get nothing at all, including no XPS file.

    From IE, I get ... Internet Explorer (not responding)

    From the Windows Photo Viewer ... it works!

    Help!

    Thanks.   - Vince


    • Edited by vesf Friday, August 29, 2014 12:37 AM
    Friday, August 29, 2014 12:35 AM

Answers

  • Problem solved!

    Apparently, the XPS Writer needs delete permission in %TEMP%.

    Before: "authenticated users" could do anything except delete in %TEMP% ... "users" somewhat less ... "system" and "administrators" had full control.

    I am "vefatica", an administrator running with a UAC-crippled token.  Apparently, for some apps that was not enough.  I'd like to know more about the differences between those apps which could use the XPS Writer and those which couldn't.  As (crippled) "vefatica", I can manually delete things in %TEMP% with no hassle.

    When I specifically added "vefatica" with full control over %TEMP%, all the XPS printing problems went away.

     - Vince

    • Marked as answer by vesf Saturday, September 06, 2014 8:49 PM
    Saturday, September 06, 2014 8:49 PM

All replies

  • Hi vesf,

    Please take the following steps for troubleshooting.
    1.Go to Control Panel\Hardware and Sound\Devices and Printers.
    2.Right click on XPS printer and choose Troubleshoot.

    You could check the event log to see if any errors we could track with.
    http://windows.microsoft.com/en-us/windows/what-information-event-logs-event-viewer#1TC=windows-7

    Best regards,
    Fangzhou CHEN

    Friday, August 29, 2014 2:45 PM
  • Hi vesf,

    Please take the following steps for troubleshooting.
    1.Go to Control Panel\Hardware and Sound\Devices and Printers.
    2.Right click on XPS printer and choose Troubleshoot.

    You could check the event log to see if any errors we could track with.
    http://windows.microsoft.com/en-us/windows/what-information-event-logs-event-viewer#1TC=windows-7

    Best regards,
    Fangzhou CHEN

    Hi, Fangzhou.

    First suggestion from the wizard: make it the default printer, don't want that, skipped.

    No further suggestions.

    There were no events recorded in any of the major logs, and none in\Application and Services Logs\Microsoft\Windows\Print Service\Admin, where print failures often show up.

    In \Application and Services Logs\Microsoft\Microsoft Office Alerts was essentially the same info I saw in the message box (in a failed print attempt from Excel).

    Microsoft Excel
    Your file could not be printed due to an error on Microsoft XPS Document Writer on e00:. There are several possible reasons:

    • There may not be enough memory available. Try closing files and programs you aren't using.
    • If you use a network for printing, there may be a problem with the network connection or the printer driver.
    • There may be loose cables or a bad connection between your computer and printer.

    For more information about troubleshooting printing problems, click Help.
    P1: 100125
    P2: 14.0.4763.1000
    P3:
    P4:

    Saturday, August 30, 2014 4:06 PM
  • The Office Alerts log also has the Outlook failure mentioned in my first post:

    Microsoft Outlook
    Printer not ready.
    P1: 301665
    P2: 14.0.4763.1000
    P3: gkcq
    P4: 0x80004005

    It contains no mention of the perviously mentioned silent failure from WinWord.

    Saturday, August 30, 2014 4:12 PM
  • And, for what it's worth, I did (temporarily) make the XPS Document Writer the default printer.  That changed nothing.
    Saturday, August 30, 2014 4:15 PM
  • In addition, the XPS Document Writer's "Print test page" fails.  If I specify the desktop as the location for the test page, an icon appears momentarily then disappears.

    At that moment, the Security log shows two successful "NULL SID" logons and (apparently corresponding) "ANONYMOUS" logoffs 11 seconds later.  I couldn't find any other logged events.

    And (probably a different issue) EVERY time I (successfully) print anything on the default printer I get an event (like the one below) in the PrintServices\Admin log.

    The document l:\Projects\multinom\multinom.cpp, owned by vefatica, failed to print on printer HP LaserJet 1020. Try to print the document again, or restart the print spooler.
    Data type: RAW. Size of the spool file in bytes: 105258. Number of bytes printed: 105258. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\ZZ. Win32 error code returned by the print processor: 0. The operation completed successfully.

    Saturday, August 30, 2014 6:19 PM
  • And it also works from MSPaint.

     - Vince

    Saturday, August 30, 2014 8:58 PM
  • And I can successfully print to the XPS Document Writer from third-party apps, a Nikon (camera) utility, and Adobe Acrobat.  So far, I've been able to print (to XPS) only PNG, JPEG. and PDF files (not DOCX, XLSX, TXT, or whatever format is used by IE).  Could I be missing some format specifications (files) for other file types?
    Sunday, August 31, 2014 2:14 AM
  • I find XPS files are larger than other formats like PDF which are better tuned for library use

    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 31, 2014 2:31 AM
  • A recap and some NEW info.

    I can successfully print to the XPS Document Writer from Photo Viewer, a Nikon (camera) utility, MSPaint, and DevEnv (DevStudio) ... JPG, PNG, PDF, CPP.

    I cannot print to the XPS Document Writer from Excel, Winword, Outlook, IE, or Notepad (details in earlier posts) or FireFox.

    I just discovered that if I start Excel, Winword, Notepad, or FireFox elevated, I can print to the XPS Document Writer.

    In all my tests, the target folder has been either the desktop folder or the Documents folder.  I have explicit (by my username) "Full control" permissions on those folders (inherited from my profile folder).

     - Vince


    • Edited by vesf Sunday, August 31, 2014 4:19 AM
    Sunday, August 31, 2014 4:15 AM
  • I guess you were using a limited account, I use an administrator level account so I do not run into issues

    this seems to be a general permissions issue 

    might be an idea to change the XPS write to allow everyone to use it, might mitigate your problem of saving the file to another location


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 31, 2014 9:59 AM
  • I don't have a limited account on this (or any) machine.  There is only one user, me, "vefatica", an administrator.  The permissions on the XPS Doc Writer already allow "everyone" and separately, "vefatica" (by name), to print.

    See my recap.  Un-elevated, I can print to the XPS Doc Writer with some software and not with other software.  And when it fails, it fails regardless of the file's destination.  I would like some help changing this behavior.

    Sunday, August 31, 2014 4:40 PM
  • do you have UAC turned off? That can assist to see if elevation is working properly.


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 31, 2014 6:08 PM
  • UAC is on.
    Sunday, August 31, 2014 6:26 PM
  • UAC is on.

    guess you are stuck to save it to desktop, then move the file elsewhere


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 31, 2014 7:06 PM
  • UAC is on.

    guess you are stuck to save it to desktop, then move the file elsewhere


    What are you talking about?  The save-file location is irrelevant.  Some apps can print to the XPS Writer; some cannot.  The XPS Writer cannot even print a test page ... not to the desktop ... not to anywhere.
    Sunday, August 31, 2014 7:22 PM
  • Try running the program as administrator, if that does not work....

    might be time for a fresh install of Windows 7 now that its 5 years old


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 31, 2014 8:33 PM
  • I've already said what happens when I run apps elevated.  As for reinstalling Windows ... I don't feel like trading one problem for a hundred.
    Sunday, August 31, 2014 8:47 PM
  • I've already said what happens when I run apps elevated.  As for reinstalling Windows ... I don't feel like trading one problem for a hundred.

    not much else I can think of unfortunately

    maybe somebody else has a better idea


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, August 31, 2014 8:49 PM
  • With a utility of my own, I searched the registry (key names, values, data) for strings containing "xps" (case-insensitive on two machines ... one (work) where printing to XPS works, and the other (home) about which I have been complaining.  Much is the same but there are striking differences.

    The home machine, where printing to XPS doesn't work, has these classes which are completely non-existent on the machine where printing to XPS works.  In fact, "xpsprint.dll" is not mentioned in the registry of the machine on which printing to XPS works.

    HKCR\CLSID\{348ef17d-6c81-4982-92b4-ee188a43867a}\InProcServer32
        Value:
    ->    Data:  %SystemRoot%\System32\XpsPrint.dll

    HKCR\CLSID\{E1553E07-5939-4CFD-BE24-3BCEBA2F148C}\InProcServer32
        Value:
    ->    Data:  %SystemRoot%\System32\XpsPrint.dll

    And the second of these (below, "7.1") does not exist on the machine where printing to XPS works.

    -> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_none_1c8562f614ed785a\6.1
    -> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_none_1c8562f614ed785a\7.1
    -> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_none_1c8562f614ed785a

    The registry keys which exist on the problematic machine have a time stamp of 2013-11-17, the day on which I instelled IE11 (which required 10 other updates which I'll try to investigate).

    If the installation of IE11 is the culprit, I gotta laugh ... some apps can print to XPS, some can't, but IE11 is special ... it goes ballistic (not responding).

    Any thoughts?

    Monday, September 01, 2014 1:25 AM
  • I have not seen this issue with any version of IE


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Monday, September 01, 2014 1:49 AM
  • Google for "evil update" and then visit its KB page to discover it messes with XPS services.
    Monday, September 01, 2014 2:29 AM
  • Hi vesf,

    What is your current situation and which KB do you mean?

    Have you solved this issue?

    Best regards,
    Fangzhou CHEN

    Wednesday, September 03, 2014 11:47 AM
  • Hi vesf,

    What is your current situation and which KB do you mean?

    Have you solved this issue?

    Best regards,
    Fangzhou CHEN

    Hello, Fangzhou.  Thanks for your continued interest.

    I uninstalled IE11 and KB2670838 (required by IE11 and changed XPS services).  The problem was utterly unchanged.  Exactly as before (best summed up in my "recap" post) I can successfully print to the XPS Doc Writer with many apps and not with many other apps; it can't print its own test page.  Removing KB2670838 seemed so promising, but it didn't help.  So I've just been thinking about it ... waiting for an idea of what to try next.

     - Vince

    Thursday, September 04, 2014 4:58 AM
  • Problem solved!

    Apparently, the XPS Writer needs delete permission in %TEMP%.

    Before: "authenticated users" could do anything except delete in %TEMP% ... "users" somewhat less ... "system" and "administrators" had full control.

    I am "vefatica", an administrator running with a UAC-crippled token.  Apparently, for some apps that was not enough.  I'd like to know more about the differences between those apps which could use the XPS Writer and those which couldn't.  As (crippled) "vefatica", I can manually delete things in %TEMP% with no hassle.

    When I specifically added "vefatica" with full control over %TEMP%, all the XPS printing problems went away.

     - Vince

    • Marked as answer by vesf Saturday, September 06, 2014 8:49 PM
    Saturday, September 06, 2014 8:49 PM
  • I am not too sure why the XPS writer was a problem, on a clean install of 7 it works as expected in a virtual machine.

    I wonder if some program you use has changed the permissions improperly


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Saturday, September 06, 2014 9:04 PM
  • My system drive is c:.  %TEMP% is h:\temp, owned by S-1-5-21-3291446647-2681218026-3195555329-1005 who is not a user in the current Windows installation.  No doubt there's some left-over security from a previous installation of Windows.

    Regardless ... the interesting question, IMO, is why (in 3+ years) was the XPS Writer the ONLY problem with %TEMP% and why was it that ONLY SOME apps had this problem.  I'd expect that apps attempt to use the XPS Writer (any printer) in a rather generic fashion common to all of them.

     - Vince

    Sunday, September 07, 2014 12:00 AM
  • My system drive is c:.  %TEMP% is h:\temp, owned by S-1-5-21-3291446647-2681218026-3195555329-1005 who is not a user in the current Windows installation.  No doubt there's some left-over security from a previous installation of Windows.

    Regardless ... the interesting question, IMO, is why (in 3+ years) was the XPS Writer the ONLY problem with %TEMP% and why was it that ONLY SOME apps had this problem.  I'd expect that apps attempt to use the XPS Writer (any printer) in a rather generic fashion common to all of them.

     - Vince

    Now I see why, baggage account was the problem.

    I use a clean install as a baseline to reproduce issues


    Corsair Carbide 300R with TX850V2
    Asus M5A99FX PRO R2.0 CFX/SLI
    AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
    G.SKILL RipjawsX DDR3-2133 8 GB
    EVGA GTX 660 Ti FTW Signature 2 (GK104 Kepler)
    Asus PA238QR IPS LED HDMI DP 1080p
    ST2000DM001 & Windows 8.1 Professional x64
    Microsoft Wireless Desktop 2000 & Wacom Bamboo CHT470M

    Place your rig specifics into your signature like I have, makes it 100x easier to understand!

    Hardcore Games Legendary is the Only Way to Play!

    Sunday, September 07, 2014 12:30 AM