Email error - InfoPath Dev
in

InfoPath Dev

Email error

Last post 03-15-2007 08:12 AM by Clay Fox. 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • 03-02-2007 10:24 AM

    Email error

    Hello, I posted this originally to the Newbie forum but didn't get much response there and thought this forum would help me more.

    I am new to Infopath 2003. I have Outlook 2003 and am using Infopath 2003 with SharePoint. I created a form on one Sharepoint site which allowed me to email the form. I copied the form over, using the publish form wizard to another SharePoint site using the same computer. Everything (data source lookups) worked in the new SharePoint site but the email. Now I get an error "To use this feature, Microsoft Office Outlook 2003 must be set as the default e-mail program." Is there a setting that changed?

    Please help.
    Thank you.
    cvinfo1
  • 03-02-2007 11:54 AM In reply to

    I have not experienced this, and I always expected that the Outlook requirement as a client-side requirement, but I'm wondering if it is complaining about the server that SP is installed on--whether that server is expected to have Outlook installed and set as the default client... something to look into anyway.
  • 03-02-2007 12:00 PM In reply to

    Thank you Greg for replying. This looks like the culprit based on how our organization is. The mother org uses Lotus Notes. I'll look into that. Thanks!
  • 03-02-2007 12:34 PM In reply to

    Great! Let us know if that was the issue. I'm curious to find out whether IP expects the hosting server to have Outlook installed as the default email client.
  • 03-03-2007 10:26 AM In reply to

    Hi,

    I am still waiting to find out about th SP server email client inquiry from our IT team. In the meantime, I need a workaround in place to get this to our users. So, I tried this. I noticed that when I removed the data connections and ran from my computer I had no problems (obviously no SP used). But I have a SP list I need to use on the form as a data source for one of the fields. When I set a button to query a data connection it queries fine but after that I can't email. Is there a way to stop the data connection after it queries so that I can email after this query is done?

    Thanks.
  • 03-03-2007 02:15 PM In reply to

    I'm not sure how to answer that. Does someone else want to jump in here with a suggestion?
  • 03-15-2007 07:13 AM In reply to

    My IT team finally replied to this and really I am now at a loss. They state "Once the form is filled out, I believe it will be sent using the customer's local mail settings, not the server, because it's using an instance of Infopath local to the customer. There's not much we can do...

    FYI - Our Sharepoint server sends email via SMTP. SMTP mail is handled by mailoutbound.uhc.com. Servers do not use Outlook or Notes for sending email."

    Then why is that when I use the Infopath form stand alone it works fine but when I put it out on SharePoint it gets the error???

    Please help.

    Thanks.
  • 03-15-2007 08:12 AM In reply to

    To my knowledge the Mail Data Connection is all client side. When the connection runs it looks to interact with Outllok, the default mail client, to give it the To, Subject, Attachment, Body, in the same way that a mailto html link would. I would have to think that SharePoint is not the culprit but that it has something to do with the client setup and whether it is reporting Outlook as the default mail client. It may be that previewed and published forms behave a bit differently or something else is going on with the client where the default mail client is switching or something with Internet Explorer, which is where the default is set, Tools -> Internet Options -> Programs. You may want to check this through the troubleshooting process to see if this is set correctly and remains correct. I think this is where it is breaking down and is probably not really an InfoPath issue but more on the client side. It may have something to do with you corporate mail/client setups or your individual machine. I am assuming you have tried it on several other client machines witht he same result.

    Let us know.
Page 1 of 1 (8 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.