maintenance plan wizard: major

Showing posts with label major. Show all posts

Monday, March 12, 2012

Major Version number

How can I get just the majore version number of SQL Server from SQL 7 thru
SQL 2005 SP1 ?
Michael Tissington
http://www.oaklodge.com
http://www.sqlview.netCheck out SERVERPROPERTY() in the BOL.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Michael Tissington" <mtissington@.newsgroups.nospam> wrote in message
news:%23DGRbHbjGHA.1552@.TK2MSFTNGP03.phx.gbl...
How can I get just the majore version number of SQL Server from SQL 7 thru
SQL 2005 SP1 ?
Michael Tissington
http://www.oaklodge.com
http://www.sqlview.net|||Thanks for Tom's input.
Hi Michael,
In addition to Tom's suggestion here is a knowledge base article which
demonstrate how to identify version info of SQL Server(applied for
sqlserver from v6.5 to v 9.0(2005))
#How to identify your SQL Server version and edition
http://support.microsoft.com/kb/321185/en-us
Hope this also helps.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||SERVERPROPERTY was introduced in SQL Server 2000.
HTH
Kalen Delaney, SQL Server MVP
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:%23n1iyObjGHA.4044@.TK2MSFTNGP03.phx.gbl...
> Check out SERVERPROPERTY() in the BOL.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> .
> "Michael Tissington" <mtissington@.newsgroups.nospam> wrote in message
> news:%23DGRbHbjGHA.1552@.TK2MSFTNGP03.phx.gbl...
> How can I get just the majore version number of SQL Server from SQL 7 thru
> SQL 2005 SP1 ?
> --
> Michael Tissington
> http://www.oaklodge.com
> http://www.sqlview.net
>|||Hello Michael,
Have you got any further ideas on this issue or does my last reply also
help some? If there is still anything we can help, please feel free to post
here.
Regards,
Steven Cheng
Microsoft MSDN Online Support Lead
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Steven,
Unfortunatley this does not really work.
SERVERPROPERTY only works for SQL 2000 and later.
The @.@.Version used to work consistantly, however with SP1 of SQL 2005 and
double space in the formating has been changed to a single space so I can no
longer predict where the major version number is in the string.
Any more ideas please ?
Michael Tissington
http://www.oaklodge.com
http://www.sqlview.net
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:hPQMgI8jGHA.764@.TK2MSFTNGXA01.phx.gbl...
> Hello Michael,
> Have you got any further ideas on this issue or does my last reply also
> help some? If there is still anything we can help, please feel free to
> post
> here.
> Regards,
> Steven Cheng
> Microsoft MSDN Online Support Lead
>
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Hello, Michael
Try the following query:
SELECT LTRIM(SUBSTRING(@.@.VERSION,CHARINDEX('-',@.@.VERSION)+1,
CHARINDEX('.',SUBSTRING(@.@.VERSION,CHARINDEX('-',@.@.VERSION),10))-2))
This query searches for the first dot after a dash in @.@.VERSION and
returns the trimmed string between them.
Razvan
PS. I tested the above query only on SQL Server 2000 and 2005, because
I don't have a 6.5 or 7.0 server available for testing.|||Hi Michael,
Have you tried the suggestion Razvan provided?
Please let me know the result. If there is still anything we can help,
please feel free to post here.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
I do not see a solution by Razvan - where is this ?
I only see posts by Steven Cheng and Tom Moreau.
Michael Tissington
http://www.oaklodge.com
http://www.sqlview.net
"Wei Lu" <weilu@.online.microsoft.com> wrote in message
news:I6D0ufdlGHA.4948@.TK2MSFTNGXA01.phx.gbl...
> Hi Michael,
> Have you tried the suggestion Razvan provided?
> Please let me know the result. If there is still anything we can help,
> please feel free to post here.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Michael,
I have posted his suggestion here. Please have a check and let me know does
this help.
From: "Razvan Socol" <rsocol@.gmail.com>
Newsgroups: microsoft.public.sqlserver.programming
Subject: Re: Major Version number
Date: 20 Jun 2006 23:59:39 -0700
Hello, Michael
Try the following query:
SELECT LTRIM(SUBSTRING(@.@.VERSION,CHARINDEX('-',@.@.VERSION)+1,
CHARINDEX('.',SUBSTRING(@.@.VERSION,CHARINDEX('-',@.@.VERSION),10))-2))
This query searches for the first dot after a dash in @.@.VERSION and
returns the trimmed string between them.
Razvan
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.

Major Time Out Issue

I have created a database with three tables. The database has been up for a month now and contains about 20,000 records. In order to improve performance and resolve some issues I an attempting to change some of the table information. i.e. allow nulls in a few fields. When I use TSQL or the GUI to make these changes I get the following error: Timeout expired. The timeout period elapsed prior to completion of the operation or server not responding.

Source: .Net SQLClient Data Provider

I have SQL Server Express SP2 installed with .Net framework v3.0

Note: This issue appears when I attempt to delete a row from a table as well.

Any thoughts?

It is difficult to guess -there isn't enough information.

If users are in the database at the same time as you are attempting to make table wide changes, you could be experiencing 'blocking' behavior. Try making your changes when there are no users in the database. (Twenty thousand records is a very small table and most changes should happen relatively quickly.)

You might also verify the indexing.

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, ReeleezeeSolved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes')
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:
> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>> Dear All,
>> I've just installed two brand new SQL Server servers with Windows 2003
>> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
>> I now need to configure the network protocols for SQL Server on these
>> machines, but on both machines the SQL Server instances are not showing
>> up in
>> the "SQL Server 2005 Configuration manager"
>> On two other x64 SQL Server 2005 servers which we installed last year I
>> see
>> a total of 5 icons in the "SQL Server 2005 Configuration manager":
>> - SQL Server 2005 Services
>> - SQL Server 2005 Network configuration (32-bit)
>> - SQL Server 2005 Native Client Configuration (32 Bit)
>> - SQL Server 2005 Network configuration
>> - SQL Server 2005 Native Client Configuration
>> but on the two new servers only the first 3 groups are showing up.
>> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
>> Network configuration", but this group is not showing up.
>> On both servers I only have configured a default (non-named) instance.
>> Does anybody have a clue what can be wrong or have a hint as where to
>> start
>> searching for a solution?
>> Because we posted this question earlier and have not received a single
>> response I've resorted to crossposting to the following groups:
>> microsoft.public.sqlserver.server
>> microsoft.public.sqlserver.tools
>> microsoft.public.sqlserver.security
>> microsoft.public.sqlserver.setup
>>
>> Kind regards,
>> Tom and Nick, Reeleezee|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>> Dear All,
>> I've just installed two brand new SQL Server servers with Windows 2003
>> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
>> I now need to configure the network protocols for SQL Server on these
>> machines, but on both machines the SQL Server instances are not showing
>> up in
>> the "SQL Server 2005 Configuration manager"
>> On two other x64 SQL Server 2005 servers which we installed last year I
>> see
>> a total of 5 icons in the "SQL Server 2005 Configuration manager":
>> - SQL Server 2005 Services
>> - SQL Server 2005 Network configuration (32-bit)
>> - SQL Server 2005 Native Client Configuration (32 Bit)
>> - SQL Server 2005 Network configuration
>> - SQL Server 2005 Native Client Configuration
>> but on the two new servers only the first 3 groups are showing up.
>> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
>> Network configuration", but this group is not showing up.
>> On both servers I only have configured a default (non-named) instance.
>> Does anybody have a clue what can be wrong or have a hint as where to
>> start
>> searching for a solution?
>> Because we posted this question earlier and have not received a single
>> response I've resorted to crossposting to the following groups:
>> microsoft.public.sqlserver.server
>> microsoft.public.sqlserver.tools
>> microsoft.public.sqlserver.security
>> microsoft.public.sqlserver.setup
>>
>> Kind regards,
>> Tom and Nick, Reeleezee

Major SQL Server 2k5 x64 configuration problem

Major Search Problem

Hi,
I got a problem on searching a keyword with '&'.
I run this query and I got all records with '&'.
select * from freetexttable(table1, *, 'AT&T');
I run this and I got records with AT&T.
select * from table1 where fieldname1 like '%AT&T%'
Since 'AT' and 'T' are considered noise words, how can I search for
'AT&T' as a whole word?
Thanks in advance.
Baldwin
remove t and at from your noise word list, rebuild your catalogs and it
should work.
RelevantNoise.com - dedicated to mining blogs for business intelligence.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Baldwin" <ibaldwinjr@.gmail.com> wrote in message
news:1194974569.682896.215800@.v2g2000hsf.googlegro ups.com...
> Hi,
> I got a problem on searching a keyword with '&'.
> I run this query and I got all records with '&'.
> select * from freetexttable(table1, *, 'AT&T');
> I run this and I got records with AT&T.
> select * from table1 where fieldname1 like '%AT&T%'
> Since 'AT' and 'T' are considered noise words, how can I search for
> 'AT&T' as a whole word?
> Thanks in advance.
> Baldwin
>

Major query optimiser weirdness with UDFs and SPs on SQL 2000

There is something very strange going on here. Tested with ADO 2.7 and
MSDE/2000. At first, things look quite sensible.

You have a simple SQL query, let's say

select * from mytab where col1 = 1234

Now, let's write a simple VB program to do this query back to an
MSDE/2000 database on our local machine. Effectively, we'll

rs.open sSQL
rs.close

and do that 1,000 times. We wont bother fetching the result set, it
isn't important in this example.

No problem. On my machine this takes around 1.6 seconds and modifying
the code so that the column value in the where clause changes each
time (i.e col1 = nnnn), doesn't make a substantial difference to this
time. Well, that all seems reasonable, so moving right along...

Now we do it with a stored procedure

create procedure proctest(@.id int)
as
select * from mytab where col1 = @.id

and we now find that executing

proctest nnnn

1,000 times takes around 1.6 seconds whether or not the argument
changes. So far so good. No obvious saving, but then we wouldn't
expect any. The query is very simple, after all.

Well, get to the point!

Now create a table-returning UDF

create function functest(@.id int) returns table as

return
(
select * from mytab where col1 = @.id
)

try calling that 1,000 times as

select * from functest(nnnn)

and we get around 5.5 seconds on my machine if the argument changes,
otherwise 1.6 seconds if it remains the same for each call.

Hmm, looks like the query plan is discarded if the argument changes.
Well, that's fair enough I guess. UDFs might well be more expensive...
gotta be careful about using them. It's odd that discarding the query
plan seems to be SO expensive, but hey, waddya expect?. (perhaps the
UDF is completely rebuilt, who knows)

last test, then. Create an SP that calls the UDF

create procedure proctest1(@.id int)
as
select * from functest(@.id)

Ok, here's the $64,000 question. How long will this take if @.id
changes each time. The raw UDF took 5.5 seconds, remember, so this
should be slightly slower.

But... IT IS NOT.. It takes 1.6 seconds whether or not @.id changes.
Somehow, the UDF becomes FOUR TIMES more efficient when wrapped in an
SP.

My theory, which I stress is not entirely scientific, goes something
like this:-

I deduce that SQL Server decides to reuse the query plan in this
circumstance but does NOT when the UDF is called directly. This is
counter-intuitive but it may be because SQL Server's query parser is
tuned for conventional SQL i.e it can say

well, I've got

select * from mytab WHERE [something or other]

and now I've got

select * from mytab WHERE [something else]

so I can probably re-use the query plan from last time. (I don't know
if it is this clever, but it does seem to know when two
textually-different queries have some degree of commonality)

Whereas with

select * from UDF(arg1)

and

select * from UDF(arg2)

it goes... hmm, mebbe not... I better not risk it.

But with

sp_something arg1

and

sp_something arg2

it goes... yup, i'll just go call it... and because the SP was already
compiled, the internal call to the UDF already has a query plan.

Anyway, that's the theory. For more complex UDFs, by the way, the
performance increase can be a lot more substantial. On a big complex
UDF with a bunch of joins, I measured a tenfold increase in
performance just by wrapping it in an SP, as above.

Obviously, wrapping a UDF in an SP isn't generally a good thing; the
idea of UDFs is to allow the column list and where clause to filter
the rowset of the UDF, but if you are repeatedly calling the UDF with
the same where clause and column list, this will make it a *lot*
faster.Andrew Mayo (ajmayo@.my-deja.com) writes:
> try calling that 1,000 times as
> select * from functest(nnnn)
> and we get around 5.5 seconds on my machine if the argument changes,
> otherwise 1.6 seconds if it remains the same for each call.
> Hmm, looks like the query plan is discarded if the argument changes.
> Well, that's fair enough I guess. UDFs might well be more expensive...
> gotta be careful about using them. It's odd that discarding the query
> plan seems to be SO expensive, but hey, waddya expect?. (perhaps the
> UDF is completely rebuilt, who knows)

The reason why the call to the UDF takes longer time is simple,
and you would have obtained the same result if you had called the
bare SQL statement with different values for 1234.

To wit, a table-valued UDF is not really a function: it's a macro, so
when you call it on your own, this is the same as invoking the naked
SQL statement.

Here, this costs you performance, but normally this works to your
advantage. You use the table-valued UDF in a query, and the optimizer
can then work with the expanded, potentially creating a better plan
than if had to first had to evaluate the UDF on its own.

A good way to illustrate this, is to write three functions, one of
each kind that all return the value of @.@.nestlevel.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <sommar@.algonet.se> wrote in message news:<Xns940E3E3B9C99Yazorman@.127.0.0.1>...
[snip]
> The reason why the call to the UDF takes longer time is simple,
> and you would have obtained the same result if you had called the
> bare SQL statement with different values for 1234.
Hmm. Interesting. But I did state in the original post that I had also
tried the bare SQL statement with *different* values for the column
value and that this does *not* affect the execution time. This would
appear to contradict your expected observation.

I have done quite a bit of testing with more complex queries and again
the cost of the raw query does not seem to be affected significantly
by changing the substituted argument (I have only done this for the
one argument case)

The most complex query I have tested involves several joins, has a
CASE statement, and has the argument parametrically substituted in
four places within the query. The execution time for this query is
around 8 seconds per 100 iterations running on the local server. This
figure is almost constant, regardless of the parameter value, which is
numeric.

If I wrap this into a UDF, it also takes 8 seconds for 100 iterations,
UNLESS I keep the argument the same. If I do that, execution time
drops to 0.4 seconds.

If I wrap it into an SP, execution time drops to 0.4 seconds
regardless of the passed-in argument. If I then call the UDF from the
SP, the execution time remains at 0.4 seconds regardless of the
argument.

However, if a UDF is essentially a macro (and unfortunately lacking
the source code for SQL Server I have no idea how they are
implemented), then I can see that effectively each time the UDF is
invoked, if the arguments change, then the UDF is effectively rebuilt
- presumably, this is equivalent to recompiling a stored procedure -
but if the UDF is already inside a precompiled SP, then this process
does not need to occur. That would make sense.|||Andrew Mayo (ajmayo@.my-deja.com) writes:
> Hmm. Interesting. But I did state in the original post that I had also
> tried the bare SQL statement with *different* values for the column
> value and that this does *not* affect the execution time. This would
> appear to contradict your expected observation.

It could be that the single SQL statement is autoparameterized, but
when it is packaged in a UDF it is not.

> However, if a UDF is essentially a macro (and unfortunately lacking
> the source code for SQL Server I have no idea how they are
> implemented), then I can see that effectively each time the UDF is
> invoked, if the arguments change, then the UDF is effectively rebuilt
> - presumably, this is equivalent to recompiling a stored procedure -
> but if the UDF is already inside a precompiled SP, then this process
> does not need to occur. That would make sense.

Not that this only apply to inlined table function. If you were to
put the SELECT in a multi-statement UDF, I predict that the execution
time is the same as for the stored procedure, or possibly somewhat
higher, since there is some overhead for the table variable.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Major Problems with Calculated Fields

Is anyone else having problems with Calculated Members? Everything was working fine with viewing the cubes in the browser, in Reporting Services, and via Pivot tables...but once I put in some simple calculated members (simple parallel period functions), query times are extremely slow, everything locks up,unexpected Visual Studio crashes occur...SSAS pretty much becomes unusable.

Anyone with similar experiences?

You should see some performance improvements in SP1.

In limited number of cases you can use NON_EMPTY_BEHAVIOR when defining you calculated member. You got to be careful with it for parallel period such that you might not have a value for certain measure in parallel period. But if you can guarantee that, you should see way better performance.

Hope that helps.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Do you know if this is a problem with SSAS, Reporting Services, or the OLAP 9.0 Provider? I seem to be having the same problem when using Reporting Services 2000 and the 9.0 Provider. If I can't report on SSAS 2005 easily, I simply can't upgrade until the issues are resolved.

Friday, March 9, 2012

Major problems setting up RS and deploying a report

As usual I'm learning by doing and I'm not sure I know what I'm doing.
We have a legacy server running Windows Server 2003 and Sql Server 2000.
We want to run a Reporting Services report off one of the tables in SQL
Server 2000 so I was told to install SQL2005 Standard including RS on the
server.
IIS has been installed. When it came time to install SQL2005 I had a few
moments of confusion. I am used to installing SQL2005 Express which seems to
automatically install a named instance. In this case I manually selected a
named instance (RS2005) because the wording of the screen seemed to imply
that the default instance of SQL2000 would be upgraded (which wouldn't be a
good idea.)
So I installed SQL2005 with a named instance and the BI Studio. I copied
over the report I wanted to deploy. Now my problem is that I cannot get it
to deploy. In BI/VS the TargetServerURL is
http://localhost/ReportServer$RS2005. All I get are connection errors: 'A
connection could not be made to the report server
http://localhost/ReportServer$RS2005. Additional information - The attempt
to connect to the report server failed. Check your connection information,
etc.'
I have run the Reporting Services Configuration manager. To save time, here
are the settings:
Report Server Status
Instance Name RS2005
Instance ID MSSQL.2
Running
--
Report Server Virtual Directory
Name ReportServer$RS2005
Website Default Website
Report Manager Virtual Directory Settings
Name Reports$RS2005
Website Default Web Site
Windows Service Identity
Service Nmae ReportServer$RS2005
Service Account LocalSystem
Built-in Account Local SystemFirst things first. Can you pull up Report Manager (this is the portal that
ships with RS and is used to manage RS).
http://yourservername/Reports/Pages/Folder.aspx
localhost only works if you are on the machine hosting RS.
Second, are you an adminstrator on that machine. All people in the local
administrator group on the machine that has RS installed will automatically
be in the RS administrators role.
Deploying is the last thing you should try.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> As usual I'm learning by doing and I'm not sure I know what I'm doing.
> We have a legacy server running Windows Server 2003 and Sql Server 2000.
> We want to run a Reporting Services report off one of the tables in SQL
> Server 2000 so I was told to install SQL2005 Standard including RS on the
> server.
> IIS has been installed. When it came time to install SQL2005 I had a few
> moments of confusion. I am used to installing SQL2005 Express which seems
> to
> automatically install a named instance. In this case I manually selected
> a
> named instance (RS2005) because the wording of the screen seemed to imply
> that the default instance of SQL2000 would be upgraded (which wouldn't be
> a
> good idea.)
> So I installed SQL2005 with a named instance and the BI Studio. I copied
> over the report I wanted to deploy. Now my problem is that I cannot get
> it
> to deploy. In BI/VS the TargetServerURL is
> http://localhost/ReportServer$RS2005. All I get are connection errors: 'A
> connection could not be made to the report server
> http://localhost/ReportServer$RS2005. Additional information - The
> attempt
> to connect to the report server failed. Check your connection
> information,
> etc.'
> I have run the Reporting Services Configuration manager. To save time,
> here
> are the settings:
> Report Server Status
> Instance Name RS2005
> Instance ID MSSQL.2
> Running
> --
> Report Server Virtual Directory
> Name ReportServer$RS2005
> Website Default Website
> Report Manager Virtual Directory Settings
> Name Reports$RS2005
> Website Default Web Site
> Windows Service Identity
> Service Nmae ReportServer$RS2005
> Service Account LocalSystem
> Built-in Account Local System
>|||No. I've tried both on the server itself and from another machine. Always
'Page cannot be found.'
(Tried with both http://<servername>/Reports and
http://<servername>/Reports$RS2005)
As far as I know I'm an administrator.
"Bruce L-C [MVP]" wrote:
> First things first. Can you pull up Report Manager (this is the portal that
> ships with RS and is used to manage RS).
> http://yourservername/Reports/Pages/Folder.aspx
> localhost only works if you are on the machine hosting RS.
> Second, are you an adminstrator on that machine. All people in the local
> administrator group on the machine that has RS installed will automatically
> be in the RS administrators role.
> Deploying is the last thing you should try.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> > As usual I'm learning by doing and I'm not sure I know what I'm doing.
> >
> > We have a legacy server running Windows Server 2003 and Sql Server 2000.
> > We want to run a Reporting Services report off one of the tables in SQL
> > Server 2000 so I was told to install SQL2005 Standard including RS on the
> > server.
> >
> > IIS has been installed. When it came time to install SQL2005 I had a few
> > moments of confusion. I am used to installing SQL2005 Express which seems
> > to
> > automatically install a named instance. In this case I manually selected
> > a
> > named instance (RS2005) because the wording of the screen seemed to imply
> > that the default instance of SQL2000 would be upgraded (which wouldn't be
> > a
> > good idea.)
> >
> > So I installed SQL2005 with a named instance and the BI Studio. I copied
> > over the report I wanted to deploy. Now my problem is that I cannot get
> > it
> > to deploy. In BI/VS the TargetServerURL is
> > http://localhost/ReportServer$RS2005. All I get are connection errors: 'A
> > connection could not be made to the report server
> > http://localhost/ReportServer$RS2005. Additional information - The
> > attempt
> > to connect to the report server failed. Check your connection
> > information,
> > etc.'
> >
> > I have run the Reporting Services Configuration manager. To save time,
> > here
> > are the settings:
> > Report Server Status
> > Instance Name RS2005
> > Instance ID MSSQL.2
> > Running
> >
> > --
> >
> > Report Server Virtual Directory
> > Name ReportServer$RS2005
> > Website Default Website
> >
> > Report Manager Virtual Directory Settings
> > Name Reports$RS2005
> > Website Default Web Site
> >
> > Windows Service Identity
> > Service Nmae ReportServer$RS2005
> > Service Account LocalSystem
> > Built-in Account Local System
> >
> >
>
>|||By what you posted it seems that you have it installed in the default
website in which case this should be working. Open up IIS adminstrator
(whatever it is called) and see if you have the websites.
By the way, you did not need to install SQL 2005. RS 2005 can use SQL 2000
for its object/metadata storage. You have to have a license for SQL Server
2005 but it does not need to be installed.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> No. I've tried both on the server itself and from another machine.
> Always
> 'Page cannot be found.'
> (Tried with both http://<servername>/Reports and
> http://<servername>/Reports$RS2005)
> As far as I know I'm an administrator.
> "Bruce L-C [MVP]" wrote:
>> First things first. Can you pull up Report Manager (this is the portal
>> that
>> ships with RS and is used to manage RS).
>> http://yourservername/Reports/Pages/Folder.aspx
>> localhost only works if you are on the machine hosting RS.
>> Second, are you an adminstrator on that machine. All people in the local
>> administrator group on the machine that has RS installed will
>> automatically
>> be in the RS administrators role.
>> Deploying is the last thing you should try.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
>> > As usual I'm learning by doing and I'm not sure I know what I'm doing.
>> >
>> > We have a legacy server running Windows Server 2003 and Sql Server
>> > 2000.
>> > We want to run a Reporting Services report off one of the tables in SQL
>> > Server 2000 so I was told to install SQL2005 Standard including RS on
>> > the
>> > server.
>> >
>> > IIS has been installed. When it came time to install SQL2005 I had a
>> > few
>> > moments of confusion. I am used to installing SQL2005 Express which
>> > seems
>> > to
>> > automatically install a named instance. In this case I manually
>> > selected
>> > a
>> > named instance (RS2005) because the wording of the screen seemed to
>> > imply
>> > that the default instance of SQL2000 would be upgraded (which wouldn't
>> > be
>> > a
>> > good idea.)
>> >
>> > So I installed SQL2005 with a named instance and the BI Studio. I
>> > copied
>> > over the report I wanted to deploy. Now my problem is that I cannot
>> > get
>> > it
>> > to deploy. In BI/VS the TargetServerURL is
>> > http://localhost/ReportServer$RS2005. All I get are connection errors:
>> > 'A
>> > connection could not be made to the report server
>> > http://localhost/ReportServer$RS2005. Additional information - The
>> > attempt
>> > to connect to the report server failed. Check your connection
>> > information,
>> > etc.'
>> >
>> > I have run the Reporting Services Configuration manager. To save time,
>> > here
>> > are the settings:
>> > Report Server Status
>> > Instance Name RS2005
>> > Instance ID MSSQL.2
>> > Running
>> >
>> > --
>> >
>> > Report Server Virtual Directory
>> > Name ReportServer$RS2005
>> > Website Default Website
>> >
>> > Report Manager Virtual Directory Settings
>> > Name Reports$RS2005
>> > Website Default Web Site
>> >
>> > Windows Service Identity
>> > Service Nmae ReportServer$RS2005
>> > Service Account LocalSystem
>> > Built-in Account Local System
>> >
>> >
>>|||By 'websites' do you mean the report directories under Default Web Site?
I have 4 report directories under the Default Web Site: ReportServer,
Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are empty.
The last two are full of what appears to be asp.net related files and
directories.
(I admit that I was under the impression that RS2005 needed a 2005 db to
store its data.)
"Bruce L-C [MVP]" wrote:
> By what you posted it seems that you have it installed in the default
> website in which case this should be working. Open up IIS adminstrator
> (whatever it is called) and see if you have the websites.
> By the way, you did not need to install SQL 2005. RS 2005 can use SQL 2000
> for its object/metadata storage. You have to have a license for SQL Server
> 2005 but it does not need to be installed.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> > No. I've tried both on the server itself and from another machine.
> > Always
> > 'Page cannot be found.'
> >
> > (Tried with both http://<servername>/Reports and
> > http://<servername>/Reports$RS2005)
> >
> > As far as I know I'm an administrator.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> First things first. Can you pull up Report Manager (this is the portal
> >> that
> >> ships with RS and is used to manage RS).
> >>
> >> http://yourservername/Reports/Pages/Folder.aspx
> >>
> >> localhost only works if you are on the machine hosting RS.
> >>
> >> Second, are you an adminstrator on that machine. All people in the local
> >> administrator group on the machine that has RS installed will
> >> automatically
> >> be in the RS administrators role.
> >>
> >> Deploying is the last thing you should try.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> > As usual I'm learning by doing and I'm not sure I know what I'm doing.
> >> >
> >> > We have a legacy server running Windows Server 2003 and Sql Server
> >> > 2000.
> >> > We want to run a Reporting Services report off one of the tables in SQL
> >> > Server 2000 so I was told to install SQL2005 Standard including RS on
> >> > the
> >> > server.
> >> >
> >> > IIS has been installed. When it came time to install SQL2005 I had a
> >> > few
> >> > moments of confusion. I am used to installing SQL2005 Express which
> >> > seems
> >> > to
> >> > automatically install a named instance. In this case I manually
> >> > selected
> >> > a
> >> > named instance (RS2005) because the wording of the screen seemed to
> >> > imply
> >> > that the default instance of SQL2000 would be upgraded (which wouldn't
> >> > be
> >> > a
> >> > good idea.)
> >> >
> >> > So I installed SQL2005 with a named instance and the BI Studio. I
> >> > copied
> >> > over the report I wanted to deploy. Now my problem is that I cannot
> >> > get
> >> > it
> >> > to deploy. In BI/VS the TargetServerURL is
> >> > http://localhost/ReportServer$RS2005. All I get are connection errors:
> >> > 'A
> >> > connection could not be made to the report server
> >> > http://localhost/ReportServer$RS2005. Additional information - The
> >> > attempt
> >> > to connect to the report server failed. Check your connection
> >> > information,
> >> > etc.'
> >> >
> >> > I have run the Reporting Services Configuration manager. To save time,
> >> > here
> >> > are the settings:
> >> > Report Server Status
> >> > Instance Name RS2005
> >> > Instance ID MSSQL.2
> >> > Running
> >> >
> >> > --
> >> >
> >> > Report Server Virtual Directory
> >> > Name ReportServer$RS2005
> >> > Website Default Website
> >> >
> >> > Report Manager Virtual Directory Settings
> >> > Name Reports$RS2005
> >> > Website Default Web Site
> >> >
> >> > Windows Service Identity
> >> > Service Nmae ReportServer$RS2005
> >> > Service Account LocalSystem
> >> > Built-in Account Local System
> >> >
> >> >
> >>
> >>
> >>
>
>|||You have somehow gotten a totally messed up install. You should not have
four sites. Try this:
http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> By 'websites' do you mean the report directories under Default Web Site?
> I have 4 report directories under the Default Web Site: ReportServer,
> Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are empty.
> The last two are full of what appears to be asp.net related files and
> directories.
> (I admit that I was under the impression that RS2005 needed a 2005 db to
> store its data.)
> "Bruce L-C [MVP]" wrote:
>> By what you posted it seems that you have it installed in the default
>> website in which case this should be working. Open up IIS adminstrator
>> (whatever it is called) and see if you have the websites.
>> By the way, you did not need to install SQL 2005. RS 2005 can use SQL
>> 2000
>> for its object/metadata storage. You have to have a license for SQL
>> Server
>> 2005 but it does not need to be installed.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
>> > No. I've tried both on the server itself and from another machine.
>> > Always
>> > 'Page cannot be found.'
>> >
>> > (Tried with both http://<servername>/Reports and
>> > http://<servername>/Reports$RS2005)
>> >
>> > As far as I know I'm an administrator.
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> First things first. Can you pull up Report Manager (this is the portal
>> >> that
>> >> ships with RS and is used to manage RS).
>> >>
>> >> http://yourservername/Reports/Pages/Folder.aspx
>> >>
>> >> localhost only works if you are on the machine hosting RS.
>> >>
>> >> Second, are you an adminstrator on that machine. All people in the
>> >> local
>> >> administrator group on the machine that has RS installed will
>> >> automatically
>> >> be in the RS administrators role.
>> >>
>> >> Deploying is the last thing you should try.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >>
>> >>
>> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
>> >> > As usual I'm learning by doing and I'm not sure I know what I'm
>> >> > doing.
>> >> >
>> >> > We have a legacy server running Windows Server 2003 and Sql Server
>> >> > 2000.
>> >> > We want to run a Reporting Services report off one of the tables in
>> >> > SQL
>> >> > Server 2000 so I was told to install SQL2005 Standard including RS
>> >> > on
>> >> > the
>> >> > server.
>> >> >
>> >> > IIS has been installed. When it came time to install SQL2005 I had
>> >> > a
>> >> > few
>> >> > moments of confusion. I am used to installing SQL2005 Express which
>> >> > seems
>> >> > to
>> >> > automatically install a named instance. In this case I manually
>> >> > selected
>> >> > a
>> >> > named instance (RS2005) because the wording of the screen seemed to
>> >> > imply
>> >> > that the default instance of SQL2000 would be upgraded (which
>> >> > wouldn't
>> >> > be
>> >> > a
>> >> > good idea.)
>> >> >
>> >> > So I installed SQL2005 with a named instance and the BI Studio. I
>> >> > copied
>> >> > over the report I wanted to deploy. Now my problem is that I cannot
>> >> > get
>> >> > it
>> >> > to deploy. In BI/VS the TargetServerURL is
>> >> > http://localhost/ReportServer$RS2005. All I get are connection
>> >> > errors:
>> >> > 'A
>> >> > connection could not be made to the report server
>> >> > http://localhost/ReportServer$RS2005. Additional information - The
>> >> > attempt
>> >> > to connect to the report server failed. Check your connection
>> >> > information,
>> >> > etc.'
>> >> >
>> >> > I have run the Reporting Services Configuration manager. To save
>> >> > time,
>> >> > here
>> >> > are the settings:
>> >> > Report Server Status
>> >> > Instance Name RS2005
>> >> > Instance ID MSSQL.2
>> >> > Running
>> >> >
>> >> > --
>> >> >
>> >> > Report Server Virtual Directory
>> >> > Name ReportServer$RS2005
>> >> > Website Default Website
>> >> >
>> >> > Report Manager Virtual Directory Settings
>> >> > Name Reports$RS2005
>> >> > Website Default Web Site
>> >> >
>> >> > Windows Service Identity
>> >> > Service Nmae ReportServer$RS2005
>> >> > Service Account LocalSystem
>> >> > Built-in Account Local System
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>|||I've already tried that and it doesn't work. Also tried deleting the empty
directories. (I might have created them when I was messing with the
Reporting Services Configuration Manager.)
"Bruce L-C [MVP]" wrote:
> You have somehow gotten a totally messed up install. You should not have
> four sites. Try this:
> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> > By 'websites' do you mean the report directories under Default Web Site?
> >
> > I have 4 report directories under the Default Web Site: ReportServer,
> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are empty.
> > The last two are full of what appears to be asp.net related files and
> > directories.
> >
> > (I admit that I was under the impression that RS2005 needed a 2005 db to
> > store its data.)
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> By what you posted it seems that you have it installed in the default
> >> website in which case this should be working. Open up IIS adminstrator
> >> (whatever it is called) and see if you have the websites.
> >>
> >> By the way, you did not need to install SQL 2005. RS 2005 can use SQL
> >> 2000
> >> for its object/metadata storage. You have to have a license for SQL
> >> Server
> >> 2005 but it does not need to be installed.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> > No. I've tried both on the server itself and from another machine.
> >> > Always
> >> > 'Page cannot be found.'
> >> >
> >> > (Tried with both http://<servername>/Reports and
> >> > http://<servername>/Reports$RS2005)
> >> >
> >> > As far as I know I'm an administrator.
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> First things first. Can you pull up Report Manager (this is the portal
> >> >> that
> >> >> ships with RS and is used to manage RS).
> >> >>
> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >>
> >> >> localhost only works if you are on the machine hosting RS.
> >> >>
> >> >> Second, are you an adminstrator on that machine. All people in the
> >> >> local
> >> >> administrator group on the machine that has RS installed will
> >> >> automatically
> >> >> be in the RS administrators role.
> >> >>
> >> >> Deploying is the last thing you should try.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >>
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> > As usual I'm learning by doing and I'm not sure I know what I'm
> >> >> > doing.
> >> >> >
> >> >> > We have a legacy server running Windows Server 2003 and Sql Server
> >> >> > 2000.
> >> >> > We want to run a Reporting Services report off one of the tables in
> >> >> > SQL
> >> >> > Server 2000 so I was told to install SQL2005 Standard including RS
> >> >> > on
> >> >> > the
> >> >> > server.
> >> >> >
> >> >> > IIS has been installed. When it came time to install SQL2005 I had
> >> >> > a
> >> >> > few
> >> >> > moments of confusion. I am used to installing SQL2005 Express which
> >> >> > seems
> >> >> > to
> >> >> > automatically install a named instance. In this case I manually
> >> >> > selected
> >> >> > a
> >> >> > named instance (RS2005) because the wording of the screen seemed to
> >> >> > imply
> >> >> > that the default instance of SQL2000 would be upgraded (which
> >> >> > wouldn't
> >> >> > be
> >> >> > a
> >> >> > good idea.)
> >> >> >
> >> >> > So I installed SQL2005 with a named instance and the BI Studio. I
> >> >> > copied
> >> >> > over the report I wanted to deploy. Now my problem is that I cannot
> >> >> > get
> >> >> > it
> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> > http://localhost/ReportServer$RS2005. All I get are connection
> >> >> > errors:
> >> >> > 'A
> >> >> > connection could not be made to the report server
> >> >> > http://localhost/ReportServer$RS2005. Additional information - The
> >> >> > attempt
> >> >> > to connect to the report server failed. Check your connection
> >> >> > information,
> >> >> > etc.'
> >> >> >
> >> >> > I have run the Reporting Services Configuration manager. To save
> >> >> > time,
> >> >> > here
> >> >> > are the settings:
> >> >> > Report Server Status
> >> >> > Instance Name RS2005
> >> >> > Instance ID MSSQL.2
> >> >> > Running
> >> >> >
> >> >> > --
> >> >> >
> >> >> > Report Server Virtual Directory
> >> >> > Name ReportServer$RS2005
> >> >> > Website Default Website
> >> >> >
> >> >> > Report Manager Virtual Directory Settings
> >> >> > Name Reports$RS2005
> >> >> > Website Default Web Site
> >> >> >
> >> >> > Windows Service Identity
> >> >> > Service Nmae ReportServer$RS2005
> >> >> > Service Account LocalSystem
> >> >> > Built-in Account Local System
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Maybe I should just uninstall everything and start over.
"Bruce L-C [MVP]" wrote:
> You have somehow gotten a totally messed up install. You should not have
> four sites. Try this:
> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> > By 'websites' do you mean the report directories under Default Web Site?
> >
> > I have 4 report directories under the Default Web Site: ReportServer,
> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are empty.
> > The last two are full of what appears to be asp.net related files and
> > directories.
> >
> > (I admit that I was under the impression that RS2005 needed a 2005 db to
> > store its data.)
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> By what you posted it seems that you have it installed in the default
> >> website in which case this should be working. Open up IIS adminstrator
> >> (whatever it is called) and see if you have the websites.
> >>
> >> By the way, you did not need to install SQL 2005. RS 2005 can use SQL
> >> 2000
> >> for its object/metadata storage. You have to have a license for SQL
> >> Server
> >> 2005 but it does not need to be installed.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> > No. I've tried both on the server itself and from another machine.
> >> > Always
> >> > 'Page cannot be found.'
> >> >
> >> > (Tried with both http://<servername>/Reports and
> >> > http://<servername>/Reports$RS2005)
> >> >
> >> > As far as I know I'm an administrator.
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> First things first. Can you pull up Report Manager (this is the portal
> >> >> that
> >> >> ships with RS and is used to manage RS).
> >> >>
> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >>
> >> >> localhost only works if you are on the machine hosting RS.
> >> >>
> >> >> Second, are you an adminstrator on that machine. All people in the
> >> >> local
> >> >> administrator group on the machine that has RS installed will
> >> >> automatically
> >> >> be in the RS administrators role.
> >> >>
> >> >> Deploying is the last thing you should try.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >>
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> > As usual I'm learning by doing and I'm not sure I know what I'm
> >> >> > doing.
> >> >> >
> >> >> > We have a legacy server running Windows Server 2003 and Sql Server
> >> >> > 2000.
> >> >> > We want to run a Reporting Services report off one of the tables in
> >> >> > SQL
> >> >> > Server 2000 so I was told to install SQL2005 Standard including RS
> >> >> > on
> >> >> > the
> >> >> > server.
> >> >> >
> >> >> > IIS has been installed. When it came time to install SQL2005 I had
> >> >> > a
> >> >> > few
> >> >> > moments of confusion. I am used to installing SQL2005 Express which
> >> >> > seems
> >> >> > to
> >> >> > automatically install a named instance. In this case I manually
> >> >> > selected
> >> >> > a
> >> >> > named instance (RS2005) because the wording of the screen seemed to
> >> >> > imply
> >> >> > that the default instance of SQL2000 would be upgraded (which
> >> >> > wouldn't
> >> >> > be
> >> >> > a
> >> >> > good idea.)
> >> >> >
> >> >> > So I installed SQL2005 with a named instance and the BI Studio. I
> >> >> > copied
> >> >> > over the report I wanted to deploy. Now my problem is that I cannot
> >> >> > get
> >> >> > it
> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> > http://localhost/ReportServer$RS2005. All I get are connection
> >> >> > errors:
> >> >> > 'A
> >> >> > connection could not be made to the report server
> >> >> > http://localhost/ReportServer$RS2005. Additional information - The
> >> >> > attempt
> >> >> > to connect to the report server failed. Check your connection
> >> >> > information,
> >> >> > etc.'
> >> >> >
> >> >> > I have run the Reporting Services Configuration manager. To save
> >> >> > time,
> >> >> > here
> >> >> > are the settings:
> >> >> > Report Server Status
> >> >> > Instance Name RS2005
> >> >> > Instance ID MSSQL.2
> >> >> > Running
> >> >> >
> >> >> > --
> >> >> >
> >> >> > Report Server Virtual Directory
> >> >> > Name ReportServer$RS2005
> >> >> > Website Default Website
> >> >> >
> >> >> > Report Manager Virtual Directory Settings
> >> >> > Name Reports$RS2005
> >> >> > Website Default Web Site
> >> >> >
> >> >> > Windows Service Identity
> >> >> > Service Nmae ReportServer$RS2005
> >> >> > Service Account LocalSystem
> >> >> > Built-in Account Local System
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||My suggestion is to do that and this time do not create SQL Server 2005
database. Just point it to an existing SQL Server 2000 db that you have.
There is no advantage to the added complexity of what you were doing.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
> Maybe I should just uninstall everything and start over.
> "Bruce L-C [MVP]" wrote:
>> You have somehow gotten a totally messed up install. You should not have
>> four sites. Try this:
>> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
>> > By 'websites' do you mean the report directories under Default Web
>> > Site?
>> >
>> > I have 4 report directories under the Default Web Site: ReportServer,
>> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are
>> > empty.
>> > The last two are full of what appears to be asp.net related files and
>> > directories.
>> >
>> > (I admit that I was under the impression that RS2005 needed a 2005 db
>> > to
>> > store its data.)
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> By what you posted it seems that you have it installed in the default
>> >> website in which case this should be working. Open up IIS adminstrator
>> >> (whatever it is called) and see if you have the websites.
>> >>
>> >> By the way, you did not need to install SQL 2005. RS 2005 can use SQL
>> >> 2000
>> >> for its object/metadata storage. You have to have a license for SQL
>> >> Server
>> >> 2005 but it does not need to be installed.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
>> >> > No. I've tried both on the server itself and from another machine.
>> >> > Always
>> >> > 'Page cannot be found.'
>> >> >
>> >> > (Tried with both http://<servername>/Reports and
>> >> > http://<servername>/Reports$RS2005)
>> >> >
>> >> > As far as I know I'm an administrator.
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> First things first. Can you pull up Report Manager (this is the
>> >> >> portal
>> >> >> that
>> >> >> ships with RS and is used to manage RS).
>> >> >>
>> >> >> http://yourservername/Reports/Pages/Folder.aspx
>> >> >>
>> >> >> localhost only works if you are on the machine hosting RS.
>> >> >>
>> >> >> Second, are you an adminstrator on that machine. All people in the
>> >> >> local
>> >> >> administrator group on the machine that has RS installed will
>> >> >> automatically
>> >> >> be in the RS administrators role.
>> >> >>
>> >> >> Deploying is the last thing you should try.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >>
>> >> >>
>> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
>> >> >> > As usual I'm learning by doing and I'm not sure I know what I'm
>> >> >> > doing.
>> >> >> >
>> >> >> > We have a legacy server running Windows Server 2003 and Sql
>> >> >> > Server
>> >> >> > 2000.
>> >> >> > We want to run a Reporting Services report off one of the tables
>> >> >> > in
>> >> >> > SQL
>> >> >> > Server 2000 so I was told to install SQL2005 Standard including
>> >> >> > RS
>> >> >> > on
>> >> >> > the
>> >> >> > server.
>> >> >> >
>> >> >> > IIS has been installed. When it came time to install SQL2005 I
>> >> >> > had
>> >> >> > a
>> >> >> > few
>> >> >> > moments of confusion. I am used to installing SQL2005 Express
>> >> >> > which
>> >> >> > seems
>> >> >> > to
>> >> >> > automatically install a named instance. In this case I manually
>> >> >> > selected
>> >> >> > a
>> >> >> > named instance (RS2005) because the wording of the screen seemed
>> >> >> > to
>> >> >> > imply
>> >> >> > that the default instance of SQL2000 would be upgraded (which
>> >> >> > wouldn't
>> >> >> > be
>> >> >> > a
>> >> >> > good idea.)
>> >> >> >
>> >> >> > So I installed SQL2005 with a named instance and the BI Studio.
>> >> >> > I
>> >> >> > copied
>> >> >> > over the report I wanted to deploy. Now my problem is that I
>> >> >> > cannot
>> >> >> > get
>> >> >> > it
>> >> >> > to deploy. In BI/VS the TargetServerURL is
>> >> >> > http://localhost/ReportServer$RS2005. All I get are connection
>> >> >> > errors:
>> >> >> > 'A
>> >> >> > connection could not be made to the report server
>> >> >> > http://localhost/ReportServer$RS2005. Additional information -
>> >> >> > The
>> >> >> > attempt
>> >> >> > to connect to the report server failed. Check your connection
>> >> >> > information,
>> >> >> > etc.'
>> >> >> >
>> >> >> > I have run the Reporting Services Configuration manager. To save
>> >> >> > time,
>> >> >> > here
>> >> >> > are the settings:
>> >> >> > Report Server Status
>> >> >> > Instance Name RS2005
>> >> >> > Instance ID MSSQL.2
>> >> >> > Running
>> >> >> >
>> >> >> > --
>> >> >> >
>> >> >> > Report Server Virtual Directory
>> >> >> > Name ReportServer$RS2005
>> >> >> > Website Default Website
>> >> >> >
>> >> >> > Report Manager Virtual Directory Settings
>> >> >> > Name Reports$RS2005
>> >> >> > Website Default Web Site
>> >> >> >
>> >> >> > Windows Service Identity
>> >> >> > Service Nmae ReportServer$RS2005
>> >> >> > Service Account LocalSystem
>> >> >> > Built-in Account Local System
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Ok I did that and now I've got new problems.
I reinstalled without creating a SQL2005 db. I went through the RS Config
manager using only defaults and the DBs appear to have been created
successfully under the SQL2000 server.
Now when I try to deploy the report using VS/BI, I get an error: A
connection could not be made to the report server
http://localhost/ReportServer. Additional Information: Client found response
content type of 'text/html; charset=utf-8', but expected 'text/xml'. The
request failed with the error message: '
The rest is too long to type here (looks like a big piece of HTML or XML)
but the system event log is full of error messages like this: The
application-specific permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
permission can be modified using the Component Services administrative tool.
Could this have something to do with the fact that I wrote the report on my
desktop and then copied the entire project over to the server?
"Bruce L-C [MVP]" wrote:
> My suggestion is to do that and this time do not create SQL Server 2005
> database. Just point it to an existing SQL Server 2000 db that you have.
> There is no advantage to the added complexity of what you were doing.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
> > Maybe I should just uninstall everything and start over.
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> You have somehow gotten a totally messed up install. You should not have
> >> four sites. Try this:
> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> >> > By 'websites' do you mean the report directories under Default Web
> >> > Site?
> >> >
> >> > I have 4 report directories under the Default Web Site: ReportServer,
> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are
> >> > empty.
> >> > The last two are full of what appears to be asp.net related files and
> >> > directories.
> >> >
> >> > (I admit that I was under the impression that RS2005 needed a 2005 db
> >> > to
> >> > store its data.)
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> By what you posted it seems that you have it installed in the default
> >> >> website in which case this should be working. Open up IIS adminstrator
> >> >> (whatever it is called) and see if you have the websites.
> >> >>
> >> >> By the way, you did not need to install SQL 2005. RS 2005 can use SQL
> >> >> 2000
> >> >> for its object/metadata storage. You have to have a license for SQL
> >> >> Server
> >> >> 2005 but it does not need to be installed.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> >> > No. I've tried both on the server itself and from another machine.
> >> >> > Always
> >> >> > 'Page cannot be found.'
> >> >> >
> >> >> > (Tried with both http://<servername>/Reports and
> >> >> > http://<servername>/Reports$RS2005)
> >> >> >
> >> >> > As far as I know I'm an administrator.
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> First things first. Can you pull up Report Manager (this is the
> >> >> >> portal
> >> >> >> that
> >> >> >> ships with RS and is used to manage RS).
> >> >> >>
> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >> >>
> >> >> >> localhost only works if you are on the machine hosting RS.
> >> >> >>
> >> >> >> Second, are you an adminstrator on that machine. All people in the
> >> >> >> local
> >> >> >> administrator group on the machine that has RS installed will
> >> >> >> automatically
> >> >> >> be in the RS administrators role.
> >> >> >>
> >> >> >> Deploying is the last thing you should try.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> >> > As usual I'm learning by doing and I'm not sure I know what I'm
> >> >> >> > doing.
> >> >> >> >
> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
> >> >> >> > Server
> >> >> >> > 2000.
> >> >> >> > We want to run a Reporting Services report off one of the tables
> >> >> >> > in
> >> >> >> > SQL
> >> >> >> > Server 2000 so I was told to install SQL2005 Standard including
> >> >> >> > RS
> >> >> >> > on
> >> >> >> > the
> >> >> >> > server.
> >> >> >> >
> >> >> >> > IIS has been installed. When it came time to install SQL2005 I
> >> >> >> > had
> >> >> >> > a
> >> >> >> > few
> >> >> >> > moments of confusion. I am used to installing SQL2005 Express
> >> >> >> > which
> >> >> >> > seems
> >> >> >> > to
> >> >> >> > automatically install a named instance. In this case I manually
> >> >> >> > selected
> >> >> >> > a
> >> >> >> > named instance (RS2005) because the wording of the screen seemed
> >> >> >> > to
> >> >> >> > imply
> >> >> >> > that the default instance of SQL2000 would be upgraded (which
> >> >> >> > wouldn't
> >> >> >> > be
> >> >> >> > a
> >> >> >> > good idea.)
> >> >> >> >
> >> >> >> > So I installed SQL2005 with a named instance and the BI Studio.
> >> >> >> > I
> >> >> >> > copied
> >> >> >> > over the report I wanted to deploy. Now my problem is that I
> >> >> >> > cannot
> >> >> >> > get
> >> >> >> > it
> >> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> >> > http://localhost/ReportServer$RS2005. All I get are connection
> >> >> >> > errors:
> >> >> >> > 'A
> >> >> >> > connection could not be made to the report server
> >> >> >> > http://localhost/ReportServer$RS2005. Additional information -
> >> >> >> > The
> >> >> >> > attempt
> >> >> >> > to connect to the report server failed. Check your connection
> >> >> >> > information,
> >> >> >> > etc.'
> >> >> >> >
> >> >> >> > I have run the Reporting Services Configuration manager. To save
> >> >> >> > time,
> >> >> >> > here
> >> >> >> > are the settings:
> >> >> >> > Report Server Status
> >> >> >> > Instance Name RS2005
> >> >> >> > Instance ID MSSQL.2
> >> >> >> > Running
> >> >> >> >
> >> >> >> > --
> >> >> >> >
> >> >> >> > Report Server Virtual Directory
> >> >> >> > Name ReportServer$RS2005
> >> >> >> > Website Default Website
> >> >> >> >
> >> >> >> > Report Manager Virtual Directory Settings
> >> >> >> > Name Reports$RS2005
> >> >> >> > Website Default Web Site
> >> >> >> >
> >> >> >> > Windows Service Identity
> >> >> >> > Service Nmae ReportServer$RS2005
> >> >> >> > Service Account LocalSystem
> >> >> >> > Built-in Account Local System
> >> >> >> >
> >> >> >> >
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Can you see Report Manager. That is the first thing you need to do.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
> Ok I did that and now I've got new problems.
> I reinstalled without creating a SQL2005 db. I went through the RS Config
> manager using only defaults and the DBs appear to have been created
> successfully under the SQL2000 server.
> Now when I try to deploy the report using VS/BI, I get an error: A
> connection could not be made to the report server
> http://localhost/ReportServer. Additional Information: Client found
> response
> content type of 'text/html; charset=utf-8', but expected 'text/xml'. The
> request failed with the error message: '
> The rest is too long to type here (looks like a big piece of HTML or XML)
> but the system event log is full of error messages like this: The
> application-specific permission settings do not grant Local Activation
> permission for the COM Server application with CLSID
> {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> permission can be modified using the Component Services administrative
> tool.
> Could this have something to do with the fact that I wrote the report on
> my
> desktop and then copied the entire project over to the server?
> "Bruce L-C [MVP]" wrote:
>> My suggestion is to do that and this time do not create SQL Server 2005
>> database. Just point it to an existing SQL Server 2000 db that you have.
>> There is no advantage to the added complexity of what you were doing.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
>> > Maybe I should just uninstall everything and start over.
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> You have somehow gotten a totally messed up install. You should not
>> >> have
>> >> four sites. Try this:
>> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
>> >> > By 'websites' do you mean the report directories under Default Web
>> >> > Site?
>> >> >
>> >> > I have 4 report directories under the Default Web Site:
>> >> > ReportServer,
>> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are
>> >> > empty.
>> >> > The last two are full of what appears to be asp.net related files
>> >> > and
>> >> > directories.
>> >> >
>> >> > (I admit that I was under the impression that RS2005 needed a 2005
>> >> > db
>> >> > to
>> >> > store its data.)
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> By what you posted it seems that you have it installed in the
>> >> >> default
>> >> >> website in which case this should be working. Open up IIS
>> >> >> adminstrator
>> >> >> (whatever it is called) and see if you have the websites.
>> >> >>
>> >> >> By the way, you did not need to install SQL 2005. RS 2005 can use
>> >> >> SQL
>> >> >> 2000
>> >> >> for its object/metadata storage. You have to have a license for SQL
>> >> >> Server
>> >> >> 2005 but it does not need to be installed.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
>> >> >> > No. I've tried both on the server itself and from another
>> >> >> > machine.
>> >> >> > Always
>> >> >> > 'Page cannot be found.'
>> >> >> >
>> >> >> > (Tried with both http://<servername>/Reports and
>> >> >> > http://<servername>/Reports$RS2005)
>> >> >> >
>> >> >> > As far as I know I'm an administrator.
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> First things first. Can you pull up Report Manager (this is the
>> >> >> >> portal
>> >> >> >> that
>> >> >> >> ships with RS and is used to manage RS).
>> >> >> >>
>> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
>> >> >> >>
>> >> >> >> localhost only works if you are on the machine hosting RS.
>> >> >> >>
>> >> >> >> Second, are you an adminstrator on that machine. All people in
>> >> >> >> the
>> >> >> >> local
>> >> >> >> administrator group on the machine that has RS installed will
>> >> >> >> automatically
>> >> >> >> be in the RS administrators role.
>> >> >> >>
>> >> >> >> Deploying is the last thing you should try.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
>> >> >> >> > As usual I'm learning by doing and I'm not sure I know what
>> >> >> >> > I'm
>> >> >> >> > doing.
>> >> >> >> >
>> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
>> >> >> >> > Server
>> >> >> >> > 2000.
>> >> >> >> > We want to run a Reporting Services report off one of the
>> >> >> >> > tables
>> >> >> >> > in
>> >> >> >> > SQL
>> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
>> >> >> >> > including
>> >> >> >> > RS
>> >> >> >> > on
>> >> >> >> > the
>> >> >> >> > server.
>> >> >> >> >
>> >> >> >> > IIS has been installed. When it came time to install SQL2005
>> >> >> >> > I
>> >> >> >> > had
>> >> >> >> > a
>> >> >> >> > few
>> >> >> >> > moments of confusion. I am used to installing SQL2005 Express
>> >> >> >> > which
>> >> >> >> > seems
>> >> >> >> > to
>> >> >> >> > automatically install a named instance. In this case I
>> >> >> >> > manually
>> >> >> >> > selected
>> >> >> >> > a
>> >> >> >> > named instance (RS2005) because the wording of the screen
>> >> >> >> > seemed
>> >> >> >> > to
>> >> >> >> > imply
>> >> >> >> > that the default instance of SQL2000 would be upgraded (which
>> >> >> >> > wouldn't
>> >> >> >> > be
>> >> >> >> > a
>> >> >> >> > good idea.)
>> >> >> >> >
>> >> >> >> > So I installed SQL2005 with a named instance and the BI
>> >> >> >> > Studio.
>> >> >> >> > I
>> >> >> >> > copied
>> >> >> >> > over the report I wanted to deploy. Now my problem is that I
>> >> >> >> > cannot
>> >> >> >> > get
>> >> >> >> > it
>> >> >> >> > to deploy. In BI/VS the TargetServerURL is
>> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
>> >> >> >> > connection
>> >> >> >> > errors:
>> >> >> >> > 'A
>> >> >> >> > connection could not be made to the report server
>> >> >> >> > http://localhost/ReportServer$RS2005. Additional
>> >> >> >> > information -
>> >> >> >> > The
>> >> >> >> > attempt
>> >> >> >> > to connect to the report server failed. Check your connection
>> >> >> >> > information,
>> >> >> >> > etc.'
>> >> >> >> >
>> >> >> >> > I have run the Reporting Services Configuration manager. To
>> >> >> >> > save
>> >> >> >> > time,
>> >> >> >> > here
>> >> >> >> > are the settings:
>> >> >> >> > Report Server Status
>> >> >> >> > Instance Name RS2005
>> >> >> >> > Instance ID MSSQL.2
>> >> >> >> > Running
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> >
>> >> >> >> > Report Server Virtual Directory
>> >> >> >> > Name ReportServer$RS2005
>> >> >> >> > Website Default Website
>> >> >> >> >
>> >> >> >> > Report Manager Virtual Directory Settings
>> >> >> >> > Name Reports$RS2005
>> >> >> >> > Website Default Web Site
>> >> >> >> >
>> >> >> >> > Windows Service Identity
>> >> >> >> > Service Nmae ReportServer$RS2005
>> >> >> >> > Service Account LocalSystem
>> >> >> >> > Built-in Account Local System
>> >> >> >> >
>> >> >> >> >
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Now what. Am I forgetting some option when running RS off SQL 2000? Got a
very different error.
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later.
----
A name was started with an invalid character. Error processing resource
'http://ussog-s-a000002/Reports/Pages/Folder.aspx'...
<%@. Page language="c#" Codebehind="Folder.aspx.cs" AutoEventWireup="false"
Inherits="Microsoft.ReportingServices.UI.Folde
"Bruce L-C [MVP]" wrote:
> Can you see Report Manager. That is the first thing you need to do.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
> > Ok I did that and now I've got new problems.
> >
> > I reinstalled without creating a SQL2005 db. I went through the RS Config
> > manager using only defaults and the DBs appear to have been created
> > successfully under the SQL2000 server.
> >
> > Now when I try to deploy the report using VS/BI, I get an error: A
> > connection could not be made to the report server
> > http://localhost/ReportServer. Additional Information: Client found
> > response
> > content type of 'text/html; charset=utf-8', but expected 'text/xml'. The
> > request failed with the error message: '
> >
> > The rest is too long to type here (looks like a big piece of HTML or XML)
> > but the system event log is full of error messages like this: The
> > application-specific permission settings do not grant Local Activation
> > permission for the COM Server application with CLSID
> > {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> > permission can be modified using the Component Services administrative
> > tool.
> >
> > Could this have something to do with the fact that I wrote the report on
> > my
> > desktop and then copied the entire project over to the server?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> My suggestion is to do that and this time do not create SQL Server 2005
> >> database. Just point it to an existing SQL Server 2000 db that you have.
> >> There is no advantage to the added complexity of what you were doing.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
> >> > Maybe I should just uninstall everything and start over.
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> You have somehow gotten a totally messed up install. You should not
> >> >> have
> >> >> four sites. Try this:
> >> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> >> >> > By 'websites' do you mean the report directories under Default Web
> >> >> > Site?
> >> >> >
> >> >> > I have 4 report directories under the Default Web Site:
> >> >> > ReportServer,
> >> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2 are
> >> >> > empty.
> >> >> > The last two are full of what appears to be asp.net related files
> >> >> > and
> >> >> > directories.
> >> >> >
> >> >> > (I admit that I was under the impression that RS2005 needed a 2005
> >> >> > db
> >> >> > to
> >> >> > store its data.)
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> By what you posted it seems that you have it installed in the
> >> >> >> default
> >> >> >> website in which case this should be working. Open up IIS
> >> >> >> adminstrator
> >> >> >> (whatever it is called) and see if you have the websites.
> >> >> >>
> >> >> >> By the way, you did not need to install SQL 2005. RS 2005 can use
> >> >> >> SQL
> >> >> >> 2000
> >> >> >> for its object/metadata storage. You have to have a license for SQL
> >> >> >> Server
> >> >> >> 2005 but it does not need to be installed.
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> >> >> > No. I've tried both on the server itself and from another
> >> >> >> > machine.
> >> >> >> > Always
> >> >> >> > 'Page cannot be found.'
> >> >> >> >
> >> >> >> > (Tried with both http://<servername>/Reports and
> >> >> >> > http://<servername>/Reports$RS2005)
> >> >> >> >
> >> >> >> > As far as I know I'm an administrator.
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> First things first. Can you pull up Report Manager (this is the
> >> >> >> >> portal
> >> >> >> >> that
> >> >> >> >> ships with RS and is used to manage RS).
> >> >> >> >>
> >> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >> >> >>
> >> >> >> >> localhost only works if you are on the machine hosting RS.
> >> >> >> >>
> >> >> >> >> Second, are you an adminstrator on that machine. All people in
> >> >> >> >> the
> >> >> >> >> local
> >> >> >> >> administrator group on the machine that has RS installed will
> >> >> >> >> automatically
> >> >> >> >> be in the RS administrators role.
> >> >> >> >>
> >> >> >> >> Deploying is the last thing you should try.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> message
> >> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> >> >> > As usual I'm learning by doing and I'm not sure I know what
> >> >> >> >> > I'm
> >> >> >> >> > doing.
> >> >> >> >> >
> >> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
> >> >> >> >> > Server
> >> >> >> >> > 2000.
> >> >> >> >> > We want to run a Reporting Services report off one of the
> >> >> >> >> > tables
> >> >> >> >> > in
> >> >> >> >> > SQL
> >> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
> >> >> >> >> > including
> >> >> >> >> > RS
> >> >> >> >> > on
> >> >> >> >> > the
> >> >> >> >> > server.
> >> >> >> >> >
> >> >> >> >> > IIS has been installed. When it came time to install SQL2005
> >> >> >> >> > I
> >> >> >> >> > had
> >> >> >> >> > a
> >> >> >> >> > few
> >> >> >> >> > moments of confusion. I am used to installing SQL2005 Express
> >> >> >> >> > which
> >> >> >> >> > seems
> >> >> >> >> > to
> >> >> >> >> > automatically install a named instance. In this case I
> >> >> >> >> > manually
> >> >> >> >> > selected
> >> >> >> >> > a
> >> >> >> >> > named instance (RS2005) because the wording of the screen
> >> >> >> >> > seemed
> >> >> >> >> > to
> >> >> >> >> > imply
> >> >> >> >> > that the default instance of SQL2000 would be upgraded (which
> >> >> >> >> > wouldn't
> >> >> >> >> > be
> >> >> >> >> > a
> >> >> >> >> > good idea.)
> >> >> >> >> >
> >> >> >> >> > So I installed SQL2005 with a named instance and the BI
> >> >> >> >> > Studio.
> >> >> >> >> > I
> >> >> >> >> > copied
> >> >> >> >> > over the report I wanted to deploy. Now my problem is that I
> >> >> >> >> > cannot
> >> >> >> >> > get
> >> >> >> >> > it
> >> >> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
> >> >> >> >> > connection
> >> >> >> >> > errors:
> >> >> >> >> > 'A
> >> >> >> >> > connection could not be made to the report server
> >> >> >> >> > http://localhost/ReportServer$RS2005. Additional
> >> >> >> >> > information -
> >> >> >> >> > The
> >> >> >> >> > attempt
> >> >> >> >> > to connect to the report server failed. Check your connection
> >> >> >> >> > information,
> >> >> >> >> > etc.'
> >> >> >> >> >
> >> >> >> >> > I have run the Reporting Services Configuration manager. To
> >> >> >> >> > save
> >> >> >> >> > time,
> >> >> >> >> > here
> >> >> >> >> > are the settings:
> >> >> >> >> > Report Server Status
> >> >> >> >> > Instance Name RS2005
> >> >> >> >> > Instance ID MSSQL.2
> >> >> >> >> > Running
> >> >> >> >> >
> >> >> >> >> > --
> >> >> >> >> >
> >> >> >> >> > Report Server Virtual Directory
> >> >> >> >> > Name ReportServer$RS2005
> >> >> >> >> > Website Default Website
> >> >> >> >> >
> >> >> >> >> > Report Manager Virtual Directory Settings
> >> >> >> >> > Name Reports$RS2005
> >> >> >> >> > Website Default Web Site
> >> >> >> >> >
> >> >> >> >> > Windows Service Identity
> >> >> >> >> > Service Nmae ReportServer$RS2005
> >> >> >> >> > Service Account LocalSystem
> >> >> >> >> > Built-in Account Local System
> >> >> >> >> >
> >> >> >> >> >
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||If the RS configuration tool shows everything good it should not be a
problem.
I have never seen this error.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:23A2FD03-F2FF-4D94-A851-C2C6921C0A4A@.microsoft.com...
> Now what. Am I forgetting some option when running RS off SQL 2000? Got
> a
> very different error.
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> ----
> A name was started with an invalid character. Error processing resource
> 'http://ussog-s-a000002/Reports/Pages/Folder.aspx'...
> <%@. Page language="c#" Codebehind="Folder.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.Folde
>
> "Bruce L-C [MVP]" wrote:
>> Can you see Report Manager. That is the first thing you need to do.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
>> > Ok I did that and now I've got new problems.
>> >
>> > I reinstalled without creating a SQL2005 db. I went through the RS
>> > Config
>> > manager using only defaults and the DBs appear to have been created
>> > successfully under the SQL2000 server.
>> >
>> > Now when I try to deploy the report using VS/BI, I get an error: A
>> > connection could not be made to the report server
>> > http://localhost/ReportServer. Additional Information: Client found
>> > response
>> > content type of 'text/html; charset=utf-8', but expected 'text/xml'.
>> > The
>> > request failed with the error message: '
>> >
>> > The rest is too long to type here (looks like a big piece of HTML or
>> > XML)
>> > but the system event log is full of error messages like this: The
>> > application-specific permission settings do not grant Local Activation
>> > permission for the COM Server application with CLSID
>> > {BA126AD1-2166-11D1-B1D0-00805FC1270E}
>> > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
>> > permission can be modified using the Component Services administrative
>> > tool.
>> >
>> > Could this have something to do with the fact that I wrote the report
>> > on
>> > my
>> > desktop and then copied the entire project over to the server?
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> My suggestion is to do that and this time do not create SQL Server
>> >> 2005
>> >> database. Just point it to an existing SQL Server 2000 db that you
>> >> have.
>> >> There is no advantage to the added complexity of what you were doing.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> >> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
>> >> > Maybe I should just uninstall everything and start over.
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> You have somehow gotten a totally messed up install. You should not
>> >> >> have
>> >> >> four sites. Try this:
>> >> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
>> >> >> > By 'websites' do you mean the report directories under Default
>> >> >> > Web
>> >> >> > Site?
>> >> >> >
>> >> >> > I have 4 report directories under the Default Web Site:
>> >> >> > ReportServer,
>> >> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2
>> >> >> > are
>> >> >> > empty.
>> >> >> > The last two are full of what appears to be asp.net related files
>> >> >> > and
>> >> >> > directories.
>> >> >> >
>> >> >> > (I admit that I was under the impression that RS2005 needed a
>> >> >> > 2005
>> >> >> > db
>> >> >> > to
>> >> >> > store its data.)
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> By what you posted it seems that you have it installed in the
>> >> >> >> default
>> >> >> >> website in which case this should be working. Open up IIS
>> >> >> >> adminstrator
>> >> >> >> (whatever it is called) and see if you have the websites.
>> >> >> >>
>> >> >> >> By the way, you did not need to install SQL 2005. RS 2005 can
>> >> >> >> use
>> >> >> >> SQL
>> >> >> >> 2000
>> >> >> >> for its object/metadata storage. You have to have a license for
>> >> >> >> SQL
>> >> >> >> Server
>> >> >> >> 2005 but it does not need to be installed.
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
>> >> >> >> > No. I've tried both on the server itself and from another
>> >> >> >> > machine.
>> >> >> >> > Always
>> >> >> >> > 'Page cannot be found.'
>> >> >> >> >
>> >> >> >> > (Tried with both http://<servername>/Reports and
>> >> >> >> > http://<servername>/Reports$RS2005)
>> >> >> >> >
>> >> >> >> > As far as I know I'm an administrator.
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> First things first. Can you pull up Report Manager (this is
>> >> >> >> >> the
>> >> >> >> >> portal
>> >> >> >> >> that
>> >> >> >> >> ships with RS and is used to manage RS).
>> >> >> >> >>
>> >> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
>> >> >> >> >>
>> >> >> >> >> localhost only works if you are on the machine hosting RS.
>> >> >> >> >>
>> >> >> >> >> Second, are you an adminstrator on that machine. All people
>> >> >> >> >> in
>> >> >> >> >> the
>> >> >> >> >> local
>> >> >> >> >> administrator group on the machine that has RS installed will
>> >> >> >> >> automatically
>> >> >> >> >> be in the RS administrators role.
>> >> >> >> >>
>> >> >> >> >> Deploying is the last thing you should try.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> >> >> message
>> >> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
>> >> >> >> >> > As usual I'm learning by doing and I'm not sure I know what
>> >> >> >> >> > I'm
>> >> >> >> >> > doing.
>> >> >> >> >> >
>> >> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
>> >> >> >> >> > Server
>> >> >> >> >> > 2000.
>> >> >> >> >> > We want to run a Reporting Services report off one of the
>> >> >> >> >> > tables
>> >> >> >> >> > in
>> >> >> >> >> > SQL
>> >> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
>> >> >> >> >> > including
>> >> >> >> >> > RS
>> >> >> >> >> > on
>> >> >> >> >> > the
>> >> >> >> >> > server.
>> >> >> >> >> >
>> >> >> >> >> > IIS has been installed. When it came time to install
>> >> >> >> >> > SQL2005
>> >> >> >> >> > I
>> >> >> >> >> > had
>> >> >> >> >> > a
>> >> >> >> >> > few
>> >> >> >> >> > moments of confusion. I am used to installing SQL2005
>> >> >> >> >> > Express
>> >> >> >> >> > which
>> >> >> >> >> > seems
>> >> >> >> >> > to
>> >> >> >> >> > automatically install a named instance. In this case I
>> >> >> >> >> > manually
>> >> >> >> >> > selected
>> >> >> >> >> > a
>> >> >> >> >> > named instance (RS2005) because the wording of the screen
>> >> >> >> >> > seemed
>> >> >> >> >> > to
>> >> >> >> >> > imply
>> >> >> >> >> > that the default instance of SQL2000 would be upgraded
>> >> >> >> >> > (which
>> >> >> >> >> > wouldn't
>> >> >> >> >> > be
>> >> >> >> >> > a
>> >> >> >> >> > good idea.)
>> >> >> >> >> >
>> >> >> >> >> > So I installed SQL2005 with a named instance and the BI
>> >> >> >> >> > Studio.
>> >> >> >> >> > I
>> >> >> >> >> > copied
>> >> >> >> >> > over the report I wanted to deploy. Now my problem is that
>> >> >> >> >> > I
>> >> >> >> >> > cannot
>> >> >> >> >> > get
>> >> >> >> >> > it
>> >> >> >> >> > to deploy. In BI/VS the TargetServerURL is
>> >> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
>> >> >> >> >> > connection
>> >> >> >> >> > errors:
>> >> >> >> >> > 'A
>> >> >> >> >> > connection could not be made to the report server
>> >> >> >> >> > http://localhost/ReportServer$RS2005. Additional
>> >> >> >> >> > information -
>> >> >> >> >> > The
>> >> >> >> >> > attempt
>> >> >> >> >> > to connect to the report server failed. Check your
>> >> >> >> >> > connection
>> >> >> >> >> > information,
>> >> >> >> >> > etc.'
>> >> >> >> >> >
>> >> >> >> >> > I have run the Reporting Services Configuration manager.
>> >> >> >> >> > To
>> >> >> >> >> > save
>> >> >> >> >> > time,
>> >> >> >> >> > here
>> >> >> >> >> > are the settings:
>> >> >> >> >> > Report Server Status
>> >> >> >> >> > Instance Name RS2005
>> >> >> >> >> > Instance ID MSSQL.2
>> >> >> >> >> > Running
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> >
>> >> >> >> >> > Report Server Virtual Directory
>> >> >> >> >> > Name ReportServer$RS2005
>> >> >> >> >> > Website Default Website
>> >> >> >> >> >
>> >> >> >> >> > Report Manager Virtual Directory Settings
>> >> >> >> >> > Name Reports$RS2005
>> >> >> >> >> > Website Default Web Site
>> >> >> >> >> >
>> >> >> >> >> > Windows Service Identity
>> >> >> >> >> > Service Nmae ReportServer$RS2005
>> >> >> >> >> > Service Account LocalSystem
>> >> >> >> >> > Built-in Account Local System
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||If this stumps an MVP, then I'm really in trouble!
It's quitting time here (Eastern time). Let's continue this tomorrow.
"Bruce L-C [MVP]" wrote:
> If the RS configuration tool shows everything good it should not be a
> problem.
> I have never seen this error.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:23A2FD03-F2FF-4D94-A851-C2C6921C0A4A@.microsoft.com...
> > Now what. Am I forgetting some option when running RS off SQL 2000? Got
> > a
> > very different error.
> >
> > The XML page cannot be displayed
> > Cannot view XML input using XSL style sheet. Please correct the error and
> > then click the Refresh button, or try again later.
> >
> >
> > ----
> >
> > A name was started with an invalid character. Error processing resource
> > 'http://ussog-s-a000002/Reports/Pages/Folder.aspx'...
> >
> > <%@. Page language="c#" Codebehind="Folder.aspx.cs" AutoEventWireup="false"
> > Inherits="Microsoft.ReportingServices.UI.Folde
> >
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Can you see Report Manager. That is the first thing you need to do.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
> >> > Ok I did that and now I've got new problems.
> >> >
> >> > I reinstalled without creating a SQL2005 db. I went through the RS
> >> > Config
> >> > manager using only defaults and the DBs appear to have been created
> >> > successfully under the SQL2000 server.
> >> >
> >> > Now when I try to deploy the report using VS/BI, I get an error: A
> >> > connection could not be made to the report server
> >> > http://localhost/ReportServer. Additional Information: Client found
> >> > response
> >> > content type of 'text/html; charset=utf-8', but expected 'text/xml'.
> >> > The
> >> > request failed with the error message: '
> >> >
> >> > The rest is too long to type here (looks like a big piece of HTML or
> >> > XML)
> >> > but the system event log is full of error messages like this: The
> >> > application-specific permission settings do not grant Local Activation
> >> > permission for the COM Server application with CLSID
> >> > {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> >> > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> >> > permission can be modified using the Component Services administrative
> >> > tool.
> >> >
> >> > Could this have something to do with the fact that I wrote the report
> >> > on
> >> > my
> >> > desktop and then copied the entire project over to the server?
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> My suggestion is to do that and this time do not create SQL Server
> >> >> 2005
> >> >> database. Just point it to an existing SQL Server 2000 db that you
> >> >> have.
> >> >> There is no advantage to the added complexity of what you were doing.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
> >> >> > Maybe I should just uninstall everything and start over.
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> You have somehow gotten a totally messed up install. You should not
> >> >> >> have
> >> >> >> four sites. Try this:
> >> >> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> >> >> >> > By 'websites' do you mean the report directories under Default
> >> >> >> > Web
> >> >> >> > Site?
> >> >> >> >
> >> >> >> > I have 4 report directories under the Default Web Site:
> >> >> >> > ReportServer,
> >> >> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2
> >> >> >> > are
> >> >> >> > empty.
> >> >> >> > The last two are full of what appears to be asp.net related files
> >> >> >> > and
> >> >> >> > directories.
> >> >> >> >
> >> >> >> > (I admit that I was under the impression that RS2005 needed a
> >> >> >> > 2005
> >> >> >> > db
> >> >> >> > to
> >> >> >> > store its data.)
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> By what you posted it seems that you have it installed in the
> >> >> >> >> default
> >> >> >> >> website in which case this should be working. Open up IIS
> >> >> >> >> adminstrator
> >> >> >> >> (whatever it is called) and see if you have the websites.
> >> >> >> >>
> >> >> >> >> By the way, you did not need to install SQL 2005. RS 2005 can
> >> >> >> >> use
> >> >> >> >> SQL
> >> >> >> >> 2000
> >> >> >> >> for its object/metadata storage. You have to have a license for
> >> >> >> >> SQL
> >> >> >> >> Server
> >> >> >> >> 2005 but it does not need to be installed.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> message
> >> >> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> >> >> >> > No. I've tried both on the server itself and from another
> >> >> >> >> > machine.
> >> >> >> >> > Always
> >> >> >> >> > 'Page cannot be found.'
> >> >> >> >> >
> >> >> >> >> > (Tried with both http://<servername>/Reports and
> >> >> >> >> > http://<servername>/Reports$RS2005)
> >> >> >> >> >
> >> >> >> >> > As far as I know I'm an administrator.
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> First things first. Can you pull up Report Manager (this is
> >> >> >> >> >> the
> >> >> >> >> >> portal
> >> >> >> >> >> that
> >> >> >> >> >> ships with RS and is used to manage RS).
> >> >> >> >> >>
> >> >> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >> >> >> >>
> >> >> >> >> >> localhost only works if you are on the machine hosting RS.
> >> >> >> >> >>
> >> >> >> >> >> Second, are you an adminstrator on that machine. All people
> >> >> >> >> >> in
> >> >> >> >> >> the
> >> >> >> >> >> local
> >> >> >> >> >> administrator group on the machine that has RS installed will
> >> >> >> >> >> automatically
> >> >> >> >> >> be in the RS administrators role.
> >> >> >> >> >>
> >> >> >> >> >> Deploying is the last thing you should try.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> >> message
> >> >> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> >> >> >> > As usual I'm learning by doing and I'm not sure I know what
> >> >> >> >> >> > I'm
> >> >> >> >> >> > doing.
> >> >> >> >> >> >
> >> >> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
> >> >> >> >> >> > Server
> >> >> >> >> >> > 2000.
> >> >> >> >> >> > We want to run a Reporting Services report off one of the
> >> >> >> >> >> > tables
> >> >> >> >> >> > in
> >> >> >> >> >> > SQL
> >> >> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
> >> >> >> >> >> > including
> >> >> >> >> >> > RS
> >> >> >> >> >> > on
> >> >> >> >> >> > the
> >> >> >> >> >> > server.
> >> >> >> >> >> >
> >> >> >> >> >> > IIS has been installed. When it came time to install
> >> >> >> >> >> > SQL2005
> >> >> >> >> >> > I
> >> >> >> >> >> > had
> >> >> >> >> >> > a
> >> >> >> >> >> > few
> >> >> >> >> >> > moments of confusion. I am used to installing SQL2005
> >> >> >> >> >> > Express
> >> >> >> >> >> > which
> >> >> >> >> >> > seems
> >> >> >> >> >> > to
> >> >> >> >> >> > automatically install a named instance. In this case I
> >> >> >> >> >> > manually
> >> >> >> >> >> > selected
> >> >> >> >> >> > a
> >> >> >> >> >> > named instance (RS2005) because the wording of the screen
> >> >> >> >> >> > seemed
> >> >> >> >> >> > to
> >> >> >> >> >> > imply
> >> >> >> >> >> > that the default instance of SQL2000 would be upgraded
> >> >> >> >> >> > (which
> >> >> >> >> >> > wouldn't
> >> >> >> >> >> > be
> >> >> >> >> >> > a
> >> >> >> >> >> > good idea.)
> >> >> >> >> >> >
> >> >> >> >> >> > So I installed SQL2005 with a named instance and the BI
> >> >> >> >> >> > Studio.
> >> >> >> >> >> > I
> >> >> >> >> >> > copied
> >> >> >> >> >> > over the report I wanted to deploy. Now my problem is that
> >> >> >> >> >> > I
> >> >> >> >> >> > cannot
> >> >> >> >> >> > get
> >> >> >> >> >> > it
> >> >> >> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
> >> >> >> >> >> > connection
> >> >> >> >> >> > errors:
> >> >> >> >> >> > 'A
> >> >> >> >> >> > connection could not be made to the report server
> >> >> >> >> >> > http://localhost/ReportServer$RS2005. Additional
> >> >> >> >> >> > information -
> >> >> >> >> >> > The
> >> >> >> >> >> > attempt
> >> >> >> >> >> > to connect to the report server failed. Check your
> >> >> >> >> >> > connection
> >> >> >> >> >> > information,
> >> >> >> >> >> > etc.'
> >> >> >> >> >> >
> >> >> >> >> >> > I have run the Reporting Services Configuration manager.
> >> >> >> >> >> > To
> >> >> >> >> >> > save
> >> >> >> >> >> > time,
> >> >> >> >> >> > here
> >> >> >> >> >> > are the settings:
> >> >> >> >> >> > Report Server Status
> >> >> >> >> >> > Instance Name RS2005
> >> >> >> >> >> > Instance ID MSSQL.2
> >> >> >> >> >> > Running
> >> >> >> >> >> >
> >> >> >> >> >> > --
> >> >> >> >> >> >
> >> >> >> >> >> > Report Server Virtual Directory
> >> >> >> >> >> > Name ReportServer$RS2005
> >> >> >> >> >> > Website Default Website
> >> >> >> >> >> >
> >> >> >> >> >> > Report Manager Virtual Directory Settings
> >> >> >> >> >> > Name Reports$RS2005
> >> >> >> >> >> > Website Default Web Site
> >> >> >> >> >> >
> >> >> >> >> >> > Windows Service Identity
> >> >> >> >> >> > Service Nmae ReportServer$RS2005
> >> >> >> >> >> > Service Account LocalSystem
> >> >> >> >> >> > Built-in Account Local System
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>|||I probably forgot to mention: This server is part of a very large corporate
network, all regulated (so far as I know) using Active Directory. I have no
hands-on experience with Active Directory. Could this complicate the RS
configuration?
"Bruce L-C [MVP]" wrote:
> If the RS configuration tool shows everything good it should not be a
> problem.
> I have never seen this error.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:23A2FD03-F2FF-4D94-A851-C2C6921C0A4A@.microsoft.com...
> > Now what. Am I forgetting some option when running RS off SQL 2000? Got
> > a
> > very different error.
> >
> > The XML page cannot be displayed
> > Cannot view XML input using XSL style sheet. Please correct the error and
> > then click the Refresh button, or try again later.
> >
> >
> > ----
> >
> > A name was started with an invalid character. Error processing resource
> > 'http://ussog-s-a000002/Reports/Pages/Folder.aspx'...
> >
> > <%@. Page language="c#" Codebehind="Folder.aspx.cs" AutoEventWireup="false"
> > Inherits="Microsoft.ReportingServices.UI.Folde
> >
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Can you see Report Manager. That is the first thing you need to do.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
> >> > Ok I did that and now I've got new problems.
> >> >
> >> > I reinstalled without creating a SQL2005 db. I went through the RS
> >> > Config
> >> > manager using only defaults and the DBs appear to have been created
> >> > successfully under the SQL2000 server.
> >> >
> >> > Now when I try to deploy the report using VS/BI, I get an error: A
> >> > connection could not be made to the report server
> >> > http://localhost/ReportServer. Additional Information: Client found
> >> > response
> >> > content type of 'text/html; charset=utf-8', but expected 'text/xml'.
> >> > The
> >> > request failed with the error message: '
> >> >
> >> > The rest is too long to type here (looks like a big piece of HTML or
> >> > XML)
> >> > but the system event log is full of error messages like this: The
> >> > application-specific permission settings do not grant Local Activation
> >> > permission for the COM Server application with CLSID
> >> > {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> >> > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> >> > permission can be modified using the Component Services administrative
> >> > tool.
> >> >
> >> > Could this have something to do with the fact that I wrote the report
> >> > on
> >> > my
> >> > desktop and then copied the entire project over to the server?
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> My suggestion is to do that and this time do not create SQL Server
> >> >> 2005
> >> >> database. Just point it to an existing SQL Server 2000 db that you
> >> >> have.
> >> >> There is no advantage to the added complexity of what you were doing.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
> >> >> > Maybe I should just uninstall everything and start over.
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> You have somehow gotten a totally messed up install. You should not
> >> >> >> have
> >> >> >> four sites. Try this:
> >> >> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> >> >> >> > By 'websites' do you mean the report directories under Default
> >> >> >> > Web
> >> >> >> > Site?
> >> >> >> >
> >> >> >> > I have 4 report directories under the Default Web Site:
> >> >> >> > ReportServer,
> >> >> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2
> >> >> >> > are
> >> >> >> > empty.
> >> >> >> > The last two are full of what appears to be asp.net related files
> >> >> >> > and
> >> >> >> > directories.
> >> >> >> >
> >> >> >> > (I admit that I was under the impression that RS2005 needed a
> >> >> >> > 2005
> >> >> >> > db
> >> >> >> > to
> >> >> >> > store its data.)
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> By what you posted it seems that you have it installed in the
> >> >> >> >> default
> >> >> >> >> website in which case this should be working. Open up IIS
> >> >> >> >> adminstrator
> >> >> >> >> (whatever it is called) and see if you have the websites.
> >> >> >> >>
> >> >> >> >> By the way, you did not need to install SQL 2005. RS 2005 can
> >> >> >> >> use
> >> >> >> >> SQL
> >> >> >> >> 2000
> >> >> >> >> for its object/metadata storage. You have to have a license for
> >> >> >> >> SQL
> >> >> >> >> Server
> >> >> >> >> 2005 but it does not need to be installed.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> message
> >> >> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> >> >> >> > No. I've tried both on the server itself and from another
> >> >> >> >> > machine.
> >> >> >> >> > Always
> >> >> >> >> > 'Page cannot be found.'
> >> >> >> >> >
> >> >> >> >> > (Tried with both http://<servername>/Reports and
> >> >> >> >> > http://<servername>/Reports$RS2005)
> >> >> >> >> >
> >> >> >> >> > As far as I know I'm an administrator.
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> First things first. Can you pull up Report Manager (this is
> >> >> >> >> >> the
> >> >> >> >> >> portal
> >> >> >> >> >> that
> >> >> >> >> >> ships with RS and is used to manage RS).
> >> >> >> >> >>
> >> >> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >> >> >> >>
> >> >> >> >> >> localhost only works if you are on the machine hosting RS.
> >> >> >> >> >>
> >> >> >> >> >> Second, are you an adminstrator on that machine. All people
> >> >> >> >> >> in
> >> >> >> >> >> the
> >> >> >> >> >> local
> >> >> >> >> >> administrator group on the machine that has RS installed will
> >> >> >> >> >> automatically
> >> >> >> >> >> be in the RS administrators role.
> >> >> >> >> >>
> >> >> >> >> >> Deploying is the last thing you should try.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> >> message
> >> >> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> >> >> >> > As usual I'm learning by doing and I'm not sure I know what
> >> >> >> >> >> > I'm
> >> >> >> >> >> > doing.
> >> >> >> >> >> >
> >> >> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
> >> >> >> >> >> > Server
> >> >> >> >> >> > 2000.
> >> >> >> >> >> > We want to run a Reporting Services report off one of the
> >> >> >> >> >> > tables
> >> >> >> >> >> > in
> >> >> >> >> >> > SQL
> >> >> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
> >> >> >> >> >> > including
> >> >> >> >> >> > RS
> >> >> >> >> >> > on
> >> >> >> >> >> > the
> >> >> >> >> >> > server.
> >> >> >> >> >> >
> >> >> >> >> >> > IIS has been installed. When it came time to install
> >> >> >> >> >> > SQL2005
> >> >> >> >> >> > I
> >> >> >> >> >> > had
> >> >> >> >> >> > a
> >> >> >> >> >> > few
> >> >> >> >> >> > moments of confusion. I am used to installing SQL2005
> >> >> >> >> >> > Express
> >> >> >> >> >> > which
> >> >> >> >> >> > seems
> >> >> >> >> >> > to
> >> >> >> >> >> > automatically install a named instance. In this case I
> >> >> >> >> >> > manually
> >> >> >> >> >> > selected
> >> >> >> >> >> > a
> >> >> >> >> >> > named instance (RS2005) because the wording of the screen
> >> >> >> >> >> > seemed
> >> >> >> >> >> > to
> >> >> >> >> >> > imply
> >> >> >> >> >> > that the default instance of SQL2000 would be upgraded
> >> >> >> >> >> > (which
> >> >> >> >> >> > wouldn't
> >> >> >> >> >> > be
> >> >> >> >> >> > a
> >> >> >> >> >> > good idea.)
> >> >> >> >> >> >
> >> >> >> >> >> > So I installed SQL2005 with a named instance and the BI
> >> >> >> >> >> > Studio.
> >> >> >> >> >> > I
> >> >> >> >> >> > copied
> >> >> >> >> >> > over the report I wanted to deploy. Now my problem is that
> >> >> >> >> >> > I
> >> >> >> >> >> > cannot
> >> >> >> >> >> > get
> >> >> >> >> >> > it
> >> >> >> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
> >> >> >> >> >> > connection
> >> >> >> >> >> > errors:
> >> >> >> >> >> > 'A
> >> >> >> >> >> > connection could not be made to the report server
> >> >> >> >> >> > http://localhost/ReportServer$RS2005. Additional
> >> >> >> >> >> > information -
> >> >> >> >> >> > The
> >> >> >> >> >> > attempt
> >> >> >> >> >> > to connect to the report server failed. Check your
> >> >> >> >> >> > connection
> >> >> >> >> >> > information,
> >> >> >> >> >> > etc.'
> >> >> >> >> >> >
> >> >> >> >> >> > I have run the Reporting Services Configuration manager.
> >> >> >> >> >> > To
> >> >> >> >> >> > save
> >> >> >> >> >> > time,
> >> >> >> >> >> > here
> >> >> >> >> >> > are the settings:
> >> >> >> >> >> > Report Server Status
> >> >> >> >> >> > Instance Name RS2005
> >> >> >> >> >> > Instance ID MSSQL.2
> >> >> >> >> >> > Running
> >> >> >> >> >> >
> >> >> >> >> >> > --
> >> >> >> >> >> >
> >> >> >> >> >> > Report Server Virtual Directory
> >> >> >> >> >> > Name ReportServer$RS2005
> >> >> >> >> >> > Website Default Website
> >> >> >> >> >> >
> >> >> >> >> >> > Report Manager Virtual Directory Settings
> >> >> >> >> >> > Name Reports$RS2005
> >> >> >> >> >> > Website Default Web Site
> >> >> >> >> >> >
> >> >> >> >> >> > Windows Service Identity
> >> >> >> >> >> > Service Nmae ReportServer$RS2005
> >> >> >> >> >> > Service Account LocalSystem
> >> >> >> >> >> > Built-in Account Local System
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>|||Stop the presses!!! I have solved the problem of the missing Folder page and
the report is now successsfully deployed!!!!
The problem is not in RS. The problem is that the Dot Net Framework was
installed on the Windows 2003 server before the IIS component was installed.
The solution was simple:
"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i"
Looks like I have a few brain cells left.
"Bruce L-C [MVP]" wrote:
> If the RS configuration tool shows everything good it should not be a
> problem.
> I have never seen this error.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> news:23A2FD03-F2FF-4D94-A851-C2C6921C0A4A@.microsoft.com...
> > Now what. Am I forgetting some option when running RS off SQL 2000? Got
> > a
> > very different error.
> >
> > The XML page cannot be displayed
> > Cannot view XML input using XSL style sheet. Please correct the error and
> > then click the Refresh button, or try again later.
> >
> >
> > ----
> >
> > A name was started with an invalid character. Error processing resource
> > 'http://ussog-s-a000002/Reports/Pages/Folder.aspx'...
> >
> > <%@. Page language="c#" Codebehind="Folder.aspx.cs" AutoEventWireup="false"
> > Inherits="Microsoft.ReportingServices.UI.Folde
> >
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Can you see Report Manager. That is the first thing you need to do.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
> >> > Ok I did that and now I've got new problems.
> >> >
> >> > I reinstalled without creating a SQL2005 db. I went through the RS
> >> > Config
> >> > manager using only defaults and the DBs appear to have been created
> >> > successfully under the SQL2000 server.
> >> >
> >> > Now when I try to deploy the report using VS/BI, I get an error: A
> >> > connection could not be made to the report server
> >> > http://localhost/ReportServer. Additional Information: Client found
> >> > response
> >> > content type of 'text/html; charset=utf-8', but expected 'text/xml'.
> >> > The
> >> > request failed with the error message: '
> >> >
> >> > The rest is too long to type here (looks like a big piece of HTML or
> >> > XML)
> >> > but the system event log is full of error messages like this: The
> >> > application-specific permission settings do not grant Local Activation
> >> > permission for the COM Server application with CLSID
> >> > {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> >> > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> >> > permission can be modified using the Component Services administrative
> >> > tool.
> >> >
> >> > Could this have something to do with the fact that I wrote the report
> >> > on
> >> > my
> >> > desktop and then copied the entire project over to the server?
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> My suggestion is to do that and this time do not create SQL Server
> >> >> 2005
> >> >> database. Just point it to an existing SQL Server 2000 db that you
> >> >> have.
> >> >> There is no advantage to the added complexity of what you were doing.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
> >> >> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
> >> >> > Maybe I should just uninstall everything and start over.
> >> >> >
> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >
> >> >> >> You have somehow gotten a totally messed up install. You should not
> >> >> >> have
> >> >> >> four sites. Try this:
> >> >> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Bruce Loehle-Conger
> >> >> >> MVP SQL Server Reporting Services
> >> >> >>
> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
> >> >> >> > By 'websites' do you mean the report directories under Default
> >> >> >> > Web
> >> >> >> > Site?
> >> >> >> >
> >> >> >> > I have 4 report directories under the Default Web Site:
> >> >> >> > ReportServer,
> >> >> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2
> >> >> >> > are
> >> >> >> > empty.
> >> >> >> > The last two are full of what appears to be asp.net related files
> >> >> >> > and
> >> >> >> > directories.
> >> >> >> >
> >> >> >> > (I admit that I was under the impression that RS2005 needed a
> >> >> >> > 2005
> >> >> >> > db
> >> >> >> > to
> >> >> >> > store its data.)
> >> >> >> >
> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >
> >> >> >> >> By what you posted it seems that you have it installed in the
> >> >> >> >> default
> >> >> >> >> website in which case this should be working. Open up IIS
> >> >> >> >> adminstrator
> >> >> >> >> (whatever it is called) and see if you have the websites.
> >> >> >> >>
> >> >> >> >> By the way, you did not need to install SQL 2005. RS 2005 can
> >> >> >> >> use
> >> >> >> >> SQL
> >> >> >> >> 2000
> >> >> >> >> for its object/metadata storage. You have to have a license for
> >> >> >> >> SQL
> >> >> >> >> Server
> >> >> >> >> 2005 but it does not need to be installed.
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> --
> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >>
> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> message
> >> >> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
> >> >> >> >> > No. I've tried both on the server itself and from another
> >> >> >> >> > machine.
> >> >> >> >> > Always
> >> >> >> >> > 'Page cannot be found.'
> >> >> >> >> >
> >> >> >> >> > (Tried with both http://<servername>/Reports and
> >> >> >> >> > http://<servername>/Reports$RS2005)
> >> >> >> >> >
> >> >> >> >> > As far as I know I'm an administrator.
> >> >> >> >> >
> >> >> >> >> > "Bruce L-C [MVP]" wrote:
> >> >> >> >> >
> >> >> >> >> >> First things first. Can you pull up Report Manager (this is
> >> >> >> >> >> the
> >> >> >> >> >> portal
> >> >> >> >> >> that
> >> >> >> >> >> ships with RS and is used to manage RS).
> >> >> >> >> >>
> >> >> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
> >> >> >> >> >>
> >> >> >> >> >> localhost only works if you are on the machine hosting RS.
> >> >> >> >> >>
> >> >> >> >> >> Second, are you an adminstrator on that machine. All people
> >> >> >> >> >> in
> >> >> >> >> >> the
> >> >> >> >> >> local
> >> >> >> >> >> administrator group on the machine that has RS installed will
> >> >> >> >> >> automatically
> >> >> >> >> >> be in the RS administrators role.
> >> >> >> >> >>
> >> >> >> >> >> Deploying is the last thing you should try.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> --
> >> >> >> >> >> Bruce Loehle-Conger
> >> >> >> >> >> MVP SQL Server Reporting Services
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
> >> >> >> >> >> message
> >> >> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
> >> >> >> >> >> > As usual I'm learning by doing and I'm not sure I know what
> >> >> >> >> >> > I'm
> >> >> >> >> >> > doing.
> >> >> >> >> >> >
> >> >> >> >> >> > We have a legacy server running Windows Server 2003 and Sql
> >> >> >> >> >> > Server
> >> >> >> >> >> > 2000.
> >> >> >> >> >> > We want to run a Reporting Services report off one of the
> >> >> >> >> >> > tables
> >> >> >> >> >> > in
> >> >> >> >> >> > SQL
> >> >> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
> >> >> >> >> >> > including
> >> >> >> >> >> > RS
> >> >> >> >> >> > on
> >> >> >> >> >> > the
> >> >> >> >> >> > server.
> >> >> >> >> >> >
> >> >> >> >> >> > IIS has been installed. When it came time to install
> >> >> >> >> >> > SQL2005
> >> >> >> >> >> > I
> >> >> >> >> >> > had
> >> >> >> >> >> > a
> >> >> >> >> >> > few
> >> >> >> >> >> > moments of confusion. I am used to installing SQL2005
> >> >> >> >> >> > Express
> >> >> >> >> >> > which
> >> >> >> >> >> > seems
> >> >> >> >> >> > to
> >> >> >> >> >> > automatically install a named instance. In this case I
> >> >> >> >> >> > manually
> >> >> >> >> >> > selected
> >> >> >> >> >> > a
> >> >> >> >> >> > named instance (RS2005) because the wording of the screen
> >> >> >> >> >> > seemed
> >> >> >> >> >> > to
> >> >> >> >> >> > imply
> >> >> >> >> >> > that the default instance of SQL2000 would be upgraded
> >> >> >> >> >> > (which
> >> >> >> >> >> > wouldn't
> >> >> >> >> >> > be
> >> >> >> >> >> > a
> >> >> >> >> >> > good idea.)
> >> >> >> >> >> >
> >> >> >> >> >> > So I installed SQL2005 with a named instance and the BI
> >> >> >> >> >> > Studio.
> >> >> >> >> >> > I
> >> >> >> >> >> > copied
> >> >> >> >> >> > over the report I wanted to deploy. Now my problem is that
> >> >> >> >> >> > I
> >> >> >> >> >> > cannot
> >> >> >> >> >> > get
> >> >> >> >> >> > it
> >> >> >> >> >> > to deploy. In BI/VS the TargetServerURL is
> >> >> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
> >> >> >> >> >> > connection
> >> >> >> >> >> > errors:
> >> >> >> >> >> > 'A
> >> >> >> >> >> > connection could not be made to the report server
> >> >> >> >> >> > http://localhost/ReportServer$RS2005. Additional
> >> >> >> >> >> > information -
> >> >> >> >> >> > The
> >> >> >> >> >> > attempt
> >> >> >> >> >> > to connect to the report server failed. Check your
> >> >> >> >> >> > connection
> >> >> >> >> >> > information,
> >> >> >> >> >> > etc.'
> >> >> >> >> >> >
> >> >> >> >> >> > I have run the Reporting Services Configuration manager.
> >> >> >> >> >> > To
> >> >> >> >> >> > save
> >> >> >> >> >> > time,
> >> >> >> >> >> > here
> >> >> >> >> >> > are the settings:
> >> >> >> >> >> > Report Server Status
> >> >> >> >> >> > Instance Name RS2005
> >> >> >> >> >> > Instance ID MSSQL.2
> >> >> >> >> >> > Running
> >> >> >> >> >> >
> >> >> >> >> >> > --
> >> >> >> >> >> >
> >> >> >> >> >> > Report Server Virtual Directory
> >> >> >> >> >> > Name ReportServer$RS2005
> >> >> >> >> >> > Website Default Website
> >> >> >> >> >> >
> >> >> >> >> >> > Report Manager Virtual Directory Settings
> >> >> >> >> >> > Name Reports$RS2005
> >> >> >> >> >> > Website Default Web Site
> >> >> >> >> >> >
> >> >> >> >> >> > Windows Service Identity
> >> >> >> >> >> > Service Nmae ReportServer$RS2005
> >> >> >> >> >> > Service Account LocalSystem
> >> >> >> >> >> > Built-in Account Local System
> >> >> >> >> >> >
> >> >> >> >> >> >
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>|||Interesting. I would have thought the act of installing would have detected
and installed/configured IIS for the 2.0 framework. I guess the installer
thought everything was OK when it was not.
Glad to hear it is all OK now. One benefit. You have a simplier environment
running without SQL 2005 database and just using the 2000 database already
installed.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
news:43FC7545-4619-4E0E-8F06-9B9E2D6AF466@.microsoft.com...
> Stop the presses!!! I have solved the problem of the missing Folder page
> and
> the report is now successsfully deployed!!!!
> The problem is not in RS. The problem is that the Dot Net Framework was
> installed on the Windows 2003 server before the IIS component was
> installed.
> The solution was simple:
> "C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i"
> Looks like I have a few brain cells left.
> "Bruce L-C [MVP]" wrote:
>> If the RS configuration tool shows everything good it should not be a
>> problem.
>> I have never seen this error.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> news:23A2FD03-F2FF-4D94-A851-C2C6921C0A4A@.microsoft.com...
>> > Now what. Am I forgetting some option when running RS off SQL 2000?
>> > Got
>> > a
>> > very different error.
>> >
>> > The XML page cannot be displayed
>> > Cannot view XML input using XSL style sheet. Please correct the error
>> > and
>> > then click the Refresh button, or try again later.
>> >
>> >
>> > ----
>> >
>> > A name was started with an invalid character. Error processing resource
>> > 'http://ussog-s-a000002/Reports/Pages/Folder.aspx'...
>> >
>> > <%@. Page language="c#" Codebehind="Folder.aspx.cs"
>> > AutoEventWireup="false"
>> > Inherits="Microsoft.ReportingServices.UI.Folde
>> >
>> >
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Can you see Report Manager. That is the first thing you need to do.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in message
>> >> news:22ACC894-897A-4C62-A25D-AB116C07BD7D@.microsoft.com...
>> >> > Ok I did that and now I've got new problems.
>> >> >
>> >> > I reinstalled without creating a SQL2005 db. I went through the RS
>> >> > Config
>> >> > manager using only defaults and the DBs appear to have been created
>> >> > successfully under the SQL2000 server.
>> >> >
>> >> > Now when I try to deploy the report using VS/BI, I get an error: A
>> >> > connection could not be made to the report server
>> >> > http://localhost/ReportServer. Additional Information: Client found
>> >> > response
>> >> > content type of 'text/html; charset=utf-8', but expected 'text/xml'.
>> >> > The
>> >> > request failed with the error message: '
>> >> >
>> >> > The rest is too long to type here (looks like a big piece of HTML or
>> >> > XML)
>> >> > but the system event log is full of error messages like this: The
>> >> > application-specific permission settings do not grant Local
>> >> > Activation
>> >> > permission for the COM Server application with CLSID
>> >> > {BA126AD1-2166-11D1-B1D0-00805FC1270E}
>> >> > to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This
>> >> > security
>> >> > permission can be modified using the Component Services
>> >> > administrative
>> >> > tool.
>> >> >
>> >> > Could this have something to do with the fact that I wrote the
>> >> > report
>> >> > on
>> >> > my
>> >> > desktop and then copied the entire project over to the server?
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> My suggestion is to do that and this time do not create SQL Server
>> >> >> 2005
>> >> >> database. Just point it to an existing SQL Server 2000 db that you
>> >> >> have.
>> >> >> There is no advantage to the added complexity of what you were
>> >> >> doing.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:F5CFAD3D-6221-4DAB-923B-863B88E0D5BA@.microsoft.com...
>> >> >> > Maybe I should just uninstall everything and start over.
>> >> >> >
>> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >
>> >> >> >> You have somehow gotten a totally messed up install. You should
>> >> >> >> not
>> >> >> >> have
>> >> >> >> four sites. Try this:
>> >> >> >> http://yourservername/Reports$RS2005/Reports/Pages/Folder.aspx
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> Bruce Loehle-Conger
>> >> >> >> MVP SQL Server Reporting Services
>> >> >> >>
>> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> >> message
>> >> >> >> news:D65947A7-6E16-4331-8810-D59BBEE1487C@.microsoft.com...
>> >> >> >> > By 'websites' do you mean the report directories under Default
>> >> >> >> > Web
>> >> >> >> > Site?
>> >> >> >> >
>> >> >> >> > I have 4 report directories under the Default Web Site:
>> >> >> >> > ReportServer,
>> >> >> >> > Reports, Reports$RS2005, and ReportServer$RS2005. The first 2
>> >> >> >> > are
>> >> >> >> > empty.
>> >> >> >> > The last two are full of what appears to be asp.net related
>> >> >> >> > files
>> >> >> >> > and
>> >> >> >> > directories.
>> >> >> >> >
>> >> >> >> > (I admit that I was under the impression that RS2005 needed a
>> >> >> >> > 2005
>> >> >> >> > db
>> >> >> >> > to
>> >> >> >> > store its data.)
>> >> >> >> >
>> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >
>> >> >> >> >> By what you posted it seems that you have it installed in the
>> >> >> >> >> default
>> >> >> >> >> website in which case this should be working. Open up IIS
>> >> >> >> >> adminstrator
>> >> >> >> >> (whatever it is called) and see if you have the websites.
>> >> >> >> >>
>> >> >> >> >> By the way, you did not need to install SQL 2005. RS 2005 can
>> >> >> >> >> use
>> >> >> >> >> SQL
>> >> >> >> >> 2000
>> >> >> >> >> for its object/metadata storage. You have to have a license
>> >> >> >> >> for
>> >> >> >> >> SQL
>> >> >> >> >> Server
>> >> >> >> >> 2005 but it does not need to be installed.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >>
>> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote in
>> >> >> >> >> message
>> >> >> >> >> news:BD671A1B-82BA-466C-B6A0-7A73EB6B3FFA@.microsoft.com...
>> >> >> >> >> > No. I've tried both on the server itself and from another
>> >> >> >> >> > machine.
>> >> >> >> >> > Always
>> >> >> >> >> > 'Page cannot be found.'
>> >> >> >> >> >
>> >> >> >> >> > (Tried with both http://<servername>/Reports and
>> >> >> >> >> > http://<servername>/Reports$RS2005)
>> >> >> >> >> >
>> >> >> >> >> > As far as I know I'm an administrator.
>> >> >> >> >> >
>> >> >> >> >> > "Bruce L-C [MVP]" wrote:
>> >> >> >> >> >
>> >> >> >> >> >> First things first. Can you pull up Report Manager (this
>> >> >> >> >> >> is
>> >> >> >> >> >> the
>> >> >> >> >> >> portal
>> >> >> >> >> >> that
>> >> >> >> >> >> ships with RS and is used to manage RS).
>> >> >> >> >> >>
>> >> >> >> >> >> http://yourservername/Reports/Pages/Folder.aspx
>> >> >> >> >> >>
>> >> >> >> >> >> localhost only works if you are on the machine hosting RS.
>> >> >> >> >> >>
>> >> >> >> >> >> Second, are you an adminstrator on that machine. All
>> >> >> >> >> >> people
>> >> >> >> >> >> in
>> >> >> >> >> >> the
>> >> >> >> >> >> local
>> >> >> >> >> >> administrator group on the machine that has RS installed
>> >> >> >> >> >> will
>> >> >> >> >> >> automatically
>> >> >> >> >> >> be in the RS administrators role.
>> >> >> >> >> >>
>> >> >> >> >> >> Deploying is the last thing you should try.
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> --
>> >> >> >> >> >> Bruce Loehle-Conger
>> >> >> >> >> >> MVP SQL Server Reporting Services
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >> "B. Chernick" <BChernick@.discussions.microsoft.com> wrote
>> >> >> >> >> >> in
>> >> >> >> >> >> message
>> >> >> >> >> >> news:B0ABE746-24C8-4D92-9952-776C52F6EF9D@.microsoft.com...
>> >> >> >> >> >> > As usual I'm learning by doing and I'm not sure I know
>> >> >> >> >> >> > what
>> >> >> >> >> >> > I'm
>> >> >> >> >> >> > doing.
>> >> >> >> >> >> >
>> >> >> >> >> >> > We have a legacy server running Windows Server 2003 and
>> >> >> >> >> >> > Sql
>> >> >> >> >> >> > Server
>> >> >> >> >> >> > 2000.
>> >> >> >> >> >> > We want to run a Reporting Services report off one of
>> >> >> >> >> >> > the
>> >> >> >> >> >> > tables
>> >> >> >> >> >> > in
>> >> >> >> >> >> > SQL
>> >> >> >> >> >> > Server 2000 so I was told to install SQL2005 Standard
>> >> >> >> >> >> > including
>> >> >> >> >> >> > RS
>> >> >> >> >> >> > on
>> >> >> >> >> >> > the
>> >> >> >> >> >> > server.
>> >> >> >> >> >> >
>> >> >> >> >> >> > IIS has been installed. When it came time to install
>> >> >> >> >> >> > SQL2005
>> >> >> >> >> >> > I
>> >> >> >> >> >> > had
>> >> >> >> >> >> > a
>> >> >> >> >> >> > few
>> >> >> >> >> >> > moments of confusion. I am used to installing SQL2005
>> >> >> >> >> >> > Express
>> >> >> >> >> >> > which
>> >> >> >> >> >> > seems
>> >> >> >> >> >> > to
>> >> >> >> >> >> > automatically install a named instance. In this case I
>> >> >> >> >> >> > manually
>> >> >> >> >> >> > selected
>> >> >> >> >> >> > a
>> >> >> >> >> >> > named instance (RS2005) because the wording of the
>> >> >> >> >> >> > screen
>> >> >> >> >> >> > seemed
>> >> >> >> >> >> > to
>> >> >> >> >> >> > imply
>> >> >> >> >> >> > that the default instance of SQL2000 would be upgraded
>> >> >> >> >> >> > (which
>> >> >> >> >> >> > wouldn't
>> >> >> >> >> >> > be
>> >> >> >> >> >> > a
>> >> >> >> >> >> > good idea.)
>> >> >> >> >> >> >
>> >> >> >> >> >> > So I installed SQL2005 with a named instance and the BI
>> >> >> >> >> >> > Studio.
>> >> >> >> >> >> > I
>> >> >> >> >> >> > copied
>> >> >> >> >> >> > over the report I wanted to deploy. Now my problem is
>> >> >> >> >> >> > that
>> >> >> >> >> >> > I
>> >> >> >> >> >> > cannot
>> >> >> >> >> >> > get
>> >> >> >> >> >> > it
>> >> >> >> >> >> > to deploy. In BI/VS the TargetServerURL is
>> >> >> >> >> >> > http://localhost/ReportServer$RS2005. All I get are
>> >> >> >> >> >> > connection
>> >> >> >> >> >> > errors:
>> >> >> >> >> >> > 'A
>> >> >> >> >> >> > connection could not be made to the report server
>> >> >> >> >> >> > http://localhost/ReportServer$RS2005. Additional
>> >> >> >> >> >> > information -
>> >> >> >> >> >> > The
>> >> >> >> >> >> > attempt
>> >> >> >> >> >> > to connect to the report server failed. Check your
>> >> >> >> >> >> > connection
>> >> >> >> >> >> > information,
>> >> >> >> >> >> > etc.'
>> >> >> >> >> >> >
>> >> >> >> >> >> > I have run the Reporting Services Configuration manager.
>> >> >> >> >> >> > To
>> >> >> >> >> >> > save
>> >> >> >> >> >> > time,
>> >> >> >> >> >> > here
>> >> >> >> >> >> > are the settings:
>> >> >> >> >> >> > Report Server Status
>> >> >> >> >> >> > Instance Name RS2005
>> >> >> >> >> >> > Instance ID MSSQL.2
>> >> >> >> >> >> > Running
>> >> >> >> >> >> >
>> >> >> >> >> >> > --
>> >> >> >> >> >> >
>> >> >> >> >> >> > Report Server Virtual Directory
>> >> >> >> >> >> > Name ReportServer$RS2005
>> >> >> >> >> >> > Website Default Website
>> >> >> >> >> >> >
>> >> >> >> >> >> > Report Manager Virtual Directory Settings
>> >> >> >> >> >> > Name Reports$RS2005
>> >> >> >> >> >> > Website Default Web Site
>> >> >> >> >> >> >
>> >> >> >> >> >> > Windows Service Identity
>> >> >> >> >> >> > Service Nmae ReportServer$RS2005
>> >> >> >> >> >> > Service Account LocalSystem
>> >> >> >> >> >> > Built-in Account Local System
>> >> >> >> >> >> >
>> >> >> >> >> >> >
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>

Monday, March 12, 2012

Major Version number

Major Time Out Issue

Major SQL Server 2k5 x64 configuration problem

Major SQL Server 2k5 x64 configuration problem

Major SQL Server 2k5 x64 configuration problem

Major SQL Server 2k5 x64 configuration problem

Major Search Problem

Major query optimiser weirdness with UDFs and SPs on SQL 2000

Major Problems with Calculated Fields

Friday, March 9, 2012

Major problems setting up RS and deploying a report

maintenance plan wizard

Blog Archive

About Me