Outlook 2003 does not work with SQL Mail !

It would appear that Outlook 2003 (and 2002) does not work with SQL Mail,
unless you are using an Exchange Server. The SQL Mail program and Outlook
2003 *BOTH* try to open the Personal Folder file (.pst file) and one of them
fails.
If I close the Outlook 2003 client, SQL Mail works fine, except that the
mail does not go out! The mail only goes out when the Outlook client is
running and since the .pst file is locked, it only runs when SQL Mail is
disabled!
So I can't generate email alerts in SQL unless I close down Outlook and I
can't get those alerts to go out unless I disable SQL Mail. What a crappy
setup! ... or am I missing something?
No you are not. That is the way it is. If you want trouble free SQL Mail
with Outlook you must use Outlook 2000. Otherwise you will run into Access
denied erros in the MAPI subsystem. That is because SQL Mail does not
release MAPI. You have to shut down the SQL Server Service. Fire up
Outlook then restart the SQL Service but as soon as SQL Mail acts once you
will be right back to the MAPI access deniied errors.
George Hester
_________________________________
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:6866961B-7F29-443E-B6D3-132E20B66E95@.microsoft.com...
> It would appear that Outlook 2003 (and 2002) does not work with SQL Mail,
> unless you are using an Exchange Server. The SQL Mail program and Outlook
> 2003 *BOTH* try to open the Personal Folder file (.pst file) and one of
them
> fails.
> If I close the Outlook 2003 client, SQL Mail works fine, except that the
> mail does not go out! The mail only goes out when the Outlook client is
> running and since the .pst file is locked, it only runs when SQL Mail is
> disabled!
> So I can't generate email alerts in SQL unless I close down Outlook and I
> can't get those alerts to go out unless I disable SQL Mail. What a crappy
> setup! ... or am I missing something?
>
|||Actually there is a workaround for this issue. Let me know if you want to
hear how it is done and I can explain it to you.
George Hester
_________________________________
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:6866961B-7F29-443E-B6D3-132E20B66E95@.microsoft.com...
> It would appear that Outlook 2003 (and 2002) does not work with SQL Mail,
> unless you are using an Exchange Server. The SQL Mail program and Outlook
> 2003 *BOTH* try to open the Personal Folder file (.pst file) and one of
them
> fails.
> If I close the Outlook 2003 client, SQL Mail works fine, except that the
> mail does not go out! The mail only goes out when the Outlook client is
> running and since the .pst file is locked, it only runs when SQL Mail is
> disabled!
> So I can't generate email alerts in SQL unless I close down Outlook and I
> can't get those alerts to go out unless I disable SQL Mail. What a crappy
> setup! ... or am I missing something?
>
|||Yes, let me know what the workaround is!
Fred
"George Hester" wrote:

> Actually there is a workaround for this issue. Let me know if you want to
> hear how it is done and I can explain it to you.
> --
> George Hester
> _________________________________
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:6866961B-7F29-443E-B6D3-132E20B66E95@.microsoft.com...
> them
>
|||OK. What you do is set 2 Profiles in Microsoft Outlook. You will get your
eMail in one profile and the other will receive your SQL Alerts. The SQL
Mail holds on to the MAPI service. This is the reason for the error. So if
you start Outlook with your SQL Mail profile before SQL Mail starts then
start SQL Mail you will get your alerts. You can then close Outlook and go
back into your eMail Profile. But you cannot reopen Outlook with the SQL
Mail profile while SQL Mail is using that profile, running. You have to
stop SQL Mail then go into the SQL Mail Profile with Outlook then restart
SQL Mail.
George Hester
_________________________________
"fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
news:30265F89-8F2B-4296-8CDA-C577B9AEE5E7@.microsoft.com...[vbcol=seagreen]
> Yes, let me know what the workaround is!
>
> Fred
> "George Hester" wrote:
to[vbcol=seagreen]
Mail,[vbcol=seagreen]
Outlook[vbcol=seagreen]
of[vbcol=seagreen]
the[vbcol=seagreen]
is[vbcol=seagreen]
is[vbcol=seagreen]
and I[vbcol=seagreen]
crappy[vbcol=seagreen]
|||Sorry George, you lost me there. The problem I have with Outlook 2003 and SQL
alerts is that the SQL alerts are generated, but don't go out unless Outlook
is running.
I am not sure how having two mail profiles will help. I have tried setting
up an Outlook email profile (say OutlookMail) and a SQL email profile (say
SQLMail). If I then set up SQL Alerts to use the SQLMail profile and launch
Outlook using the OutlooMail profile, everything works, *except* that the
alerts are generated, but don't go out!
Just having Outlook running (with the OutlookMail profile) does not seem to
help the SQL alerts. They are not going out, because the SQLMail profile's
mailbox (.pst file) is not being processed, only the OutlookMail mailbox is.
Did I miss something? I even tried setting up the OutlookMail profile in
Outlook to read and process the SQLMail profile's mail file, but that did not
work either.
Help !!
"George Hester" wrote:

> OK. What you do is set 2 Profiles in Microsoft Outlook. You will get your
> eMail in one profile and the other will receive your SQL Alerts. The SQL
> Mail holds on to the MAPI service. This is the reason for the error. So if
> you start Outlook with your SQL Mail profile before SQL Mail starts then
> start SQL Mail you will get your alerts. You can then close Outlook and go
> back into your eMail Profile. But you cannot reopen Outlook with the SQL
> Mail profile while SQL Mail is using that profile, running. You have to
> stop SQL Mail then go into the SQL Mail Profile with Outlook then restart
> SQL Mail.
> --
> George Hester
> _________________________________
> "fredscuba" <fredscuba@.discussions.microsoft.com> wrote in message
> news:30265F89-8F2B-4296-8CDA-C577B9AEE5E7@.microsoft.com...
> to
> Mail,
> Outlook
> of
> the
> is
> is
> and I
> crappy
>