I can’t seem to print any reports. Specifically, I tried to print a quote and got the following message:
Unhandled Exception:
The type initializer for “DevExpress.XtraPrinting.Drawing.Watermark” threw an exception.
System.TypeInitializationException
Stack Trace:
at DevExpress.XtraPrinting.Drawing.Watermark…ctor()
at DevExpress.XtraReports.UI.XtraReport…ctor()
at AyaNova.Util.ReportHandleToolClick(ToolBase lTool, String ReportKey, Object DataSource)
at AyaNova.WorkorderForm.(Object , ToolClickEventArgs )
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
at Infragistics.Win.UltraWinToolbars.ListTool.set_SelectedItemIndex(Int32 value)
at Infragistics.Win.UltraWinToolbars.ListTool.DoDefaultActionForItem(Int32 itemIndex)
at Infragistics.Win.UltraWinToolbars.ListToolMenuItem.OnClick()
at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.DoClickProcessing(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.UIElement.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.TextUIElementBase.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.PopupControlBase.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
*** The type initializer for “DevExpress.XtraPrinting.Drawing.Watermark” threw an exception.
at DevExpress.XtraPrinting.Drawing.Watermark…ctor()
at DevExpress.XtraReports.UI.XtraReport…ctor()
at AyaNova.Util.ReportHandleToolClick(ToolBase lTool, String ReportKey, Object DataSource)
at AyaNova.WorkorderForm.(Object , ToolClickEventArgs )
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
at Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
at Infragistics.Win.UltraWinToolbars.ListTool.set_SelectedItemIndex(Int32 value)
at Infragistics.Win.UltraWinToolbars.ListTool.DoDefaultActionForItem(Int32 itemIndex)
at Infragistics.Win.UltraWinToolbars.ListToolMenuItem.OnClick()
at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.DoClickProcessing(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.PopupMenuItemUIElement.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.UIElement.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.TextUIElementBase.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
at Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
at Infragistics.Win.UltraWinToolbars.PopupControlBase.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
*** Font ‘Verdana’ doesn’t support style ‘Regular’.
at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gd
Does this occur with all computersrunning their local AyaNova.exe executable?
Logged in the AyaNova program on this station, select menu Help -> About AyaNova. Right-click within the text screen, Select All, Copy and paste that information into your reply (you can xxxxx out the SYSDBA password)
Does this occur with any report - or only a report from the Quotes navigation pane grid?
The error message includes “*** Font ‘Verdana’ doesn’t support style ‘Regular’.”
That may indicate an issue with the standard Windows font Veranda on this computer.
Open up WordPad or Microsoft Word, and type some text using Veranda size 36 - and than try to print it
Is this occurring with only this computer or all computers on the network?
If occurring with all computers, are all computers printing to the same networked printer using the same printer driver?
In AyaNova v3 in the Quotes navigation pane - select the report template “Detailed Quote” - does it respond with the same error message including “*** Font ‘Verdana’ doesn’t support style ‘Regular’.” or is the error different or does an error occur?
OK… I can print from the server, but can’t print from the client. Here’s the info in the help about AyaNova window:
License information:
Key issued: 2/15/2006 7:30:54 PM
Registered to: Computer Solutions, Inc.
Scheduleable users: 2
Option - QuickBooks interface: False
Option - Web browser interface: False
Technical information:
Machine name: AMD
AyaNova Connection: MSSQL database, connection string="Server=amdserver\SQLExpress;initial catalog=AyaNova;User Id=sa; Password=XXXXXXXX;"
Generate PM and Notify from this connection: False
OS user name: Todd
Networked: True
OS user domain name: AMD
OS version: Microsoft Windows NT 5.1.2600.0
System folder: C:\WINDOWS\system32
CLR version: 1.1.4322.2032
Current directory: C:\Program Files\Ground Zero Tech-Works Inc\AyaNova 3
Logical drives: A:\ C:\ D:\ E:\ F:\ U:\
Working set: 48988160
Primary monitor size: {Width=1024, Height=768}
Locale current culture: English (United States)
Locale currency symbol: $
Locale short date pattern: M/d/yyyy
Locale short time pattern: h:mm tt
Primary assembly: AyaNova 3.0.1.0
*** Business object assembly sub version: A (04-Feb-2006) ***
Primary assembly location: file:///C:/Program Files/Ground Zero Tech-Works Inc/AyaNova 3/AyaNova.exe
References:
System.Windows.Forms 1.0.5000.0
mscorlib 1.0.5000.0
System 1.0.5000.0
Infragistics.Win.v5.3 5.3.20053.50
System.Drawing 1.0.5000.0
Infragistics.Win.UltraWinGrid.v5.3 5.3.20053.50
log4net 1.2.9.0
Infragistics.Win.UltraWinToolbars.v5.3 5.3.20053.50
Infragistics.Win.Misc.v5.3 5.3.20053.50
Infragistics.Win.UltraWinEditors.v5.3 5.3.20053.50
GZTW.AyaNova.BLL 3.0.0.0
GZTW.WinForm.Controls 3.0.0.0
Infragistics.Win.UltraWinStatusBar.v5.3 5.3.20053.50
Infragistics.Win.UltraWinExplorerBar.v5.3 5.3.20053.50
Infragistics.Win.UltraWinSchedule.v5.3 5.3.20053.50
Infragistics.Win.UltraWinTree.v5.3 5.3.20053.50
System.Data 1.0.5000.0
DevExpress.XtraReports3 1.12.2.0
Infragistics.Win.UltraWinTabControl.v5.3 5.3.20053.50
CSLA 1.3.0.0
System 1.0.3300.0
System.Windows.Forms 1.0.3300.0
System.Drawing 1.0.3300.0
Infragistics.Shared.v5.3 5.3.20053.50
CSLA.Core.Bindablebase 1.3.0.0
mscorlib 1.0.3300.0
DevExpress.XtraNavBar3 2.7.2.0
DevExpress.Utils3 3.2.2.0
System.Xml 1.0.5000.0
FirebirdSql.Data.Firebird 1.7.0.1
DevExpress.XtraPrinting3 1.12.2.0
Session information:
User settings
User: Todd Gustafson
Language: English
UserType: Schedulable
SubContractor: False
Region: DEFAULT
Global settings
Language: English
Use Notification services: True
CJK Index: False
Use inventory: True
Use regions: True
I will be out for an hour or two… but will check back when I get back to see if you have any other suggestions. This is not an emergency as I am merely setting up the system before I open the store in a month or so.
Usually an error stating "…doesn’t support style ‘Regular’. " indicates an issue with a font itself - usually a corrupted font or an issue with the printer driver and that font.
I would first ensure that the font itself isn’t corrupted on this client networked computer.
Is the server and the client networked computer the same operating system - if so, replace the Verandafont files (I believe there are at least four in the Windows\Fonts folder)with that from the server and than reboot, and retry.
If that doesn’t address the issue - On the client networked computer, open up WordPad or Microsoft Word, and type some text using Veranda size 36 - and than try to print it - does it type, does it print?
A few additional questions if the issue continues:
Is the above text from the server that can print, or from the client networked computer that can’t print? If from the server, can you provide the text from the client networked computer that can not print this report? I want to ensure that the applicable AyaNova system files are on the client networked computer.
Were you getting the same error message on the server before installing the printer driver on the server?
on the client networked computer, in AyaNova v3 in the Quotes navigation pane - select the report template “Detailed Quote” - does it respond with the same error message including “*** Font ‘Verdana’ doesn’t support style ‘Regular’.” or is the error different or does an error occur printing that report?
Can you identify which reports you are getting the error from.
Did you replace the four font files on this client station with those from the server where it is printing successfully?
After that didyou try specifically from theQuotes navigation pane - the report template “Detailed Quote”? The reason is because this report does not utilize a Veranda font and I was hoping to get from you if you get the exact error message including the aspect near the end “…*** Font ‘Verdana’ doesn’t support style ‘Regular’.”
Please print that report and provide the entire error message you receive when printing that report template.
Was the info provided from from the server that can print, or from the client networked computer that can’t print? If from the server, can you provide the text from the client networked computer that can not print this report? I want to ensure that the applicable AyaNova system files are on the client networked computer.
Before applying the printer driver on the server, were you getting this error message also on the server?
Turns out on my client there were 5 Verdana fonts. One of them was corrupted or something, gave me an error when I tried to delete it. I managed to replace them and now I have no problems.