Authentication/Security Issue!

Hi,
I have installed SQL reporting services on the local system test machine
[standard edition] which points to a DB that is on a different machine.
Everything works ok if I use a domain account and assign security rights for
each report. But in production I will want to have a local windows account
and assign read rights on the reports individually. I tried doing this in
the test environment.
When I try to access the site using the IP I get the windows log on box.
After entering the local user account I can get to the reports but as soon
as I try and run the report it gives me this error:
The permissions granted to user [domain\user] are insufficient for
performing this operation. (rsAccessDenied)
The problem is i am not logged on as a domain user but as a local machine
user.
Was wondering if any of you have come across this error before and possibly
know the cause/solution to this.
Thanks for your help!
Regards
AnilHi Anil:
Even if you go to an IP address for the server, when you run a report
the report is rendered by an IFRAME element with the URL pointing to
the report server by name.
To verify this behavior, just right-click in the report area, select
properties, and look at the URL. You'll notice your address bar might
look like http://x.x.x.x, but the report properties URL will indicate
http://reporting. The server always uses the <ReportServerUrl> element
in RSWebApplication.config.
Since the IFRAME points you back to the server by name, IE is probably
automatically logging you in again with your domain account, which is
not in a Browse role. You can change IE's behavior in Tools ->
Internet Options -> Security -> Custom Level -> User Authentication
(at the bottom of the list).
--
Scott
http://www.OdeToCode.com
On Mon, 16 Aug 2004 12:31:41 +1200, "anil" <test@.test.com> wrote:
>Hi,
>I have installed SQL reporting services on the local system test machine
>[standard edition] which points to a DB that is on a different machine.
>Everything works ok if I use a domain account and assign security rights for
>each report. But in production I will want to have a local windows account
>and assign read rights on the reports individually. I tried doing this in
>the test environment.
>When I try to access the site using the IP I get the windows log on box.
>After entering the local user account I can get to the reports but as soon
>as I try and run the report it gives me this error:
>
>The permissions granted to user [domain\user] are insufficient for
>performing this operation. (rsAccessDenied)
>The problem is i am not logged on as a domain user but as a local machine
>user.
>Was wondering if any of you have come across this error before and possibly
>know the cause/solution to this.
>Thanks for your help!
>Regards
>Anil
>

Attaching a SQL Express database to SQL Server Standard instance...

If I create a database in SQL Express and then copy the MDF/LDF files and attach them to a machine running SQL Server 2005 Standard - will this new database have SQL Express limitations?

Are there good reasons not to do this and create the database in SQL Server Standard using scripts generated from the SQL Express instance instead?

Basically, I'm setting up a merge replication between Standard and SQL Express for a common database and I figure attaching a copy of the database created in SQL Express is the fastest way to get this started.

Moving this thread over to the Express forum. They may be able to help with the limitations question.

Thanks,
Sam

|||

You can attach the file created on SQL Express to SQL Standard Edition, they are the same product and use the same file format. The limitation are specific to SQL Express, not the database file itself. In comparing copying the file and running a scirpt, I'm not aware of any particular benefits or limitations of one over the other.

From the stand point of Replication, there is no particular reason you need to do it this way. I'm guessing that you are developing locally using SQL Express and then moving your database to SQL Standard to setup your Publication. To my knowledge (I'm not a repl expert) you don't actually need to have a copy of the database on SQL Express in order to create a Subscription once you set up your Publisher on Standard. I believe you can configure things so that a database is created at the Subscriber when you initialize a new Subscription. That's obviously a question for the Repl forum if you run into issues there.

Mike

Attaching 2000 dbs to 2005

I installed ss2005 on a new machine. I try to attach a 2000 db and it found
an error (something in a view that it didn't like) and aborted the import.
I think it aborted on finding the first error but I'm not sure.
So, am I dead in the water? Do I have to take my db back to ss2000, deal
with the error and try a ss2005 atach again? If there are a thousand errors
would I have to do this a thousand times?
What If I just tried a restore' What's the best way to approach this
problem?
Many thanks, Tinn ManTinn
If I remember well , there is na upgrade advisor to make sure that sql
server 2005 'likes' everything
Also, I'd recommend you to backup database first and then restore it on sql
server 2005
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:Oao7332hGHA.4404@.TK2MSFTNGP05.phx.gbl...
>I installed ss2005 on a new machine. I try to attach a 2000 db and it
>found an error (something in a view that it didn't like) and aborted the
>import. I think it aborted on finding the first error but I'm not sure.
> So, am I dead in the water? Do I have to take my db back to ss2000, deal
> with the error and try a ss2005 atach again? If there are a thousand
> errors would I have to do this a thousand times?
> What If I just tried a restore' What's the best way to approach this
> problem?
> Many thanks, Tinn Man
>

Attaching 2000 dbs to 2005

I installed ss2005 on a new machine. I try to attach a 2000 db and it found
an error (something in a view that it didn't like) and aborted the import.
I think it aborted on finding the first error but I'm not sure.
So, am I dead in the water? Do I have to take my db back to ss2000, deal
with the error and try a ss2005 atach again? If there are a thousand errors
would I have to do this a thousand times?
What If I just tried a restore' What's the best way to approach this
problem?
Many thanks, Tinn ManTinn
If I remember well , there is na upgrade advisor to make sure that sql
server 2005 'likes' everything
Also, I'd recommend you to backup database first and then restore it on sql
server 2005
"Tinn Man" <tm@.nospammeexcite.com> wrote in message
news:Oao7332hGHA.4404@.TK2MSFTNGP05.phx.gbl...
>I installed ss2005 on a new machine. I try to attach a 2000 db and it
>found an error (something in a view that it didn't like) and aborted the
>import. I think it aborted on finding the first error but I'm not sure.
> So, am I dead in the water? Do I have to take my db back to ss2000, deal
> with the error and try a ss2005 atach again? If there are a thousand
> errors would I have to do this a thousand times?
> What If I just tried a restore' What's the best way to approach this
> problem?
> Many thanks, Tinn Man
>

AttachDBFileName refers to original log file

Hello,

I'm using the AttachDBFilename option in the SQL connection string to attach
a database mdf file copied to another machine.

There is an error though, it seems to want to refer to a log file on the
machine the .mdf was originally created on. The error is as follows:

Could not attach file 'C:\Program Files\Strategic Systems\Time
Master\TimeMasterDat.mdf' as database 'TimeMaster'.
File activation failure. The physical file name "D:\Visual Studio 2005
Projects\Strategic\Applications\TimeMaster\Database\Strategic.TimeMaster.Database.SQL2005\TimeMasterDat_log.LDF" may be incorrect

How can I get the attach to avoid referring to this log file?

Coudl you please post your connection string here ? Seems that you are mixing up the setting for server / user instances.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Here it is:

Data Source=.\SQLExpress;AttachDBFileName=C:\Program Files\Time Master\TimeMasterDat.mdf;Initial Catalog=TimeMaster;Trusted_Connection=yes;

The mdf file should be attached to a local instance of SQLExpress. The mdf has been copied from my development machine and the it seems to think that this mdf file is refering to this log file.

It shouldn't, it should create a log file on the local machine.

|||Try to add the "User Instance=true;" to the connectionstring.|||

That worked, but creating another User Instance was not really what I was looking to do, but will probably do

Thanks

|||Did you want to attach the database to the server for a server instance ? or did you want to use the user instance feature of SQL Express ? If you want to use the user instance you WILL have to create one instance per database.

-Jens.|||A server instance I suppose. The server and client being on the same machine.|||

If you want to use a server attached instance you will have to attach the database first (if you have no log LDF file you will have to try to attach the database using sp_attach_single_file_db) using sp_attachdb or the equivalent GUI action in the managment studio.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

AttachDBFileName - refers to previous log file

Hello,
I'm using the AttachDBFilename option in the SQL connection string to attach
a database to a SQLExpress instance on another machine.
The is an error though, it seems to want to refer to a log file on the
machine the .mdf was originally created on. The error is as follows:
Could not attach file 'C:\Program Files\Strategic Systems\Time
Master\TimeMasterDat.mdf' as database 'TimeMaster'.
File activation failure. The physical file name "D:\Visual Studio 2005
Projects\Strategic\Applications\TimeMaster\Databas e\Strategic.TimeMaster.Database.SQL2005\TimeMaster Dat_log.LDF" may be incorrect
How can I get the attach to avoid referring to this log file?
Answered in
http://forums.microsoft.com/forums/ShowPost.aspx?PostID=1081110&SiteID=1
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de

AttachDBFileName - refers to previous log file

Hello,
I'm using the AttachDBFilename option in the SQL connection string to attach
a database to a SQLExpress instance on another machine.
The is an error though, it seems to want to refer to a log file on the
machine the .mdf was originally created on. The error is as follows:
Could not attach file 'C:\Program Files\Strategic Systems\Time
Master\TimeMasterDat.mdf' as database 'TimeMaster'.
File activation failure. The physical file name "D:\Visual Studio 2005
Projects\Strategic\Applications\TimeMast
er\Database\Strategic.TimeMaster.Dat
abase.SQL2005\TimeMasterDat_log.LDF" may be incorrect
How can I get the attach to avoid referring to this log file?Answered in
http://forums.microsoft.com/forums/...081110&SiteID=1
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--

Attach/Detach database

I need to copy my SQL Server 2000 database from my development machine to
the server of one of the client. By using Enterprise Manager I was going to
detach db from my server, create a database with the same name on a new
server, detach it, replace files on the new server with my copies and attach
both databases on both servers back.
Unfortunately my server displays Attach Database entry only in popup menu. I
have nothing to attach yet.
I did this operation several times and had no problem before. Probably I
detached some of the unimportant databases and forgot to attach it back.
How can I refresh (clean up whatever) Enterprise Manager memory about last
operation in order to have the ability to use Detach feature?
Thank you
Al
Hi
I would recommend that you do this from Query Analyser, there is no need to
create the database first.
http://support.microsoft.com/default...en-us%3b224071
John
"vul" <aaa@.optonline.net> wrote in message
news:enYHb8trEHA.3900@.TK2MSFTNGP10.phx.gbl...
> I need to copy my SQL Server 2000 database from my development machine to
> the server of one of the client. By using Enterprise Manager I was going
to
> detach db from my server, create a database with the same name on a new
> server, detach it, replace files on the new server with my copies and
attach
> both databases on both servers back.
> Unfortunately my server displays Attach Database entry only in popup menu.
I
> have nothing to attach yet.
> I did this operation several times and had no problem before. Probably I
> detached some of the unimportant databases and forgot to attach it back.
> How can I refresh (clean up whatever) Enterprise Manager memory about last
> operation in order to have the ability to use Detach feature?
> Thank you
> Al
>
|||The detach option is context-sensitive so you need to first select the
desired database in the tree.
You should not create a new database before attaching. Detach the database
and copy the files to the new server. In the Attach database dialog,
specify the mdf file, click Verify and specify the desired database name in
the 'Attach As' box. You can change the locations of the other files in the
list, if needed.
You might also consider using the sp_attach_db and sp_detach_db stored
procedures. See the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"vul" <aaa@.optonline.net> wrote in message
news:enYHb8trEHA.3900@.TK2MSFTNGP10.phx.gbl...
>I need to copy my SQL Server 2000 database from my development machine to
> the server of one of the client. By using Enterprise Manager I was going
> to
> detach db from my server, create a database with the same name on a new
> server, detach it, replace files on the new server with my copies and
> attach
> both databases on both servers back.
> Unfortunately my server displays Attach Database entry only in popup menu.
> I
> have nothing to attach yet.
> I did this operation several times and had no problem before. Probably I
> detached some of the unimportant databases and forgot to attach it back.
> How can I refresh (clean up whatever) Enterprise Manager memory about last
> operation in order to have the ability to use Detach feature?
> Thank you
> Al
>

Attach/Detach database

I need to copy my SQL Server 2000 database from my development machine to
the server of one of the client. By using Enterprise Manager I was going to
detach db from my server, create a database with the same name on a new
server, detach it, replace files on the new server with my copies and attach
both databases on both servers back.
Unfortunately my server displays Attach Database entry only in popup menu. I
have nothing to attach yet.
I did this operation several times and had no problem before. Probably I
detached some of the unimportant databases and forgot to attach it back.
How can I refresh (clean up whatever) Enterprise Manager memory about last
operation in order to have the ability to use Detach feature?
Thank you
AlHi
I would recommend that you do this from Query Analyser, there is no need to
create the database first.
http://support.microsoft.com/defaul...ben-us%3b224071
John
"vul" <aaa@.optonline.net> wrote in message
news:enYHb8trEHA.3900@.TK2MSFTNGP10.phx.gbl...
> I need to copy my SQL Server 2000 database from my development machine to
> the server of one of the client. By using Enterprise Manager I was going
to
> detach db from my server, create a database with the same name on a new
> server, detach it, replace files on the new server with my copies and
attach
> both databases on both servers back.
> Unfortunately my server displays Attach Database entry only in popup menu.
I
> have nothing to attach yet.
> I did this operation several times and had no problem before. Probably I
> detached some of the unimportant databases and forgot to attach it back.
> How can I refresh (clean up whatever) Enterprise Manager memory about last
> operation in order to have the ability to use Detach feature?
> Thank you
> Al
>|||The detach option is context-sensitive so you need to first select the
desired database in the tree.
You should not create a new database before attaching. Detach the database
and copy the files to the new server. In the Attach database dialog,
specify the mdf file, click Verify and specify the desired database name in
the 'Attach As' box. You can change the locations of the other files in the
list, if needed.
You might also consider using the sp_attach_db and sp_detach_db stored
procedures. See the Books Online for more information.
Hope this helps.
Dan Guzman
SQL Server MVP
"vul" <aaa@.optonline.net> wrote in message
news:enYHb8trEHA.3900@.TK2MSFTNGP10.phx.gbl...
>I need to copy my SQL Server 2000 database from my development machine to
> the server of one of the client. By using Enterprise Manager I was going
> to
> detach db from my server, create a database with the same name on a new
> server, detach it, replace files on the new server with my copies and
> attach
> both databases on both servers back.
> Unfortunately my server displays Attach Database entry only in popup menu.
> I
> have nothing to attach yet.
> I did this operation several times and had no problem before. Probably I
> detached some of the unimportant databases and forgot to attach it back.
> How can I refresh (clean up whatever) Enterprise Manager memory about last
> operation in order to have the ability to use Detach feature?
> Thank you
> Al
>