Showing posts with label sbs. Show all posts
Showing posts with label sbs. Show all posts

Monday, March 19, 2012

cannot write to sql 2000 database after about 2 hours uptime

Hi
I have a sql 2000 sp3 database running on SBS 2003 that seems to
ignore any writes after about 2 hours of it being up. It works fine after i
reboot the server or restart the sql service, but after a couple hours it
will not edit the database again. If i restart the service, it works fine
again. Also, i was looking at the sql logs and they are odd. it says
'starting up database {my database name}' about 20 times in a row when the
database is started, then says 'Configuration option 'show advanced options'
changed from 1 to 1. Run the RECONFIGURE statement to install' and then
gives an error 15457. Please help me fix my database.
Thanks in advance.
Leszek
Hi
Error 15457 is just an informational one. Ig gets generated the Enterprise
Manager and has nothing to do with the Db issue.
If there are no other errors in you event log, it means that SQL is Ok and
your application is the problem.
You may want to make sure that your DB is not set as 'Auto Close' as this
affects performance.
Regards
Mike
"Leszek" wrote:

> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>
>
|||Hi
Db is not set as 'Auto Close'. I have noticed that problem occured when is
more then 100 process in sql .
Regards
Leszek
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...[vbcol=seagreen]
> Hi
> Error 15457 is just an informational one. Ig gets generated the Enterprise
> Manager and has nothing to do with the Db issue.
> If there are no other errors in you event log, it means that SQL is Ok and
> your application is the problem.
> You may want to make sure that your DB is not set as 'Auto Close' as this
> affects performance.
> Regards
> Mike
> "Leszek" wrote:
after i[vbcol=seagreen]
it[vbcol=seagreen]
fine[vbcol=seagreen]
the[vbcol=seagreen]
options'[vbcol=seagreen]
then[vbcol=seagreen]
|||The problem here is not going to be an easy one to fix.
There are a couple of things you can look at however to
get a bit closer to the proble.
Firstly have you run the performance monitor to see what
is happening to your server i.e. Disk, Memory and the like.
Secondly you may want to set up a trace to see what
commands are being sent to the server.
Finally another thing you can do is send me a copy of your
database script, I don't need the table definitions, sp,
views or functions, just the configuration options when
you create the database, for security purposes leave the
create database statement in, but change the db name. I
will have a quick look at it and see if I can spot
anything odd.
Finally what is your server specification i.e. ram, hard
disk space ect.
My email if you need it is
peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
Peter
"The length of this document defends it well against the
risk of its being read."
Winston Churchill

>--Original Message--
>Hi
>Db is not set as 'Auto Close'. I have noticed that
problem occured when is
>more then 100 process in sql .
>Regards
>Leszek
>
>"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
message[vbcol=seagreen]
>news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
generated the Enterprise[vbcol=seagreen]
that SQL is Ok and[vbcol=seagreen]
as 'Auto Close' as this[vbcol=seagreen]
2003 that seems to[vbcol=seagreen]
It works fine[vbcol=seagreen]
>after i
after a couple hours[vbcol=seagreen]
>it
service, it works[vbcol=seagreen]
>fine
are odd. it says[vbcol=seagreen]
times in a row when[vbcol=seagreen]
>the
option 'show advanced[vbcol=seagreen]
>options'
to install' and
>then
>
>.
>
|||Aplication works since few monts on other server and there everything is
fine.
Regarding performance monitor. When system works fine and i try to open site
with many difficult query , procesor usage show about 50 % and it take 10
sec - site is loaded. If it doesn't work procesor usage is always about 1%
but i can't load the site.
Sql Profile show that query is sent to server.
Leszek
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:158001c4a221$b242cfc0$a301280a@.phx.gbl...[vbcol=seagreen]
> The problem here is not going to be an easy one to fix.
> There are a couple of things you can look at however to
> get a bit closer to the proble.
> Firstly have you run the performance monitor to see what
> is happening to your server i.e. Disk, Memory and the like.
> Secondly you may want to set up a trace to see what
> commands are being sent to the server.
> Finally another thing you can do is send me a copy of your
> database script, I don't need the table definitions, sp,
> views or functions, just the configuration options when
> you create the database, for security purposes leave the
> create database statement in, but change the db name. I
> will have a quick look at it and see if I can spot
> anything odd.
> Finally what is your server specification i.e. ram, hard
> disk space ect.
> My email if you need it is
> peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
> Peter
> "The length of this document defends it well against the
> risk of its being read."
> Winston Churchill
>
> problem occured when is
> message
> generated the Enterprise
> that SQL is Ok and
> as 'Auto Close' as this
> 2003 that seems to
> It works fine
> after a couple hours
> service, it works
> are odd. it says
> times in a row when
> option 'show advanced
> to install' and
|||Hi Leszek,
Have you used the enterprise manager to see if anything is locking a table
and preventing the updates? Perhaps a certain function or piece of code is
being executed after about 2 hours and that may look like the database won't
accept updates.
Wayne
"Leszek" <aaa@.addressnotexists.com> wrote in message
news:Odc7a3goEHA.2380@.TK2MSFTNGP14.phx.gbl...
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after
> i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced
> options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>

cannot write to sql 2000 database after about 2 hours uptime

Hi
I have a sql 2000 sp3 database running on SBS 2003 that seems to
ignore any writes after about 2 hours of it being up. It works fine after i
reboot the server or restart the sql service, but after a couple hours it
will not edit the database again. If i restart the service, it works fine
again. Also, i was looking at the sql logs and they are odd. it says
'starting up database {my database name}' about 20 times in a row when the
database is started, then says 'Configuration option 'show advanced options'
changed from 1 to 1. Run the RECONFIGURE statement to install' and then
gives an error 15457. Please help me fix my database.
Thanks in advance.
LeszekHi
Error 15457 is just an informational one. Ig gets generated the Enterprise
Manager and has nothing to do with the Db issue.
If there are no other errors in you event log, it means that SQL is Ok and
your application is the problem.
You may want to make sure that your DB is not set as 'Auto Close' as this
affects performance.
Regards
Mike
"Leszek" wrote:
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>
>|||Hi
Db is not set as 'Auto Close'. I have noticed that problem occured when is
more then 100 process in sql .
Regards
Leszek
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
> Hi
> Error 15457 is just an informational one. Ig gets generated the Enterprise
> Manager and has nothing to do with the Db issue.
> If there are no other errors in you event log, it means that SQL is Ok and
> your application is the problem.
> You may want to make sure that your DB is not set as 'Auto Close' as this
> affects performance.
> Regards
> Mike
> "Leszek" wrote:
> > Hi
> >
> >
> > I have a sql 2000 sp3 database running on SBS 2003 that seems to
> > ignore any writes after about 2 hours of it being up. It works fine
after i
> > reboot the server or restart the sql service, but after a couple hours
it
> > will not edit the database again. If i restart the service, it works
fine
> > again. Also, i was looking at the sql logs and they are odd. it says
> > 'starting up database {my database name}' about 20 times in a row when
the
> > database is started, then says 'Configuration option 'show advanced
options'
> > changed from 1 to 1. Run the RECONFIGURE statement to install' and
then
> > gives an error 15457. Please help me fix my database.
> >
> > Thanks in advance.
> >
> > Leszek
> >
> >
> >|||The problem here is not going to be an easy one to fix.
There are a couple of things you can look at however to
get a bit closer to the proble.
Firstly have you run the performance monitor to see what
is happening to your server i.e. Disk, Memory and the like.
Secondly you may want to set up a trace to see what
commands are being sent to the server.
Finally another thing you can do is send me a copy of your
database script, I don't need the table definitions, sp,
views or functions, just the configuration options when
you create the database, for security purposes leave the
create database statement in, but change the db name. I
will have a quick look at it and see if I can spot
anything odd.
Finally what is your server specification i.e. ram, hard
disk space ect.
My email if you need it is
peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
Peter
"The length of this document defends it well against the
risk of its being read."
Winston Churchill
>--Original Message--
>Hi
>Db is not set as 'Auto Close'. I have noticed that
problem occured when is
>more then 100 process in sql .
>Regards
>Leszek
>
>"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
message
>news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
>> Hi
>> Error 15457 is just an informational one. Ig gets
generated the Enterprise
>> Manager and has nothing to do with the Db issue.
>> If there are no other errors in you event log, it means
that SQL is Ok and
>> your application is the problem.
>> You may want to make sure that your DB is not set
as 'Auto Close' as this
>> affects performance.
>> Regards
>> Mike
>> "Leszek" wrote:
>> > Hi
>> >
>> >
>> > I have a sql 2000 sp3 database running on SBS
2003 that seems to
>> > ignore any writes after about 2 hours of it being up.
It works fine
>after i
>> > reboot the server or restart the sql service, but
after a couple hours
>it
>> > will not edit the database again. If i restart the
service, it works
>fine
>> > again. Also, i was looking at the sql logs and they
are odd. it says
>> > 'starting up database {my database name}' about 20
times in a row when
>the
>> > database is started, then says 'Configuration
option 'show advanced
>options'
>> > changed from 1 to 1. Run the RECONFIGURE statement
to install' and
>then
>> > gives an error 15457. Please help me fix my database.
>> >
>> > Thanks in advance.
>> >
>> > Leszek
>> >
>> >
>> >
>
>.
>|||Aplication works since few monts on other server and there everything is
fine.
Regarding performance monitor. When system works fine and i try to open site
with many difficult query , procesor usage show about 50 % and it take 10
sec - site is loaded. If it doesn't work procesor usage is always about 1%
but i can't load the site.
Sql Profile show that query is sent to server.
Leszek
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:158001c4a221$b242cfc0$a301280a@.phx.gbl...
> The problem here is not going to be an easy one to fix.
> There are a couple of things you can look at however to
> get a bit closer to the proble.
> Firstly have you run the performance monitor to see what
> is happening to your server i.e. Disk, Memory and the like.
> Secondly you may want to set up a trace to see what
> commands are being sent to the server.
> Finally another thing you can do is send me a copy of your
> database script, I don't need the table definitions, sp,
> views or functions, just the configuration options when
> you create the database, for security purposes leave the
> create database statement in, but change the db name. I
> will have a quick look at it and see if I can spot
> anything odd.
> Finally what is your server specification i.e. ram, hard
> disk space ect.
> My email if you need it is
> peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
> Peter
> "The length of this document defends it well against the
> risk of its being read."
> Winston Churchill
>
> >--Original Message--
> >Hi
> >
> >Db is not set as 'Auto Close'. I have noticed that
> problem occured when is
> >more then 100 process in sql .
> >
> >Regards
> >Leszek
> >
> >
> >"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
> message
> >news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
> >> Hi
> >>
> >> Error 15457 is just an informational one. Ig gets
> generated the Enterprise
> >> Manager and has nothing to do with the Db issue.
> >>
> >> If there are no other errors in you event log, it means
> that SQL is Ok and
> >> your application is the problem.
> >>
> >> You may want to make sure that your DB is not set
> as 'Auto Close' as this
> >> affects performance.
> >>
> >> Regards
> >> Mike
> >>
> >> "Leszek" wrote:
> >>
> >> > Hi
> >> >
> >> >
> >> > I have a sql 2000 sp3 database running on SBS
> 2003 that seems to
> >> > ignore any writes after about 2 hours of it being up.
> It works fine
> >after i
> >> > reboot the server or restart the sql service, but
> after a couple hours
> >it
> >> > will not edit the database again. If i restart the
> service, it works
> >fine
> >> > again. Also, i was looking at the sql logs and they
> are odd. it says
> >> > 'starting up database {my database name}' about 20
> times in a row when
> >the
> >> > database is started, then says 'Configuration
> option 'show advanced
> >options'
> >> > changed from 1 to 1. Run the RECONFIGURE statement
> to install' and
> >then
> >> > gives an error 15457. Please help me fix my database.
> >> >
> >> > Thanks in advance.
> >> >
> >> > Leszek
> >> >
> >> >
> >> >
> >
> >
> >.
> >|||Hi Leszek,
Have you used the enterprise manager to see if anything is locking a table
and preventing the updates? Perhaps a certain function or piece of code is
being executed after about 2 hours and that may look like the database won't
accept updates.
Wayne
"Leszek" <aaa@.addressnotexists.com> wrote in message
news:Odc7a3goEHA.2380@.TK2MSFTNGP14.phx.gbl...
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after
> i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced
> options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>

Sunday, February 19, 2012

Cannot setup SQL Mail on SBS 2003

I have SQL Server 2000 setup on a SBS 2003 Premium server, with Exchange
2003.
I set up SQL Mail to use the only profile available, which is "ExchangeAdmin
SBS (0x codes following)".
When I try a simple xp_sendmail to an existing email address, I get the
following:
xp_sendmail: failed with mail error 0x80004005
When I search Microsoft.com, or all of the Web, I see that there is a
workaround specified by Microsoft:
http://support.microsoft.com/kb/293422/EN-US/
The problem is that I cannot "Locate the user object directly associated
with the Exchange 2000 mailbox". First of, I have Exchange 2003, not 2000.
Second, I cannot find the specified "ExchangeAdmin SBS ..." account.
I also tried installing Outlook, creating a profile with a user called
"SQLEmailAccount", so that I could locate it in AD and apply the workaround,
but when I open Enterprise manager, and try to select this email profile for
SQL Mail (as described at the top of this email), it simply does not
appear...
It seems that I can nonetheless use a workaround, as I found a few SPs which
create a CDO object (a bit like what you would do in ASP) and talk to it,
but I'd like to be able to use xp_sendmail in order to allow contractors to
use standard programming techniques.
Thanks a lot in advance for your help!Nicolas Verhaeghe wrote:
>I have SQL Server 2000 setup on a SBS 2003 Premium server, with Exchange
>2003.
>I set up SQL Mail to use the only profile available, which is
>"ExchangeAdmin SBS (0x codes following)".
Hmmm, not sure where that's from, since SBS normally has no MAPI profiles
at all by default.
Have you configured SQL Server and all associated services to run under a
user account, rather than LocalSystem (the default)?
>When I try a simple xp_sendmail to an existing email address, I get the
>following:
>xp_sendmail: failed with mail error 0x80004005
>When I search Microsoft.com, or all of the Web, I see that there is a
>workaround specified by Microsoft:
>http://support.microsoft.com/kb/293422/EN-US/
>The problem is that I cannot "Locate the user object directly associated
>with the Exchange 2000 mailbox". First of, I have Exchange 2003, not 2000.
>Second, I cannot find the specified "ExchangeAdmin SBS ..." account.
It's not an account, it's a MAPI profile belonging to a user account. MAPI
profiles belong to user accounts, and can only be accessed and manipulated
by the user account they belong to.
>I also tried installing Outlook, creating a profile with a user called
>"SQLEmailAccount", so that I could locate it in AD and apply the
>workaround, but when I open Enterprise manager, and try to select this
>email profile for SQL Mail (as described at the top of this email), it
>simply does not appear...
AARGH. Get Outlook *OFF* your SBS as fast as possible. Outlook is *not*
supported for installation on an Exchange Server (like SBS).
>It seems that I can nonetheless use a workaround, as I found a few SPs
>which create a CDO object (a bit like what you would do in ASP) and talk
>to it, but I'd like to be able to use xp_sendmail in order to allow
>contractors to use standard programming techniques.
The KB articles you need are:
304967 How to Configure SQL Server to Send Email on SBS 2000
http://support.microsoft.com/?id=304967
and
228736 SAMPLE Profman2.exe - MAPI Profile Manager v2.0
http://support.microsoft.com/?id=228736
While the first article says SBS2000, it applies equally to SBS2003. But
creating the MAPI profile is much easier to do with PROFMAN (from the
second KB) than all the registry hacking the first article suggests you do.
Steve Foster [SBS MVP]
---
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Cannot setup SQL Mail on SBS 2003

I have SQL Server 2000 setup on a SBS 2003 Premium server, with Exchange
2003.
I set up SQL Mail to use the only profile available, which is "ExchangeAdmin
SBS (0x codes following)".
When I try a simple xp_sendmail to an existing email address, I get the
following:
xp_sendmail: failed with mail error 0x80004005
When I search Microsoft.com, or all of the Web, I see that there is a
workaround specified by Microsoft:
http://support.microsoft.com/kb/293422/EN-US/
The problem is that I cannot "Locate the user object directly associated
with the Exchange 2000 mailbox". First of, I have Exchange 2003, not 2000.
Second, I cannot find the specified "ExchangeAdmin SBS ..." account.
I also tried installing Outlook, creating a profile with a user called
"SQLEmailAccount", so that I could locate it in AD and apply the workaround,
but when I open Enterprise manager, and try to select this email profile for
SQL Mail (as described at the top of this email), it simply does not
appear...
It seems that I can nonetheless use a workaround, as I found a few SPs which
create a CDO object (a bit like what you would do in ASP) and talk to it,
but I'd like to be able to use xp_sendmail in order to allow contractors to
use standard programming techniques.
Thanks a lot in advance for your help!
Nicolas Verhaeghe wrote:

>I have SQL Server 2000 setup on a SBS 2003 Premium server, with Exchange
>2003.
>I set up SQL Mail to use the only profile available, which is
>"ExchangeAdmin SBS (0x codes following)".
Hmmm, not sure where that's from, since SBS normally has no MAPI profiles
at all by default.
Have you configured SQL Server and all associated services to run under a
user account, rather than LocalSystem (the default)?

>When I try a simple xp_sendmail to an existing email address, I get the
>following:
>xp_sendmail: failed with mail error 0x80004005
>When I search Microsoft.com, or all of the Web, I see that there is a
>workaround specified by Microsoft:
>http://support.microsoft.com/kb/293422/EN-US/
>The problem is that I cannot "Locate the user object directly associated
>with the Exchange 2000 mailbox". First of, I have Exchange 2003, not 2000.
>Second, I cannot find the specified "ExchangeAdmin SBS ..." account.
It's not an account, it's a MAPI profile belonging to a user account. MAPI
profiles belong to user accounts, and can only be accessed and manipulated
by the user account they belong to.

>I also tried installing Outlook, creating a profile with a user called
>"SQLEmailAccount", so that I could locate it in AD and apply the
>workaround, but when I open Enterprise manager, and try to select this
>email profile for SQL Mail (as described at the top of this email), it
>simply does not appear...
AARGH. Get Outlook *OFF* your SBS as fast as possible. Outlook is *not*
supported for installation on an Exchange Server (like SBS).

>It seems that I can nonetheless use a workaround, as I found a few SPs
>which create a CDO object (a bit like what you would do in ASP) and talk
>to it, but I'd like to be able to use xp_sendmail in order to allow
>contractors to use standard programming techniques.
The KB articles you need are:
304967 How to Configure SQL Server to Send Email on SBS 2000
http://support.microsoft.com/?id=304967
and
228736 SAMPLE Profman2.exe - MAPI Profile Manager v2.0
http://support.microsoft.com/?id=228736
While the first article says SBS2000, it applies equally to SBS2003. But
creating the MAPI profile is much easier to do with PROFMAN (from the
second KB) than all the registry hacking the first article suggests you do.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Cannot setup SQL Mail on SBS 2003

I have SQL Server 2000 setup on a SBS 2003 Premium server, with Exchange
2003.
I set up SQL Mail to use the only profile available, which is "ExchangeAdmin
SBS (0x codes following)".
When I try a simple xp_sendmail to an existing email address, I get the
following:
xp_sendmail: failed with mail error 0x80004005
When I search Microsoft.com, or all of the Web, I see that there is a
workaround specified by Microsoft:
http://support.microsoft.com/kb/293422/EN-US/
The problem is that I cannot "Locate the user object directly associated
with the Exchange 2000 mailbox". First of, I have Exchange 2003, not 2000.
Second, I cannot find the specified "ExchangeAdmin SBS ..." account.
I also tried installing Outlook, creating a profile with a user called
"SQLEmailAccount", so that I could locate it in AD and apply the workaround,
but when I open Enterprise manager, and try to select this email profile for
SQL Mail (as described at the top of this email), it simply does not
appear...
It seems that I can nonetheless use a workaround, as I found a few SPs which
create a CDO object (a bit like what you would do in ASP) and talk to it,
but I'd like to be able to use xp_sendmail in order to allow contractors to
use standard programming techniques.
Thanks a lot in advance for your help!Nicolas XXXXXXXXX wrote:

>I have SQL Server 2000 setup on a SBS 2003 Premium server, with Exchange
>2003.
>I set up SQL Mail to use the only profile available, which is
>"ExchangeAdmin SBS (0x codes following)".
Hmmm, not sure where that's from, since SBS normally has no MAPI profiles
at all by default.
Have you configured SQL Server and all associated services to run under a
user account, rather than LocalSystem (the default)?

>When I try a simple xp_sendmail to an existing email address, I get the
>following:
>xp_sendmail: failed with mail error 0x80004005
>When I search Microsoft.com, or all of the Web, I see that there is a
>workaround specified by Microsoft:
>http://support.microsoft.com/kb/293422/EN-US/
>The problem is that I cannot "Locate the user object directly associated
>with the Exchange 2000 mailbox". First of, I have Exchange 2003, not 2000.
>Second, I cannot find the specified "ExchangeAdmin SBS ..." account.
It's not an account, it's a MAPI profile belonging to a user account. MAPI
profiles belong to user accounts, and can only be accessed and manipulated
by the user account they belong to.

>I also tried installing Outlook, creating a profile with a user called
>"SQLEmailAccount", so that I could locate it in AD and apply the
>workaround, but when I open Enterprise manager, and try to select this
>email profile for SQL Mail (as described at the top of this email), it
>simply does not appear...
AARGH. Get Outlook *OFF* your SBS as fast as possible. Outlook is *not*
supported for installation on an Exchange Server (like SBS).

>It seems that I can nonetheless use a workaround, as I found a few SPs
>which create a CDO object (a bit like what you would do in ASP) and talk
>to it, but I'd like to be able to use xp_sendmail in order to allow
>contractors to use standard programming techniques.
The KB articles you need are:
304967 How to Configure SQL Server to Send Email on SBS 2000
http://support.microsoft.com/?id=304967
and
228736 SAMPLE Profman2.exe - MAPI Profile Manager v2.0
http://support.microsoft.com/?id=228736
While the first article says SBS2000, it applies equally to SBS2003. But
creating the MAPI profile is much easier to do with PROFMAN (from the
second KB) than all the registry hacking the first article suggests you do.
Steve Foster [SBS MVP]
---
MVPs do not work for Microsoft. Please reply only to the newsgroups.