http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D= sql
and got it working nicely. I would like to elaborate on this. Rather = then sending a succeed registration page to the client I would like to = send them a page telling them an email has been sent to their e-mail = address. That part of it I can do. My trouble is once I generate a = password for the client I need to let SQL 2000 SP3 know it's time to = send them an e-mail. Is this a trigger? Can anyone suggest what = applications I might need to do this (except Exchange) and some = guidelines on how this can be done? Thanks.
I cannot use Exchange for this as I have Outlook 2003 installed and it = is not supported on the same server where Exchange 2003 is installed. I = only have the one Server Windows 2000 SP3.
-- George Hester
__________________________________Assuming you are using a stored procedure to generate the password, you can
send an e-mail from the stored procedure (I really don't recommend doing
this in a trigger). You can see some information about sending e-mail from
SQL Server at http://www.aspfaq.com/2403
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
I was following this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;247931&Product=sql
and got it working nicely. I would like to elaborate on this. Rather then
sending a succeed registration page to the client I would like to send them
a page telling them an email has been sent to their e-mail address. That
part of it I can do. My trouble is once I generate a password for the
client I need to let SQL 2000 SP3 know it's time to send them an e-mail. Is
this a trigger? Can anyone suggest what applications I might need to do
this (except Exchange) and some guidelines on how this can be done? Thanks.
I cannot use Exchange for this as I have Outlook 2003 installed and it is
not supported on the same server where Exchange 2003 is installed. I only
have the one Server Windows 2000 SP3.
--
George Hester
__________________________________|||Hi Aaron:
Can you believe it? I got the SQL Mail setup and it seems to be =working. Using my ISPs SMTP server. I did the test and it connected to =the MAPI profile successfully. Anyway I proceeded to use the extended =stored procedure xp_sendmail in Query Analyzer:
xp_sendmail @.recipients =3D 'hesterloli@.hotmail.com',
@.message =3D 'Hello',
@.subject =3D 'From SQL Server 2000'
Actually I sent one to that address and one to my POP3 account. Both =successfully as reported by Query Analyzer.
But I forgot to have Outlook 2003 open before I did that. So to see if =I got the mail I went to open Outlook 2003. Know what happened? =Outlook 2003 could not open. I use MAPI profiles and when I tried to =start Outlook 2003 the Error message I got was, "The service could not =be started." No offer to start in safe mode. Just the error message =box. I post it next time if I can replicate the issue again.
All I know is that it sounds like some dll went belly-up. I rebooted =and Outlook 2003 was fine and there were the two e-mails from SQL in =Outlook 2003 and Outlook Express which handles my Hotmail account.
Now I don't know what to do. I could try the xp_sendmail again with =Outlook 2003 open and see if that avoids the issue. But I just don't =know. Ever heard of this before?
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> Assuming you are using a stored procedure to generate the password, =you can
> send an e-mail from the stored procedure (I really don't recommend =doing
> this in a trigger). You can see some information about sending e-mail =from
> SQL Server at http://www.aspfaq.com/2403
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> > > > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> I was following this article:
> > =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
> > and got it working nicely. I would like to elaborate on this. Rather =then
> sending a succeed registration page to the client I would like to send =them
> a page telling them an email has been sent to their e-mail address. =That
> part of it I can do. My trouble is once I generate a password for the
> client I need to let SQL 2000 SP3 know it's time to send them an =e-mail. Is
> this a trigger? Can anyone suggest what applications I might need to =do
> this (except Exchange) and some guidelines on how this can be done? =Thanks.
> > I cannot use Exchange for this as I have Outlook 2003 installed and it =is
> not supported on the same server where Exchange 2003 is installed. I =only
> have the one Server Windows 2000 SP3.
> > -- > George Hester
> __________________________________
> >|||This is a multi-part message in MIME format.
--=_NextPart_000_000F_01C3C2BA.A0DC3EC0
Content-Type: multipart/alternative;
boundary="--=_NextPart_001_0010_01C3C2BA.A0DDC560"
--=_NextPart_001_0010_01C3C2BA.A0DDC560
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
That's the strangest thing. I use xp_sendmail in Query Analyzer send =the mail to myself at my ISP. And the mail goes into my Inbox. Yes =that's right. Not my Outbox. But my Inbox. I saw an unsent mail there =so deleted it. Tried xp_sendmail again and sure enough there it was =ahgain in my Inbox. But as I was writng this it flew out of my Inbox =for destinations unknown. I suspect it will come back to me. Oh and =Outlook 2003 seems to have survived. I need to close it down and =re-open it to be sure...Nope it is dead dead dead. No error this time =but it won't start. Ah there it was in Task Manager. Let me end the =process and try again... well here's the error:
Got to reboot again. See ya...
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> Assuming you are using a stored procedure to generate the password, =you can
> send an e-mail from the stored procedure (I really don't recommend =doing
> this in a trigger). You can see some information about sending e-mail =from
> SQL Server at http://www.aspfaq.com/2403
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> > > > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> I was following this article:
> > =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
> > and got it working nicely. I would like to elaborate on this. Rather =then
> sending a succeed registration page to the client I would like to send =them
> a page telling them an email has been sent to their e-mail address. =That
> part of it I can do. My trouble is once I generate a password for the
> client I need to let SQL 2000 SP3 know it's time to send them an =e-mail. Is
> this a trigger? Can anyone suggest what applications I might need to =do
> this (except Exchange) and some guidelines on how this can be done? =Thanks.
> > I cannot use Exchange for this as I have Outlook 2003 installed and it =is
> not supported on the same server where Exchange 2003 is installed. I =only
> have the one Server Windows 2000 SP3.
> > -- > George Hester
> __________________________________
> >
--=_NextPart_001_0010_01C3C2BA.A0DDC560
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
That's the strangest thing. I use =xp_sendmail in Query Analyzer send the mail to myself at my ISP. And the mail =goes into my Inbox. Yes that's right. Not my Outbox. But my =Inbox. I saw an unsent mail there so deleted it. Tried =xp_sendmail again and sure enough there it was ahgain in my Inbox. But as I =was writng this it flew out of my Inbox for destinations unknown. I suspect =it will come back to me. Oh and Outlook 2003 seems to have survived. =I need to close it down and re-open it to be sure...Nope it is dead dead =dead. No error this time but it won't start. Ah there it was in Task =Manager. Let me end the process and try again... well here's the =error:
Got to reboot again. See =ya...
-- George Hester__________________________________
"Aaron Bertrand [MVP]" wrote in message news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...> =Assuming you are using a stored procedure to generate the password, you can> send =an e-mail from the stored procedure (I really don't recommend doing> =this in a trigger). You can see some information about sending e-mail =from> SQL Server at > > -- > Aaron Bertrand> SQL Server MVP> => > > > > "George Hester"
--=_NextPart_001_0010_01C3C2BA.A0DDC560--
--=_NextPart_000_000F_01C3C2BA.A0DC3EC0
Content-Type: image/gif;
name="outlookerror07.gif"
Content-Transfer-Encoding: base64
Content-ID: <000a01c3c2e4$89a91f00$c673c318@.hesterloli.com>
R0lGODlh7AF+AAAAACwAAAAA7AF+AIYAAABAQEABBHwAAX4AAn4AAH8AAIABA30AA34BBH0BBXwB
BnsBBnwCCHoBB3sCB3sCCHsDC3gDDHgEDnYDDXcDDXgDDncEDncED3YEEHUEEHYCCXkCCXoCCnkD
CnkDC3kGGHAGGXAHGXAHGm8HGnAHG24HHG4IHG4HG28IH2wIIGwIHW0IHW4IHm0IH20JIGsJIGwE
EXQEEXUFEnQFE3MFE3QFFHMFFXIGFXIGFnEGFnIFFXMGF3EGGHEJImoJIWsJImsJI2oKJGqAAACA
gIAAAP8A/wD/AAD//wDU0Mj///8AUkAAAAAAAABSQAAAAAAAAAAAAEBAQEBAQEBAQEBACgAAAAAA
AAAAAFJAAAAAAAAAUkAAAAAAAAAAAABAQEBAQEBAQEBAQAoAAAAAAAAAAABSQAAAAAAAAFJAAAAA
AAAAAAAAQEBAQEBAQEBAQEAKAAAAAAAAAAAAUkAAAAAAAABSQAAAAAAAAAAAAEBAQEBAQEBAQEBA
CgAAAAAAAAAH/4BJgoOEhYaHiImKi4yNjo+QkZKTlJWWl5iZmpucnZ6aAUlKo6SlpqeoqaqrrK2u
r7CxsrO0tba3uLm6u7y9vr+5RKFKn8XGx8jJysvMzc7P0IfCoklC1tfY2dhB3N3e3+Dh4t4w5ebm
Kenq6+zt7u/rJvLz9CX29/j5+vYk/f7/AAMG5EGwoMGDCBMm3MGDocOGEB3SmEijhsWLGDNq3Mix
44WPIEOKFGmhpMmTKEtWWMmyJcsIMGPKnEmzps2bMSFEeMCzp8+fQIMKHfrzgNGjSJMqXWrUwAGn
UJ9KjQrVgNWrWLNmTTKNmLav2saJDXKurNly6ciehQGvrdt0KP/iyo1Lr64JfgLz/iuhdyAJHn8D
Ax6ssLBhhDsSJ66xg7HjxjV4UKzYsbJlixdqfNScuYKGCppDZx4teuSFlKhPuly9EqdrmhBiy55N
VDbR27h7HnhggLfv3sAfMB1OvKnW41mfIl9uleuwamCjCxlLvTq3FEFSrH3LPQUK7+C/iw9vd969
8vL28ePbF+BgwYIPF1RMv779+/gXT77sUbT/zKEFmJkGBFZg2oEhpaYga6u95iBMOkUYgYQUTmih
bbnhttuGwnXYYW8I+BYiiMQBR9VUKJ6oYorKWQVLAM11BV10ANQIwDbWfbPWjtjtyFZbMIwnZHjv
xOXCXOilx17/ewEtySR87+0Qn3wMyYdYfvRFth9/XGZEGmkEEvjfmKYpmBqDLtFUAQRrtlnhmxPO
JuecdGZop1C7iahnb0z91hSLJ7bInFbKEcOIMDE+Z82N2tjoqDU5ggNpdTBkZxYpbqHlHQyYYpoC
CZ+Gh0KQR5JX3nnolTBKPiQ4+c8oAr0HmA4k0GolQTvogOWuvDZGUZcaDRjmsJiNCVqBCCZrJmpo
tlRTBRG0+YEHHlxoLZzYXhvnnT2F6O0DI/7mW54g+qYnAiXy1pS4wAHqropXGboIogY4R801N9Yo
RL5HHAGAEUYwGsQo3xBMMDg+npWdWuaMUs4o7piSDsQpUEzx/zqjonBkkHTJY8pdrpIAa6sj+8NX
yCIr4dd7tbb8l5U6xCzzzDQf1Gtjkv0KLJcakFlDmD5/WeayKDX7kpoQfFDBB0xf6OaaF9IpdZ3c
PgABAldffVtv4CLg7bd89tnuioEOilyhg9RIiNrOJXqvEEfgi2+//wYMKSnd4C3WpGNVip12DSvx
sBLtXAyxxYRjHB4LjDfOuHcmjDLPqvbUtSrJSuDT6uYBlfyPrC3TaiuVNJc+88321aDzzsUOS2yx
X/6MbLIHEl200dA+y/TuH2jLJoVPZ0shBFWDG5vx3ybvU7led+3tcMFFzy6g6pI9VbxrAyAI223X
K+M1cfcL9/++Q9ho93SlDIz3wek7LDinpAQOsfoOwy94KesYTninhydeCgsoKIV4PKaEyWVuZKsq
hapUlrLLNZCBCGQg6ETXsluZ7oI265WWVse6yvQsdsISEwj/MxLbqQZ3SONd0yLkpmtN7YUY4lbW
sKa8b/GEa177GrjGJbbqvUsqgjLbVdCWPe51z15e2Rf48OUofaGPfkpQnxQPxo32RXGKVyRL/dz3
voupQ38V858Yw6iOAI4RVGY04AJLELkDZg5za1xjBFNGR3+wLHQVJN0FS4e6+qhuIh1snevEBDv/
hMlAtBuaCS2Au9zNpAIeUGHvgPc731nyTcSrGtZ4QsMdKq//JyBKAAISIMrmoYspY2OXn6zHSkHJ
K23aIwS9kDijfOVrX0UoAgCQgASBXZF9UTRYFqVYKYdh0ZhbvF8XE5c/ZvZvYmP04ilSYAIUtFGN
sJJjAeGYzQRCUGWl+Bx8KDg6+eyxdBnk1QYBGUgP+gxoIxRaCRfJSBTSJJIqdBq2YAjD4s1QazUE
JSdJSVBR8nApq/yhU4IoxKq8MgmOkiWMvKcoIRRBbovK5S57eTdwCFOKeYtiMUVKMPsFc5nwG1zh
nLm/MZIRYmi82HdIQEBsvtGbJ8NpyhbYD1iFU5yA6Qc5X3aYXJ3zdH1UzB8p08EQuu4iIzxkIhVp
wkbaRJKT/5xQ8PTZQuFtS5OZ7GRABTrKghr0lEuRnlp9SBW2vgt7sNxeLI/4PWtcNJcW3ZcBbMTR
JxbspCCtokjVN1KyCJawKU3mSr/YUmg6lmLfGUVcQmVAm3Jzm9q8bE/ByVk7jhOPFjyqzNK5q3Uy
tZ0b+eCYiBXP0pCEnlalCVa1Kjx+vtCfNASoJ3d4w4GaNVzDSWgrGSpEIkJ0rscVxCzryqi8LqqJ
vvQoYKFITC3izaQLK8Xg0OIpxnoKcY4NI8TMiCmaEpAUIDMFX0ixxgey56dz7Mcdh2olo4pWV0nV
DzubKrtBQnW1s5tqgmBrT9lKkrZb9Wpti7dJ5O3Whr0ta/9Bn4fK6qlybAp9q4sasdyKKlFft8SG
wCJFDsNWihuVOjGKF8aj7pTxxUX6jjpAlSSQac4ErVrP5jSHsrxMELQwu68OSIsl06K2I6qNHTyD
xpl5LjK2M5mtgm07NdzO8MG8NZeECQrcHrYyKsQ1m3EV0eG3iVg6fCOxiU2cYob5zVLb4c54wAMX
8IDqxXMJlTVPhZe5oKAfJ+McoJ8EVH/QV4/3za9+T7szp77unQEW8EfoWU+jXfXAv0swgis5ZQaH
VbefjLBZzwq9C09PRW4lW7yIwOpWu9rVE6UlmsGiZhQLoc24NuyKexRnIGVMO7/+dZ3Fo7HJojFJ
9vCzXHD/HOiT6ZjQP6ZgaO9L5PwY+ciphbQImUxV20FZJlK+ZJyoTDUZ5jagIeotuEbdZYRieLgN
TY5VAkDvetv73rGu66yzUWtb5xrX5VgY4M7ylnJkjC0HD3YZWRAkjpnKLvxQtlx2LOge62W+QC6q
kPGb36W209FAKySYIi1pSn8b3JgOHtQUfMlMcqvBYsUyWdkNrlJDxdRfVmi8tSLrffO73zC49Zpz
bVheEzxTv274qFwQJDp/x3GjAmDHTlVNiaOg2TsONLQ/K+0gU9sgN7s2tjOSZENuu7W1I7ClDZzP
KZN7TlaOeahxSPOwuTvV7grzoPQ+KFpG4++AD7zgB0/4/8Ib/vDKfQ7iF8/4xjv+8ZCP/CZkJPnK
W/7ymM+85otB+c17/vOgD73oG9/50Zv+9KhPveopUfrVu/71sI/95lsv+9rb/va4hwbtc8/73vv+
95HYPfCHT/zi5174xk++8pcveuQz//nQjz7pFS/96lv/+oJ3fiOGwP3ucx/74A+/+Aeh/UR0v1/o
R3/3x8/+9i+//IcYQvrnP/8huF8RRmwE2/LvCeQmwv+Z4H8AKHgDGID6twkFSAkJ2H8LmHjUAAnc
R38SqH72h4A2YoD4d4CFwD1q04CQMFcFeIHbkzYk+IH8V4IQpYH/tzYqOIIruAwgaIIJGIOM4IEo
iAg2+P9/EZWDi+CBOQh/gyB/EziE/VKBmMCDjtCANgiAHIiEKjiANEiDkiCFG3iDL3iFKViDVYiF
yECFPWiFKLiECHiEYDgJPugIQJgEQkiERGiElQCF+yeCESVXsSSCsKQ9crh/KWiHe9iHddiBWWiH
efiHeGhEAnhchYiHdLiILMiCMXiBhHiHLhiCjiiIcaiHiLiBl2gIgwiClyiAHWiJh+iIJAiJjJiJ
gdiIdbiHohiJqZiFOHiHnsiEm4iKkmiLiZCGa8iGEzgERHAJC6iII/iIpciJjViFmEiKiiiMcuWC
fRiGsMiEyAiNyEWFh0iMw1iM2TiDpOiM2biNNyiF1aj/jc9YjuPojMx4juSYjtHYjsw4ieD4jeb4
isFIjeF4jO+IjrA4L9S3CLvYL0pAhAFZf7/4hoewg+vojpxojabojfDoh/hYiuLYjluYkPKIiIY4
jfLIjo9YjxaJkNs4h/rojdjIig25jxPZRMe4kQrJkvy3jBDpksUIk1fYkXzYhCdpjxzWj+ZHf6Qw
gT9Zf5YgjTJZlAtJkfO4hav4jhPZjCVJlBZZjvu4kvP4lArJjQlplfkIjSSZlRWpjiVZkUbJkTM5
jTCplWW5lRF5kUc5ihH5gzyJCP9oCj5ZCgQ5lF/ZklW5gikJhteIklw5lgdZgn0ZmCOJlkW5iitJ
ljJp/42GiZhJOZKReZhemZh5uZcsiZRQqJNTaZScyY8P6I91GZQAaZcEWZAK2Il66YrJdYutCZLN
aIXCmJODeIvVSItNGYi1qIm3GYe6OYv6iJuK+ZuJqJh8GJvHiYoiKYeyyY646JoY6ZSnyJxdCY9R
WJuSuZmHmX+iGFdF5JC5GJeG8I/oR5dHYJ7054v3t54GyZ6PV37kWZ6qMITq6Z72mYT3OX2h2ZND
mAptyGr5GaACWnnwyYanwIa+iJoDuqAMWngFKpDo2YsAaobaWYad4JYKSID4CXwVCp6w54TOcILS
IJ6FEJ/yeaD0OaGRgJUWygkYqoViGQ0hCJt/B6It+v8IavmiPZicg9mCysCiVNmZPYqfSPigErgK
KaqgOMqFNrqiMfqFT/oMHimkldekxnilNxqlGeijyWClWeqhUIqGJEoIJmqeEZp+CUqhrkiIa/qb
vMmI2CiS0QmnhtidbzqnymmneDqky/mStUiTbiqVrImn2GmbhKmHa0qdPOqhqpmnwHmThzqcgDqd
kBiKw6iooUiT2Mmc47iohgB/5BmhZ3oECaqkG3qVWTmci+mVjumZwXmPggmZU2qVsMqKr3qpGpmX
YWmMXjipe+mFflmZudqZstqagxmn8RiT6CiNKfmXjwCq8zeqZ1qqZmiPNgmIsbmqjVmrjPmWcqqV
sFn/nM4Zi8H5rbOIrd+okswKld1aREspi88YriYpouyql9Gpjt0Ime7aku9KjBwYjie5q1J5KGNK
pqMJlKOQnirqpK+6q6Corb/KrfZ6q1jarhMLrGs5sJo4lZ3qkOwKlhNLkbOZlqwKo28ZlUx5rBS7
lYjZr+s4rrSqsWoZnvupCKEqkAq7sB9orcJaq6s5mfq6sicbqx/Jp1HZjQNbmBD7s/WancpKllGI
pUKrtFSqtCxbmS57kTCLssRKpYigi7z4n62WoYY6p9T5nI4Kr2y6lpa4r6dom3Z6nefKqFx5nHEr
lmcrkW7JmtwpiPs6m5WKiX67kH96qHSYqFLbikI6/4cgmbV+2IQomYdwyquQALZhK6E6e39e2qCN
t7mxl4ZqeLk5a6qay7mo57mwB7pqaKK9WKqka7qwG7vIoLpcwbqnObaym7u6awy0W7sRKIHd92ou
2qW7W7zK17vKRQTe532v9rpTKJv9N5nGAJXGW73PgLzJ27zNO4ZgOrzdywyoa73iW7kF+6zay4DF
OYl9m6g4uYzY2qjwOrmROL+7Ob72O3nla3h92aHF2q3jyrSqmrLfe78EPAnYK6XWSr39y7QSq67e
aavLWsASjAkHHKKcmZEXjKqC+Zkcm475KKITHMJklr+FR7X4usDFmsHMirSEKcIuDJoP9Xjo6r64
Of+56vu+gCupbquchtq2g/vCQFwIFQx94RvERvysJDx+RXzETDzCNdvEUBzEQxzFVAy7U1zFWLyg
V5zFXHyfW9zFYHx/XxzGZCx+Y1zGaGx9Z5zGbPx8a9zGcGx8bxzHdPx7c1zHeIx7d5zHfPy5SdzH
gJx8exzIhGx6g1zIiPx5h5zIjIx5i9zIkBx5j5zF0FXJlnzJmJzJmqzJkezEMdzJawMMoqwKAbDE
bTzJWAwAn0ygpQzKX/vHiazKnicMpszGqFzFsgyOZwmRu9zLvPzLvhxLtOzKI/rExAxRhlLLXegc
yozGt0zFuax5w3zMEmXMxJzLRfzD2czM1FzNq+z/ytGsCVHrtZUwzd3sd+eMzAN8qskqztyczs8c
xeFMhpXIea0Mz7CMyNiMgRIZvebczfEMxfMMjGb5Cf9MzQHdxPvMz8Y5vAd9zAnNxAN9hP+6zsF3
z+cc0Ue80FX6zhmdz4U80azczGWs0UbM0ZKnPQ9NzCYdxNEczMAc0zA907/s0QAN0oQs0pK30q7c
0kCsytob1EI91ERd1EbN06Ds0y8MAPjW1E791FAd1VIN1SRNxkrtwpuc1Vq91Vydzujs1WANelcd
1mQtCWNd1mi9k9ac1my9eGfd1nDtzXE9126N03R91/a81ni918vw1nxd1n7912Ed2ILt1YRd2B/N
QxVHvdiM3diO/diQHdmSPdmUXdmWfdmYndmavdmc3dmPPdWgHdqiPdqkXdqmfdqondqqvdqs3dqu
/dqwHduyPdtQHQgAOw==--=_NextPart_000_000F_01C3C2BA.A0DC3EC0--|||I know that XP gets annoyed if I have two mail users at the same time on one machine (one is SQL
Server, the other is me, as interactive user), where W2K was OK with it. It seems "reasonable" that
W2KS is based on XP and exposes the same behavior. Did you consider using xp_smtp_sendmail instead?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:ONOZbMuwDHA.3116@.tk2msftngp13.phx.gbl...
Hi Aaron:
Can you believe it? I got the SQL Mail setup and it seems to be working. Using my ISPs SMTP
server. I did the test and it connected to the MAPI profile successfully. Anyway I proceeded to
use the extended stored procedure xp_sendmail in Query Analyzer:
xp_sendmail @.recipients = 'hesterloli@.hotmail.com',
@.message = 'Hello',
@.subject = 'From SQL Server 2000'
Actually I sent one to that address and one to my POP3 account. Both successfully as reported by
Query Analyzer.
But I forgot to have Outlook 2003 open before I did that. So to see if I got the mail I went to
open Outlook 2003. Know what happened? Outlook 2003 could not open. I use MAPI profiles and when
I tried to start Outlook 2003 the Error message I got was, "The service could not be started." No
offer to start in safe mode. Just the error message box. I post it next time if I can replicate
the issue again.
All I know is that it sounds like some dll went belly-up. I rebooted and Outlook 2003 was fine and
there were the two e-mails from SQL in Outlook 2003 and Outlook Express which handles my Hotmail
account.
Now I don't know what to do. I could try the xp_sendmail again with Outlook 2003 open and see if
that avoids the issue. But I just don't know. Ever heard of this before?
--
George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> Assuming you are using a stored procedure to generate the password, you can
> send an e-mail from the stored procedure (I really don't recommend doing
> this in a trigger). You can see some information about sending e-mail from
> SQL Server at http://www.aspfaq.com/2403
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
> "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> I was following this article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;247931&Product=sql
> and got it working nicely. I would like to elaborate on this. Rather then
> sending a succeed registration page to the client I would like to send them
> a page telling them an email has been sent to their e-mail address. That
> part of it I can do. My trouble is once I generate a password for the
> client I need to let SQL 2000 SP3 know it's time to send them an e-mail. Is
> this a trigger? Can anyone suggest what applications I might need to do
> this (except Exchange) and some guidelines on how this can be done? Thanks.
> I cannot use Exchange for this as I have Outlook 2003 installed and it is
> not supported on the same server where Exchange 2003 is installed. I only
> have the one Server Windows 2000 SP3.
> --
> George Hester
> __________________________________
>|||No I didn't have to reboot. I just had to shut down the services =mssqlserver and sqlserveragent. Then Outllook 2003 fired up and I =restarted the services. Another bug? Looks like it. With Outlook 2003 =installed along side of SQL 2000 SP3 using xp_sendmail causes Outlook =2003 to fail if it is closed and restarted after using the above =extended stored procedure in Windows 2000 Server SP3.
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> Assuming you are using a stored procedure to generate the password, =you can
> send an e-mail from the stored procedure (I really don't recommend =doing
> this in a trigger). You can see some information about sending e-mail =from
> SQL Server at http://www.aspfaq.com/2403
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> > > > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> I was following this article:
> > =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
> > and got it working nicely. I would like to elaborate on this. Rather =then
> sending a succeed registration page to the client I would like to send =them
> a page telling them an email has been sent to their e-mail address. =That
> part of it I can do. My trouble is once I generate a password for the
> client I need to let SQL 2000 SP3 know it's time to send them an =e-mail. Is
> this a trigger? Can anyone suggest what applications I might need to =do
> this (except Exchange) and some guidelines on how this can be done? =Thanks.
> > I cannot use Exchange for this as I have Outlook 2003 installed and it =is
> not supported on the same server where Exchange 2003 is installed. I =only
> have the one Server Windows 2000 SP3.
> > -- > George Hester
> __________________________________
> >|||I have to echo Tibor's suggestion, and consider the free, much-less-hassle
xp_smtp_sendmail. If you have any doubts about it, consider that it was
written by a Microsoft employee who knows his ____ and, in addition, my
company is using it in production and swears by it (because we used to swear
*at* SQL Mail).
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:eKwgUVuwDHA.1736@.TK2MSFTNGP09.phx.gbl...
No I didn't have to reboot. I just had to shut down the services
mssqlserver and sqlserveragent. Then Outllook 2003 fired up and I restarted
the services. Another bug? Looks like it. With Outlook 2003 installed
along side of SQL 2000 SP3 using xp_sendmail causes Outlook 2003 to fail if
it is closed and restarted after using the above extended stored procedure
in Windows 2000 Server SP3.|||I plan to. No issue with whatever works. But the bug still exists. =Too bad it is not published or at least something akin to it. I am =pretty sure I know what it is. The SQL Mail using ExtendedMAPI is not =releasing (signing off) correctly. I have seen this type of thing =before using a dll made by a MVP whose is a messaging expert. It is =called Redemption. His dll has the same type of issue. He says it is =an issue with Outlook itself. It may be. But his dll and this SQLMail =both exhibit the same destructive quality towards Outlook.
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:uipC3NwwDHA.3216@.TK2MSFTNGP11.phx.gbl...
> I have to echo Tibor's suggestion, and consider the free, =much-less-hassle
> xp_smtp_sendmail. If you have any doubts about it, consider that it =was
> written by a Microsoft employee who knows his ____ and, in addition, =my
> company is using it in production and swears by it (because we used to =swear
> *at* SQL Mail).
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> > > > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:eKwgUVuwDHA.1736@.TK2MSFTNGP09.phx.gbl...
> No I didn't have to reboot. I just had to shut down the services
> mssqlserver and sqlserveragent. Then Outllook 2003 fired up and I =restarted
> the services. Another bug? Looks like it. With Outlook 2003 =installed
> along side of SQL 2000 SP3 using xp_sendmail causes Outlook 2003 to =fail if
> it is closed and restarted after using the above extended stored =procedure
> in Windows 2000 Server SP3.
> >|||Tibor for this stored procedure to work I have to use my ISP's SMTP =server. They are blocking my port 25. Can I use that in this case and =if so how? Thanks.
-- George Hester
__________________________________
"Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message news:#uVbGVuwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> I know that XP gets annoyed if I have two mail users at the same time =on one machine (one is SQL
> Server, the other is me, as interactive user), where W2K was OK with =it. It seems "reasonable" that
> W2KS is based on XP and exposes the same behavior. Did you consider =using xp_smtp_sendmail instead?
> > -- > Tibor Karaszi, SQL Server MVP
> Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:ONOZbMuwDHA.3116@.tk2msftngp13.phx.gbl...
> Hi Aaron:
> > Can you believe it? I got the SQL Mail setup and it seems to be =working. Using my ISPs SMTP
> server. I did the test and it connected to the MAPI profile =successfully. Anyway I proceeded to
> use the extended stored procedure xp_sendmail in Query Analyzer:
> > xp_sendmail @.recipients =3D 'hesterloli@.hotmail.com',
> @.message =3D 'Hello',
> @.subject =3D 'From SQL Server 2000'
> > Actually I sent one to that address and one to my POP3 account. Both =successfully as reported by
> Query Analyzer.
> > But I forgot to have Outlook 2003 open before I did that. So to see =if I got the mail I went to
> open Outlook 2003. Know what happened? Outlook 2003 could not open. =I use MAPI profiles and when
> I tried to start Outlook 2003 the Error message I got was, "The =service could not be started." No
> offer to start in safe mode. Just the error message box. I post it =next time if I can replicate
> the issue again.
> > All I know is that it sounds like some dll went belly-up. I rebooted =and Outlook 2003 was fine and
> there were the two e-mails from SQL in Outlook 2003 and Outlook =Express which handles my Hotmail
> account.
> > Now I don't know what to do. I could try the xp_sendmail again with =Outlook 2003 open and see if
> that avoids the issue. But I just don't know. Ever heard of this =before?
> > -- > George Hester
> __________________________________
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> > Assuming you are using a stored procedure to generate the password, =you can
> > send an e-mail from the stored procedure (I really don't recommend =doing
> > this in a trigger). You can see some information about sending =e-mail from
> > SQL Server at http://www.aspfaq.com/2403
> >
> > -- > > Aaron Bertrand
> > SQL Server MVP
> > http://www.aspfaq.com/
> >
> >
> >
> >
> > "George Hester" <hesterloli@.hotmail.com> wrote in message
> > news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> > I was following this article:
> >
> > =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
> >
> > and got it working nicely. I would like to elaborate on this. =Rather then
> > sending a succeed registration page to the client I would like to =send them
> > a page telling them an email has been sent to their e-mail address. =That
> > part of it I can do. My trouble is once I generate a password for =the
> > client I need to let SQL 2000 SP3 know it's time to send them an =e-mail. Is
> > this a trigger? Can anyone suggest what applications I might need =to do
> > this (except Exchange) and some guidelines on how this can be done? =Thanks.
> >
> > I cannot use Exchange for this as I have Outlook 2003 installed and =it is
> > not supported on the same server where Exchange 2003 is installed. =I only
> > have the one Server Windows 2000 SP3.
> >
> > -- > > George Hester
> > __________________________________
> >
> >
> >|||Yes, you need an SMTP server, which IMO is the very strength of the solution. No MAPI etc. MAPI was
never designed as a multi-user app (say you have SQL Server and an interactive user at the same
time), nor was it designed to be used but by interactive users. That is why you have soo many KB
articles on the subject so there's a KB article which serves as just an index to all the other KB
articles.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:OIZhP81wDHA.1576@.TK2MSFTNGP11.phx.gbl...
Tibor for this stored procedure to work I have to use my ISP's SMTP server. They are blocking my
port 25. Can I use that in this case and if so how? Thanks.
--
George Hester
__________________________________
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in message
news:#uVbGVuwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> I know that XP gets annoyed if I have two mail users at the same time on one machine (one is SQL
> Server, the other is me, as interactive user), where W2K was OK with it. It seems "reasonable"
that
> W2KS is based on XP and exposes the same behavior. Did you consider using xp_smtp_sendmail
instead?
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:ONOZbMuwDHA.3116@.tk2msftngp13.phx.gbl...
> Hi Aaron:
> Can you believe it? I got the SQL Mail setup and it seems to be working. Using my ISPs SMTP
> server. I did the test and it connected to the MAPI profile successfully. Anyway I proceeded to
> use the extended stored procedure xp_sendmail in Query Analyzer:
> xp_sendmail @.recipients = 'hesterloli@.hotmail.com',
> @.message = 'Hello',
> @.subject = 'From SQL Server 2000'
> Actually I sent one to that address and one to my POP3 account. Both successfully as reported by
> Query Analyzer.
> But I forgot to have Outlook 2003 open before I did that. So to see if I got the mail I went to
> open Outlook 2003. Know what happened? Outlook 2003 could not open. I use MAPI profiles and
when
> I tried to start Outlook 2003 the Error message I got was, "The service could not be started." No
> offer to start in safe mode. Just the error message box. I post it next time if I can replicate
> the issue again.
> All I know is that it sounds like some dll went belly-up. I rebooted and Outlook 2003 was fine
and
> there were the two e-mails from SQL in Outlook 2003 and Outlook Express which handles my Hotmail
> account.
> Now I don't know what to do. I could try the xp_sendmail again with Outlook 2003 open and see if
> that avoids the issue. But I just don't know. Ever heard of this before?
> --
> George Hester
> __________________________________
> "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> > Assuming you are using a stored procedure to generate the password, you can
> > send an e-mail from the stored procedure (I really don't recommend doing
> > this in a trigger). You can see some information about sending e-mail from
> > SQL Server at http://www.aspfaq.com/2403
> >
> > --
> > Aaron Bertrand
> > SQL Server MVP
> > http://www.aspfaq.com/
> >
> >
> >
> >
> > "George Hester" <hesterloli@.hotmail.com> wrote in message
> > news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> > I was following this article:
> >
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;247931&Product=sql
> >
> > and got it working nicely. I would like to elaborate on this. Rather then
> > sending a succeed registration page to the client I would like to send them
> > a page telling them an email has been sent to their e-mail address. That
> > part of it I can do. My trouble is once I generate a password for the
> > client I need to let SQL 2000 SP3 know it's time to send them an e-mail. Is
> > this a trigger? Can anyone suggest what applications I might need to do
> > this (except Exchange) and some guidelines on how this can be done? Thanks.
> >
> > I cannot use Exchange for this as I have Outlook 2003 installed and it is
> > not supported on the same server where Exchange 2003 is installed. I only
> > have the one Server Windows 2000 SP3.
> >
> > --
> > George Hester
> > __________________________________
> >
> >
>|||> But the bug still exists.
Have you submitted it as a bug? Do you have a bug number?
From your description, sounds like a configuration issue, not a bug.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||> Tibor for this stored procedure to work I have to use my ISP's SMTP
server.
Are you running this out of your house? If your ISP is your only path to
the Internet, how do you plan to send mail using any solution?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Could be who knows. It's been known to happen. But honestly I wonder =how much of a configuration I can do to make a MAPI profile in the =Control Panel. Have Outlook work with it without issue. Have SQL Mail =see all three profiles. And run the xp-sendmail extended stored =procedure. And then get the error I showed you after shutting down and =restarting Outlook 2002. If it's a configuration issue then the =defaults are error prone. Becuase I did nothing else then follow the =GUI's.
-- George Hester
__________________________________
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message =news:e26eDN#wDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > But the bug still exists.
> > Have you submitted it as a bug? Do you have a bug number?
> > From your description, sounds like a configuration issue, not a bug.
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||Well there is nothing I can do about it Tibor. My ISP is not going to =open my port 25. I could send them a Christmas present they ain't going =to do it. I could change the port to say 2525. But that won't help as =the stored procedure says it is explicitly desgined for SMTP on port 25. = Mine works fine it just cannot talk to the outside world.
-- George Hester
__________________________________
"Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message news:#ygbjd6wDHA.3216@.TK2MSFTNGP11.phx.gbl...
> Yes, you need an SMTP server, which IMO is the very strength of the =solution. No MAPI etc. MAPI was
> never designed as a multi-user app (say you have SQL Server and an =interactive user at the same
> time), nor was it designed to be used but by interactive users. That =is why you have soo many KB
> articles on the subject so there's a KB article which serves as just =an index to all the other KB
> articles.
> > -- > Tibor Karaszi, SQL Server MVP
> Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:OIZhP81wDHA.1576@.TK2MSFTNGP11.phx.gbl...
> Tibor for this stored procedure to work I have to use my ISP's SMTP =server. They are blocking my
> port 25. Can I use that in this case and if so how? Thanks.
> > -- > George Hester
> __________________________________
> "Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message
> news:#uVbGVuwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> > I know that XP gets annoyed if I have two mail users at the same =time on one machine (one is SQL
> > Server, the other is me, as interactive user), where W2K was OK with =it. It seems "reasonable"
> that
> > W2KS is based on XP and exposes the same behavior. Did you consider =using xp_smtp_sendmail
> instead?
> >
> > -- > > Tibor Karaszi, SQL Server MVP
> > Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> >
> >
> > "George Hester" <hesterloli@.hotmail.com> wrote in message
> > news:ONOZbMuwDHA.3116@.tk2msftngp13.phx.gbl...
> > Hi Aaron:
> >
> > Can you believe it? I got the SQL Mail setup and it seems to be =working. Using my ISPs SMTP
> > server. I did the test and it connected to the MAPI profile =successfully. Anyway I proceeded to
> > use the extended stored procedure xp_sendmail in Query Analyzer:
> >
> > xp_sendmail @.recipients =3D 'hesterloli@.hotmail.com',
> > @.message =3D 'Hello',
> > @.subject =3D 'From SQL Server 2000'
> >
> > Actually I sent one to that address and one to my POP3 account. =Both successfully as reported by
> > Query Analyzer.
> >
> > But I forgot to have Outlook 2003 open before I did that. So to see =if I got the mail I went to
> > open Outlook 2003. Know what happened? Outlook 2003 could not =open. I use MAPI profiles and
> when
> > I tried to start Outlook 2003 the Error message I got was, "The =service could not be started." No
> > offer to start in safe mode. Just the error message box. I post it =next time if I can replicate
> > the issue again.
> >
> > All I know is that it sounds like some dll went belly-up. I =rebooted and Outlook 2003 was fine
> and
> > there were the two e-mails from SQL in Outlook 2003 and Outlook =Express which handles my Hotmail
> > account.
> >
> > Now I don't know what to do. I could try the xp_sendmail again with =Outlook 2003 open and see if
> > that avoids the issue. But I just don't know. Ever heard of this =before?
> >
> > -- > > George Hester
> > __________________________________
> > "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> > news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> > > Assuming you are using a stored procedure to generate the =password, you can
> > > send an e-mail from the stored procedure (I really don't recommend =doing
> > > this in a trigger). You can see some information about sending =e-mail from
> > > SQL Server at http://www.aspfaq.com/2403
> > >
> > > -- > > > Aaron Bertrand
> > > SQL Server MVP
> > > http://www.aspfaq.com/
> > >
> > >
> > >
> > >
> > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> > > news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > I was following this article:
> > >
> > > =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
> > >
> > > and got it working nicely. I would like to elaborate on this. =Rather then
> > > sending a succeed registration page to the client I would like to =send them
> > > a page telling them an email has been sent to their e-mail =address. That
> > > part of it I can do. My trouble is once I generate a password for =the
> > > client I need to let SQL 2000 SP3 know it's time to send them an =e-mail. Is
> > > this a trigger? Can anyone suggest what applications I might need =to do
> > > this (except Exchange) and some guidelines on how this can be =done? Thanks.
> > >
> > > I cannot use Exchange for this as I have Outlook 2003 installed =and it is
> > > not supported on the same server where Exchange 2003 is installed. = I only
> > > have the one Server Windows 2000 SP3.
> > >
> > > -- > > > George Hester
> > > __________________________________
> > >
> > >
> >
> >
> >|||Yes. Yes. Oh it works fine using xp-sendmail. No problem except for =the crashing Outlook 2002. That is not my ISP's fault. I can also use =CDO. But this is a little different and I would be happy with =xp-sendmail if I could just get SQL to release the call to MAPI after it =finishes the stored procedure. The one you recommend won't work because =my ISP has blocked my port 25. Unless I can get the stored procedure to =expect my SMTP server on port 2525 say. Then it will work.
-- George Hester
__________________________________
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message =news:#sEzMO#wDHA.4060@.TK2MSFTNGP11.phx.gbl...
> > Tibor for this stored procedure to work I have to use my ISP's SMTP
> server.
> > Are you running this out of your house? If your ISP is your only path =to
> the Internet, how do you plan to send mail using any solution?
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||> My ISP is not going to open my port 25.
Do they really have the ability to block a port OUTBOUND? In my experience,
the port blocking has been inbound...
In any case,
> the stored procedure says it is explicitly desgined for SMTP on port 25.
Did you actually *read* the docs on xp_smtp_sendmail? From
http://www.sqldev.net/xp/xpsmtp.htm:
@.port INT 25 Optional Valid socket port number Port number
for SMTP service, default port 25
--
Aaron Bertrand
SQL Server MVP|||See my other reply.
--
Aaron Bertrand
SQL Server MVP
"George Hester" <hesterloli@.hotmail.com> wrote in message
news:uvs8ycCxDHA.2708@.TK2MSFTNGP09.phx.gbl...
Yes. Yes. Oh it works fine using xp-sendmail. No problem except for the
crashing Outlook 2002. That is not my ISP's fault. I can also use CDO.
But this is a little different and I would be happy with xp-sendmail if I
could just get SQL to release the call to MAPI after it finishes the stored
procedure. The one you recommend won't work because my ISP has blocked my
port 25. Unless I can get the stored procedure to expect my SMTP server on
port 2525 say. Then it will work.|||Um thanks Aaron. Yes I read as much as I could understand. We all know =the word Oui in French. But I bet if you looked at a book from Marcel =Proust in the original you may have trouble finding that word.
-- George Hester
__________________________________
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message =news:OELpqlCxDHA.2156@.TK2MSFTNGP09.phx.gbl...
> > My ISP is not going to open my port 25.
> > Do they really have the ability to block a port OUTBOUND? In my =experience,
> the port blocking has been inbound...
> > In any case,
> > > the stored procedure says it is explicitly desgined for SMTP on port =25.
> > Did you actually *read* the docs on xp_smtp_sendmail? From
> http://www.sqldev.net/xp/xpsmtp.htm:
> > @.port INT 25 Optional Valid socket port number Port =number
> for SMTP service, default port 25
> > -- > Aaron Bertrand
> SQL Server MVP
> >|||A configuration issue was not it. It was how I called the extended =stored procedure xp_sendmail. See there is a statment in the BOL or at =Microsoft not sure which that when xp_sendmail is called we must first =call xp_startmail. It's true that this is not necessary but I believe =it is best to do all the procedures and determine if my issue still =occurs.
So this time I made a batch that looks like this:
DECLARE @.hc int
EXEC @.hc =3D xp_startmail @.user =3D 'My MAPI Profile',
@.password =3D NULL
If @.hc =3D 0
EXEC @.hc =3D xp_sendmail @.recipients =3D 'hesterloli@.hotmail.com',
@.message =3D 'Hello',
@.subject =3D 'From SQL Server 2000 SQL Mail'
If @.hc =3D 0
EXEC xp_stopmail
and put this in Query Analyzer. I ran it. All worked well there. The =SQL Mail started, the Mail was sent, and the SQL Mail stopped. And sure =enough I got the mail.
I then quit Outlook 2003 and tried to start it up again to see if I =avoided the error I posted a bit ago. No error.
If you think there is a better way to write this batch I'd appreciate =it. I just tried whatever I could get to not give me an error in Query =analyzer when I checked the statements.
-- George Hester
__________________________________
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message =news:e26eDN#wDHA.2448@.TK2MSFTNGP12.phx.gbl...
> > But the bug still exists.
> > Have you submitted it as a bug? Do you have a bug number?
> > From your description, sounds like a configuration issue, not a bug.
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||Hi Tibor. I got it to work. Thanks for that right now it seems the =ticket. And you too Aaron.
-- George Hester
__________________________________
"Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message news:#ygbjd6wDHA.3216@.TK2MSFTNGP11.phx.gbl...
> Yes, you need an SMTP server, which IMO is the very strength of the =solution. No MAPI etc. MAPI was
> never designed as a multi-user app (say you have SQL Server and an =interactive user at the same
> time), nor was it designed to be used but by interactive users. That =is why you have soo many KB
> articles on the subject so there's a KB article which serves as just =an index to all the other KB
> articles.
> > -- > Tibor Karaszi, SQL Server MVP
> Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> news:OIZhP81wDHA.1576@.TK2MSFTNGP11.phx.gbl...
> Tibor for this stored procedure to work I have to use my ISP's SMTP =server. They are blocking my
> port 25. Can I use that in this case and if so how? Thanks.
> > -- > George Hester
> __________________________________
> "Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message
> news:#uVbGVuwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> > I know that XP gets annoyed if I have two mail users at the same =time on one machine (one is SQL
> > Server, the other is me, as interactive user), where W2K was OK with =it. It seems "reasonable"
> that
> > W2KS is based on XP and exposes the same behavior. Did you consider =using xp_smtp_sendmail
> instead?
> >
> > -- > > Tibor Karaszi, SQL Server MVP
> > Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> >
> >
> > "George Hester" <hesterloli@.hotmail.com> wrote in message
> > news:ONOZbMuwDHA.3116@.tk2msftngp13.phx.gbl...
> > Hi Aaron:
> >
> > Can you believe it? I got the SQL Mail setup and it seems to be =working. Using my ISPs SMTP
> > server. I did the test and it connected to the MAPI profile =successfully. Anyway I proceeded to
> > use the extended stored procedure xp_sendmail in Query Analyzer:
> >
> > xp_sendmail @.recipients =3D 'hesterloli@.hotmail.com',
> > @.message =3D 'Hello',
> > @.subject =3D 'From SQL Server 2000'
> >
> > Actually I sent one to that address and one to my POP3 account. =Both successfully as reported by
> > Query Analyzer.
> >
> > But I forgot to have Outlook 2003 open before I did that. So to see =if I got the mail I went to
> > open Outlook 2003. Know what happened? Outlook 2003 could not =open. I use MAPI profiles and
> when
> > I tried to start Outlook 2003 the Error message I got was, "The =service could not be started." No
> > offer to start in safe mode. Just the error message box. I post it =next time if I can replicate
> > the issue again.
> >
> > All I know is that it sounds like some dll went belly-up. I =rebooted and Outlook 2003 was fine
> and
> > there were the two e-mails from SQL in Outlook 2003 and Outlook =Express which handles my Hotmail
> > account.
> >
> > Now I don't know what to do. I could try the xp_sendmail again with =Outlook 2003 open and see if
> > that avoids the issue. But I just don't know. Ever heard of this =before?
> >
> > -- > > George Hester
> > __________________________________
> > "Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
> > news:Ok8Io0rwDHA.1512@.TK2MSFTNGP10.phx.gbl...
> > > Assuming you are using a stored procedure to generate the =password, you can
> > > send an e-mail from the stored procedure (I really don't recommend =doing
> > > this in a trigger). You can see some information about sending =e-mail from
> > > SQL Server at http://www.aspfaq.com/2403
> > >
> > > -- > > > Aaron Bertrand
> > > SQL Server MVP
> > > http://www.aspfaq.com/
> > >
> > >
> > >
> > >
> > > "George Hester" <hesterloli@.hotmail.com> wrote in message
> > > news:ugKtPGrwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> > > I was following this article:
> > >
> > > =http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
> > >
> > > and got it working nicely. I would like to elaborate on this. =Rather then
> > > sending a succeed registration page to the client I would like to =send them
> > > a page telling them an email has been sent to their e-mail =address. That
> > > part of it I can do. My trouble is once I generate a password for =the
> > > client I need to let SQL 2000 SP3 know it's time to send them an =e-mail. Is
> > > this a trigger? Can anyone suggest what applications I might need =to do
> > > this (except Exchange) and some guidelines on how this can be =done? Thanks.
> > >
> > > I cannot use Exchange for this as I have Outlook 2003 installed =and it is
> > > not supported on the same server where Exchange 2003 is installed. = I only
> > > have the one Server Windows 2000 SP3.
> > >
> > > -- > > > George Hester
> > > __________________________________
> > >
> > >
> >
> >
> >
No comments:
Post a Comment