[FLEX-14591] Printing an application twice causes RTE - ArgumentError: Error #2004: One of the parameters is invalid.

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Won't Fix
• Affects Version/s: Adobe Flex SDK 2.0.1 (Release)
• Component/s: Print Management
• Environment: Affected OS(s): Windows; Affected OS(s): Windows XP; Browser: Internet Explorer 7.x; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 21/Apr/08 10:59
• Updated: 15/Apr/11 14:46
• Resolved: 08/Oct/08 15:45

Description

Steps to reproduce:
1. Run attached MXML application.
2. Press Print button.
3. Print to valid printer.
4. Press Print button again.
5. Attempt to print to valid printer. --> RTE

Actual Results:

ArgumentError: Error #2004: One of the parameters is invalid.
at flash.display::Graphics/drawRect()
at mx.skins::RectangularBorder/http://www.adobe.com/2006/flex/mx/internal::adjustBackgroundImage()[E:\dev\flex_201_borneo\sdk\frameworks\mx\skins\RectangularBorder.as:423]
at mx.core::Container/scrollChildren()[E:\dev\flex_201_borneo\sdk\frameworks\mx\core\Container.as:4706]
at mx.core::Container/validateDisplayList()[E:\dev\flex_201_borneo\sdk\frameworks\mx\core\Container.as:2814]
at mx.managers::LayoutManager/validateDisplayList()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\LayoutManager.as:600]
at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\LayoutManager.as:673]
at mx.managers::LayoutManager/validateNow()[E:\dev\flex_201_borneo\sdk\frameworks\mx\managers\LayoutManager.as:726]
at mx.printing::FlexPrintJob/addObject()[E:\dev\flex_201_borneo\sdk\frameworks\mx\printing\FlexPrintJob.as:328]
at FlexPrinting/onPrint()[C:\Documents and Settings\bmantuano\My Documents\Flex Builder 3\Test\FlexPrinting.mxml:20]
at FlexPrinting/___Button1_click()[C:\Documents and Settings\bmantuano\My Documents\Flex Builder 3\Test\FlexPrinting

Expected Results:
Application prints normally.

Workaround (if any):

The issue seems to be resolved in the Flex 3 SDK, but we're unable to use this for other reasons. Can this same fix be incorporated into 2.0.1 HotFix 3?