UFT throws error and AUT is closed when trying to change FONT Style

  • Questions
  • UFT throws error and AUT is closed when trying to change FONT Style
Tags:
Question ID: 107818
1
0

If I have UFT and my AUT open, if I want to change the FONT Style in Options > Text Editor > Fonts & Colors, then my AUT crashes/closes and UFT shows the following error:

Exception of type: System.ArgumentException. Source: System.Drawing. Occured in Void CreateNativeFont() method
Exception message is: Font ‘Vidaloka’ does not support style ‘Regular’.
Exception trace is: at System.Drawing.Font.CreateNativeFont()
at System.Drawing.Font.Initialize(FontFamily family, Single emSize, FontStyle style, GraphicsUnit unit, Byte gdiCharSet, Boolean gdiVerticalFont)
at System.Drawing.Font..ctor(FontFamily family, Single emSize)
at HP.UFT.ConfigurationUI.FontDescriptor.DetectMonospaced(FontFamily fontFamily)
at HP.UFT.ConfigurationUI.FontSelectionControl.PrepareFontList(Object state)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

SharpDevelop Version : 4.1.1.0-00000000
.NET Version : 4.0.30319.1
OS Version : Microsoft Windows NT 6.1.7600.0
Current culture : English (United States) (en-US)
Working Set Memory : 213800kb
GC Heap Memory : 19549kb

An unexpected error occurred.

Click 'OK' to close this application. Click 'Details' to display technical details
on this error which may help you solve the problem, or can be used when
contacting customer support.

—- Post-error application state information:
Installed 3rd party AddIns: [${res:Addin.UFT.File.Dialog.UFT.Only} 11.50.0.0], [ActiveScreenPane 0.0.0.0], [QTP DataTable Addin], [QTP Debugger addin based on UT Debugger 0.0.0.0], [QTP FileDialog 0.0.0.0], [HP QTP Property Tabs 0.0.0.0], [ALM Storage 11.50.0.0], [HP Basic Extensibility 11.50.0.0], [HP Designer UI Extensibility 11.50.0.0], [HP SOAReplayAPI Extensibility 11.50.0.0], [${res:HP_Async} 11.50.0.0], [${res:HP_Checkpoints} 11.50.0.0], [${res:STDataProvider_HP_Data_Providers} 11.50.0.0], [${res:BasicActivity_HP_Basic_Activities} 11.50.0.0], [${res:HP_BPT_Integration} 11.50.0.0], [HP CSharp Translation Layer 11.50.0.0], [${res:HP_Database_Activities} 11.50.0.0], [${res:HP_Standard_Import_Technologies} 11.50.0.0], [HP Framework Upgraders 11.50.0.0], [${res:HP_FTP_Activities} 11.50.0.0], [ST Debugger addin based on UT Debugger 11.50.0.0], [${res:HTTP_Activity} 11.50.0.0], [${res:HP_Receiver_Activity} 11.50.0.0], [Run Step Pad 11.50.0.0], [${res:HP_Java_Call_Addin} 11.50.0.0], [${res:HP_JMS_Technology} 11.50.0.0], [${res:HP_LoadRunner_Integration} 11.50.0.0], [${res:HP_MQ_Activities} 11.50.0.0], [${res:PropertySheet_HP_Basic_Property_Sheet} 11.50.0.0], [${res:HP_Rest_Technology} 11.50.0.0], [${res:HP_UFT_STM} 11.50.0.0], [${res:HP_Service_Test_runner} 11.50.0.0], [HP Basic Framework 11.50.0.0], [Toolbox Default Presenter 11.50.0.0], [HP Toolbox UI Extensibility 11.50.0.0], [${res:HP_Transform_JSON_Addin} 11.50.0.0], [${res:HP_Transform_Xml_Addin} 11.50.0.0], [${res:HP_QTP_test_runner} 11.50.0.0], [${res:HP_Validate_Xml_Addin} 11.50.0.0], [VTD Extensibility 11.50.0.0], [${res:HP_Run_Vugen_Addin} 11.50.0.0], [${res:Wait_Activity} 11.50.0.0], [${res:WSImportTechnology_HP_Standard_Import_Technologies} 11.50.0.0], [HP Shell Services 11.50.0.0], [${res:Addin.UFT.Data.Explorer} 11.50.0.0], [UTT Configuration UI 11.50.0.0], [Debug Pad Wrapper Extension addin for UTT 11.50.0.0], [UTT Debug Basic implementation addin for UTT 11.50.0.0], [UTT File Dialog 11.50.0.0], [${res:Addin.UFT.File.System} 11.50.0.0], [${res:Addin.UFT.ALM} 11.50.0.0], [UTT Connection Addin 11.50.0

Marked as spam
Posted by (Questions: 346, Answers: 13)
Asked on July 31, 2017 3:37 am
5 views
Answers
2
Private answer

It looks like UFT isn't able to support different styles for that problem font (''Vidaloka'')...or that font simply doesn't have any styles associated with it (bold, regular, etc.) and is throwing UFT off. You'll most likely just need to uninstall it from your system (Windows Control Panel > Fonts > Select your font (e.g. 'Vidaloka') > Delete. See if this helps.

Marked as spam
Posted by (Questions: 0, Answers: 694)
Answered on July 31, 2017 1:24 pm
Thanks a bunch. I uninstalled the font in question, and am now able to change my FONT Style without issue.
( at July 31, 2017 1:24 pm)