Databases
StackOverflow2013
Postsdbo
POWeird error printing PrintDocument object in .NET
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWeird error printing PrintDocument object in .NET
    primarykey
    data
    text
    <p>I have a Winforms application that generates its own PrintDocument object for printing. It works fine in XP and Windows 7 with my own testing, but one user has been getting the following exception in Vista when they select the print command with an open document:</p> <pre><code>************** Exception Text ************** System.ArgumentException: Handle 0 is not valid. at System.Drawing.Printing.PrinterSettings.SetHdevmode(IntPtr hdevmode) at System.Windows.Forms.PrintDialog.UpdatePrinterSettings(IntPtr hDevMode, IntPtr hDevNames, Int16 copies, Int32 flags, PrinterSettings settings, PageSettings pageSettings) at System.Windows.Forms.PrintDialog.ShowPrintDialog(IntPtr hwndOwner, WndProc hookProcPtr, PRINTDLG data) at System.Windows.Forms.PrintDialog.RunDialog(IntPtr hwndOwner) at System.Windows.Forms.CommonDialog.ShowDialog(IWin32Window owner) at System.Windows.Forms.CommonDialog.ShowDialog() at Deck_Studio.DSMain.PrintDeck(Object sender, EventArgs e) at System.Windows.Forms.MenuItem.OnClick(EventArgs e) at System.Windows.Forms.MenuItem.MenuItemData.Execute() at System.Windows.Forms.Command.Invoke() at System.Windows.Forms.Command.DispatchID(Int32 id) at System.Windows.Forms.Control.WmCommand(Message&amp; m) at System.Windows.Forms.Control.WndProc(Message&amp; m) at System.Windows.Forms.ScrollableControl.WndProc(Message&amp; m) at System.Windows.Forms.ContainerControl.WndProc(Message&amp; m) at System.Windows.Forms.Form.WndProc(Message&amp; m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) </code></pre> <p>I'm having a hard time piecing out the nature of this error and any potential ways of duplicating this. The manifest on the executable is in the "limited" permissions mode and even having the user run the application as an administrator generates the error.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USDillie-O
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COIt sounds like the print driver is not behaving (first guess). Does this happen with all printers on that user's computer?
      singulars
      1. POWeird error printing PrintDocument object in .NET
      1. USMichael Todd
    2. COThey've tried their Adobe stiller, XPS writer, and basic printer and got the error.
      singulars
      1. POWeird error printing PrintDocument object in .NET
      1. USDillie-O
    3. COSo it doesn't appear to be a specific printer at fault. And it's not a permissions issue. If it isn't an O/S problem (i.e. try it on another desktop using Vista), I'd have to go with how MusiGenesis answered: default printer not set.
      singulars
      1. POWeird error printing PrintDocument object in .NET
      1. USMichael Todd
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload