Internet Explorer Script Error Outlook 2003 Printing
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Getting Script error when printing from Outlook 2003 Microsoft Office > Outlook IT Pro Discussions Question 0 Sign in to vote Outlook 2003 giving Internet Explorer Script Error, Line 2252. The user cannot print from Outlook, but he can print from all other applications. If he is in the Outlook Webaccess he can print. If he is in Outlook 2003 on his desktop to a different printer he still gets the Internet Explorer Script Error, Line 2252. The PC is up today, he can print from I.E. 8. Can this be the result of a print driver or a corrupt Outlook profile? Windows XP SP3, 32 bit Thanks leggsf Monday, July 09, 2012 8:36 PM Reply | Quote Answers 0 Sign in to vote Is it this problem: http://www.outlook-tips.net/tips/script-error-printing-outlook-2003/ ? Diane Poremsky [MVP - Outlook] Outlook Daily Tips | Outlook & Exchange Solutions Center Subscribe to Exchange Messaging Outlook weekly newsletter Marked as answer by Rex ZhangModerator Monday, July 16, 2012 1:06 AM Monday, July 09, 2012 9:54 PM Reply | Quote All replies 0 Sign in to vote Is it this problem: http://www.outlook-tips.net/tips/script-error-printing-outlook-2003/ ? Diane Poremsky [MVP - Outlook] Outlook Daily Tips | Outlook & Exchange Solutions Center Subscribe to Exchange Messaging Outlook weekly newsletter Marked as answer by Rex ZhangModerator Monday, July 16, 2012 1:06 AM Monday, July 09, 2012 9:54 PM Reply | Quote 0 Sign in to vote Hi Diane, no this is a little different as
to print from Outlook 2003 in a TS/RDS session with IE9 installed ★★★★★★★★★★★★★★★ Paul Adams (ex-MSFT)November 3, 201114 Share 0 0 Update 2012-01-11: There is now a hotfix available for Windows 7 / Server 2008 R2 to address this issue – KB2647169 Update 2012-02-16: The above hotfix has now been extended to cover Windows Vista / Server 2008 A customer had a case recently where a Windows Server 2008 x86 SP2 server had Office 2003 and Internet Explorer 9 installed, and when users in TS sessions try to print HTML format emails from Outlook, the following error https://social.technet.microsoft.com/Forums/office/en-US/6deb0a2d-1256-4114-9eea-d327f0857a25/getting-script-error-when-printing-from-outlook-2003?forum=outlook is displayed: Line: 2053 Char: 1 Error: The system cannot find the file specified Code: 0 URL: res://ieframe.dll/preview.js Plain text, and RTF format emails print just fine – the problem is specifically HTML format (which makes sense as this would invoke the HTML rendering engine shared with the OS and IE). Others have reported the same issue on Windows Server 2008 R2 in RDS sessions, and only https://blogs.technet.microsoft.com/mrsnrub/2011/11/03/script-error-resieframe-dllpreview-js-trying-to-print-from-outlook-2003-in-a-tsrds-session-with-ie9-installed/ after upgrading from IE8 to IE9 – so on the surface the problem appears to be with an IE component, however that’s actually not the problem here… First, what file is it that the system cannot find? Here’s how we find out… First, download Process Monitor. Next, start Outlook 2003 and open an HTML format email so you are ready to repro the problem. Now start Process Monitor so we are logging all I/O events. Now click the Print button on the Outlook toolbar and get the error up. TIP: Don’t clear the error message by clicking OK – this will just generate more activity and we’ve already recorded the problem. Now switch to Process Monitor and stop it recording, then filter on Process Name = OUTLOOK.EXE. Filter out all but file I/O events to reduce the list, and use a highlight rule for Result = NAME NOT FOUND. Scroll down the list and you can get an idea as to what Outlook is doing as it renders the elements of the mail in the Temporary Internet Files folder in the user profile. The actual files created will vary, as the mail content and name for the
InstalledSlipstick SystemsHome / Outlook / Outlook 2003 / Printing Errors in Outlook 2003 with IE9 Installed Last reviewed on November 8, 2012 —1 Comment Users in a terminal http://www.slipstick.com/outlook/2003/print-errors-in-outlook-2003-with-ie9-installed/ services environment are reporting a script error, res://ieframe.dll/preview.js, when they attempt to http://discussions.citrix.com/topic/290819-cannot-print-html-email-from-outlook-2003-since-upgrading-to-internet-explorer-9/ print email in Outlook 2003 after installing Internet Explorer 9. This is due to a problem printing to a non-redirected printer. There are three possible solutions: set a registry to key to force all printouts to RTF format, print messages as plain text, or create a Fonts folder under internet explorer the Windows directory. Of course, rolling back to IE8 will solve the problem too. Cause Paul Adams [MSFT] full explanation is here: Script error ‘res://ieframe.dll/preview.js’ trying to print from Outlook 2003 in a RS/RDS session with IE9 installed Short version: This is caused by the process trying to open a folder that does not exist. This is why creating the missing folder internet explorer script at %HOMEDRIVE%%HOMEPATH%\Windows\Fonts works. (For most users the folder is C:\Users\%USERNAME%\Windows\Fonts.) Why does this only happen when IE9 is installed? Because there is a design change in how IE9 invokes printing APIs in the OS. Applications (including Outlook 2003) that are not "Terminal Service aware" will have their API calls are marked as such, which leads to an incorrect code path being followed when trying to enumerate the path to the fonts folder. If the application is marked as TS aware, then the system fonts folder is used (%SYSTEMROOT%\Fonts) and printing works. A note worth repeating: this is not the root cause of all scripting errors. It is just one specific symptom tied directly to the presence of an IE version after 8.0, and only in Terminal server/remote desktop scenarios. Two of the solutions will need to be implemented by the administrator. The first solution, printing in plain text, will work for all end-users. Solution 1: Print in Plain Text Format. If you need to print most messages, set Outlook to read all mail as plain text in Tools > Options > Prefer
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenApp XenApp 6.0 for Windows Server 2008 R2 Printing (HDX Plug-n-Play Printing) Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Cannot print HTML email from Outlook 2003 since upgrading to Internet Explorer 9 Started by JOYCE CARUTHERS , 20 July 2011 - 08:36 PM Login to Reply 3 replies to this topic JOYCE CARUTHERS Members #1 JOYCE CARUTHERS 2 posts Posted 20 July 2011 - 08:36 PM Since upgrading to Internet Explorer 9, we can no longer print HTML email from Outlook 2003. RTF and text are fine, but with HTML we get the following script error:An error has occurred in the script on this page.Line: 2053Char: 1Error: The system cannot find the file specified.Code: 0URL: res://ieframe.dll/preview.jsIf the email has an option to view in web browser, it will print, but you are missing the email header information. We can save the email message locally, open it, and print it.We have tried adding the registry e