Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts

Monday, March 26, 2012

Error 8198: Unable to determine if the owner has server access...

We recently converted our NT 4 domain to Active Directory, and jobs started
failing with messages like the following. Evidently, SQL Server is having
trouble verifying the credentials of the job owner:
The job failed. Unable to determine if the owner (<Domain>\<user> ) of job
<JobName> has server access (reason: Could not obtain information about
Windows NT group/user (<Domain>\<user> ) '. [SQLSTATE 42000] (Error 8198)
).
I see there are KB articles talking about pre-2000 compatibility, but both
the domain controller and the SQL Server machine are running Windows Server
2003. Does anyone know how to fix this?
(Yes, you can change the job owner as a workaround, but this won't keep
future jobs from being owned by Windows users unless we switch everyone over
to SQL authentication)
Thanks.Check this kb;
825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
Start
http://support.microsoft.com/?id=825042
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

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

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

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

Friday, February 17, 2012

Error 21776:

I'm doing the following:
use master
exec sp_grantlogin 'DOMAIN\ug_ITSec_SQL'
exec sp_addsrvrolemember 'DOMAIN\ug_ITSec_SQL', 'securityadmin'
Then after, trying to grant that new login db_owner permissions, for
example, by running the following:
use master
go
exec sp_grantdbaccess 'DOMAIN\ug_ITSec_SQL', 'ug_ITSec_SQL'
exec sp_addrolemember 'db_owner','ug_ITSec_SQL'
However, when I then click on the Login and check out the database access, I
get the following strange error:
"Error 21776: [SQL-DMO] The name 'ug_ITSec_SQL' was not found in the Use
rs
collection. If the name is a qualified name use [] to seprate the vario
us
parts of the name, then try again."
However, once I go to the individual database - master in this case, and
click on the User, view it, close it, and go back to the Login... it is all
cleared up. As if clicking and viewing the User in the database cleared
something up?
Anyone ever see this sort of behavior?I think we can forget it - some information is getting cached somewhere,
somehow, but closing and re-launching Enterprise Manager seems to clear it
up.
Now that I've spent a half day scouring the Internet and newsgroups, I can
continue with my script that was working! It was just bothersome that I
couldn't immediately check the properties of the login without getting that
error.
"A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
news:uwaWqeatGHA.1888@.TK2MSFTNGP03.phx.gbl...
> I'm doing the following:
> use master
> exec sp_grantlogin 'DOMAIN\ug_ITSec_SQL'
> exec sp_addsrvrolemember 'DOMAIN\ug_ITSec_SQL', 'securityadmin'
> Then after, trying to grant that new login db_owner permissions, for
> example, by running the following:
> use master
> go
> exec sp_grantdbaccess 'DOMAIN\ug_ITSec_SQL', 'ug_ITSec_SQL'
> exec sp_addrolemember 'db_owner','ug_ITSec_SQL'
>
> However, when I then click on the Login and check out the database access,
> I get the following strange error:
> "Error 21776: [SQL-DMO] The name 'ug_ITSec_SQL' was not found in the U
sers
> collection. If the name is a qualified name use [] to seprate the var
ious
> parts of the name, then try again."
> However, once I go to the individual database - master in this case, and
> click on the User, view it, close it, and go back to the Login... it is
> all cleared up. As if clicking and viewing the User in the database
> cleared something up?
> Anyone ever see this sort of behavior?
>|||> Anyone ever see this sort of behavior?
Yes, this is normal. The GUI object browser caches data for performance
reasons. When changes are made externally, you need to manually refresh the
tree by right-clicking and selecting refresh.
Hope this helps.
Dan Guzman
SQL Server MVP
"A McGuire" <allen.mcguire@.gmail.com.invalid> wrote in message
news:uwaWqeatGHA.1888@.TK2MSFTNGP03.phx.gbl...
> I'm doing the following:
> use master
> exec sp_grantlogin 'DOMAIN\ug_ITSec_SQL'
> exec sp_addsrvrolemember 'DOMAIN\ug_ITSec_SQL', 'securityadmin'
> Then after, trying to grant that new login db_owner permissions, for
> example, by running the following:
> use master
> go
> exec sp_grantdbaccess 'DOMAIN\ug_ITSec_SQL', 'ug_ITSec_SQL'
> exec sp_addrolemember 'db_owner','ug_ITSec_SQL'
>
> However, when I then click on the Login and check out the database access,
> I get the following strange error:
> "Error 21776: [SQL-DMO] The name 'ug_ITSec_SQL' was not found in the U
sers
> collection. If the name is a qualified name use [] to seprate the var
ious
> parts of the name, then try again."
> However, once I go to the individual database - master in this case, and
> click on the User, view it, close it, and go back to the Login... it is
> all cleared up. As if clicking and viewing the User in the database
> cleared something up?
> Anyone ever see this sort of behavior?
>