In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
Thanks
SalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default...b;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB)42147483647470470
min server memory (MB)02147483647256256
set working set size0111
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/default...b;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you should
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>
Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts
Monday, March 26, 2012
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks
Error 823, Severity: 24
In the event viewer, I am getting an error "17122 : Initdata: Warning: Could
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
not set working size to 470281KB.
My sql is configured to have min = 128 and max RAM = 480281 in the server
properties
sheet(fixed memory configurarion).
What is SQL trying to set here and whjy?
ThanksSalamElias,
I am afraid that I don't really know what is happening, but I see that 823
is a Windows I/O error. When it happens it usually is followed by another
error. One KB article on this is:
http://support.microsoft.com/defaul...kb;en-us;274310
Do you have "set working set size" set to 1 instead of 0? If so, you should
have the min and max server memory set the same.
FWIW,
Russell Fields
"SalamElias" <eliassal@.online.nospam> wrote in message
news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> In the event viewer, I am getting an error "17122 : Initdata: Warning:
Could
> not set working size to 470281KB.
> My sql is configured to have min = 128 and max RAM = 480281 in the server
> properties
> sheet(fixed memory configurarion).
> What is SQL trying to set here and whjy?
> Thanks|||I ran sp_Configure, Ihave the folowing figues :
sp_configure
max server memory (MB) 4 2147483647 470 470
min server memory (MB) 0 2147483647 256 256
set working set size 0 1 1 1
When I the server RAM proprty sheet, Dynamically configure SQL Server
memoery with the min and max values indicated above as well as the "Reserve
physical memory for SQL Server " is checked.
So what should I do to stilluse these min max values and not set them both
with the same value
Thanks
Do you mean that I should have min = max = 470
"Russell Fields" wrote:
> SalamElias,
> I am afraid that I don't really know what is happening, but I see that 823
> is a Windows I/O error. When it happens it usually is followed by another
> error. One KB article on this is:
> http://support.microsoft.com/defaul...kb;en-us;274310
> Do you have "set working set size" set to 1 instead of 0? If so, you shou
ld
> have the min and max server memory set the same.
> FWIW,
> Russell Fields
> "SalamElias" <eliassal@.online.nospam> wrote in message
> news:51E27D77-090D-48F6-81DD-EB4203BCFCAE@.microsoft.com...
> Could
>
>sql
Sunday, February 19, 2012
Error 22022: Problems with email
We have a number of SQL Servers up and running. Until recently, all but one
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know:)
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know:)
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
Error 22022: Problems with email
We have a number of SQL Servers up and running. Until recently, all but one
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
Chris
Hi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
Chris
Hi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in message
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>
|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
Error 22022: Problems with email
We have a number of SQL Servers up and running. Until recently, all but one
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
were joined to our domain, and were configured correctly to send email (in
response to scheduled tasks etc).
We have now added the last server to the domain - however, this server is
configured for email but via Mercury rather than Exchange.
I'm not sure if it this alternative setup, or whether I have done something
wrong with the configuration, but when I use the Test facility in the
Reporting tab, I get the following error:
"Error 22022: SQLServerAgent. Error: The SQLServerAgent mail session is not
running; check the mail profile and/or the SQLServerAgent Service startup
account in the SQLServerAgent properties dialog"
Other points to note:
I've just changed the SQLServer account (and SQLServer Agent) to use a new
account that is an ordinary domain user, and a local machine admin.
When selecting the MAPI profile in SQL Mail, the Test feature works OK.
I can send POP3 emails from Outlook successfully.
There is no Global Address List to pick an email account from (since the
email server is mercury). I tried creating an Outlook contact for the
operator, which *can* be selected within SQL Server, but this didnt work
either.
I'm not sure if any of these points are helpful, but I thought might
possibly be relevant.
Thanks in advance...
ChrisHi Chris,
From your descriptions, I understood that your SQL Mail could not work
successfully with the error 22022 using Mercury mail system. Have I
understood you? If there is anything I misunderstood, please feel free to
let me know
First of all, I am not sure whether Mercury could be used instead of
Exchange Server. BTW, I am afraid it doesn't
Anyway, you could do the following steps to troubleshooting this issue
1. make sure your SQL Agent account and SQL Server start-up account are
correct
(you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
Click "Properties" -> Log On -> This account)
2. ensured that sqlagent is configured with a valid mail profile, and then
restart sql agent
3. Are you able to send mail with that profile and with xp_sendmail?
4. Try to create a new mail profile associating to SQL Agent Mail and try
again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I have decided to wait until the email server is upgraded to Exchange 2003,
and then try again..
Thanks
""Mingqing Cheng [MSFT]"" <v-mingqc@.online.microsoft.com> wrote in messa
ge
news:dgT4LEwYEHA.2688@.cpmsftngxa06.phx.gbl...
> Hi Chris,
> From your descriptions, I understood that your SQL Mail could not work
> successfully with the error 22022 using Mercury mail system. Have I
> understood you? If there is anything I misunderstood, please feel free to
> let me know
> First of all, I am not sure whether Mercury could be used instead of
> Exchange Server. BTW, I am afraid it doesn't
> Anyway, you could do the following steps to troubleshooting this issue
> 1. make sure your SQL Agent account and SQL Server start-up account are
> correct
> (you could go Start -> Run -> "services.msc" -> SQLServerAgent -> Right
> Click "Properties" -> Log On -> This account)
> 2. ensured that sqlagent is configured with a valid mail profile, and then
> restart sql agent
> 3. Are you able to send mail with that profile and with xp_sendmail?
> 4. Try to create a new mail profile associating to SQL Agent Mail and try
> again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are here to be of assistance!
>
> Sincerely yours,
> Mingqing Cheng
> Microsoft Developer Community Support
> ---
> Introduction to Yukon! - http://www.microsoft.com/sql/yukon
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>|||Hi,
Thanks for your updates!
Would you so kind as to give me a time schedule so that I could follow up
in time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||After speaking to my colleagues, it appears it will be a good 3 months until
we get the servers upgraded, so just forget about it.
I'll repost if I still get problems then.
Thanks
Chris
Subscribe to:
Posts (Atom)