[THIN] Re: Outlook 2003 .msg Files

  • From: "JAlexander" <jalexander@xxxxxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Wed, 17 Oct 2007 14:56:43 -0400

yep -- there is a "%"... I created another published Outlook without the "%", 
assigned the .msg redirection to that published app, did an app refresh and 
then tried to open a .msg but it returned the same error.  The published app 
runs:

"C:\Program Files\Microsoft Office\OFFICE11\OUTLOOK.EXE" "%*"
  ----- Original Message ----- 
  From: Joe Shonk 
  To: thin@xxxxxxxxxxxxx 
  Sent: Wednesday, October 17, 2007 1:43 PM
  Subject: [THIN] Re: Outlook 2003 .msg Files


  What line are you using to publish the app?  Are you putting a "%*" after 
c:\program files\office11\outlook.exe?

   

  From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf 
Of JAlexander
  Sent: Wednesday, October 17, 2007 10:38 AM
  To: thin@xxxxxxxxxxxxx
  Subject: [THIN] Outlook 2003 .msg Files

   

  Hi all.  I'm running PS4.5 Platinum on Windows 2003 server and using PNAgent 
with Content Redirection.  Outlook 2003 is a published app and the content 
redirection is set to open .msg files with Outlook 2003.

   

  When a user (or an admin for that matter) attempts to open a .msg file, 
Outlook appears to open and then pops up with "Cannot start Microsoft Office 
Outlook.  The command line argument is not valid.  Verify the switch you are 
using."

   

  When Outlook is already running, attempts to open the .msg file returns "The 
command line argument is not valid.  Verify the switch you are using."  I have 
searched high and low and the only documentation I find on this error is from 
2004 in reference to Metaframe XP.  The end result was to apply a Citrix 
service pack.  There is a reg key referenced in that article re: the mailto 
setting but that setting is correctly set to open Outlook.


  I tried a another published version of Outlook without any switches but I get 
the same message.

   

  Has anyone else experienced this?

   

  Thanks for any input.

   

   

Other related posts: