In troublshooting a rights issue I changed the ReportServer service to
run under a domain acount (rather than network service).
I believe this may have affected my ability to run subscriptions as
well as random authentication issues.
I am unable to extract the encryption key which I believe is tied to
making the account change above.
Is it adviseable to delete the key and re-specify the values with
rsconfig?Changing the report server windows serivce account is not a trivial
operation as I'm sure you've discovered :-(.
Regarding deleteing the secure information - if you have a back up of you
symmetric key (which is highly recommended) or are in a web farm
configuration where at least one of the other report servers still can
decrypt the key, then you shouldn't need to.
If you do not have the symmetric key:
Yes. Deleteing the secure information is required to reuse the report server
database. This will not alter your reports, but you will need to reenter
any information for data source connection strings and username/password
combinations.
As a note on changing the windows service account user - if your report
server database is remote, you will need to use a network enabled account.
The easiest way to change the account is acutally to reinstall :-(. The
reason for this is that the account you choose needs permissions on many
folders in the file system. Enumerating these is challenging and you'd have
an easier time reinstalling.
Best of luck,
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jim" <emailjeffp@.yahoo.com> wrote in message
news:1106872525.453713.36200@.f14g2000cwb.googlegroups.com...
> In troublshooting a rights issue I changed the ReportServer service to
> run under a domain acount (rather than network service).
> I believe this may have affected my ability to run subscriptions as
> well as random authentication issues.
> I am unable to extract the encryption key which I believe is tied to
> making the account change above.
> Is it adviseable to delete the key and re-specify the values with
> rsconfig?
>
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Friday, March 23, 2012
reportserver login failed
Hello
I have a report server running on a win2003 sp1 domain controller. The
reportServer database is sql2005 sp2 also running on the domain controller.
Now I´m trying to configure a report. The reports datasource is a SqlServer
2000 database also running on the domain controller
The connection string is "Data Source=localhost;Initial Catalog=MyDataDB"
If I try to run the report I´ve got a login error (rsLogonFailed)
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)
I think it isn´t the connection to the sql2000 database because I have tried
to prompt the user to type credentials. The same error
Any ideas?
regards
BjörnFound it.
Had to allow the user to login local
Björn
"Berger" <prodevteam@.gmx.net> schrieb im Newsbeitrag
news:OzxacToCIHA.4472@.TK2MSFTNGP05.phx.gbl...
> Hello
> I have a report server running on a win2003 sp1 domain controller. The
> reportServer database is sql2005 sp2 also running on the domain
> controller.
> Now I´m trying to configure a report. The reports datasource is a
> SqlServer 2000 database also running on the domain controller
> The connection string is "Data Source=localhost;Initial Catalog=MyDataDB"
> If I try to run the report I´ve got a login error (rsLogonFailed)
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)
> I think it isn´t the connection to the sql2000 database because I have
> tried to prompt the user to type credentials. The same error
> Any ideas?
> regards
> Björn
>
I have a report server running on a win2003 sp1 domain controller. The
reportServer database is sql2005 sp2 also running on the domain controller.
Now I´m trying to configure a report. The reports datasource is a SqlServer
2000 database also running on the domain controller
The connection string is "Data Source=localhost;Initial Catalog=MyDataDB"
If I try to run the report I´ve got a login error (rsLogonFailed)
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)
I think it isn´t the connection to the sql2000 database because I have tried
to prompt the user to type credentials. The same error
Any ideas?
regards
BjörnFound it.
Had to allow the user to login local
Björn
"Berger" <prodevteam@.gmx.net> schrieb im Newsbeitrag
news:OzxacToCIHA.4472@.TK2MSFTNGP05.phx.gbl...
> Hello
> I have a report server running on a win2003 sp1 domain controller. The
> reportServer database is sql2005 sp2 also running on the domain
> controller.
> Now I´m trying to configure a report. The reports datasource is a
> SqlServer 2000 database also running on the domain controller
> The connection string is "Data Source=localhost;Initial Catalog=MyDataDB"
> If I try to run the report I´ve got a login error (rsLogonFailed)
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)
> I think it isn´t the connection to the sql2000 database because I have
> tried to prompt the user to type credentials. The same error
> Any ideas?
> regards
> Björn
>
ReportServer directory not available outside firewall
We are attempting to expose our reports to the internet without much luck.
The domain name is not set up yet, so we are accessing by IP. There are 2
virtual folders - Reports and ReportServer are set up with Windows
authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
prompted, login and then see the list of reports. When I click on a report,
I get prompted again, but login fails and I get 401. Where should I start
looking? Most problems I see from others have to do with the Reports
directory, but their ReportServer directory works.I think 401 is an 'Unauthorised' error. Check your firewall settings, but
pay specific attention to the IIS and .NET authentication as well. Are you
using windows or forms based authentication?
"danb" wrote:
> We are attempting to expose our reports to the internet without much luck.
> The domain name is not set up yet, so we are accessing by IP. There are 2
> virtual folders - Reports and ReportServer are set up with Windows
> authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
> prompted, login and then see the list of reports. When I click on a report,
> I get prompted again, but login fails and I get 401. Where should I start
> looking? Most problems I see from others have to do with the Reports
> directory, but their ReportServer directory works.|||Yes, 401 wit h a message about invalid credentials, but as I said, I was able
to log in to the /ReportServer folder successfully and then it prompted me
again for some reason when I clicked on any report.
Check the firewall for what?
Windows authentication is being used on both Reports and ReportServer folders.
Server is Windows 2003 Server.
"CraigyBoop" wrote:
> I think 401 is an 'Unauthorised' error. Check your firewall settings, but
> pay specific attention to the IIS and .NET authentication as well. Are you
> using windows or forms based authentication?
> "danb" wrote:
> > We are attempting to expose our reports to the internet without much luck.
> > The domain name is not set up yet, so we are accessing by IP. There are 2
> > virtual folders - Reports and ReportServer are set up with Windows
> > authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
> > prompted, login and then see the list of reports. When I click on a report,
> > I get prompted again, but login fails and I get 401. Where should I start
> > looking? Most problems I see from others have to do with the Reports
> > directory, but their ReportServer directory works.
The domain name is not set up yet, so we are accessing by IP. There are 2
virtual folders - Reports and ReportServer are set up with Windows
authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
prompted, login and then see the list of reports. When I click on a report,
I get prompted again, but login fails and I get 401. Where should I start
looking? Most problems I see from others have to do with the Reports
directory, but their ReportServer directory works.I think 401 is an 'Unauthorised' error. Check your firewall settings, but
pay specific attention to the IIS and .NET authentication as well. Are you
using windows or forms based authentication?
"danb" wrote:
> We are attempting to expose our reports to the internet without much luck.
> The domain name is not set up yet, so we are accessing by IP. There are 2
> virtual folders - Reports and ReportServer are set up with Windows
> authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
> prompted, login and then see the list of reports. When I click on a report,
> I get prompted again, but login fails and I get 401. Where should I start
> looking? Most problems I see from others have to do with the Reports
> directory, but their ReportServer directory works.|||Yes, 401 wit h a message about invalid credentials, but as I said, I was able
to log in to the /ReportServer folder successfully and then it prompted me
again for some reason when I clicked on any report.
Check the firewall for what?
Windows authentication is being used on both Reports and ReportServer folders.
Server is Windows 2003 Server.
"CraigyBoop" wrote:
> I think 401 is an 'Unauthorised' error. Check your firewall settings, but
> pay specific attention to the IIS and .NET authentication as well. Are you
> using windows or forms based authentication?
> "danb" wrote:
> > We are attempting to expose our reports to the internet without much luck.
> > The domain name is not set up yet, so we are accessing by IP. There are 2
> > virtual folders - Reports and ReportServer are set up with Windows
> > authentication. When I go to http://xxx.xxx.xxx.xxx/ReportServer, I get
> > prompted, login and then see the list of reports. When I click on a report,
> > I get prompted again, but login fails and I get 401. Where should I start
> > looking? Most problems I see from others have to do with the Reports
> > directory, but their ReportServer directory works.
Wednesday, March 21, 2012
Reports vs. ReportServer permissions
I have created and deployed my reports on my report server, then I have set the appropriate permissions for MYDOMAIN\Domain Users (System User + Browser Role) across the whole report server (inluding the Home folder and its My Sample Reports subfolder). However, when I (as the domain user) access http://myreportserver/Reports I see nothing, only the empty Home folder. The same time, when I access http://myreportserver/ReportServer I can browse all I need and even generate reports. Please explain, what is wrong with my Report Manager at http://myreportserver/Reports, what security issues I may have. Thanks in advance.Thanks for no response 
but we have already solved the problem by adding missed <identity impersonate="true" /> line to C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\web.config. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp for details.
but we have already solved the problem by adding missed <identity impersonate="true" /> line to C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\web.config. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp for details.
Monday, March 12, 2012
Reports deployment
Our production environment sits on a different domain, behind a firewall. We
need to deploy our reports to our production server, but can't deploy to the
other domain. Also we are avoiding putting VS .NET on the production server
by not installing the Report Designer.
So, I was thinking we could deploy the reports to CD to get them to the
production domain. This is our first foray with RS.. is there an
article/resource where we can learn more about what specific files we need to
deploy?
thx,
JanYou have two options. One is to put your rds and rdl files onto a CD and go
to a PC in the other domain that has Report Designer on it and use that to
deploy to the server. Note that Report Designer does not need to be on the
server. Your other choice is to write a deployment script/app that takes and
deploys your reports. Note that deployment is not copying files. Report
Server is putting the reports into the database. No rdl files exist on your
server. SOAP (web services) are used by the Report Designer to deploy and
you can do the same thing.
What is the reason you can't deploy to your server, that it is on another
domain? I would think that deploying to another domain should be possible.
Search this newsgroup with deploy as the subject and you will find a variety
of posts. In particular Teo mentions creating a script. Another one talks
about deploying to a server in another domain.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:B0F23AB4-F114-4111-819C-AA52BC50F729@.microsoft.com...
> Our production environment sits on a different domain, behind a firewall.
We
> need to deploy our reports to our production server, but can't deploy to
the
> other domain. Also we are avoiding putting VS .NET on the production
server
> by not installing the Report Designer.
> So, I was thinking we could deploy the reports to CD to get them to the
> production domain. This is our first foray with RS.. is there an
> article/resource where we can learn more about what specific files we need
to
> deploy?
> thx,
> Jan|||Thanks Bruce, that is a big help.
It would be possible to deploy across domains if our security dept permitted
it. Our production domain is locked down with very limited access for
security reasons.
"Bruce L-C [MVP]" wrote:
> You have two options. One is to put your rds and rdl files onto a CD and go
> to a PC in the other domain that has Report Designer on it and use that to
> deploy to the server. Note that Report Designer does not need to be on the
> server. Your other choice is to write a deployment script/app that takes and
> deploys your reports. Note that deployment is not copying files. Report
> Server is putting the reports into the database. No rdl files exist on your
> server. SOAP (web services) are used by the Report Designer to deploy and
> you can do the same thing.
> What is the reason you can't deploy to your server, that it is on another
> domain? I would think that deploying to another domain should be possible.
> Search this newsgroup with deploy as the subject and you will find a variety
> of posts. In particular Teo mentions creating a script. Another one talks
> about deploying to a server in another domain.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jan" <Jan@.discussions.microsoft.com> wrote in message
> news:B0F23AB4-F114-4111-819C-AA52BC50F729@.microsoft.com...
> > Our production environment sits on a different domain, behind a firewall.
> We
> > need to deploy our reports to our production server, but can't deploy to
> the
> > other domain. Also we are avoiding putting VS .NET on the production
> server
> > by not installing the Report Designer.
> >
> > So, I was thinking we could deploy the reports to CD to get them to the
> > production domain. This is our first foray with RS.. is there an
> > article/resource where we can learn more about what specific files we need
> to
> > deploy?
> >
> > thx,
> > Jan
>
>
need to deploy our reports to our production server, but can't deploy to the
other domain. Also we are avoiding putting VS .NET on the production server
by not installing the Report Designer.
So, I was thinking we could deploy the reports to CD to get them to the
production domain. This is our first foray with RS.. is there an
article/resource where we can learn more about what specific files we need to
deploy?
thx,
JanYou have two options. One is to put your rds and rdl files onto a CD and go
to a PC in the other domain that has Report Designer on it and use that to
deploy to the server. Note that Report Designer does not need to be on the
server. Your other choice is to write a deployment script/app that takes and
deploys your reports. Note that deployment is not copying files. Report
Server is putting the reports into the database. No rdl files exist on your
server. SOAP (web services) are used by the Report Designer to deploy and
you can do the same thing.
What is the reason you can't deploy to your server, that it is on another
domain? I would think that deploying to another domain should be possible.
Search this newsgroup with deploy as the subject and you will find a variety
of posts. In particular Teo mentions creating a script. Another one talks
about deploying to a server in another domain.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jan" <Jan@.discussions.microsoft.com> wrote in message
news:B0F23AB4-F114-4111-819C-AA52BC50F729@.microsoft.com...
> Our production environment sits on a different domain, behind a firewall.
We
> need to deploy our reports to our production server, but can't deploy to
the
> other domain. Also we are avoiding putting VS .NET on the production
server
> by not installing the Report Designer.
> So, I was thinking we could deploy the reports to CD to get them to the
> production domain. This is our first foray with RS.. is there an
> article/resource where we can learn more about what specific files we need
to
> deploy?
> thx,
> Jan|||Thanks Bruce, that is a big help.
It would be possible to deploy across domains if our security dept permitted
it. Our production domain is locked down with very limited access for
security reasons.
"Bruce L-C [MVP]" wrote:
> You have two options. One is to put your rds and rdl files onto a CD and go
> to a PC in the other domain that has Report Designer on it and use that to
> deploy to the server. Note that Report Designer does not need to be on the
> server. Your other choice is to write a deployment script/app that takes and
> deploys your reports. Note that deployment is not copying files. Report
> Server is putting the reports into the database. No rdl files exist on your
> server. SOAP (web services) are used by the Report Designer to deploy and
> you can do the same thing.
> What is the reason you can't deploy to your server, that it is on another
> domain? I would think that deploying to another domain should be possible.
> Search this newsgroup with deploy as the subject and you will find a variety
> of posts. In particular Teo mentions creating a script. Another one talks
> about deploying to a server in another domain.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jan" <Jan@.discussions.microsoft.com> wrote in message
> news:B0F23AB4-F114-4111-819C-AA52BC50F729@.microsoft.com...
> > Our production environment sits on a different domain, behind a firewall.
> We
> > need to deploy our reports to our production server, but can't deploy to
> the
> > other domain. Also we are avoiding putting VS .NET on the production
> server
> > by not installing the Report Designer.
> >
> > So, I was thinking we could deploy the reports to CD to get them to the
> > production domain. This is our first foray with RS.. is there an
> > article/resource where we can learn more about what specific files we need
> to
> > deploy?
> >
> > thx,
> > Jan
>
>
Reports behind a domain with SSL
Greetings,
SSL was recently applied to the domain the reports are behind. I have been trying to get the "unsecure dialog" to not appear when viewing a RS report.
The report is embeded in a div tag in the aspx page. When accessing the site via https everything still works, if left unchanged, except the "unsecure content" dialog is displayed before the report renders.
When I change the URL of the div tag to https:\\<RSSERVER>\<REPORTCOMMAND>, I get the following error:
"Content was blocked because it was not signed by a valid security certificate."
Anyone know what I need to do to make this work?
http://msdn2.microsoft.com/en-us/library/ms345223.aspx needs to be followed.Friday, March 9, 2012
ReportManager and domain name change
Hi,
The fully qualified domain name of the reporting services server has changed
and that caused the Report Manager to stop working. Iâ'm using SQL 2000
Reporting Services on Windows Server 2003 .
I tracked the issue down to /Reports/Pages/Report.aspx page where that page
calls the actual report in a IFRAME and the IFRAME is calling the report with
the old domain name.
I found a configuration setting <UrlRoot> in the C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config config
file that used the old domain name. However, even changing that property to a
new domain name had no effect (tired touching web.configs, bouncing the
website).
Any suggestions greatly appreciated.
Thanks,
AlexFrom an issue I had with something similar on my CRM system here are some
notes passed on to me that I think might help you. I was changing mine from
a fullqualified domain name to a domain.local name but these would still
apply for you as well:
These instructions assume you are using SQL 2000 SP4.
First, on the server where SRS is installed, open the two files
rswebapplication.config at C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager and rsreportserver.config at
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer
with notepad and search for https://fqdn.yourdomain.com. Once you find this
replace it with https://YourNetBiosServerName.domain.local and save and
close the files.
On the same server, open the registry and modify the following registry
values at HKLM | SOFTWARE | Microsoft | Microsoft SQL Server | 80 |
Reporting Services to replace https://fqdn.yourdomain.com/ReportServer with
https://YourNetBiosServerName.domain.local/ReportServer.
RSVirtualDir - should be
https://YourNetBiosServerName.domain.local/ReportServer
WAVirtualDir - should be https://YourNetBiosServerName.domain.local/Reports
Gary
"alex" <alex@.discussions.microsoft.com> wrote in message
news:2E0195F3-5F67-4196-A119-9CDFC08656DA@.microsoft.com...
> Hi,
> The fully qualified domain name of the reporting services server has
> changed
> and that caused the Report Manager to stop working. I'm using SQL 2000
> Reporting Services on Windows Server 2003 .
> I tracked the issue down to /Reports/Pages/Report.aspx page where that
> page
> calls the actual report in a IFRAME and the IFRAME is calling the report
> with
> the old domain name.
> I found a configuration setting <UrlRoot> in the C:\Program
> Files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config
> config
> file that used the old domain name. However, even changing that property
> to a
> new domain name had no effect (tired touching web.configs, bouncing the
> website).
> Any suggestions greatly appreciated.
> Thanks,
> Alex
>
The fully qualified domain name of the reporting services server has changed
and that caused the Report Manager to stop working. Iâ'm using SQL 2000
Reporting Services on Windows Server 2003 .
I tracked the issue down to /Reports/Pages/Report.aspx page where that page
calls the actual report in a IFRAME and the IFRAME is calling the report with
the old domain name.
I found a configuration setting <UrlRoot> in the C:\Program Files\Microsoft
SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config config
file that used the old domain name. However, even changing that property to a
new domain name had no effect (tired touching web.configs, bouncing the
website).
Any suggestions greatly appreciated.
Thanks,
AlexFrom an issue I had with something similar on my CRM system here are some
notes passed on to me that I think might help you. I was changing mine from
a fullqualified domain name to a domain.local name but these would still
apply for you as well:
These instructions assume you are using SQL 2000 SP4.
First, on the server where SRS is installed, open the two files
rswebapplication.config at C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportManager and rsreportserver.config at
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer
with notepad and search for https://fqdn.yourdomain.com. Once you find this
replace it with https://YourNetBiosServerName.domain.local and save and
close the files.
On the same server, open the registry and modify the following registry
values at HKLM | SOFTWARE | Microsoft | Microsoft SQL Server | 80 |
Reporting Services to replace https://fqdn.yourdomain.com/ReportServer with
https://YourNetBiosServerName.domain.local/ReportServer.
RSVirtualDir - should be
https://YourNetBiosServerName.domain.local/ReportServer
WAVirtualDir - should be https://YourNetBiosServerName.domain.local/Reports
Gary
"alex" <alex@.discussions.microsoft.com> wrote in message
news:2E0195F3-5F67-4196-A119-9CDFC08656DA@.microsoft.com...
> Hi,
> The fully qualified domain name of the reporting services server has
> changed
> and that caused the Report Manager to stop working. I'm using SQL 2000
> Reporting Services on Windows Server 2003 .
> I tracked the issue down to /Reports/Pages/Report.aspx page where that
> page
> calls the actual report in a IFRAME and the IFRAME is calling the report
> with
> the old domain name.
> I found a configuration setting <UrlRoot> in the C:\Program
> Files\Microsoft
> SQL Server\MSSQL\Reporting Services\ReportServer\RSReportServer.config
> config
> file that used the old domain name. However, even changing that property
> to a
> new domain name had no effect (tired touching web.configs, bouncing the
> website).
> Any suggestions greatly appreciated.
> Thanks,
> Alex
>
Saturday, February 25, 2012
reporting user access rights on SQL7
I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000 (i
n
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
n
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
reporting user access rights on SQL7
I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000 (in
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
another domain 2).
To map the users from the domains, I need to know which users are configured
on the databases, plus which access rights and roles they have.
Can I get a report of this?
Does SQL have a default stored procedure for this?
Best regards,
-Peter-
Peter Geelen
System Engineer
www.identitymanagement.bePeter
Start quering sysusers system table , sp_helprotect system stored procedure
"Peter Geelen" <PeterGeelen@.discussions.microsoft.com> wrote in message
news:F767749C-6397-4791-8986-FE3A28D25D41@.microsoft.com...
>I need to migrate a SQL 7 database server (in domain 1) to a new SQL 2000
>(in
> another domain 2).
> To map the users from the domains, I need to know which users are
> configured
> on the databases, plus which access rights and roles they have.
> Can I get a report of this?
> Does SQL have a default stored procedure for this?
> Best regards,
> -Peter-
>
> Peter Geelen
> System Engineer
> www.identitymanagement.be
Subscribe to:
Posts (Atom)