This coponent generates a similar error to that reported for the PrintPreview. The following is whhat I reported to Microsoft (Jamshed Damkewala):
Jamshed,
Here is what little information I can provide:
The code leading up to the showing of my print dialog:
' Bring up the print selection dialog
DlgPrint = New Medicomp.Controls.Dialogs.PrintDlg
With DlgPrint
.BackColor = Me.BackColor
.SetParent(CType(Me, Medicomp.Controls.Dialogs.IPostDlg), MedClient)
.SetOptions(mintNarrativeItemtag, mintNarrativeOptions, myHeaderPrintMode, mintNarrativeOutput, mstrRTFBegin, mstrRTFEnd, mbolAllowEdit, mstrPath, gobjConfiguration.RTFStyles, Filename)
If (ovcOutline.OutlineNodes.Count > 0) Then
arSections.Add(New Medicomp.Controls.Dialogs.CPrintSection(ovcOutline.OutlineNodes, Medicomp.Controls.Dialogs.PrintElement.OutlineView, "Outline View"))
End If
.SetData(strHeading, arSections, arEncounters, mstrPrintFooterLeft)
.SetExportButtonMode(myExportButtonMode)
.NoteFormat = myPrintNoteFormat
If (.ShowDialog(Me) = Windows.Forms.DialogResult.OK) Then
I can confirm that the dialog gets the Activated event before the error message. The exact error is attached.
Our print dialog uses Infragistics components for printing:
Infragistics.Win.Printing.UltraPrintPreviewControl
Infragistics.Win.Printing.UltraPrintDocument(Me.components)
Infragistics.Win.Printing.UltraPrintPreviewThumbnail
The underlying print document is the UltraPrintDocument which is inherited from System.Drawing.Printing.PrintDocument. When our dialog is first activated, there is nothing added to the UltraPrintDocument. After the Activate event is received, the dialog gets the following two events; no other upDocument event gets raised (i.e. no PagePrinting. PageBodyPrinting, or PagePrinted. After the EndPrint event, the error is received. I did add some additional event handlers and got the QueryPageSettings event prior to the EndPrint event.
Private Sub upDocument_BeginPrint(ByVal sender As Object, ByVal e As System.Drawing.Printing.PrintEventArgs) Handles upDocument.BeginPrint
upDocument.OriginAtMargins = False
End Sub
Private Sub upDocument_EndPrint(ByVal sender As Object, ByVal e As System.Drawing.Printing.PrintEventArgs) Handles upDocument.EndPrint
Dim pa As System.Drawing.Printing.PrintAction = e.PrintAction
If (Not upDocument.PrintController.IsPreview) Then
CloseDialog()
This event is received after the BeginPrint:
Private Sub upDocument_QueryPageSettings(sender As Object, e As System.Drawing.Printing.QueryPageSettingsEventArgs) Handles upDocument.QueryPageSettings
Debug.WriteLine("upDocument_QueryPageSettings")
I understand that Infragistics is also looking into this as they are getting other reports of the same error after installing the security update.
I realize this is sketchy, but that is all I have at the moment.
Hello Roy,
Thanks for provided information. We already know about this issue and it will be fixed soon. I Already create a case for you with reference number CAS-90645-FNDMRN. I`ll provide you additional information through the case. Let me know if you have any questions.
Regards
We're also experiencing the same error, meaning the doctors who use our software cannot currently print. Do you have an ETA of when you'll have a patch out? Thanks...
Hello Philipw,
We expect to publish our new service release which contains the fix for this issue at May 11 (next Friday). You could check the projected date at http://ko.infragistics.com/support/service-releases.aspx#ServiceReleases
Let me know if you have any questions.
Hi,
The new service release is available. You could find it at : Infragistics.com -> My IG -> My Keys and Downloads.
Great. Thank you for the fast responses, much appreciated.
Looks like the links to the downloads did not get preserved when I saved the message. If someone advises me how to preserve the links, I will repost.
According to Jamshed Damkewala of Microsoft, I have permission to provide this information to Infragistics. The hotfixes are not being made universally available, but only to users who complain about the issue to them. The security update that started this whole mess is in the process of being revised, but since that will be pushed out via Windows Update, it will bbe awhile before that is available. In the meantime, the links here should get you to the fix needed. And since the error was introduced to all framework versions, all have to be fixed. Here is the gist of the email that I got from Jamshed.
...there are different hotfixes for different versions of the .NET Framework and in some cases also by platform. You can download the hotfixes for the various .NET Framework versions/platforms:
.NET Version
Platform
x86
x64
IA64
.NET Framework 2.0 SP2 (3.5 SP1)
Windows Server 2003 SP2, Windows XP SP3
Download
Windows Vista SP2, Windows Server 2008 SP2
Windows 7, Windows Server 2008 R2
Windows 7 SP1, Windows Server 2008 R2 SP1
.NET Framework 4
All supported platforms
Hi Roy_medicomp
Thank you very much for the shared informaiton !