Outlook 2003 Internet Explorer Script Error Printing
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 23 Oct 2016 17:19:55 GMT by s_nt6 (squid/3.5.20)
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, http://answers.microsoft.com/en-us/office/forum/officeversion_other-outlook/script-error-while-printing-using-outlook-2003/1c5b78e5-cc09-487b-b203-fadfa1050de5 and when users in TS sessions try to print HTML format emails from Outlook, the following error 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 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/ 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 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 = NAM
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 services environment are reporting a script http://www.slipstick.com/outlook/2003/print-errors-in-outlook-2003-with-ie9-installed/ error, res://ieframe.dll/preview.js, when they attempt to 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 the Windows directory. Of course, rolling back to IE8 will solve the outlook 2003 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 at %HOMEDRIVE%%HOMEPATH%\Windows\Fonts works. (For most users the folder is C:\Users\%USERNAME%\Windows\Fonts.) Why does this only happen when IE9 outlook 2003 internet 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 > Preferences > Email Options. Enable the option to Read All Standard Mail in Plain Text. With this option enabled, all mail is rendered in plain text format. You can switch an HTML message to render as HTML