Hi All,
note: I am discussing the number of users in the database not the user
'connections'
I was trying to find some documentation from microsoft which specifies the
maximum number of users that can be created in a single sql2k database.
We seem to be hitting the limit at 16379.
The error raised is:
Server: Msg 15065, Level 16, State 1, Procedure sp_grantdbaccess, Line 160
All user IDs have been assigned.
The following section of code from sp_grantdbaccess suggests that 16379 is
the limit:
/////////////////////////////////////////////
-- OBTAIN NEW UID (RESERVE 1-4) --
if user_name(5) IS NULL
select @.uid = 5
else
select @.uid = min(uid)+1 from sysusers
where uid = 5 and uid < (16384 - 1) -- stay in users range
and user_name(uid+1) is null -- uid not in use
if @.uid is null
begin
raiserror(15065,-1,-1)
return (1)
end
/////////////////////////////////////////////
Can anyone confirm this?
Is there any Microsoft Documentation which states that 16379 is the maximum
number of database users in sql2k.
(Could not find it in the sql books online)
Thanks
Vikram
--
Vikram Vamshi
Eclipsys Corporation> Is there any Microsoft Documentation which states that 16379 is the
maximum
> number of database users in sql2k.
Yes.
http://support.microsoft.com/?id=303879
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||That is exactly what I was looking for.
Thanks
Vikram
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message
news:uSozZCPvDHA.2712@.tk2msftngp13.phx.gbl...
> > Is there any Microsoft Documentation which states that 16379 is the
> maximum
> > number of database users in sql2k.
> Yes.
> http://support.microsoft.com/?id=303879
>
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
>
>|||This limitation is documented here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;303879
For that number of users consider using Windows Authentication and adding
domain user groups as database users rather than adding the users
individually. This should be much easier to manage than user-level security.
--
David Portas
--
Please reply only to the newsgroup
--
Showing posts with label reposting. Show all posts
Showing posts with label reposting. Show all posts
Wednesday, March 7, 2012
Reposting: How to extract (and email) only 1 client's data from th
Hi,
My vb.net app will use msde for database needs. The app is a tool in which the app user (companyA) will do some planning for their clients. So basically, the database will have information about all the clients (Sam, Julia, Peter, Nancy etc) of our cust
omer (companyA). Now suppose there is some error happening in the application for user Nancy, and we want the companyA to send us only Nancy's data so that we can duplicate the error and debug it. How do we do that...
In previous versions of our app where we used the flat files for data storage, we will just tell the companyA to email us Nancy.ourFile so that we can have a look at the data which is causing the problem. How to extract only Nancy's data from the whole d
atabase...
Thanks
dev
hi,
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:782E4169-30DB-4AEF-B7BC-CC375DABE132@.microsoft.com...
> Hi,
> My vb.net app will use msde for database needs. The app is a tool in
which the app user
>(companyA) will do some planning for their clients. So basically, the
database will have
>information about all the clients (Sam, Julia, Peter, Nancy etc) of our
customer (companyA).
> Now suppose there is some error happening in the application for user
Nancy, and we want
> the companyA to send us only Nancy's data so that we can duplicate the
error and debug it.
> How do we do that...
> In previous versions of our app where we used the flat files for data
storage, we will just tell the
> companyA to email us Nancy.ourFile so that we can have a look at the data
which is causing
>the problem. How to extract only Nancy's data from the whole database...
> Thanks
> dev
>
it depends how you can identify Nancys' data...
if it's a complete database, than detach it, zip it and mail it...
if data is shared with other user's data, than you have to filter on perhaps
owner.tableName.col_User = 'Nancy' and export it to a flat file, probably
using BCP, something like
c:\>BCP "SELECT * FROM [db_name].[owner].[table/view name] WHERE colUser =
'Nancy'" queryout c:\NacyData_objName.txt -c -S(local) -T
make a batch file with all the queryout BCP commands...
or provide a DTS to be executed locally to equally export to file
those file will be then BCP in on testing server for toubleshouting...
good idea? =;-)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
My vb.net app will use msde for database needs. The app is a tool in which the app user (companyA) will do some planning for their clients. So basically, the database will have information about all the clients (Sam, Julia, Peter, Nancy etc) of our cust
omer (companyA). Now suppose there is some error happening in the application for user Nancy, and we want the companyA to send us only Nancy's data so that we can duplicate the error and debug it. How do we do that...
In previous versions of our app where we used the flat files for data storage, we will just tell the companyA to email us Nancy.ourFile so that we can have a look at the data which is causing the problem. How to extract only Nancy's data from the whole d
atabase...
Thanks
dev
hi,
"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:782E4169-30DB-4AEF-B7BC-CC375DABE132@.microsoft.com...
> Hi,
> My vb.net app will use msde for database needs. The app is a tool in
which the app user
>(companyA) will do some planning for their clients. So basically, the
database will have
>information about all the clients (Sam, Julia, Peter, Nancy etc) of our
customer (companyA).
> Now suppose there is some error happening in the application for user
Nancy, and we want
> the companyA to send us only Nancy's data so that we can duplicate the
error and debug it.
> How do we do that...
> In previous versions of our app where we used the flat files for data
storage, we will just tell the
> companyA to email us Nancy.ourFile so that we can have a look at the data
which is causing
>the problem. How to extract only Nancy's data from the whole database...
> Thanks
> dev
>
it depends how you can identify Nancys' data...
if it's a complete database, than detach it, zip it and mail it...
if data is shared with other user's data, than you have to filter on perhaps
owner.tableName.col_User = 'Nancy' and export it to a flat file, probably
using BCP, something like
c:\>BCP "SELECT * FROM [db_name].[owner].[table/view name] WHERE colUser =
'Nancy'" queryout c:\NacyData_objName.txt -c -S(local) -T
make a batch file with all the queryout BCP commands...
or provide a DTS to be executed locally to equally export to file
those file will be then BCP in on testing server for toubleshouting...
good idea? =;-)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Reposting: Expand All / Collapse All feature
1. Is there a way to Expand All nodes or Collapse All Nodes in a drill-down
report designed with RS ? I find it annoying to click every + sign to open
all nodes. Maybe, there is an easier way that I do not know.
2. When the same drill-down report is partially expanded and I export the
report as-it-is to Excel, the exported file has only the partial
data.....only the data that was expanded. The other data is never exported.
What can I do to resolve this ?
Please respond.Yes, you can do this.
Step 1) Create a textbox outside of your table/matrix. Give it a name, e.g.
Toggler. Step 2) Highlight the row you want to hide/show. Set its Visibility
Hidden property to False, and use the textbox you created at Step 1 as the
ToggleItem property.
Charles Kangai, MCT, MCDBA
"DC" wrote:
> 1. Is there a way to Expand All nodes or Collapse All Nodes in a drill-down
> report designed with RS ? I find it annoying to click every + sign to open
> all nodes. Maybe, there is an easier way that I do not know.
> 2. When the same drill-down report is partially expanded and I export the
> report as-it-is to Excel, the exported file has only the partial
> data.....only the data that was expanded. The other data is never exported.
> What can I do to resolve this ?
> Please respond.
>
>|||Also, if you put the visibility settings at Group line level (i.e.
highlight the whole group by clicking on the left hand tab) rather cell
level, when you export to Excel you'll get full outlining/grouping for
ALL data regardless of how the report is currently 'expanded'. (This
only works with SP1).
Regards
Chris
Charles Kangai wrote:
> Yes, you can do this.
> Step 1) Create a textbox outside of your table/matrix. Give it a
> name, e.g. Toggler. Step 2) Highlight the row you want to hide/show.
> Set its Visibility Hidden property to False, and use the textbox you
> created at Step 1 as the ToggleItem property.
> Charles Kangai, MCT, MCDBA
> "DC" wrote:
> > 1. Is there a way to Expand All nodes or Collapse All Nodes in a
> > drill-down report designed with RS ? I find it annoying to click
> > every + sign to open all nodes. Maybe, there is an easier way that
> > I do not know.
> >
> > 2. When the same drill-down report is partially expanded and I
> > export the report as-it-is to Excel, the exported file has only the
> > partial data.....only the data that was expanded. The other data
> > is never exported. What can I do to resolve this ?
> >
> > Please respond.
> >
> >
> >
> >|||Here is an expand all that I am using:
Create Report parameter: "ExpandAll"
Available Values:
Label: Yes Value: True
Label: No Value: False
Default Value: No
Group1: =Fields!Status.Value
Initial Appearance Expression: =IIF( Parameters!ExpandAll.Value = true,
true, false)
Group2 =Fields!Name.Value
Initial Appearance Expression: =IIF( Parameters!ExpandAll.Value = true,
true, false)
Visibility:
Hidden expression: =IIF( Parameters!ExpandAll.Value = true, False, True)
ToggleItem: Status
Detail records:
Visibility:
Hidden expression: =IIF( Parameters!ExpandAll.Value = true, false, true)
ToggleItem: Name
Good luck,
Chuck Kee
"Chris McGuigan" wrote:
> Also, if you put the visibility settings at Group line level (i.e.
> highlight the whole group by clicking on the left hand tab) rather cell
> level, when you export to Excel you'll get full outlining/grouping for
> ALL data regardless of how the report is currently 'expanded'. (This
> only works with SP1).
> Regards
> Chris
> Charles Kangai wrote:
> > Yes, you can do this.
> > Step 1) Create a textbox outside of your table/matrix. Give it a
> > name, e.g. Toggler. Step 2) Highlight the row you want to hide/show.
> > Set its Visibility Hidden property to False, and use the textbox you
> > created at Step 1 as the ToggleItem property.
> >
> > Charles Kangai, MCT, MCDBA
> >
> > "DC" wrote:
> >
> > > 1. Is there a way to Expand All nodes or Collapse All Nodes in a
> > > drill-down report designed with RS ? I find it annoying to click
> > > every + sign to open all nodes. Maybe, there is an easier way that
> > > I do not know.
> > >
> > > 2. When the same drill-down report is partially expanded and I
> > > export the report as-it-is to Excel, the exported file has only the
> > > partial data.....only the data that was expanded. The other data
> > > is never exported. What can I do to resolve this ?
> > >
> > > Please respond.
> > >
> > >
> > >
> > >
>
report designed with RS ? I find it annoying to click every + sign to open
all nodes. Maybe, there is an easier way that I do not know.
2. When the same drill-down report is partially expanded and I export the
report as-it-is to Excel, the exported file has only the partial
data.....only the data that was expanded. The other data is never exported.
What can I do to resolve this ?
Please respond.Yes, you can do this.
Step 1) Create a textbox outside of your table/matrix. Give it a name, e.g.
Toggler. Step 2) Highlight the row you want to hide/show. Set its Visibility
Hidden property to False, and use the textbox you created at Step 1 as the
ToggleItem property.
Charles Kangai, MCT, MCDBA
"DC" wrote:
> 1. Is there a way to Expand All nodes or Collapse All Nodes in a drill-down
> report designed with RS ? I find it annoying to click every + sign to open
> all nodes. Maybe, there is an easier way that I do not know.
> 2. When the same drill-down report is partially expanded and I export the
> report as-it-is to Excel, the exported file has only the partial
> data.....only the data that was expanded. The other data is never exported.
> What can I do to resolve this ?
> Please respond.
>
>|||Also, if you put the visibility settings at Group line level (i.e.
highlight the whole group by clicking on the left hand tab) rather cell
level, when you export to Excel you'll get full outlining/grouping for
ALL data regardless of how the report is currently 'expanded'. (This
only works with SP1).
Regards
Chris
Charles Kangai wrote:
> Yes, you can do this.
> Step 1) Create a textbox outside of your table/matrix. Give it a
> name, e.g. Toggler. Step 2) Highlight the row you want to hide/show.
> Set its Visibility Hidden property to False, and use the textbox you
> created at Step 1 as the ToggleItem property.
> Charles Kangai, MCT, MCDBA
> "DC" wrote:
> > 1. Is there a way to Expand All nodes or Collapse All Nodes in a
> > drill-down report designed with RS ? I find it annoying to click
> > every + sign to open all nodes. Maybe, there is an easier way that
> > I do not know.
> >
> > 2. When the same drill-down report is partially expanded and I
> > export the report as-it-is to Excel, the exported file has only the
> > partial data.....only the data that was expanded. The other data
> > is never exported. What can I do to resolve this ?
> >
> > Please respond.
> >
> >
> >
> >|||Here is an expand all that I am using:
Create Report parameter: "ExpandAll"
Available Values:
Label: Yes Value: True
Label: No Value: False
Default Value: No
Group1: =Fields!Status.Value
Initial Appearance Expression: =IIF( Parameters!ExpandAll.Value = true,
true, false)
Group2 =Fields!Name.Value
Initial Appearance Expression: =IIF( Parameters!ExpandAll.Value = true,
true, false)
Visibility:
Hidden expression: =IIF( Parameters!ExpandAll.Value = true, False, True)
ToggleItem: Status
Detail records:
Visibility:
Hidden expression: =IIF( Parameters!ExpandAll.Value = true, false, true)
ToggleItem: Name
Good luck,
Chuck Kee
"Chris McGuigan" wrote:
> Also, if you put the visibility settings at Group line level (i.e.
> highlight the whole group by clicking on the left hand tab) rather cell
> level, when you export to Excel you'll get full outlining/grouping for
> ALL data regardless of how the report is currently 'expanded'. (This
> only works with SP1).
> Regards
> Chris
> Charles Kangai wrote:
> > Yes, you can do this.
> > Step 1) Create a textbox outside of your table/matrix. Give it a
> > name, e.g. Toggler. Step 2) Highlight the row you want to hide/show.
> > Set its Visibility Hidden property to False, and use the textbox you
> > created at Step 1 as the ToggleItem property.
> >
> > Charles Kangai, MCT, MCDBA
> >
> > "DC" wrote:
> >
> > > 1. Is there a way to Expand All nodes or Collapse All Nodes in a
> > > drill-down report designed with RS ? I find it annoying to click
> > > every + sign to open all nodes. Maybe, there is an easier way that
> > > I do not know.
> > >
> > > 2. When the same drill-down report is partially expanded and I
> > > export the report as-it-is to Excel, the exported file has only the
> > > partial data.....only the data that was expanded. The other data
> > > is never exported. What can I do to resolve this ?
> > >
> > > Please respond.
> > >
> > >
> > >
> > >
>
Reposting: Database Version Issue
I just installed SP2 for 2005 standard edition and am getting the following
error when trying to use report server:
"The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)"
When I go into Reporting service configuration tool, the update button
returns the following:
"The database version matches your Reporting services installation"
and the database version is reported as 'C.0.8.54'.
this is critical and I need to get this up and running again. Any ideas?
--
John Cleveland
Network Manager
Urban systems LtdHave you installed any SQL service packs BEFORE adding other parts
like 'reporting services'
Also, there was a critical patch sent through windows update that
updates SQL server. Not sure if that is causing you problems.
On Apr 13, 1:16 am, John Cleveland
<JohnClevel...@.discussions.microsoft.com> wrote:
> I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
> --
> John Cleveland
> Network Manager
> Urban systems Ltd|||SP1 was already installed. reporting services was installed pre sp1.
I've narrowed down the sequence of events that lead to this issue. It seems
there was a reporting services update that was installed without my knowledge
that was intended for sp2 installs. SP2 wasn't installed yet. even though
sp2 is now installed, i still get the error message listed previously.
--
John Cleveland
Network Manager
Urban systems Ltd
"gommo" wrote:
> Have you installed any SQL service packs BEFORE adding other parts
> like 'reporting services'
> Also, there was a critical patch sent through windows update that
> updates SQL server. Not sure if that is causing you problems.
> On Apr 13, 1:16 am, John Cleveland
> <JohnClevel...@.discussions.microsoft.com> wrote:
> > I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
>
>|||Is there a possibility that you actually have two different db's and your
reportserver instance is pointed at the "wrong" one frm the POV of the one
that your web application thinks it should connect to?
This might have happened if the person applying the update is not the
administrator of the box. See
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
It can also happen if you apply the update in the wrong identity, even if
you are an administrator (I know that from personal experience <sigh> FWIW
the ReportServer database has a sprocwhere this is hard coded. I kid you
not. I think it gets adjusted during upgrades with a file called
catalog.sql. )
Short version of the fix described in that thread: you have to stop IIS and
RS and copy the files that were truly upgraded to the correct location --
but you should probably read the thread.
HTH,
>L<
"John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
>I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is
> not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report
> server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
>
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||I actually have this fixed now, it was caused by the sp2 upgrade. I
uninstalled rs, reinstalled and applied sp2 once again and all is fine.
Reports cam back properly, but the data sources had to be reconfigured. No
biggie.
Thanks for your suggestions though.
--
John Cleveland
Network Manager
Urban systems Ltd
"Lisa Slater Nicholls" wrote:
> Is there a possibility that you actually have two different db's and your
> reportserver instance is pointed at the "wrong" one frm the POV of the one
> that your web application thinks it should connect to?
> This might have happened if the person applying the update is not the
> administrator of the box. See
> http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
> It can also happen if you apply the update in the wrong identity, even if
> you are an administrator (I know that from personal experience <sigh> FWIW
> the ReportServer database has a sprocwhere this is hard coded. I kid you
> not. I think it gets adjusted during upgrades with a file called
> catalog.sql. )
> Short version of the fix described in that thread: you have to stop IIS and
> RS and copy the files that were truly upgraded to the correct location --
> but you should probably read the thread.
> HTH,
> >L<
>
> "John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
> news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
> >I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is
> > not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report
> > server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
> >
>
error when trying to use report server:
"The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)"
When I go into Reporting service configuration tool, the update button
returns the following:
"The database version matches your Reporting services installation"
and the database version is reported as 'C.0.8.54'.
this is critical and I need to get this up and running again. Any ideas?
--
John Cleveland
Network Manager
Urban systems LtdHave you installed any SQL service packs BEFORE adding other parts
like 'reporting services'
Also, there was a critical patch sent through windows update that
updates SQL server. Not sure if that is causing you problems.
On Apr 13, 1:16 am, John Cleveland
<JohnClevel...@.discussions.microsoft.com> wrote:
> I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
> --
> John Cleveland
> Network Manager
> Urban systems Ltd|||SP1 was already installed. reporting services was installed pre sp1.
I've narrowed down the sequence of events that lead to this issue. It seems
there was a reporting services update that was installed without my knowledge
that was intended for sp2 installs. SP2 wasn't installed yet. even though
sp2 is now installed, i still get the error message listed previously.
--
John Cleveland
Network Manager
Urban systems Ltd
"gommo" wrote:
> Have you installed any SQL service packs BEFORE adding other parts
> like 'reporting services'
> Also, there was a critical patch sent through windows update that
> updates SQL server. Not sure if that is causing you problems.
> On Apr 13, 1:16 am, John Cleveland
> <JohnClevel...@.discussions.microsoft.com> wrote:
> > I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
>
>|||Is there a possibility that you actually have two different db's and your
reportserver instance is pointed at the "wrong" one frm the POV of the one
that your web application thinks it should connect to?
This might have happened if the person applying the update is not the
administrator of the box. See
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
It can also happen if you apply the update in the wrong identity, even if
you are an administrator (I know that from personal experience <sigh> FWIW
the ReportServer database has a sprocwhere this is hard coded. I kid you
not. I think it gets adjusted during upgrades with a file called
catalog.sql. )
Short version of the fix described in that thread: you have to stop IIS and
RS and copy the files that were truly upgraded to the correct location --
but you should probably read the thread.
HTH,
>L<
"John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
>I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is
> not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report
> server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
>
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||I actually have this fixed now, it was caused by the sp2 upgrade. I
uninstalled rs, reinstalled and applied sp2 once again and all is fine.
Reports cam back properly, but the data sources had to be reconfigured. No
biggie.
Thanks for your suggestions though.
--
John Cleveland
Network Manager
Urban systems Ltd
"Lisa Slater Nicholls" wrote:
> Is there a possibility that you actually have two different db's and your
> reportserver instance is pointed at the "wrong" one frm the POV of the one
> that your web application thinks it should connect to?
> This might have happened if the person applying the update is not the
> administrator of the box. See
> http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
> It can also happen if you apply the update in the wrong identity, even if
> you are an administrator (I know that from personal experience <sigh> FWIW
> the ReportServer database has a sprocwhere this is hard coded. I kid you
> not. I think it gets adjusted during upgrades with a file called
> catalog.sql. )
> Short version of the fix described in that thread: you have to stop IIS and
> RS and copy the files that were truly upgraded to the correct location --
> but you should probably read the thread.
> HTH,
> >L<
>
> "John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
> news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
> >I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is
> > not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report
> > server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
> >
>
reposting: bkup and resore strategy. Please reply
Hi,
My vb.net app will use database which will be deployed using MSDE on client
machines. I will provide UI to client in my app to backup and restore the d
atabase. My app will work with one database, for e.g. MyAppDB. My question
is what are the best pract
ices for doing this:
a) Should I choose Full or Simple mode. There is no mission critical data.
But as my clients will be using MSDE, will setting up the recovery mode as
Full cause the database and log size limits to cross the 2GB limit soon. Is
it better if I choose SIMP
LE recovery mode. What do you suggest.
b) Should I back up the system databases also, if yes then what should be th
e order of backing these up (and then in what order should the databases be
restored)
c) Does the MSDE login information also needs to be backed up. At max I wil
l have just one custom login and sa. I am using SQL Authentication.
d) Will I need to close my application and make sure that my apps' MSDE inst
ance is not running before backing up the databases.
d) I want to provide user the option to choose the backup location. How wil
l I figure out if they chose something like tape drive or zip drive. How sh
ould I handle this scenario.
e) Also how can I find out if there is sufficient space on the hard drive to
backup the database. Are there any standard sql functions to check that.
f) Should I do database log file backup too while backing up the database.
sorry for so many questions.
thanks
newbie
Print | Copy URL of this post
Expand All Collapse AllSee answers inline:
"newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:3DFC5E47-73A3-4CFC-9161-0AF13E789AD5@.microsoft.com...
> Hi,
> My vb.net app will use database which will be deployed using MSDE on
client machines. I will provide UI to client in my app to backup and
restore the database. My app will work with one database, for e.g. MyAppDB.
My question is what are the best practices for doing this:
> a) Should I choose Full or Simple mode. There is no mission critical
data. But as my clients will be using MSDE, will setting up the recovery
mode as Full cause the database and log size limits to cross the 2GB limit
soon. Is it better if I choose SIMPLE recovery mode. What do you suggest.
I almost always use either full or bulk-logged, although there are a few
instances where simple is appropriate. Basically you need to determine in
the event of failure do you want to be able to recover to the point of
failure, or is it good engoug to recover from the last full backup? As for
size limits, you can control the size of the log by backing it up regularly.
Besides, I am pretty sure that the 2Gb size limit is on the data file, not
the log.
> b) Should I back up the system databases also, if yes then what should be
the order of backing these up (and then in what order should the databases
be restored)
Yes, at least master and msdb, but the order of backing them up is not
important. Master would be the first to be restored
> c) Does the MSDE login information also needs to be backed up. At max I
will have just one custom login and sa. I am using SQL Authentication.
The logins are stored in master.
> d) Will I need to close my application and make sure that my apps' MSDE
instance is not running before backing up the databases.
No, backups are an online operation.
> d) I want to provide user the option to choose the backup location. How
will I figure out if they chose something like tape drive or zip drive. How
should I handle this scenario.
That's an application issue, you stated that you were providing them a front
end UI to backup the databases. The destination of the backup files is just
one of the BACKUP command arguments. There are also several arguments that
apply only to tape backup operations that you might want to take into
consideration.
> e) Also how can I find out if there is sufficient space on the hard drive
to backup the database. Are there any standard sql functions to check that.
There isn't a function that will estimate the size of the backup, but you
can read the msdb..backupset table to get the size of the last backup (or an
average of the last several) and estimate the size based on that.
> f) Should I do database log file backup too while backing up the database.
Not at the same time, although it won't hurt anything, there's just no
reason to do them at the same time.
> sorry for so many questions.
> thanks
> newbie
>
> Print | Copy URL of this post
>
> Expand All Collapse All
>|||Thanks don. Here are few more concerns that I have:
1> Is there any way to zip the .bak files into just 1 file ising T-sql or wi
ll I have to resort to 3rd party solutions for compression (as .Net doesn't
have any compression lib)
2> What happens if one user chooses to backup while others are still working
on the same database (imagine a small office setup with few computers and m
y app on all of them and the db on one central machine). Will the backup wor
k fine in this situation or
will the users need to log off.
3> Also we are not aiming at schedule backups option right now. Our clients
will have to go to the UI screen and backup the database themselves when the
y want to. So in this situation should I restore system databases also when
the users choose to restore
my app's db from the backed up location. And do I need to backup the system
databases always when they choose to backup my apps db or just before any ma
jor important changes.
Thanks
My vb.net app will use database which will be deployed using MSDE on client
machines. I will provide UI to client in my app to backup and restore the d
atabase. My app will work with one database, for e.g. MyAppDB. My question
is what are the best pract
ices for doing this:
a) Should I choose Full or Simple mode. There is no mission critical data.
But as my clients will be using MSDE, will setting up the recovery mode as
Full cause the database and log size limits to cross the 2GB limit soon. Is
it better if I choose SIMP
LE recovery mode. What do you suggest.
b) Should I back up the system databases also, if yes then what should be th
e order of backing these up (and then in what order should the databases be
restored)
c) Does the MSDE login information also needs to be backed up. At max I wil
l have just one custom login and sa. I am using SQL Authentication.
d) Will I need to close my application and make sure that my apps' MSDE inst
ance is not running before backing up the databases.
d) I want to provide user the option to choose the backup location. How wil
l I figure out if they chose something like tape drive or zip drive. How sh
ould I handle this scenario.
e) Also how can I find out if there is sufficient space on the hard drive to
backup the database. Are there any standard sql functions to check that.
f) Should I do database log file backup too while backing up the database.
sorry for so many questions.
thanks
newbie
Print | Copy URL of this post
Expand All Collapse AllSee answers inline:
"newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:3DFC5E47-73A3-4CFC-9161-0AF13E789AD5@.microsoft.com...
> Hi,
> My vb.net app will use database which will be deployed using MSDE on
client machines. I will provide UI to client in my app to backup and
restore the database. My app will work with one database, for e.g. MyAppDB.
My question is what are the best practices for doing this:
> a) Should I choose Full or Simple mode. There is no mission critical
data. But as my clients will be using MSDE, will setting up the recovery
mode as Full cause the database and log size limits to cross the 2GB limit
soon. Is it better if I choose SIMPLE recovery mode. What do you suggest.
I almost always use either full or bulk-logged, although there are a few
instances where simple is appropriate. Basically you need to determine in
the event of failure do you want to be able to recover to the point of
failure, or is it good engoug to recover from the last full backup? As for
size limits, you can control the size of the log by backing it up regularly.
Besides, I am pretty sure that the 2Gb size limit is on the data file, not
the log.
> b) Should I back up the system databases also, if yes then what should be
the order of backing these up (and then in what order should the databases
be restored)
Yes, at least master and msdb, but the order of backing them up is not
important. Master would be the first to be restored
> c) Does the MSDE login information also needs to be backed up. At max I
will have just one custom login and sa. I am using SQL Authentication.
The logins are stored in master.
> d) Will I need to close my application and make sure that my apps' MSDE
instance is not running before backing up the databases.
No, backups are an online operation.
> d) I want to provide user the option to choose the backup location. How
will I figure out if they chose something like tape drive or zip drive. How
should I handle this scenario.
That's an application issue, you stated that you were providing them a front
end UI to backup the databases. The destination of the backup files is just
one of the BACKUP command arguments. There are also several arguments that
apply only to tape backup operations that you might want to take into
consideration.
> e) Also how can I find out if there is sufficient space on the hard drive
to backup the database. Are there any standard sql functions to check that.
There isn't a function that will estimate the size of the backup, but you
can read the msdb..backupset table to get the size of the last backup (or an
average of the last several) and estimate the size based on that.
> f) Should I do database log file backup too while backing up the database.
Not at the same time, although it won't hurt anything, there's just no
reason to do them at the same time.
> sorry for so many questions.
> thanks
> newbie
>
> Print | Copy URL of this post
>
> Expand All Collapse All
>|||Thanks don. Here are few more concerns that I have:
1> Is there any way to zip the .bak files into just 1 file ising T-sql or wi
ll I have to resort to 3rd party solutions for compression (as .Net doesn't
have any compression lib)
2> What happens if one user chooses to backup while others are still working
on the same database (imagine a small office setup with few computers and m
y app on all of them and the db on one central machine). Will the backup wor
k fine in this situation or
will the users need to log off.
3> Also we are not aiming at schedule backups option right now. Our clients
will have to go to the UI screen and backup the database themselves when the
y want to. So in this situation should I restore system databases also when
the users choose to restore
my app's db from the backed up location. And do I need to backup the system
databases always when they choose to backup my apps db or just before any ma
jor important changes.
Thanks
reposting: bkup and resore strategy. Please reply
Hi,
My vb.net app will use database which will be deployed using MSDE on client machines. I will provide UI to client in my app to backup and restore the database. My app will work with one database, for e.g. MyAppDB. My question is what are the best pract
ices for doing this:
a) Should I choose Full or Simple mode. There is no mission critical data. But as my clients will be using MSDE, will setting up the recovery mode as Full cause the database and log size limits to cross the 2GB limit soon. Is it better if I choose SIMP
LE recovery mode. What do you suggest.
b) Should I back up the system databases also, if yes then what should be the order of backing these up (and then in what order should the databases be restored)
c) Does the MSDE login information also needs to be backed up. At max I will have just one custom login and sa. I am using SQL Authentication.
d) Will I need to close my application and make sure that my apps' MSDE instance is not running before backing up the databases.
d) I want to provide user the option to choose the backup location. How will I figure out if they chose something like tape drive or zip drive. How should I handle this scenario.
e) Also how can I find out if there is sufficient space on the hard drive to backup the database. Are there any standard sql functions to check that.
f) Should I do database log file backup too while backing up the database.
sorry for so many questions.
thanks
newbie
Print | Copy URL of this post
Expand All Collapse All
See answers inline:
"newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:3DFC5E47-73A3-4CFC-9161-0AF13E789AD5@.microsoft.com...
> Hi,
> My vb.net app will use database which will be deployed using MSDE on
client machines. I will provide UI to client in my app to backup and
restore the database. My app will work with one database, for e.g. MyAppDB.
My question is what are the best practices for doing this:
> a) Should I choose Full or Simple mode. There is no mission critical
data. But as my clients will be using MSDE, will setting up the recovery
mode as Full cause the database and log size limits to cross the 2GB limit
soon. Is it better if I choose SIMPLE recovery mode. What do you suggest.
I almost always use either full or bulk-logged, although there are a few
instances where simple is appropriate. Basically you need to determine in
the event of failure do you want to be able to recover to the point of
failure, or is it good engoug to recover from the last full backup? As for
size limits, you can control the size of the log by backing it up regularly.
Besides, I am pretty sure that the 2Gb size limit is on the data file, not
the log.
> b) Should I back up the system databases also, if yes then what should be
the order of backing these up (and then in what order should the databases
be restored)
Yes, at least master and msdb, but the order of backing them up is not
important. Master would be the first to be restored
> c) Does the MSDE login information also needs to be backed up. At max I
will have just one custom login and sa. I am using SQL Authentication.
The logins are stored in master.
> d) Will I need to close my application and make sure that my apps' MSDE
instance is not running before backing up the databases.
No, backups are an online operation.
> d) I want to provide user the option to choose the backup location. How
will I figure out if they chose something like tape drive or zip drive. How
should I handle this scenario.
That's an application issue, you stated that you were providing them a front
end UI to backup the databases. The destination of the backup files is just
one of the BACKUP command arguments. There are also several arguments that
apply only to tape backup operations that you might want to take into
consideration.
> e) Also how can I find out if there is sufficient space on the hard drive
to backup the database. Are there any standard sql functions to check that.
There isn't a function that will estimate the size of the backup, but you
can read the msdb..backupset table to get the size of the last backup (or an
average of the last several) and estimate the size based on that.
> f) Should I do database log file backup too while backing up the database.
Not at the same time, although it won't hurt anything, there's just no
reason to do them at the same time.
> sorry for so many questions.
> thanks
> newbie
>
> Print | Copy URL of this post
>
> Expand All Collapse All
>
|||Thanks don. Here are few more concerns that I have:
1> Is there any way to zip the .bak files into just 1 file ising T-sql or will I have to resort to 3rd party solutions for compression (as .Net doesn't have any compression lib)
2> What happens if one user chooses to backup while others are still working on the same database (imagine a small office setup with few computers and my app on all of them and the db on one central machine). Will the backup work fine in this situation or
will the users need to log off.
3> Also we are not aiming at schedule backups option right now. Our clients will have to go to the UI screen and backup the database themselves when they want to. So in this situation should I restore system databases also when the users choose to restore
my app's db from the backed up location. And do I need to backup the system databases always when they choose to backup my apps db or just before any major important changes.
Thanks
My vb.net app will use database which will be deployed using MSDE on client machines. I will provide UI to client in my app to backup and restore the database. My app will work with one database, for e.g. MyAppDB. My question is what are the best pract
ices for doing this:
a) Should I choose Full or Simple mode. There is no mission critical data. But as my clients will be using MSDE, will setting up the recovery mode as Full cause the database and log size limits to cross the 2GB limit soon. Is it better if I choose SIMP
LE recovery mode. What do you suggest.
b) Should I back up the system databases also, if yes then what should be the order of backing these up (and then in what order should the databases be restored)
c) Does the MSDE login information also needs to be backed up. At max I will have just one custom login and sa. I am using SQL Authentication.
d) Will I need to close my application and make sure that my apps' MSDE instance is not running before backing up the databases.
d) I want to provide user the option to choose the backup location. How will I figure out if they chose something like tape drive or zip drive. How should I handle this scenario.
e) Also how can I find out if there is sufficient space on the hard drive to backup the database. Are there any standard sql functions to check that.
f) Should I do database log file backup too while backing up the database.
sorry for so many questions.
thanks
newbie
Print | Copy URL of this post
Expand All Collapse All
See answers inline:
"newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:3DFC5E47-73A3-4CFC-9161-0AF13E789AD5@.microsoft.com...
> Hi,
> My vb.net app will use database which will be deployed using MSDE on
client machines. I will provide UI to client in my app to backup and
restore the database. My app will work with one database, for e.g. MyAppDB.
My question is what are the best practices for doing this:
> a) Should I choose Full or Simple mode. There is no mission critical
data. But as my clients will be using MSDE, will setting up the recovery
mode as Full cause the database and log size limits to cross the 2GB limit
soon. Is it better if I choose SIMPLE recovery mode. What do you suggest.
I almost always use either full or bulk-logged, although there are a few
instances where simple is appropriate. Basically you need to determine in
the event of failure do you want to be able to recover to the point of
failure, or is it good engoug to recover from the last full backup? As for
size limits, you can control the size of the log by backing it up regularly.
Besides, I am pretty sure that the 2Gb size limit is on the data file, not
the log.
> b) Should I back up the system databases also, if yes then what should be
the order of backing these up (and then in what order should the databases
be restored)
Yes, at least master and msdb, but the order of backing them up is not
important. Master would be the first to be restored
> c) Does the MSDE login information also needs to be backed up. At max I
will have just one custom login and sa. I am using SQL Authentication.
The logins are stored in master.
> d) Will I need to close my application and make sure that my apps' MSDE
instance is not running before backing up the databases.
No, backups are an online operation.
> d) I want to provide user the option to choose the backup location. How
will I figure out if they chose something like tape drive or zip drive. How
should I handle this scenario.
That's an application issue, you stated that you were providing them a front
end UI to backup the databases. The destination of the backup files is just
one of the BACKUP command arguments. There are also several arguments that
apply only to tape backup operations that you might want to take into
consideration.
> e) Also how can I find out if there is sufficient space on the hard drive
to backup the database. Are there any standard sql functions to check that.
There isn't a function that will estimate the size of the backup, but you
can read the msdb..backupset table to get the size of the last backup (or an
average of the last several) and estimate the size based on that.
> f) Should I do database log file backup too while backing up the database.
Not at the same time, although it won't hurt anything, there's just no
reason to do them at the same time.
> sorry for so many questions.
> thanks
> newbie
>
> Print | Copy URL of this post
>
> Expand All Collapse All
>
|||Thanks don. Here are few more concerns that I have:
1> Is there any way to zip the .bak files into just 1 file ising T-sql or will I have to resort to 3rd party solutions for compression (as .Net doesn't have any compression lib)
2> What happens if one user chooses to backup while others are still working on the same database (imagine a small office setup with few computers and my app on all of them and the db on one central machine). Will the backup work fine in this situation or
will the users need to log off.
3> Also we are not aiming at schedule backups option right now. Our clients will have to go to the UI screen and backup the database themselves when they want to. So in this situation should I restore system databases also when the users choose to restore
my app's db from the backed up location. And do I need to backup the system databases always when they choose to backup my apps db or just before any major important changes.
Thanks
Reposting: attempting to overcome cascading parameter refresh - with two sets of parameter
Let's say I have three cascading parameters. I make the selections in
P1, P2, P3. Now I change the selection in P2 in the next round.
Is there a way to 'remember' the previously selected parameter value -
somewhere... anywhere...'No responses... so I guess this is not possible.
Or is it because no one understood my question?
I want to somehow 'hold' the value of the selected parameter. And when
the user changes the parameter, I just want to be able to refrence his
previous selection.
Do I do this with another report behind the scenes?|||If you are still asking. The question is do you want a default or just the
user selection to stay?
"Harsh" wrote:
> No responses... so I guess this is not possible.
> Or is it because no one understood my question?
> I want to somehow 'hold' the value of the selected parameter. And when
> the user changes the parameter, I just want to be able to refrence his
> previous selection.
> Do I do this with another report behind the scenes?
>
P1, P2, P3. Now I change the selection in P2 in the next round.
Is there a way to 'remember' the previously selected parameter value -
somewhere... anywhere...'No responses... so I guess this is not possible.
Or is it because no one understood my question?
I want to somehow 'hold' the value of the selected parameter. And when
the user changes the parameter, I just want to be able to refrence his
previous selection.
Do I do this with another report behind the scenes?|||If you are still asking. The question is do you want a default or just the
user selection to stay?
"Harsh" wrote:
> No responses... so I guess this is not possible.
> Or is it because no one understood my question?
> I want to somehow 'hold' the value of the selected parameter. And when
> the user changes the parameter, I just want to be able to refrence his
> previous selection.
> Do I do this with another report behind the scenes?
>
Saturday, February 25, 2012
Repost: sql7 maintenance jobs hang
Hi group,
the following has been posted and did not receive any response. In hope to
get some leads I am reposting it here.
we have a sql7 server,
Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86)
May 29 2003 15:21:25
Copyright (c) 1988-2002 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
For a while now, it has been seeing hanging db maintenance jobs. The jobs
are initiated, but never goes beyond that -- the maintenance task is not
done before the hanging of the job. EM shows that the jobs are running but
loses the ability of managing them. One needs to end the processes with the
windows task manager. When manually initiated, the jobs can run through.
The jobs are not necessarily the same(different days can have different jobs
experiencing the problem, some can be the same), but all came from db
maintenance plan. A job hung yesterday may not hang today. Recreating the
db maint plan does not solve the problem.
Any suggestions are appreciated.
QuentinQuentin
Are you using the repair minor errors option? That tends
to cause problems in maint plans.
Any other problems on the server, I had a similar problem
and it was being caused by another process clashing with
the checkpoint process, but that eventually killed the
whole system.
Regards
John|||John,
thanks for the response.
The repair minor errors option is not being used. We are aware of that
problem.
We are trying to identify other problems on the server but came out empty
handed so far.
Quentin
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message
news:003201c3a86e$ccafad40$a301280a@.phx.gbl...
> Quentin
> Are you using the repair minor errors option? That tends
> to cause problems in maint plans.
> Any other problems on the server, I had a similar problem
> and it was being caused by another process clashing with
> the checkpoint process, but that eventually killed the
> whole system.
> Regards
> John
the following has been posted and did not receive any response. In hope to
get some leads I am reposting it here.
we have a sql7 server,
Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86)
May 29 2003 15:21:25
Copyright (c) 1988-2002 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
For a while now, it has been seeing hanging db maintenance jobs. The jobs
are initiated, but never goes beyond that -- the maintenance task is not
done before the hanging of the job. EM shows that the jobs are running but
loses the ability of managing them. One needs to end the processes with the
windows task manager. When manually initiated, the jobs can run through.
The jobs are not necessarily the same(different days can have different jobs
experiencing the problem, some can be the same), but all came from db
maintenance plan. A job hung yesterday may not hang today. Recreating the
db maint plan does not solve the problem.
Any suggestions are appreciated.
QuentinQuentin
Are you using the repair minor errors option? That tends
to cause problems in maint plans.
Any other problems on the server, I had a similar problem
and it was being caused by another process clashing with
the checkpoint process, but that eventually killed the
whole system.
Regards
John|||John,
thanks for the response.
The repair minor errors option is not being used. We are aware of that
problem.
We are trying to identify other problems on the server but came out empty
handed so far.
Quentin
"John Bandettini" <anonymous@.discussions.microsoft.com> wrote in message
news:003201c3a86e$ccafad40$a301280a@.phx.gbl...
> Quentin
> Are you using the repair minor errors option? That tends
> to cause problems in maint plans.
> Any other problems on the server, I had a similar problem
> and it was being caused by another process clashing with
> the checkpoint process, but that eventually killed the
> whole system.
> Regards
> John
Repost: Security level already for "RosettaMgr"
As an MSDN subscriber, I though I was supposed to get a guaranteed response
here. I am reposting this since no one responded to my 1st inquiry.
Out of the blue this morning our Report Server stopped working with the
following error:
Configuration Error
...
Parser Error Message: Security Level already defined for RosettaMgr
Source Error:
Line 22: <securityPolicy>
Line 23: <trustlevel name="RosettaMgr"
policyFile="rsmgrpolicy.config" />
Line 24: </securityPolicy>
line 24: <trust level="RosettaMgr" originUrl="" />
Removing the offending lines from web.config resolved the problem but I'm
unclear why this happened suddenly. I'm also leery of removing these
settings without fully understanding the implications. If anyone has any
insight as to the cause of this error or can intelligently explain the
<securityPolicy> and <trust level> settings I sure would appreciate a little
feedback.
Thanks,
Rich BakosHi Rich,
Sorry that you're encountering trouble. Not sure where your expectation was
set regarding guaranteed response If you could let me know that would be
very helpful. AFAIK, MS doesn't guarantee responses on this newsgroup -
you're actually talking with many folks on the product team directly. Though
we'd love to answer all questions, we're also trying to ship an awesome
product as part of SQL Server 2005. I'm sure you understand our quandry
:-).
Now your question:
Report Manager ships with a default security group called RosettaMgr.
Removing this line is not desired. The relevant section of the file reads:
<securityPolicy>
<trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
</securityPolicy>
<trust level="RosettaMgr" originUrl=""/>
What this line does is it ensure that the report manager loads code, that it
assigns the code the correct permission defined in the rsmgrpolicy.config
file.
This is a shot in the dark but the web.config file included with an
application follows a hierarchy based on other web.config files that come
before it. You can read up on this here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod92.asp
Are you running another application that also uses ASP.Net on the same
server? Has any web.config changed on your server shortly before your
application started to fail?
One other questions - did you move/copy the report manager virtual
directory?
-Lukasz
"Richard Bakos" <bakos@.nospam.nospam> wrote in message
news:%23PAol8DGFHA.444@.TK2MSFTNGP15.phx.gbl...
> As an MSDN subscriber, I though I was supposed to get a guaranteed
> response
> here. I am reposting this since no one responded to my 1st inquiry.
> Out of the blue this morning our Report Server stopped working with the
> following error:
> Configuration Error
> ...
> Parser Error Message: Security Level already defined for RosettaMgr
>
> Source Error:
> Line 22: <securityPolicy>
> Line 23: <trustlevel name="RosettaMgr"
> policyFile="rsmgrpolicy.config" />
> Line 24: </securityPolicy>
> line 24: <trust level="RosettaMgr" originUrl="" />
> Removing the offending lines from web.config resolved the problem but I'm
> unclear why this happened suddenly. I'm also leery of removing these
> settings without fully understanding the implications. If anyone has any
> insight as to the cause of this error or can intelligently explain the
> <securityPolicy> and <trust level> settings I sure would appreciate a
> little
> feedback.
> Thanks,
> Rich Bakos
>
>|||Lukasz Pawlowski [MSFT] wrote:
Hi Lukasz.
Thanks for you response.
> Sorry that you're encountering trouble. Not sure where your
> expectation was set regarding guaranteed response If you could let
> me know that would be very helpful.
My mistake, the page says a "commitment" to respond rather than a guarantee.
http://msdn.microsoft.com/newsgroups/managed/
> <securityPolicy>
> <trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
> </securityPolicy>
> <trust level="RosettaMgr" originUrl=""/>
Yes. Those are the offending lines and the server will not run with those
elements defined. To add to the problem, we can not move reports to
different folders or update definitions since removing the offending
elements. Everything else appears to work correctly.
Here is the exact text of the error:
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Security level already defined for 'RosettaMgr'.
Source Error:
Line 21: <httpRuntime executionTimeout="9000"/>
Line 22: <securityPolicy>
Line 23: <trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
Line 24: </securityPolicy>
Line 25: <trust level="RosettaMgr" originUrl=""/>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\web.config Line: 23
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573
> What this line does is it ensure that the report manager loads code,
> that it assigns the code the correct permission defined in the
> rsmgrpolicy.config file.
Thanks for the explaination but this doesn't explain why I'm getting a parse
error complaining that a Security level is already defined. My web.config
files had not been changed until the day I removed the offending elements.
> Are you running another application that also uses ASP.Net on the same
> server?
No. However, the web.config for the report server also contains the elements
sin question.
>Has any web.config changed on your server shortly before
> your application started to fail?
No.
> One other questions - did you move/copy the report manager virtual
> directory?
No.
Any other insight you might have certainly would be helpful.
Thanks,
Rich Bakos|||Richard Bakos wrote:
> No. However, the web.config for the report server also contains the
> elements sin question.
My mistake. The element definitions are not identical. Once defines
RosettaMgr while the other defines RosettaSrv.
Rich|||The solution to your problem is to install the ASP.Net hotfix for a
canonicalization issue. You can do this from the following KB article:
http://support.microsoft.com/kb/887787
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Bakos" <bakos@.nospam.nospam> wrote in message
news:uYe6DZKGFHA.560@.TK2MSFTNGP15.phx.gbl...
> Richard Bakos wrote:
>> No. However, the web.config for the report server also contains the
>> elements sin question.
> My mistake. The element definitions are not identical. Once defines
> RosettaMgr while the other defines RosettaSrv.
> Rich
>|||Lukasz Pawlowski [MSFT] wrote:
Hi Lukasz,
> The solution to your problem is to install the ASP.Net hotfix for a
> canonicalization issue. You can do this from the following KB
> article:
That made no difference. The problem still exists.
Rich Bakos
here. I am reposting this since no one responded to my 1st inquiry.
Out of the blue this morning our Report Server stopped working with the
following error:
Configuration Error
...
Parser Error Message: Security Level already defined for RosettaMgr
Source Error:
Line 22: <securityPolicy>
Line 23: <trustlevel name="RosettaMgr"
policyFile="rsmgrpolicy.config" />
Line 24: </securityPolicy>
line 24: <trust level="RosettaMgr" originUrl="" />
Removing the offending lines from web.config resolved the problem but I'm
unclear why this happened suddenly. I'm also leery of removing these
settings without fully understanding the implications. If anyone has any
insight as to the cause of this error or can intelligently explain the
<securityPolicy> and <trust level> settings I sure would appreciate a little
feedback.
Thanks,
Rich BakosHi Rich,
Sorry that you're encountering trouble. Not sure where your expectation was
set regarding guaranteed response If you could let me know that would be
very helpful. AFAIK, MS doesn't guarantee responses on this newsgroup -
you're actually talking with many folks on the product team directly. Though
we'd love to answer all questions, we're also trying to ship an awesome
product as part of SQL Server 2005. I'm sure you understand our quandry
:-).
Now your question:
Report Manager ships with a default security group called RosettaMgr.
Removing this line is not desired. The relevant section of the file reads:
<securityPolicy>
<trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
</securityPolicy>
<trust level="RosettaMgr" originUrl=""/>
What this line does is it ensure that the report manager loads code, that it
assigns the code the correct permission defined in the rsmgrpolicy.config
file.
This is a shot in the dark but the web.config file included with an
application follows a hierarchy based on other web.config files that come
before it. You can read up on this here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod92.asp
Are you running another application that also uses ASP.Net on the same
server? Has any web.config changed on your server shortly before your
application started to fail?
One other questions - did you move/copy the report manager virtual
directory?
-Lukasz
"Richard Bakos" <bakos@.nospam.nospam> wrote in message
news:%23PAol8DGFHA.444@.TK2MSFTNGP15.phx.gbl...
> As an MSDN subscriber, I though I was supposed to get a guaranteed
> response
> here. I am reposting this since no one responded to my 1st inquiry.
> Out of the blue this morning our Report Server stopped working with the
> following error:
> Configuration Error
> ...
> Parser Error Message: Security Level already defined for RosettaMgr
>
> Source Error:
> Line 22: <securityPolicy>
> Line 23: <trustlevel name="RosettaMgr"
> policyFile="rsmgrpolicy.config" />
> Line 24: </securityPolicy>
> line 24: <trust level="RosettaMgr" originUrl="" />
> Removing the offending lines from web.config resolved the problem but I'm
> unclear why this happened suddenly. I'm also leery of removing these
> settings without fully understanding the implications. If anyone has any
> insight as to the cause of this error or can intelligently explain the
> <securityPolicy> and <trust level> settings I sure would appreciate a
> little
> feedback.
> Thanks,
> Rich Bakos
>
>|||Lukasz Pawlowski [MSFT] wrote:
Hi Lukasz.
Thanks for you response.
> Sorry that you're encountering trouble. Not sure where your
> expectation was set regarding guaranteed response If you could let
> me know that would be very helpful.
My mistake, the page says a "commitment" to respond rather than a guarantee.
http://msdn.microsoft.com/newsgroups/managed/
> <securityPolicy>
> <trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
> </securityPolicy>
> <trust level="RosettaMgr" originUrl=""/>
Yes. Those are the offending lines and the server will not run with those
elements defined. To add to the problem, we can not move reports to
different folders or update definitions since removing the offending
elements. Everything else appears to work correctly.
Here is the exact text of the error:
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Security level already defined for 'RosettaMgr'.
Source Error:
Line 21: <httpRuntime executionTimeout="9000"/>
Line 22: <securityPolicy>
Line 23: <trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
Line 24: </securityPolicy>
Line 25: <trust level="RosettaMgr" originUrl=""/>
Source File: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\web.config Line: 23
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573
> What this line does is it ensure that the report manager loads code,
> that it assigns the code the correct permission defined in the
> rsmgrpolicy.config file.
Thanks for the explaination but this doesn't explain why I'm getting a parse
error complaining that a Security level is already defined. My web.config
files had not been changed until the day I removed the offending elements.
> Are you running another application that also uses ASP.Net on the same
> server?
No. However, the web.config for the report server also contains the elements
sin question.
>Has any web.config changed on your server shortly before
> your application started to fail?
No.
> One other questions - did you move/copy the report manager virtual
> directory?
No.
Any other insight you might have certainly would be helpful.
Thanks,
Rich Bakos|||Richard Bakos wrote:
> No. However, the web.config for the report server also contains the
> elements sin question.
My mistake. The element definitions are not identical. Once defines
RosettaMgr while the other defines RosettaSrv.
Rich|||The solution to your problem is to install the ASP.Net hotfix for a
canonicalization issue. You can do this from the following KB article:
http://support.microsoft.com/kb/887787
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard Bakos" <bakos@.nospam.nospam> wrote in message
news:uYe6DZKGFHA.560@.TK2MSFTNGP15.phx.gbl...
> Richard Bakos wrote:
>> No. However, the web.config for the report server also contains the
>> elements sin question.
> My mistake. The element definitions are not identical. Once defines
> RosettaMgr while the other defines RosettaSrv.
> Rich
>|||Lukasz Pawlowski [MSFT] wrote:
Hi Lukasz,
> The solution to your problem is to install the ASP.Net hotfix for a
> canonicalization issue. You can do this from the following KB
> article:
That made no difference. The problem still exists.
Rich Bakos
Repost of VB Run-time error '3211'
I'm reposting this because i tried deleteing the table manually and
recreating it manually. It works OK after that, but when i try it again, it
gives the error again. There are four tables, but it only happens on the
"ITEMS" table.
I'm trying to execute the following code and i am getting this error:
"Run-time error '3211'; The database engine could not lock table 'Items'
becuase it is already in use by another person or process".
This code is being executed in AccessXP using an ODBC connection to a server
DB. I'm not sure exactly which statement it is giving the error on.
All other computers were turned off and the one computer was restarted, but
we still get the error. The table is not being used by a form.
Any help would be greatly appreciated.
Tony
========================================
====================================
=================================
CurrentDb.Execute "DROP TABLE Items"
DoCmd.TransferDatabase acImport, "ODBC Database", _
" ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=0;
DecimalSymbol=.;;TABLE=Items", _
acTable, "Items", "Items"
CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items (ItemNumber)"How can you not be sure what statement is giving the error? Add a msgbox
before each statement :-)
Two ideas - neither of which might be the cause, but they would be easy to
check:
(1) Is "items" a reserved word in Access? (I do not have it here to check.)
If so, try [Items].
(2) Try caching the currentdb reference: (You should really do this anyway)
dim db as database
set db = currentdb()
' do things with db, not currentdb().
set db = nothing
HTH,
TC
"Tony Girgenti" <antoniongirgenti@.comcast.net> wrote in message
news:OeD2wd04DHA.2772@.TK2MSFTNGP09.phx.gbl...
it
server
but
========================================
====================================[QUO
TE]
> =================================
> CurrentDb.Execute "DROP TABLE Items"
> DoCmd.TransferDatabase acImport, "ODBC Database", _
>[/QUOTE]
" ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=0;[QUOT
E]
> DecimalSymbol=.;;TABLE=Items", _
> acTable, "Items", "Items"
> CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items[/QUOTE]
(ItemNumber)"|||"Tony Girgenti" <antoniongirgenti@.comcast.net> wrote in message
news:OeD2wd04DHA.2772@.TK2MSFTNGP09.phx.gbl...
Hi Tony,
I am assuming you did not want to *link* to
the SQL table?
Would you mind changing your local table
name to "tblItems" then try the following:
'--
Dim strSQL As String
Debug.Print "About to delete table."
CurrentDb.Execute "DROP TABLE tblItems", dbFailOnError
Debug.Print "Have deleted table."
strSQL = "SELECT Items.* INTO tblItems " _
& "FROM Items IN '' [ODBC;DSN=DEMO2ENG;DATABASE=];"
Debug.Print "Make table query: " & vbCrLf & strSQL
CurrentDb.Execute strSQL, dbFailOnError
Debug.Print "Have executed make table."
Debug.Print "About to create index."
strSQL = "CREATE UNIQUE INDEX ItemNumIdx ON tblItems (ItemNumber);"
CurrentDb.Execute strSQL, dbFailOnError
Debug.Print "Have created index."
'--
{from tip provided by John Viescas}
To see what needs to go in between the brackets,
temporarily link to remote table "Items," then in
Immediate Window type the following:
?CurrentDb.Tabledefs("Items").Connect
Place whatever this returns inside the brackets,
then delete link to "Items."
Please respond back if I have misunderstood.
Good luck,
Gary Walter|||Tony,
It is not considered to be polite to cross-post the same question to several
news groups, because of this your message is ignored by many skilled news
group readers. And then again resending the same question over and over
again is even more rude.
Regards,
"Tony Girgenti" <antoniongirgenti@.comcast.net> wrote in message
news:OeD2wd04DHA.2772@.TK2MSFTNGP09.phx.gbl...
I'm reposting this because i tried deleteing the table manually and
recreating it manually. It works OK after that, but when i try it again, it
gives the error again. There are four tables, but it only happens on the
"ITEMS" table.
I'm trying to execute the following code and i am getting this error:
"Run-time error '3211'; The database engine could not lock table 'Items'
becuase it is already in use by another person or process".
This code is being executed in AccessXP using an ODBC connection to a server
DB. I'm not sure exactly which statement it is giving the error on.
All other computers were turned off and the one computer was restarted, but
we still get the error. The table is not being used by a form.
Any help would be greatly appreciated.
Tony
========================================
====================================
=================================
CurrentDb.Execute "DROP TABLE Items"
DoCmd.TransferDatabase acImport, "ODBC Database", _
" ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=0;
DecimalSymbol=.;;TABLE=Items", _
acTable, "Items", "Items"
CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items (ItemNumber)"
recreating it manually. It works OK after that, but when i try it again, it
gives the error again. There are four tables, but it only happens on the
"ITEMS" table.
I'm trying to execute the following code and i am getting this error:
"Run-time error '3211'; The database engine could not lock table 'Items'
becuase it is already in use by another person or process".
This code is being executed in AccessXP using an ODBC connection to a server
DB. I'm not sure exactly which statement it is giving the error on.
All other computers were turned off and the one computer was restarted, but
we still get the error. The table is not being used by a form.
Any help would be greatly appreciated.
Tony
========================================
====================================
=================================
CurrentDb.Execute "DROP TABLE Items"
DoCmd.TransferDatabase acImport, "ODBC Database", _
" ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=0;
DecimalSymbol=.;;TABLE=Items", _
acTable, "Items", "Items"
CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items (ItemNumber)"How can you not be sure what statement is giving the error? Add a msgbox
before each statement :-)
Two ideas - neither of which might be the cause, but they would be easy to
check:
(1) Is "items" a reserved word in Access? (I do not have it here to check.)
If so, try [Items].
(2) Try caching the currentdb reference: (You should really do this anyway)
dim db as database
set db = currentdb()
' do things with db, not currentdb().
set db = nothing
HTH,
TC
"Tony Girgenti" <antoniongirgenti@.comcast.net> wrote in message
news:OeD2wd04DHA.2772@.TK2MSFTNGP09.phx.gbl...
quote:
> I'm reposting this because i tried deleteing the table manually and
> recreating it manually. It works OK after that, but when i try it again,
it
quote:
> gives the error again. There are four tables, but it only happens on the
> "ITEMS" table.
> I'm trying to execute the following code and i am getting this error:
> "Run-time error '3211'; The database engine could not lock table 'Items'
> becuase it is already in use by another person or process".
> This code is being executed in AccessXP using an ODBC connection to a
server
quote:
> DB. I'm not sure exactly which statement it is giving the error on.
> All other computers were turned off and the one computer was restarted,
but
quote:
> we still get the error. The table is not being used by a form.
> Any help would be greatly appreciated.
> Tony
>
========================================
====================================[QUO
TE]
> =================================
> CurrentDb.Execute "DROP TABLE Items"
> DoCmd.TransferDatabase acImport, "ODBC Database", _
>[/QUOTE]
" ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=0;[QUOT
E]
> DecimalSymbol=.;;TABLE=Items", _
> acTable, "Items", "Items"
> CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items[/QUOTE]
(ItemNumber)"|||"Tony Girgenti" <antoniongirgenti@.comcast.net> wrote in message
news:OeD2wd04DHA.2772@.TK2MSFTNGP09.phx.gbl...
quote:
> I'm reposting this because i tried deleteing the table manually and
> recreating it manually. It works OK after that, but when i try it again,
it
> gives the error again. There are four tables, but it only happens on the
> "ITEMS" table.
> I'm trying to execute the following code and i am getting this error:
> "Run-time error '3211'; The database engine could not lock table 'Items'
> becuase it is already in use by another person or process".
> This code is being executed in AccessXP using an ODBC connection to a serv
er
> DB. I'm not sure exactly which statement it is giving the error on.
> All other computers were turned off and the one computer was restarted, bu
t
> we still get the error. The table is not being used by a form.
> Any help would be greatly appreciated.
> Tony
> ========================================
==================================
==
> =================================
> CurrentDb.Execute "DROP TABLE Items"
> DoCmd.TransferDatabase acImport, "ODBC Database", _
> " ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=
0;
> DecimalSymbol=.;;TABLE=Items", _
> acTable, "Items", "Items"
> CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items (ItemNumber
)"
>
>
Hi Tony,
I am assuming you did not want to *link* to
the SQL table?
Would you mind changing your local table
name to "tblItems" then try the following:
'--
Dim strSQL As String
Debug.Print "About to delete table."
CurrentDb.Execute "DROP TABLE tblItems", dbFailOnError
Debug.Print "Have deleted table."
strSQL = "SELECT Items.* INTO tblItems " _
& "FROM Items IN '' [ODBC;DSN=DEMO2ENG;DATABASE=];"
Debug.Print "Make table query: " & vbCrLf & strSQL
CurrentDb.Execute strSQL, dbFailOnError
Debug.Print "Have executed make table."
Debug.Print "About to create index."
strSQL = "CREATE UNIQUE INDEX ItemNumIdx ON tblItems (ItemNumber);"
CurrentDb.Execute strSQL, dbFailOnError
Debug.Print "Have created index."
'--
{from tip provided by John Viescas}
To see what needs to go in between the brackets,
temporarily link to remote table "Items," then in
Immediate Window type the following:
?CurrentDb.Tabledefs("Items").Connect
Place whatever this returns inside the brackets,
then delete link to "Items."
Please respond back if I have misunderstood.
Good luck,
Gary Walter|||Tony,
It is not considered to be polite to cross-post the same question to several
news groups, because of this your message is ignored by many skilled news
group readers. And then again resending the same question over and over
again is even more rude.
Regards,
"Tony Girgenti" <antoniongirgenti@.comcast.net> wrote in message
news:OeD2wd04DHA.2772@.TK2MSFTNGP09.phx.gbl...
I'm reposting this because i tried deleteing the table manually and
recreating it manually. It works OK after that, but when i try it again, it
gives the error again. There are four tables, but it only happens on the
"ITEMS" table.
I'm trying to execute the following code and i am getting this error:
"Run-time error '3211'; The database engine could not lock table 'Items'
becuase it is already in use by another person or process".
This code is being executed in AccessXP using an ODBC connection to a server
DB. I'm not sure exactly which statement it is giving the error on.
All other computers were turned off and the one computer was restarted, but
we still get the error. The table is not being used by a form.
Any help would be greatly appreciated.
Tony
========================================
====================================
=================================
CurrentDb.Execute "DROP TABLE Items"
DoCmd.TransferDatabase acImport, "ODBC Database", _
" ODBC;DSN=DEMO2ENG;ArrayFetchOn=1;ArrayBu
fferSize=8;DBQ=DEMO2ENG;OpenMode=0;
DecimalSymbol=.;;TABLE=Items", _
acTable, "Items", "Items"
CurrentDb.Execute "CREATE UNIQUE INDEX ItemNumIdx ON Items (ItemNumber)"
Subscribe to:
Posts (Atom)