Exchange 2003 and "xp_sendmail: failed with mail error 0x80070005" error

Hello,
We just migrated a mailbox that sql server agent was using as a MAPI
profile to Exchange 2003 from Exchnage 2000.
I can successfully start sql agent with this profile. SQLmail is configured
successfully with this profile.
But I am having the above error when I try to use xp_sendmail from query
analyzer. Any ideas?
Thanks,
Biva
I had a similar problem a couple of weeks ago and did a lot of research
with no results. This was causing issues with us for at least a week.
For the heck of it I went into Query analyzer and ran xp_stopmail, then
xp_startmail. Don't know why, but this did it for us. We have been using
xp_Sendmail now for over a week without any errors.
Jim
"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:40fc1289$0$978$39cecf19@.news.twtelecom.net...
> Hello,
> We just migrated a mailbox that sql server agent was using as a MAPI
> profile to Exchange 2003 from Exchnage 2000.
> I can successfully start sql agent with this profile. SQLmail is
configured
> successfully with this profile.
> But I am having the above error when I try to use xp_sendmail from query
> analyzer. Any ideas?
> Thanks,
> Biva
>
|||Hi Jim,
You are awesome. That was it. I did xp_stopmail and xp_startmail and
now its working fine. Thanks a bunch for your help. Saved me a lot of
time.
biva
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Exchange 2003 and "xp_sendmail: failed with mail error 0x80070005" error

Hello,
We just migrated a mailbox that sql server agent was using as a MAPI
profile to Exchange 2003 from Exchnage 2000.
I can successfully start sql agent with this profile. SQLmail is configured
successfully with this profile.
But I am having the above error when I try to use xp_sendmail from query
analyzer. Any ideas?
Thanks,
BivaI had a similar problem a couple of weeks ago and did a lot of research
with no results. This was causing issues with us for at least a week.
For the heck of it I went into Query analyzer and ran xp_stopmail, then
xp_startmail. Don't know why, but this did it for us. We have been using
xp_Sendmail now for over a week without any errors.
Jim
"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:40fc1289$0$978$39cecf19@.news.twtelecom.net...
> Hello,
> We just migrated a mailbox that sql server agent was using as a MAPI
> profile to Exchange 2003 from Exchnage 2000.
> I can successfully start sql agent with this profile. SQLmail is
configured
> successfully with this profile.
> But I am having the above error when I try to use xp_sendmail from query
> analyzer. Any ideas?
> Thanks,
> Biva
>

Exchange 2003 and "xp_sendmail: failed with mail error 0x80070005" error

Hello,
We just migrated a mailbox that sql server agent was using as a MAPI
profile to Exchange 2003 from Exchnage 2000.
I can successfully start sql agent with this profile. SQLmail is configured
successfully with this profile.
But I am having the above error when I try to use xp_sendmail from query
analyzer. Any ideas?
Thanks,
BivaI had a similar problem a couple of weeks ago and did a lot of research
with no results. This was causing issues with us for at least a week.
For the heck of it I went into Query analyzer and ran xp_stopmail, then
xp_startmail. Don't know why, but this did it for us. We have been using
xp_Sendmail now for over a week without any errors.
Jim
"Biva" <biva.yauchler@.redprairie.com> wrote in message
news:40fc1289$0$978$39cecf19@.news.twtelecom.net...
> Hello,
> We just migrated a mailbox that sql server agent was using as a MAPI
> profile to Exchange 2003 from Exchnage 2000.
> I can successfully start sql agent with this profile. SQLmail is
configured
> successfully with this profile.
> But I am having the above error when I try to use xp_sendmail from query
> analyzer. Any ideas?
> Thanks,
> Biva
>|||Hi Jim,
You are awesome. That was it. I did xp_stopmail and xp_startmail and
now its working fine. Thanks a bunch for your help. Saved me a lot of
time.
biva
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

excessive memory usage problem

We have recently migrated from a Windows Server 2000/Sql Server 2000
Standard Edition machine to Windows Server 2003 Standard Edition/Sql
Server 2000 Standard Edition. We are using the machine as a combined
web and database server running asp and com dll's. The old machine had
about 1GB Ram and sql server used about 700Mb and the machine ran ok.
On the new machine with 2.5GB Ram sql server seems to gradually build
up its memory use to 1.9GB from 300mb after a reeboot. The machine
seems be experiencing some performance problems even though we have
the same amount of website traffic as before, I suspect the memory
usage is a problem, it seems as if sql server it not releasing memory.
Is their a way to diagnose/control this? Is it possible that there is
some difference in windows 2003(with IIS 6) that causes sql server to
retain more memory, perhaps not relasing database connections from asp
as quickly as before'
We have the latest service pack on sql server 2000.
Thanks
ScottIn EM, RClick the server/ props/ memory/ set a max.
>--Original Message--
>We have recently migrated from a Windows Server 2000/Sql
Server 2000
>Standard Edition machine to Windows Server 2003
Standard Edition/Sql
>Server 2000 Standard Edition. We are using the machine as
a combined
>web and database server running asp and com dll's. The
old machine had
>about 1GB Ram and sql server used about 700Mb and the
machine ran ok.
>On the new machine with 2.5GB Ram sql server seems to
gradually build
>up its memory use to 1.9GB from 300mb after a reeboot.
The machine
>seems be experiencing some performance problems even
though we have
>the same amount of website traffic as before, I suspect
the memory
>usage is a problem, it seems as if sql server it not
releasing memory.
>Is their a way to diagnose/control this? Is it possible
that there is
>some difference in windows 2003(with IIS 6) that causes
sql server to
>retain more memory, perhaps not relasing database
connections from asp
>as quickly as before'
>We have the latest service pack on sql server 2000.
>Thanks
>Scott
>.
>|||AFAIK, IIS6/Win2003 should be faster than your previous environment.
If SQL takes 1.9GB, you still have 0.6GB for OS and asp, which is double the
amount you had in your previous configuration, right?
The behaviour you describe is by design I believe - SQLServer will take as
much memory as it can (up to 2GB).
Are you _very_ sure that you have the latest service pack?
I have just very recently been studying maybe a bit similar
ASP/COM/IIS5/SQLServer2000 system which encountered performance problems
(after SP3 installation), and was finally cured when we (re)installed very
latest SP3a to application servers. The effect was really amazing. Our app
was using ODBC.
Just an idea,
pexi
<scott_mcarthur2003@.yahoo.co.uk> wrote in message
news:92c92d63.0311200800.124926ff@.posting.google.com...
> We have recently migrated from a Windows Server 2000/Sql Server 2000
> Standard Edition machine to Windows Server 2003 Standard Edition/Sql
> Server 2000 Standard Edition. We are using the machine as a combined
> web and database server running asp and com dll's. The old machine had
> about 1GB Ram and sql server used about 700Mb and the machine ran ok.
> On the new machine with 2.5GB Ram sql server seems to gradually build
> up its memory use to 1.9GB from 300mb after a reeboot. The machine
> seems be experiencing some performance problems even though we have
> the same amount of website traffic as before, I suspect the memory
> usage is a problem, it seems as if sql server it not releasing memory.
> Is their a way to diagnose/control this? Is it possible that there is
> some difference in windows 2003(with IIS 6) that causes sql server to
> retain more memory, perhaps not relasing database connections from asp
> as quickly as before'
> We have the latest service pack on sql server 2000.
> Thanks
> Scott|||Despite the wording in Q814410, below memoryLeak is fixed in SP3A according
to our tests:
http://support.microsoft.com/default.aspx?scid=kb;en-us;814410
which might explain your experience with SP3A.
/jensk
"Pexi" <pekkadotheimonen@.plenwaredotnospamdotcom> wrote in message
news:ef8Jz05rDHA.560@.TK2MSFTNGP11.phx.gbl...
> AFAIK, IIS6/Win2003 should be faster than your previous environment.
> If SQL takes 1.9GB, you still have 0.6GB for OS and asp, which is double
the
> amount you had in your previous configuration, right?
> The behaviour you describe is by design I believe - SQLServer will take as
> much memory as it can (up to 2GB).
> Are you _very_ sure that you have the latest service pack?
> I have just very recently been studying maybe a bit similar
> ASP/COM/IIS5/SQLServer2000 system which encountered performance problems
> (after SP3 installation), and was finally cured when we (re)installed very
> latest SP3a to application servers. The effect was really amazing. Our app
> was using ODBC.
> Just an idea,
> pexi
> <scott_mcarthur2003@.yahoo.co.uk> wrote in message
> news:92c92d63.0311200800.124926ff@.posting.google.com...
> > We have recently migrated from a Windows Server 2000/Sql Server 2000
> > Standard Edition machine to Windows Server 2003 Standard Edition/Sql
> > Server 2000 Standard Edition. We are using the machine as a combined
> > web and database server running asp and com dll's. The old machine had
> > about 1GB Ram and sql server used about 700Mb and the machine ran ok.
> > On the new machine with 2.5GB Ram sql server seems to gradually build
> > up its memory use to 1.9GB from 300mb after a reeboot. The machine
> > seems be experiencing some performance problems even though we have
> > the same amount of website traffic as before, I suspect the memory
> > usage is a problem, it seems as if sql server it not releasing memory.
> > Is their a way to diagnose/control this? Is it possible that there is
> > some difference in windows 2003(with IIS 6) that causes sql server to
> > retain more memory, perhaps not relasing database connections from asp
> > as quickly as before'
> >
> > We have the latest service pack on sql server 2000.
> >
> > Thanks
> >
> > Scott
>