This is too weird.
I'm following
http://support.microsoft.com/Defaul...1/wct091301.asp
to troubleshoot why SQLAgentMail does not send notifications on our SQL 2000
server. Looks like I need to logon as the startup user account to get mail
profile configured. But after I logon the SQL server using the startup
domain account that runs both the server and the agent, I don't see any Mail
icon in the control panel. Logging on as other users does not have this
problem.
Any ideas?
BingHave you considered other alternatives?
http://www.aspfaq.com/2403
http://www.aspfaq.com/
(Reverse address to reply.)
"bing" <bing@.discussions.microsoft.com> wrote in message
news:3B45529C-D273-4B72-9DEA-B01E13BC6F2C@.microsoft.com...
> This is too weird.
> I'm following
>
http://support.microsoft.com/Defaul...1/wct091301.asp
> to troubleshoot why SQLAgentMail does not send notifications on our SQL
2000
> server. Looks like I need to logon as the startup user account to get
mail
> profile configured. But after I logon the SQL server using the startup
> domain account that runs both the server and the agent, I don't see any
Mail
> icon in the control panel. Logging on as other users does not have this
> problem.
> Any ideas?
> Bing|||That indicates that mail is not configured for the service
account you are logging in as. Follow the steps in the
following:
INF: How to Configure SQL Mail
http://support.microsoft.com/?id=263556
-Sue
On Tue, 18 Jan 2005 14:57:02 -0800, "bing"
<bing@.discussions.microsoft.com> wrote:
>This is too weird.
>I'm following
>http://support.microsoft.com/Defaul...1/wct091301.asp
>to troubleshoot why SQLAgentMail does not send notifications on our SQL 200
0
>server. Looks like I need to logon as the startup user account to get mail
>profile configured. But after I logon the SQL server using the startup
>domain account that runs both the server and the agent, I don't see any Mai
l
>icon in the control panel. Logging on as other users does not have this
>problem.
>Any ideas?
>Bing|||Yup, you said it right. Looks like Microsoft office outlook was upgraded
from 2000 to 2003 on our SQL server at some point. But the mail
configuration for the SQL service account was not maintained at the same
time. I just went into outlook 2003 and get mail configured for the service
account. SQLAgentMail works fine now. Thanks all who replied.
Bing
"Sue Hoegemeier" wrote:
> That indicates that mail is not configured for the service
> account you are logging in as. Follow the steps in the
> following:
> INF: How to Configure SQL Mail
> http://support.microsoft.com/?id=263556
> -Sue
> On Tue, 18 Jan 2005 14:57:02 -0800, "bing"
> <bing@.discussions.microsoft.com> wrote:
>
>|||Glad it was that easy to sort out. In my experience, it usually involves a
lot more hair- and teeth-pulling. :-)
http://www.aspfaq.com/
(Reverse address to reply.)
"bing" <bing@.discussions.microsoft.com> wrote in message
news:382E13A2-F995-4FE0-86F4-124CA6BB3210@.microsoft.com...
> Yup, you said it right. Looks like Microsoft office outlook was upgraded
> from 2000 to 2003 on our SQL server at some point. But the mail
> configuration for the SQL service account was not maintained at the same
> time. I just went into outlook 2003 and get mail configured for the
service
> account. SQLAgentMail works fine now. Thanks all who replied.
>
Showing posts with label defaul. Show all posts
Showing posts with label defaul. Show all posts
Friday, March 30, 2012
No Mail icon in control panel?
Labels:
aspto,
control,
database,
defaul,
followinghttp,
icon,
mail,
microsoft,
mysql,
notifications,
oracle,
panel,
server,
sql,
sqlagentmail,
troubleshoot,
wct091301,
weird
Monday, March 26, 2012
No disk in drive a:
Hi RM,
Have a look at this:
http://support.microsoft.com/defaul...;281345&sd=tech
Ray
"RM" wrote:
> Good morning
> We ask for help please for the following:
> From a Windows XP SP2 via Terminal Services (mstsc.exe) we were accessing
a
> Windows Server 2003 SP1/SQL 2000 SP4.
> After remote instruction to be restarted the SQL Server Service, this
> service aparentely stops OK, but does not start again
> with an error on the master Database.
> Note: in Task Manager the SQL Process was still active, not possible to
> eliminate
> After some attempts to restart the service, we note that other DBs were al
so
> alocated. Allways working via Terminal.
>
> When finally we went to the phisical Server, to restart the machine, we no
te
> the dialog message: There is no disk in drive a:
> Note: this dialog does not appear on the terminal side
> When this msg was accepted the situation was reestablished.
>
> Is this a known error?
> How to solve?
> How to be sure that the dialog msg is really mapped to the Terminal
> environment?
> Thanks
> Regards
> Rui Mendon?a
>
>Good morning
We ask for help please for the following:
From a Windows XP SP2 via Terminal Services (mstsc.exe) we were accessing a
Windows Server 2003 SP1/SQL 2000 SP4.
After remote instruction to be restarted the SQL Server Service, this
service aparentely stops OK, but does not start again
with an error on the master Database.
Note: in Task Manager the SQL Process was still active, not possible to
eliminate
After some attempts to restart the service, we note that other DBs were also
alocated. Allways working via Terminal.
When finally we went to the phisical Server, to restart the machine, we note
the dialog message: There is no disk in drive a:
Note: this dialog does not appear on the terminal side
When this msg was accepted the situation was reestablished.
Is this a known error?
How to solve?
How to be sure that the dialog msg is really mapped to the Terminal
environment?
Thanks
Regards
Rui Mendona|||Hi RM,
Have a look at this:
http://support.microsoft.com/defaul...;281345&sd=tech
Ray
"RM" wrote:
> Good morning
> We ask for help please for the following:
> From a Windows XP SP2 via Terminal Services (mstsc.exe) we were accessing
a
> Windows Server 2003 SP1/SQL 2000 SP4.
> After remote instruction to be restarted the SQL Server Service, this
> service aparentely stops OK, but does not start again
> with an error on the master Database.
> Note: in Task Manager the SQL Process was still active, not possible to
> eliminate
> After some attempts to restart the service, we note that other DBs were al
so
> alocated. Allways working via Terminal.
>
> When finally we went to the phisical Server, to restart the machine, we no
te
> the dialog message: There is no disk in drive a:
> Note: this dialog does not appear on the terminal side
> When this msg was accepted the situation was reestablished.
>
> Is this a known error?
> How to solve?
> How to be sure that the dialog msg is really mapped to the Terminal
> environment?
> Thanks
> Regards
> Rui Mendon?a
>
>|||Hello Rui,
I agree with Ray this issue is related to default error mode handling. Some
settings in terminal session blocks the error dialog which causes the
process of SQL Server to hang. You may want to check if you log on to
Windows with same domain user account and if the issue occurs with other
user account.
Also, please change the registry key ErrorMode Value = 2 to see if there is
any side effect. Usually this error message "There is no disk in drive a:"
does not cause real issue and can be ignored. You may still see the
information logged in event log though the dialog does not prompt.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Rui,
I agree with Ray this issue is related to default error mode handling. Some
settings in terminal session blocks the error dialog which causes the
process of SQL Server to hang. You may want to check if you log on to
Windows with same domain user account and if the issue occurs with other
user account.
Also, please change the registry key ErrorMode Value = 2 to see if there is
any side effect. Usually this error message "There is no disk in drive a:"
does not cause real issue and can be ignored. You may still see the
information logged in event log though the dialog does not prompt.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I Thank you all for the help.
I have posted a very urgent situation in "microsoft.public.sqlserver.server"
with the name "Event ID: 17052 Urgent"
Please Help
Thanks a lot
Rui Mendona
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:sJNUcJalGHA.5164@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> I agree with Ray this issue is related to default error mode handling.
> Some
> settings in terminal session blocks the error dialog which causes the
> process of SQL Server to hang. You may want to check if you log on to
> Windows with same domain user account and if the issue occurs with other
> user account.
> Also, please change the registry key ErrorMode Value = 2 to see if there
> is
> any side effect. Usually this error message "There is no disk in drive a:"
> does not cause real issue and can be ignored. You may still see the
> information logged in event log though the dialog does not prompt.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||I Thank you all for the help.
I have posted a very urgent situation in "microsoft.public.sqlserver.server"
with the name "Event ID: 17052 Urgent"
Please Help
Thanks a lot
Rui Mendona
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:sJNUcJalGHA.5164@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> I agree with Ray this issue is related to default error mode handling.
> Some
> settings in terminal session blocks the error dialog which causes the
> process of SQL Server to hang. You may want to check if you log on to
> Windows with same domain user account and if the issue occurs with other
> user account.
> Also, please change the registry key ErrorMode Value = 2 to see if there
> is
> any side effect. Usually this error message "There is no disk in drive a:"
> does not cause real issue and can be ignored. You may still see the
> information logged in event log though the dialog does not prompt.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Rui,
Please note I'v replied in that in that thread. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Rui,
Please note I'v replied in that in that thread. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Have a look at this:
http://support.microsoft.com/defaul...;281345&sd=tech
Ray
"RM" wrote:
> Good morning
> We ask for help please for the following:
> From a Windows XP SP2 via Terminal Services (mstsc.exe) we were accessing
a
> Windows Server 2003 SP1/SQL 2000 SP4.
> After remote instruction to be restarted the SQL Server Service, this
> service aparentely stops OK, but does not start again
> with an error on the master Database.
> Note: in Task Manager the SQL Process was still active, not possible to
> eliminate
> After some attempts to restart the service, we note that other DBs were al
so
> alocated. Allways working via Terminal.
>
> When finally we went to the phisical Server, to restart the machine, we no
te
> the dialog message: There is no disk in drive a:
> Note: this dialog does not appear on the terminal side
> When this msg was accepted the situation was reestablished.
>
> Is this a known error?
> How to solve?
> How to be sure that the dialog msg is really mapped to the Terminal
> environment?
> Thanks
> Regards
> Rui Mendon?a
>
>Good morning
We ask for help please for the following:
From a Windows XP SP2 via Terminal Services (mstsc.exe) we were accessing a
Windows Server 2003 SP1/SQL 2000 SP4.
After remote instruction to be restarted the SQL Server Service, this
service aparentely stops OK, but does not start again
with an error on the master Database.
Note: in Task Manager the SQL Process was still active, not possible to
eliminate
After some attempts to restart the service, we note that other DBs were also
alocated. Allways working via Terminal.
When finally we went to the phisical Server, to restart the machine, we note
the dialog message: There is no disk in drive a:
Note: this dialog does not appear on the terminal side
When this msg was accepted the situation was reestablished.
Is this a known error?
How to solve?
How to be sure that the dialog msg is really mapped to the Terminal
environment?
Thanks
Regards
Rui Mendona|||Hi RM,
Have a look at this:
http://support.microsoft.com/defaul...;281345&sd=tech
Ray
"RM" wrote:
> Good morning
> We ask for help please for the following:
> From a Windows XP SP2 via Terminal Services (mstsc.exe) we were accessing
a
> Windows Server 2003 SP1/SQL 2000 SP4.
> After remote instruction to be restarted the SQL Server Service, this
> service aparentely stops OK, but does not start again
> with an error on the master Database.
> Note: in Task Manager the SQL Process was still active, not possible to
> eliminate
> After some attempts to restart the service, we note that other DBs were al
so
> alocated. Allways working via Terminal.
>
> When finally we went to the phisical Server, to restart the machine, we no
te
> the dialog message: There is no disk in drive a:
> Note: this dialog does not appear on the terminal side
> When this msg was accepted the situation was reestablished.
>
> Is this a known error?
> How to solve?
> How to be sure that the dialog msg is really mapped to the Terminal
> environment?
> Thanks
> Regards
> Rui Mendon?a
>
>|||Hello Rui,
I agree with Ray this issue is related to default error mode handling. Some
settings in terminal session blocks the error dialog which causes the
process of SQL Server to hang. You may want to check if you log on to
Windows with same domain user account and if the issue occurs with other
user account.
Also, please change the registry key ErrorMode Value = 2 to see if there is
any side effect. Usually this error message "There is no disk in drive a:"
does not cause real issue and can be ignored. You may still see the
information logged in event log though the dialog does not prompt.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Rui,
I agree with Ray this issue is related to default error mode handling. Some
settings in terminal session blocks the error dialog which causes the
process of SQL Server to hang. You may want to check if you log on to
Windows with same domain user account and if the issue occurs with other
user account.
Also, please change the registry key ErrorMode Value = 2 to see if there is
any side effect. Usually this error message "There is no disk in drive a:"
does not cause real issue and can be ignored. You may still see the
information logged in event log though the dialog does not prompt.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I Thank you all for the help.
I have posted a very urgent situation in "microsoft.public.sqlserver.server"
with the name "Event ID: 17052 Urgent"
Please Help
Thanks a lot
Rui Mendona
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:sJNUcJalGHA.5164@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> I agree with Ray this issue is related to default error mode handling.
> Some
> settings in terminal session blocks the error dialog which causes the
> process of SQL Server to hang. You may want to check if you log on to
> Windows with same domain user account and if the issue occurs with other
> user account.
> Also, please change the registry key ErrorMode Value = 2 to see if there
> is
> any side effect. Usually this error message "There is no disk in drive a:"
> does not cause real issue and can be ignored. You may still see the
> information logged in event log though the dialog does not prompt.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||I Thank you all for the help.
I have posted a very urgent situation in "microsoft.public.sqlserver.server"
with the name "Event ID: 17052 Urgent"
Please Help
Thanks a lot
Rui Mendona
""privatenews"" <petery@.online.microsoft.com> wrote in message
news:sJNUcJalGHA.5164@.TK2MSFTNGXA01.phx.gbl...
> Hello Rui,
> I agree with Ray this issue is related to default error mode handling.
> Some
> settings in terminal session blocks the error dialog which causes the
> process of SQL Server to hang. You may want to check if you log on to
> Windows with same domain user account and if the issue occurs with other
> user account.
> Also, please change the registry key ErrorMode Value = 2 to see if there
> is
> any side effect. Usually this error message "There is no disk in drive a:"
> does not cause real issue and can be ignored. You may still see the
> information logged in event log though the dialog does not prompt.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Rui,
Please note I'v replied in that in that thread. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Rui,
Please note I'v replied in that in that thread. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)