Problem with SQL Mail and Oulook 2003

Here try this. Outlook 2003 and SQL 2000 SP3.
Open Outlook 2003. Then go to SQL Server Manager and browse to where the
settings are for SQL Mail. Make sure the MAPI profile you choose there is
the MAPI profile you used to sign into Outlook 2003. Then Test the SQL Mail
by clicking Test. You should get a MAPI session was initialized. Then
close out of SQL Server Manager. Bring up Outlook 2003 and close it. Now
try to start Outlook 2003. You will get an error that the Outlook folders
could not be initialized and Outlook 2003 will shut down. The only way to
fix this is to stop the MSSQL services. Then you will be able to open
Outlook 2003.
George Hester
_________________________________> The only way to

quote:

---

> fix this is to stop the MSSQL services. Then you will be able to open
> Outlook 2003.

---

Or to use a different profile.
Or to not use a SQL Server machine for reading client e-mail (is it a
server, or a desktop? you need to pick one...).
Or to use a different solution for e-mail within SQL Server (e.g. avoid MAPI
altogether).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Or to fix the SQL Mail so that it releases the MAPI session when it =
finishes? Doesn't that sound like a reasonable expectation?
--=20
George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =
news:ebcRGeM2DHA.2208@.TK2MSFTNGP12.phx.gbl...

quote:

---

open[QUOTE]
>=20
> Or to use a different profile.
>=20
> Or to not use a SQL Server machine for reading client e-mail (is it a
> server, or a desktop? you need to pick one...).
>=20
> Or to use a different solution for e-mail within SQL Server (e.g. =

---

avoid MAPI

quote:

---

> altogether).
>=20
> --=20
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>=20
>

---

|||>> Or to fix the SQL Mail so that it releases the MAPI session when it
finishes? Doesn't that sound like a reasonable expectation?
A little more work involved there, than the changes I proposed to your
strategy (seeing as this clearly doesn't affect a large number of
customers).
Frankly, I'd rather they focus their attention on Yukon than tending to
onesy-twosy "bugs" where people aren't using the software as intended
anyway...
A|||Oh well I suppose I am the only person in the world who thinks it would be a
good idea for SQL Mail to release the MAPI session when it finishes. Too
bad huh?
George Hester
_________________________________
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:esQrocV2DHA.2308@.TK2MSFTNGP11.phx.gbl...

quote:

---

> finishes? Doesn't that sound like a reasonable expectation?
> A little more work involved there, than the changes I proposed to your
> strategy (seeing as this clearly doesn't affect a large number of
> customers).
> Frankly, I'd rather they focus their attention on Yukon than tending to
> onesy-twosy "bugs" where people aren't using the software as intended
> anyway...
> A
>

---

Problem with SQL Mail and Oulook 2003

Here try this. Outlook 2003 and SQL 2000 SP3.
Open Outlook 2003. Then go to SQL Server Manager and browse to where the
settings are for SQL Mail. Make sure the MAPI profile you choose there is
the MAPI profile you used to sign into Outlook 2003. Then Test the SQL Mail
by clicking Test. You should get a MAPI session was initialized. Then
close out of SQL Server Manager. Bring up Outlook 2003 and close it. Now
try to start Outlook 2003. You will get an error that the Outlook folders
could not be initialized and Outlook 2003 will shut down. The only way to
fix this is to stop the MSSQL services. Then you will be able to open
Outlook 2003.
--
George Hester
_________________________________> The only way to
> fix this is to stop the MSSQL services. Then you will be able to open
> Outlook 2003.
Or to use a different profile.
Or to not use a SQL Server machine for reading client e-mail (is it a
server, or a desktop? you need to pick one...).
Or to use a different solution for e-mail within SQL Server (e.g. avoid MAPI
altogether).
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Or to fix the SQL Mail so that it releases the MAPI session when it =finishes? Doesn't that sound like a reasonable expectation?
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:ebcRGeM2DHA.2208@.TK2MSFTNGP12.phx.gbl...
> > The only way to
> > fix this is to stop the MSSQL services. Then you will be able to =open
> > Outlook 2003.
> > Or to use a different profile.
> > Or to not use a SQL Server machine for reading client e-mail (is it a
> server, or a desktop? you need to pick one...).
> > Or to use a different solution for e-mail within SQL Server (e.g. =avoid MAPI
> altogether).
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||>> Or to fix the SQL Mail so that it releases the MAPI session when it
finishes? Doesn't that sound like a reasonable expectation?
A little more work involved there, than the changes I proposed to your
strategy (seeing as this clearly doesn't affect a large number of
customers).
Frankly, I'd rather they focus their attention on Yukon than tending to
onesy-twosy "bugs" where people aren't using the software as intended
anyway...
A|||Oh well I suppose I am the only person in the world who thinks it would be a
good idea for SQL Mail to release the MAPI session when it finishes. Too
bad huh?
--
George Hester
_________________________________
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:esQrocV2DHA.2308@.TK2MSFTNGP11.phx.gbl...
> >> Or to fix the SQL Mail so that it releases the MAPI session when it
> finishes? Doesn't that sound like a reasonable expectation?
> A little more work involved there, than the changes I proposed to your
> strategy (seeing as this clearly doesn't affect a large number of
> customers).
> Frankly, I'd rather they focus their attention on Yukon than tending to
> onesy-twosy "bugs" where people aren't using the software as intended
> anyway...
> A
>sql

problem with sql mail

i have configured sql mail to send emails to outlook with exchange server
running with outlook ... but the problem iam facing is that although the
option of "sent messages to the sent items folder " is cliecked under the
sql agent mail and also in the outlook but still any mail that goes through
sql mail is delivered successfully to the recipient but does not go the sent
items folder of outlook
would appreciate any help on this thnaksIf you are running SQL Server 2000, SQL Mail for SQL Server
2000 does not save a copy of sent messages in the Sent Items
folder. If you need a copy of the messages, you need to cc:
them to an exchange account and create an Outlook message
rule that routes these message copies to the Sent Items
folder.
For more info, refer to:
INF: Common SQL Mail Problems
http://support.microsoft.com/?scid=315886
The section: Q7: Why do I not have any sent messages in the
Sent Items folder explains this issue.
-Sue
On Sun, 7 Mar 2004 15:09:13 +1100, "afsheen"
<afsheenj@.hotmial.com> wrote:

>i have configured sql mail to send emails to outlook with exchange server
>running with outlook ... but the problem iam facing is that although the
>option of "sent messages to the sent items folder " is cliecked under the
>sql agent mail and also in the outlook but still any mail that goes through
>sql mail is delivered successfully to the recipient but does not go the sen
t
>items folder of outlook
>would appreciate any help on this thnaks
>

Problem with Outlook BCM database upgrade

I upgraded from Office 2003 to 2007 beta, and now I have the problem that I cannot use my Outlook BCM database. At starting up, Outlook offers to upgrade that database on my PC, than asks to back it up. That backup always fails, and I even cannot open a new database. Is this a known issue? I had it also when upgrading Outlook 2003 to SP1, but then I could make a new database.I have the same problem to...
somebody knows the answer?