having trouble getting reporting services installed properly

Hi,
I am running Windows 2000 and VS 2003.
I installed Reporting Services with service pack 2.
When I type: in http://reportserver/reports I get an access denied 403 error.
When I go into IIS Manager and look for the Report folder properties I can't
find the Reports virtual directory. It does not exist.
So, how is it when I goto http://reportserver/reports I get a 403 error and
not a 404: File not found error.
The service is run as the executable: reportingservicesservice.exe
(discovered this through internet searches) on the machine, but when I search
for it, I can't find the file.
I have created a report and successfully viewed it in the VS 2003 Report
Designer, but the reporting services and Report Manager don't exist.
I do have this directory with lots of files, but I don't seem to have the
start page for Reporting Manaer anywhere on my system.
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
Could someone please advise.
Thank You
ChrisDid you open the reportning services configuration manager (new with 2005)
and configure the 2 folders. In 2005 it doesnt automatically create the 2
virtual folders, you have to explicitly create them through the configuration
manager.
Go to reporting services configuration (it should be somewhere in your
"START --> All programs") and connect to your report server, and make sure
the virtual directory tabs are green checked. If not set them
"Chris" wrote:
> Hi,
> I am running Windows 2000 and VS 2003.
> I installed Reporting Services with service pack 2.
> When I type: in http://reportserver/reports I get an access denied 403 error.
> When I go into IIS Manager and look for the Report folder properties I can't
> find the Reports virtual directory. It does not exist.
> So, how is it when I goto http://reportserver/reports I get a 403 error and
> not a 404: File not found error.
> The service is run as the executable: reportingservicesservice.exe
> (discovered this through internet searches) on the machine, but when I search
> for it, I can't find the file.
> I have created a report and successfully viewed it in the VS 2003 Report
> Designer, but the reporting services and Report Manager don't exist.
> I do have this directory with lots of files, but I don't seem to have the
> start page for Reporting Manaer anywhere on my system.
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> Could someone please advise.
> Thank You
> Chris|||Hi Nagini,
I am not using SQL Server 2005, I am using SQL Server 2000.
Thanks
Chris
"Nagini Indugula" wrote:
> Did you open the reportning services configuration manager (new with 2005)
> and configure the 2 folders. In 2005 it doesnt automatically create the 2
> virtual folders, you have to explicitly create them through the configuration
> manager.
> Go to reporting services configuration (it should be somewhere in your
> "START --> All programs") and connect to your report server, and make sure
> the virtual directory tabs are green checked. If not set them
> "Chris" wrote:
> > Hi,
> >
> > I am running Windows 2000 and VS 2003.
> >
> > I installed Reporting Services with service pack 2.
> >
> > When I type: in http://reportserver/reports I get an access denied 403 error.
> >
> > When I go into IIS Manager and look for the Report folder properties I can't
> > find the Reports virtual directory. It does not exist.
> >
> > So, how is it when I goto http://reportserver/reports I get a 403 error and
> > not a 404: File not found error.
> >
> > The service is run as the executable: reportingservicesservice.exe
> > (discovered this through internet searches) on the machine, but when I search
> > for it, I can't find the file.
> >
> > I have created a report and successfully viewed it in the VS 2003 Report
> > Designer, but the reporting services and Report Manager don't exist.
> >
> > I do have this directory with lots of files, but I don't seem to have the
> > start page for Reporting Manaer anywhere on my system.
> >
> > C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> >
> > Could someone please advise.
> >
> > Thank You
> >
> > Chris

Having Different Versions of Crystal Reports (8,9) in the same web application

See, We have a web application which is developed using Webclass Designer and currently runs on IIS 4.0 and IIS 5.0. It also contains a Reports Menu thorugh which the end user sees the data. These reports are mainly displayed using Crystal Reports 8.0.0.371. There are around 110 reports. The client wants specifically only couple of these reports to be migrated to version 9.0 leaving the rest. The reports are mainly opened, passed with SQL query etc in a single class file. So this is common for all the reports. Just that the object of this class file is created in every instance. The reference of CRAXDRT.dll of version 8 is added as a reference in this class file so that objects can be created.



Now my question is , is it possible to have two different versions of Crystal Reports in the same application. It means that ideally the support files are different. Also , it will be not possible for the report’s class file present in VB to refer both 8 and 9 at the same time. This is what I feel but as usual the client needs some support docs if this is true. Hence I need ur expert opinion on this.


Any help in this issue ...Please share ur expert opinionsHi,
I wish to do the same, did you manage to solve this problem, or does any1 else have any input?

Having a problem with ReportViewer Drill-Throughs

I'm having a problem with the Report Viewer in ASP.NET. I have a report that drills-through to other reports using the Action->Jump to report setting. This works perfectly in the VS Report Builder Preview screen, as well as in the Report Manager when I upload it. However, on my aspx page, clicking any item in the viewer makes the page just refresh. I can't find any articles on this anywhere. Any Ideas?You guys are ridiculously helpful, by the way.Anything on this? I really don't understand what's going on.|||Finally figured this out.You need to add a handler for the Drillthrough event, and make sure you're not reloading your main report on Postback.sql

hardcoding password instead of showing password box everytime

Dear all
Everytime, when my aspx application connect with the reports, it will also
show the password box for the input of username and password, however, can we
avoid it to show the password box? I want to implicity hardcoding the
username and password into the aspx and i don't want to show the password box
in the IEYou can use stored credentials for the data sources. In report manager, go
to the properties page of the report, click on the data sources tab and
specify a user name / pwd and click apply to store these credentials.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Joe" <Joe@.discussions.microsoft.com> wrote in message
news:81E41716-A88F-4C3B-B785-6012F6767E9D@.microsoft.com...
> Dear all
> Everytime, when my aspx application connect with the reports, it will also
> show the password box for the input of username and password, however, can
> we
> avoid it to show the password box? I want to implicity hardcoding the
> username and password into the aspx and i don't want to show the password
> box
> in the IE
>|||No the password prompt is from I.E. it ask from the domain user password to
see whether it have the right to see the reports or not, not the data sources
password
"Robert Bruckner [MSFT]" wrote:
> You can use stored credentials for the data sources. In report manager, go
> to the properties page of the report, click on the data sources tab and
> specify a user name / pwd and click apply to store these credentials.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Joe" <Joe@.discussions.microsoft.com> wrote in message
> news:81E41716-A88F-4C3B-B785-6012F6767E9D@.microsoft.com...
> > Dear all
> > Everytime, when my aspx application connect with the reports, it will also
> > show the password box for the input of username and password, however, can
> > we
> > avoid it to show the password box? I want to implicity hardcoding the
> > username and password into the aspx and i don't want to show the password
> > box
> > in the IE
> >
>
>

Hard Coded parameters

Is it possible to force parameters into the reports so enabling me to force a user id value into every report that is picked up from the list. The user ID is a system value and I don't want end users having any knowledge of it?

Cheers

Darren

Hello Darren,

What you can do is create a hidden/internal parameter so that the end user can not see it. From BOL:

Hidden

Select this option if the parameter value should not appear on the report. Although hidden parameters do not appear on a report, they can be set in other ways (for example, in subscriptions and through URLs).

Internal

Select this option if the parameter cannot be changed at run time. On a published report, no visual evidence is provided to indicate that this parameter exists.

Hope this helps.

Jarret

|||

Hi Jarret,

I think this may be the answer, I need to provide a list of published reports , how would we then get the hidden parameter into it.

Can we display a URL with the user ID already in it which will then render the report viewer with the other optional parameters to be picked. How do we stop somebody constructing a URL with a different user ID.

A hidden parameter sounds like the right option but I'm confused how to populate it.

Cheers, Darren

|||

If you're wanting to keep it out of the URL as well, you'll need to go with an Internal parameter, since it can not be changed at run time. Hidden parameters can be changed through the URL. You can change the value of this from within your Report Manager. Go to the properties of your report, then go into the Parameters section. In there, you can change the default value to whatever you like.

Hope this helps.

Jarret

|||Is the Internal parameter fixed in the report then? I want to be able to change the value based on the user running the report but do not want them to be able to change to a user ID not associated to them.|||

I'm not sure how you were planning to change the user ID of the user running the report, but you can set an expression for the default value of any parameter through VS.

If you put =User!UserID as the Default value for your parameter, it will show the domain account used.

Just remember, if you use a hidden parameter, someone can manipulate the value via the URL. This is not possible with an internal parameter.

Jarret

|||

Thanks Jarret,

I think I know what we will do know. The web site maintains a guid session token for each user which originates from the database initially so if I use this as my hidden parameter and let the reports stored procedure calculate the user ID based on this I will be safe.

Cheers

|||

That sounds like it would work, but someone can pass in that parameter via the URL since you're using a hidden parameter. The internal parameter should work in this situation too, and you don't have to worry about it being changed by a user.

Anyway, I'm glad you have a solution. Can you mark this one as answered so others can see the solution?

Jarret

Handling optional parameters

On many reports I have optional parameters, for example if the employee is filled in it will run for that employee but if it's null it runs for all employees. Which is the best way to handle this?

The two options I am currently looking at are:

select * from employee where (employee.id = @.EmpID or @.EmpID is Null)

select * from employee where isnull(@.empID, employee.id) = employee.id

Anyone else have a different solution?

Currently we use the OR approach and I wanted to see if anyone had any thoughts before switching to using IsNull, which seems a bit better.

OR can be slow. I always use the ISNULL approach.

|||

Another way to do this is, you can include "*(ALL) " in you employee dataset and you can default the parameter to "*(ALL)". Now pass back the selected value to the Stored Procedure

IF (@.EMPID= '*(ALL)'

select * from Employee

Else

Select * form Employee where employee.id=@.EMPID

This way it is more intuitive to End Users.

|||

The problem with using the if (@.EmpID is null) is that then you need to maintain two queries. And for some reports that have 3 or more optional parameters this could mean having 8 or more queries to maintain just for optional parameters. We also thought about using an expression for the query but some of the clients like to use the generic query view if they edit the report so this makes that option unavailable.

I think we will be using the isnull option for our solution.

Thanks

|||

I thought this blog post was useful for this topic. You can combine approaches if you want.

http://bloggingabout.net/blogs/egiardina/archive/2007/06/26/sql-server-reporting-services-optional-parameters.aspx

|||

Techquest wrote:

Another way to do this is, you can include "*(ALL) " in you employee dataset and you can default the parameter to "*(ALL)". Now pass back the selected value to the Stored Procedure

IF (@.EMPID= '*(ALL)'

select * from Employee

Else

Select * form Employee where employee.id=@.EMPID

This way it is more intuitive to End Users.

Not everyone uses stored procs to serve reports.

|||

Found an issue using the IsNull approach. If the optional parameter can be null in the table it will not return the null values.

EX. Middle name is a nullable field

select * from Employee where MiddleName = IsNull(@.MiddleName, MiddleName)

This won't return all values when the parameter is null, will return all values that have any non null MiddleName.

Think it may be safer to use the OR approach now because other people that use modify reports not familiar with this may use IsNull is cases it should not be used.

Anyone have any suggestions around this? I know most of the time the optional parameter does not go against a nullable field but could cause a lot of problems if you did it by mistake.

Thanks,

Kevin

|||

Yeah, avoid nullable fields

In case you do have them though you could use:

select * from Employee where COALESCE(MiddleName, '') = COALESCE(@.MiddleName, MiddleName, '')

COALESCE is basibcally like ISNULL but it takes any number of parameters rather than just 2 and returns the first non-null value.

|||

COALESCE functions differently than IsNull though. If you look at the execution plan, these both are the same:

select * from employee where employee.id = COALESCE(@.EmpID, employee.id)

select * from employee where (employee.id = @.EmpID or @.EmpID is Null)

This defeats the purpose of using IsNull for the better exectution with some indexes.

Handling Languages in Reports

Hello,
I have a French and English user base and I would like to display reports in
the language of preference of the user. However, I am not certain as to a
best practice for this within VStudio. In addition, how can I make the
reportserver display a french GUI?
Any help would be apprecaited,
--
RyanHi Ryan,
My understanding of this issue is: You want to show different layout based
on different language in reporting services. If I misunderstood your
concern, please feel free to let me know.
You can use the locale settings on a client computer to determine how a
report appears to the user. For example, you can create a report that uses
a different query expression based on the locale information returned by
the User.Language global variable. The query may change to retrieve
localized information from a different column depending on the language
returned. You can also use an expression in the language settings of the
report or report items based on this variable.
While you can change the language settings of a report, you must be careful
about any display issues this may cause. For example, changing the locale
setting of the report can change the date format in the report, but it can
also change the currency format. Unless there is a conversion process in
place for the currency, this may cause the incorrect currency symbol to be
displayed in the report. To avoid this, set the language information on the
individual items that you want to change, or set the item with the currency
data to a specific language.
Here is a BOL article for your reference:
International Considerations for Reporting Services
http://msdn2.microsoft.com/en-us/library/ms156493(d=ide).aspx
Hope this will be helpful!
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.|||Thank-you Wei,
I will have a look at that and I may have a follow-up question for you at a
later date.
--
Ryan
"Wei Lu [MSFT]" wrote:
> Hi Ryan,
> My understanding of this issue is: You want to show different layout based
> on different language in reporting services. If I misunderstood your
> concern, please feel free to let me know.
> You can use the locale settings on a client computer to determine how a
> report appears to the user. For example, you can create a report that uses
> a different query expression based on the locale information returned by
> the User.Language global variable. The query may change to retrieve
> localized information from a different column depending on the language
> returned. You can also use an expression in the language settings of the
> report or report items based on this variable.
> While you can change the language settings of a report, you must be careful
> about any display issues this may cause. For example, changing the locale
> setting of the report can change the date format in the report, but it can
> also change the currency format. Unless there is a conversion process in
> place for the currency, this may cause the incorrect currency symbol to be
> displayed in the report. To avoid this, set the language information on the
> individual items that you want to change, or set the item with the currency
> data to a specific language.
> Here is a BOL article for your reference:
> International Considerations for Reporting Services
> http://msdn2.microsoft.com/en-us/library/ms156493(d=ide).aspx
> Hope this will be helpful!
> 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 Ryan,
Thank you for your update.
I will close this issue now and if you have any questions about this issue,
please feel free to re-enter the newsgroup and post it under this thread. I
will reply as soon as possible.
Have a nice day!
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.

Handheld Devices

Just wondering has anyone every tried viewing reports on handheld devices. I
can to the report server but if the report has parameters they don't show up.
Any thoughts?I too am wanting to do this, here is what I have found...
http://groups-beta.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/c49464e1742ffad8/50f2ae5563f23dea