SP3 problem - command line argument is not valid. Verify the switc

[Guest]

After installing Service Pack 3, my Scan-to-Email function on my Brother
MFC-8860DN scanner now generates an error message from Outlook:

"The command line argument is not valid. Verify the switch you are using."

Did not have any problems with this until SP3 was installed. Brother isn't
touching the issue - they are referring everyone to Microsoft. I haven't let
them off the hook entirely - after all, they should at least tell me what
switch it is they're using (and disable it), but clearly something was
disabled in SP3.

I know others are having this problem - anyone discovered a workaround
(other than scanning to file instead?)

 

[Roady [MVP]]

Apparently their application is not compatible with Outlook 2003 SP3.

My guess is that they are generating a "mailto:" command with an "attach" or
"attachment" switch which isn't RFC compliant in the first place. Outlook
2003 pre-SP3 offered a custom Microsoft protocol extension for attachment
support on the mailto protocol but has now implemented a fully RFC compliant
mailto protocol.

I suggest that they either implement the outlook.exe /a command line to
directly attach an item or even better; use the OOM to do it
programmatically.

 

[Guest]

Thanks for the reply. When I initially contacted Brother I got the runaround
with "Contact Microsoft." But I told them I wanted to talk with someone else
about it, and they set it up to have their software guys call me today.

We had a meaningful discussion about it today. Armed with your reply, I
actually sounded like I knew what I was talking about. The tech informed me
that they were already aware of the problem and that they were working on a
patch to correct it. Which of course, begs the question - why aren't they
having their first line support personnel explain that to the people that
call in? A classic case of two hands not knowing what the others are doing.
If they had simply told me that in the first place, I would have been content
to wait for the patch.

Appreciate the information.

-Scott

 

[Roady [MVP]]

You're welcome!

Thanks for the reply. When I initially contacted Brother I got the
runaround
with "Contact Microsoft." But I told them I wanted to talk with someone
else
about it, and they set it up to have their software guys call me today.

We had a meaningful discussion about it today. Armed with your reply, I
actually sounded like I knew what I was talking about. The tech informed
me
that they were already aware of the problem and that they were working on
a
patch to correct it. Which of course, begs the question - why aren't they
having their first line support personnel explain that to the people that
call in? A classic case of two hands not knowing what the others are
doing.
If they had simply told me that in the first place, I would have been
content
to wait for the patch.

Appreciate the information.

-Scott

 

[Guest]

Same problem here. A pertinent Kbase article might be:

http://support.microsoft.com/kb/823923

I'm going to try backing the Office SP3 update out since that's easier on
the affected users.

Cheers.


Chris