Showing posts with label login. Show all posts
Showing posts with label login. Show all posts

Thursday, March 22, 2012

Email Subscription Problem

Regards,
When a non administrative person sets up an email subscription to a
particular report, the "to" field defaults to their login name rather than
their email address.
So for jsmith@.microsoft.com, the "to" field defaults to "jsmith" and is read
only so it can't be changed.
Once the subscription is made, the email goes to jsmith, which doesn't
resolve to anything causing a bounce-back.
Is there a setting to tell Reporting Services to use the AD email address
for users if available? Or is there a way to default the domain for missing
domains?
There has to be a setting in one of the config files.
Any help would be greatly appreciated!
Benjamin PierceIf all you need is to add host name to the email, there is a DefaultHostName
element in the RSReportServer config file. This will add the host name to
any email address that does not have one.
If you want all users to be able to edit the TO line set the
SendEmailToUserAlias element to false and then every user will have a blank
TO line that they can set.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Benjamin Pierce" <bpierce@.opentext.com> wrote in message
news:OmZZyvLTFHA.3264@.TK2MSFTNGP15.phx.gbl...
> Regards,
> When a non administrative person sets up an email subscription to a
> particular report, the "to" field defaults to their login name rather than
> their email address.
> So for jsmith@.microsoft.com, the "to" field defaults to "jsmith" and is
> read
> only so it can't be changed.
> Once the subscription is made, the email goes to jsmith, which doesn't
> resolve to anything causing a bounce-back.
> Is there a setting to tell Reporting Services to use the AD email address
> for users if available? Or is there a way to default the domain for
> missing
> domains?
> There has to be a setting in one of the config files.
> Any help would be greatly appreciated!
> Benjamin Pierce
>|||Thanks Daniel,
Adding a DefaultHostName worked like a charm. VERY MUCH APPRECIATED!
Benjamin Pierce
"Daniel Reib (MSFT)" <danreib@.online.microsoft.com> wrote in message
news:O9fs3QQTFHA.3188@.TK2MSFTNGP09.phx.gbl...
> If all you need is to add host name to the email, there is a
DefaultHostName
> element in the RSReportServer config file. This will add the host name to
> any email address that does not have one.
> If you want all users to be able to edit the TO line set the
> SendEmailToUserAlias element to false and then every user will have a
blank
> TO line that they can set.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Benjamin Pierce" <bpierce@.opentext.com> wrote in message
> news:OmZZyvLTFHA.3264@.TK2MSFTNGP15.phx.gbl...
> > Regards,
> >
> > When a non administrative person sets up an email subscription to a
> > particular report, the "to" field defaults to their login name rather
than
> > their email address.
> >
> > So for jsmith@.microsoft.com, the "to" field defaults to "jsmith" and is
> > read
> > only so it can't be changed.
> >
> > Once the subscription is made, the email goes to jsmith, which doesn't
> > resolve to anything causing a bounce-back.
> >
> > Is there a setting to tell Reporting Services to use the AD email
address
> > for users if available? Or is there a way to default the domain for
> > missing
> > domains?
> >
> > There has to be a setting in one of the config files.
> >
> > Any help would be greatly appreciated!
> >
> > Benjamin Pierce
> >
> >
>

Friday, March 9, 2012

EM vs QA login

This morning I have a (2000) server that continually
times out when I try to connect via Ent. Manager. It is
registred through an sa Sql Server login that has not
changed in months. Also, I upped the login timeout in EM
to 10 seconds and it still timed out.
The odd thin is this: I can connect instantly through
Query Analyzer through this same sa login and the server
looks very quiet in Perf Mon.
Is there something different about how Sql Server logins
through Enterprise Manager? Any ideas what would cause
this?
The login process should be the same. Though, EM will try to execute a bunch
of queries after a successful login to get server/database properties.
Try up the timeout to at least 60 seconds.
-oj
"Stsh" <anonymous@.discussions.microsoft.com> wrote in message
news:057301c53ebe$672f0410$a501280a@.phx.gbl...
> This morning I have a (2000) server that continually
> times out when I try to connect via Ent. Manager. It is
> registred through an sa Sql Server login that has not
> changed in months. Also, I upped the login timeout in EM
> to 10 seconds and it still timed out.
> The odd thin is this: I can connect instantly through
> Query Analyzer through this same sa login and the server
> looks very quiet in Perf Mon.
> Is there something different about how Sql Server logins
> through Enterprise Manager? Any ideas what would cause
> this?

EM vs QA login

This morning I have a (2000) server that continually
times out when I try to connect via Ent. Manager. It is
registred through an sa Sql Server login that has not
changed in months. Also, I upped the login timeout in EM
to 10 seconds and it still timed out.
The odd thin is this: I can connect instantly through
Query Analyzer through this same sa login and the server
looks very quiet in Perf Mon.
Is there something different about how Sql Server logins
through Enterprise Manager? Any ideas what would cause
this?The login process should be the same. Though, EM will try to execute a bunch
of queries after a successful login to get server/database properties.
Try up the timeout to at least 60 seconds.
--
-oj
"Stsh" <anonymous@.discussions.microsoft.com> wrote in message
news:057301c53ebe$672f0410$a501280a@.phx.gbl...
> This morning I have a (2000) server that continually
> times out when I try to connect via Ent. Manager. It is
> registred through an sa Sql Server login that has not
> changed in months. Also, I upped the login timeout in EM
> to 10 seconds and it still timed out.
> The odd thin is this: I can connect instantly through
> Query Analyzer through this same sa login and the server
> looks very quiet in Perf Mon.
> Is there something different about how Sql Server logins
> through Enterprise Manager? Any ideas what would cause
> this?

EM vs QA login

This morning I have a (2000) server that continually
times out when I try to connect via Ent. Manager. It is
registred through an sa Sql Server login that has not
changed in months. Also, I upped the login timeout in EM
to 10 seconds and it still timed out.
The odd thin is this: I can connect instantly through
Query Analyzer through this same sa login and the server
looks very quiet in Perf Mon.
Is there something different about how Sql Server logins
through Enterprise Manager? Any ideas what would cause
this?The login process should be the same. Though, EM will try to execute a bunch
of queries after a successful login to get server/database properties.
Try up the timeout to at least 60 seconds.
-oj
"Stsh" <anonymous@.discussions.microsoft.com> wrote in message
news:057301c53ebe$672f0410$a501280a@.phx.gbl...
> This morning I have a (2000) server that continually
> times out when I try to connect via Ent. Manager. It is
> registred through an sa Sql Server login that has not
> changed in months. Also, I upped the login timeout in EM
> to 10 seconds and it still timed out.
> The odd thin is this: I can connect instantly through
> Query Analyzer through this same sa login and the server
> looks very quiet in Perf Mon.
> Is there something different about how Sql Server logins
> through Enterprise Manager? Any ideas what would cause
> this?

Wednesday, March 7, 2012

EM does not display Login Name

All,
After adding Domain users to a database I get the situation where some
display in the "Users" section without a Login Name.
The users still function correctly, but some have Login Names and some
don't. Another note is that we have Production and Test servers on differen
t
boxes and a user can display different ways on each.
So, my question is, why does this happen? And more importantly, is there
some subtle problem behind the scenes that means I can't just ignore this
symptom?
Thanks,
Simon.
P.S. For example:
Name Login Name Database Access
---
User1 Domain\U1 Permit
User2 Permit
User3 Domain\U3 Permit
^- no login name for Domain\U2Simon wrote:

> Name Login Name Database Access
> ---
> User1 Domain\U1 Permit
> User2 Permit
> User3 Domain\U3 Permit
> ^- no login name for Domain\U2
Simon,
we are encountering the same effect, when I do a RESTORE from a Database Bac
kup
from a Server which is not in the Windows Domain. I suppose it has something
to
do with an orphaned User SID.
I suppose when you enter
use mydb
sp_helpuser
you get NULL in the Login column.
Suggestion: Use a script with 'sp_dropuser' resp. 'sp_revokedbaccess' and 'g
rantdbaccess' to delete and rebuild the
user(s).
If the DB owner user dbo is also void, use 'sp_changedbowner' to reassign it
.
Joachim|||Hi Joachim,
Yes, sp_helpuser does return null. However, we are using a script with the
mentioned sp's to add users to this database. Way the app works is by a use
r
entering details passed through to the script (sp). Some work, some don't.
We have two machines (Prod & Test) and the results can differ. UserA might
be fine on Prod but not on Test, UserB might befine on Test but not on Prod.
Repeatedly dropping and adding the user gets consistent results on each
machine, whether that be by script, Query Analyser, Enterprise Manager. I
can spot no common denominator, and have found no way to make a "nulling"
user not-null.
Only other thing that I can think worth mentioning: at the Security | Logins
level we have added "Domain\All Users" to grant all users server access.
Database access is granted on a user by user basis (via the script mentioned
earlier.)
Simon.
"Joachim Hofmann" wrote:

> Simon wrote:
>
> Simon,
> we are encountering the same effect, when I do a RESTORE from a Database B
ackup
> from a Server which is not in the Windows Domain. I suppose it has somethi
ng to
> do with an orphaned User SID.
> I suppose when you enter
> use mydb
> sp_helpuser
> you get NULL in the Login column.
> Suggestion: Use a script with 'sp_dropuser' resp. 'sp_revokedbaccess' and
'grantdbaccess' to delete and rebuild the
> user(s).
> If the DB owner user dbo is also void, use 'sp_changedbowner' to reassign
it.
>
> Joachim
>|||You can have null for the login name where there isn't a
matching record in the syslogins table in the master
database. The syslogins table and the sysusers table will be
joined on sid. If no matching record is found in syslogins
by sid, then the login name is null and nothing will display
for Login Name in Enterprise Manager.
-Sue
On Mon, 28 Feb 2005 14:53:03 -0800, "Simon"
<Simon@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi Joachim,
>Yes, sp_helpuser does return null. However, we are using a script with the
>mentioned sp's to add users to this database. Way the app works is by a us
er
>entering details passed through to the script (sp). Some work, some don't.
>We have two machines (Prod & Test) and the results can differ. UserA might
>be fine on Prod but not on Test, UserB might befine on Test but not on Prod
.
>Repeatedly dropping and adding the user gets consistent results on each
>machine, whether that be by script, Query Analyser, Enterprise Manager. I
>can spot no common denominator, and have found no way to make a "nulling"
>user not-null.
>Only other thing that I can think worth mentioning: at the Security | Login
s
>level we have added "Domain\All Users" to grant all users server access.
>Database access is granted on a user by user basis (via the script mentione
d
>earlier.)
>Simon.
>
>"Joachim Hofmann" wrote:
>

Friday, February 17, 2012

Effective Permissions Error with Domain User

If I create a new Login at the server level for a domain group :i.e.,
MyDomain\Domain Users
Then I go add a user tied into this new Login to my database i.e., Northwind
or pubs to add a user tied to this login.
Why is it then when I go to Database Properties -> Permissions and select
Effective Permissions on this new user I get the following error:
TITLE: Microsoft SQL Server Management Studio
Cannot show requested dialog.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
Cannot execute as the server principal because the principal "EGUIRES\Domain
Users" does not exist, this type of principal cannot be impersonated, or you
do not have permission. (Microsoft SQL Server, Error: 15406)
For help, click:
tSrc=MSSQLServer&EvtID=15406&LinkId=20476" target="_blank">http://go.microsoft.com/fwlink?Prod...06&LinkId=20476
BUTTONS:
OK
The guest account seems fine for this but any manual entries I try that is
linked to my domain gets this error.
I would appreciate any light you can shed on this
Scott EguiresScott
Did you get these database from SQL Server 2000 by using a RESTORE command?
What is the compatibilty level of both databases?
"Scott Eguires" <ScottEguires@.discussions.microsoft.com> wrote in message
news:870F7328-15EF-40E5-B7ED-7F9262C46DD7@.microsoft.com...
> If I create a new Login at the server level for a domain group :i.e.,
> MyDomain\Domain Users
> Then I go add a user tied into this new Login to my database i.e.,
> Northwind
> or pubs to add a user tied to this login.
>
> Why is it then when I go to Database Properties -> Permissions and select
> Effective Permissions on this new user I get the following error:
>
> TITLE: Microsoft SQL Server Management Studio
> --
> Cannot show requested dialog.
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Cannot execute as the server principal because the principal
> "EGUIRES\Domain
> Users" does not exist, this type of principal cannot be impersonated, or
> you
> do not have permission. (Microsoft SQL Server, Error: 15406)
> For help, click:
> EvtSrc=MSSQLServer&EvtID=15406&LinkId=20476" target="_blank">http://go.microsoft.com/fwlink?Prod...06&LinkId=20476
> --
> BUTTONS:
> OK
>
> The guest account seems fine for this but any manual entries I try that is
> linked to my domain gets this error.
>
>
> I would appreciate any light you can shed on this
>
> Scott Eguires
>|||Yes I did. I set the database compatibility to 2005. WHat is interesting i
s
that Effective Permissions work for the Domain\Administrator group. I did a
server profile trace and found that it was calling the Execute As User. Thi
s
led me to the following clues:
When I run the following:
EXECUTE AS USER = 'MYDOMAIN\Domain Users';
I get the error:
Msg 15517, Level 16, State 1, Line 1
Cannot execute as the database principal because the principal
"MYDOMAIN\Domain Users" does not exist, this type of principal cannot be
impersonated, or you do not have permission.
But if I run:
EXECUTE AS USER = 'MYDOMAIN\Administrator';
It works fine.
This leads me to believe it is some sort of permissions issue.
Any info would be greatly appreciated.
Thanks
"Uri Dimant" wrote:

> Scott
> Did you get these database from SQL Server 2000 by using a RESTORE command
?
> What is the compatibilty level of both databases?
>
> "Scott Eguires" <ScottEguires@.discussions.microsoft.com> wrote in message
> news:870F7328-15EF-40E5-B7ED-7F9262C46DD7@.microsoft.com...
>
>|||Scott
Is the 'MYDOMAIN\Domain Users' login a member of sysadmin server role.Is
the user a member of loca Administrator group on a computer when you run
SQL Server?
"Scott Eguires" <ScottEguires@.discussions.microsoft.com> wrote in message
news:2D896D0E-CA3E-49A6-9B90-CE157B2A56E6@.microsoft.com...[vbcol=seagreen]
> Yes I did. I set the database compatibility to 2005. WHat is interesting
> is
> that Effective Permissions work for the Domain\Administrator group. I did
> a
> server profile trace and found that it was calling the Execute As User.
> This
> led me to the following clues:
> When I run the following:
> EXECUTE AS USER = 'MYDOMAIN\Domain Users';
> I get the error:
> Msg 15517, Level 16, State 1, Line 1
> Cannot execute as the database principal because the principal
> "MYDOMAIN\Domain Users" does not exist, this type of principal cannot be
> impersonated, or you do not have permission.
>
> But if I run:
> EXECUTE AS USER = 'MYDOMAIN\Administrator';
> It works fine.
> This leads me to believe it is some sort of permissions issue.
> Any info would be greatly appreciated.
> Thanks
>
> "Uri Dimant" wrote:
>|||No the 'MYDOMAIN\Domain Users' login is neither a member of the local
administrator
group nor a member of the sysadmin server role on the machine I am running
SQL Server.
"Uri Dimant" wrote:

> Scott
> Is the 'MYDOMAIN\Domain Users' login a member of sysadmin server role.Is
> the user a member of loca Administrator group on a computer when you run
> SQL Server?
>
>
>
> "Scott Eguires" <ScottEguires@.discussions.microsoft.com> wrote in message
> news:2D896D0E-CA3E-49A6-9B90-CE157B2A56E6@.microsoft.com...
>
>|||Scott
I tried tp reproduce the problem on my worstation SQL Server 2005 (Dev
Edition)
1) Restore a database from SQL Server 2000 which had an user called 'John'
(I changed compatibility level to 90)
2) Create a new Login 'NewJohn' and granted him an access to the database
(non sysadmin)
3) Right Click on the database --Properties --Permissions ( I sow
'John' user along with'NewJohn' )
4) Click on Effective Permissions ( I got the same error)
5) Click on Remove button and removed 'John' user
6) Click on Effective Permissions again and now it working
I think it is because that user "John" was transfered as a database user
(orphaned) without mapping to any login on the new server
MS has provided two stored procedures to move the logins with their original
SID but it worked fime on SS2K and I have not tried yet on SS2005
"Scott Eguires" <ScottEguires@.discussions.microsoft.com> wrote in message
news:4F36A7F9-3108-4142-875A-2DB8CA46ABB3@.microsoft.com...[vbcol=seagreen]
> No the 'MYDOMAIN\Domain Users' login is neither a member of the local
> administrator
> group nor a member of the sysadmin server role on the machine I am running
> SQL Server.
>
> "Uri Dimant" wrote:
>|||It seems that you cannot execute as user on a Group. Which makes sense sinc
e
the text is
Execute as User. So this tells me I will never be able to get the effective
permissions for a group
through the SQL Workbench tool which is fine I suppose. I had an additional
problem in that I had
my service account was set to local and needed to set it to a domain user
with appropriate rights. Without that my Execute as user fails since it
cannot resolve the user in my domain.
Scott Eguires
"Uri Dimant" wrote:

> Scott
> Is the 'MYDOMAIN\Domain Users' login a member of sysadmin server role.Is
> the user a member of loca Administrator group on a computer when you run
> SQL Server?
>
>
>
> "Scott Eguires" <ScottEguires@.discussions.microsoft.com> wrote in message
> news:2D896D0E-CA3E-49A6-9B90-CE157B2A56E6@.microsoft.com...
>
>