Showing posts with label viewing. Show all posts
Showing posts with label viewing. Show all posts

Monday, March 12, 2012

Problem when viewing reports in browser

Hi,
I have a report that use fixedheader in some of its tablecolumn. The
reports also using drill through.
In report designer, the fixedheader works fine. Also when I'm jump to
another report (the drill through), there is a "back to parent report"
button in the new report shown.
The problem is, when I deploy the report to the report server. When
I'm viewing the report in the browser (ie 6), the fixedheader doesn't
work. Also the "back to parent report" button, gone.
How can I solve this? ThxOn Mar 29, 12:00 pm, "Alphonse" <amphysv...@.gmail.com> wrote:
> Hi,
> I have a report that use fixedheader in some of its tablecolumn. The
> reports also using drill through.
> In report designer, the fixedheader works fine. Also when I'm jump to
> another report (the drill through), there is a "back to parent report"
> button in the new report shown.
> The problem is, when I deploy the report to the report server. When
> I'm viewing the report in the browser (ie 6), the fixedheader doesn't
> work. Also the "back to parent report" button, gone.
> How can I solve this? Thx
Fix the fixedheader bug. Its because I'm merging some cells in the
fixed column. After split all the merging cells, the freeze pane works
fine in the browser. I guess this is a bug, cause it didn't error in
the report designer preview.
Still have problem with the "back to parent report" in the browser.
Any help for this issue, would greatly appreciated.
Thanks

Wednesday, March 7, 2012

Problem viewing the site after uploading

HI,

I have upladed my application to my remote server but then I get an error message. I am a beginner so any help would be appreciated and if possible explain the solution to me in a simpler format. Here is the error message:

Server Error in '/' Application.


Anerror has occurred while establishing a connection to the server. Whenconnecting to SQL Server 2005, this failure may be caused by the factthat under the default settings SQL Server does not allow remoteconnections. (provider: SQL Network Interfaces, error: 26 - ErrorLocating Server/Instance Specified)

Description:Anunhandled exception occurred during the execution of the current webrequest. Please review the stack trace for more information about theerror and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by thefact that under the default settings SQL Server does not allow remoteconnections. (provider: SQL Network Interfaces, error: 26 - ErrorLocating Server/Instance Specified)

Source Error:

The source code that generated this unhandled exception can only beshown when compiled in debug mode. To enable this, please follow one ofthe below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@. Page Language="C#" Debug="true" %
or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration
Note that this second technique will cause all files within a givenapplication to be compiled in debug mode. The first technique willcause only that particular file to be compiled in debug mode.

Important:Running applications in debug mode does incur a memory/performanceoverhead. You should make sure that an application has debuggingdisabled before deploying into production scenario.

Thanks in advance.

In sql 2005 you have to enable remoteconnection to access the DB from other machine. To enable Remote connection in SQL 20005 follow these steps

Under SQL2005 program menu follow configuration Tools =>SQL Server Surface Area Configuration => Select Server Surface Area Configuration for Services and Connections.

It will lead to a window with a treeview select Remote connections.Then Select Local and Remote Connections.

Thats it, now you can connect your SQL Server without any problem

Hope this will help you

Problem viewing the history of the job I ran manually

Hey guys. I've a job thta I ran manually and when i tried to look for the history, it doesn't show anything. How would I see why it failed. I also tried to look at the sysjobhistory table and nothing there. The thing is, if the agent runs the job, it shows it there but if I run it manually, it doesn't. I know that's not the case in SQL 2000.

Please advice, how to check that. Thank you.

Tej

As explicitly stated in book online,

"Contains information about the execution of scheduled jobs by SQL Server Agent. This table is stored in the msdb database."

So, all sql job execution is logged into sysjobhistory. How did you invoke the job manually? Do make sure you haven't cleared the history info.

If need to, run sql profiler and see if the job is started and if history is written to sysjobhistory table.|||

Hey oj,

What I meant by manual execution is that I right clicked the job and ran it manually. When I do that and go to the Job activity Monitor, it would go to Step 0, which I think is the preparation phase and before even going to step one it finishes. And it doesn't get logged. I've captured the SP:Completed,SP:Starting,StmtCompleted,SP:StmtStarting,SQL:BatchCompleted,SQL:BatchStarting.

I see a call so sp_help_jobstep sp and then it calls the sp_sqlagent_log_jobhistory to log the failure.

I dont see it actually trying to run the jobstep.It's still failing. I had to restart the agent. When I did that, it started logging stuff but the problem is that, this job calls a SSIS package to be executed. It fails saying 'The package execution failed'. When I run the package with my account, it runs fine. When I right click the job and run the package, it runs as SQL Server service account which is also a local admin on the box. And it fails. What would the next step be in order to figure out where the problem is?

Thank you

Tej

|||

HI

I faced this type of issue with job history view. when we tried to view the job history, it runs some scripts in back ground(we can capture thru profile), there microsoft has defined servername variable as 30, but my server name has more than 30 charecters length. I fixed this issue by reducing the server name to 30 charecters.

my solution may help u if ur server name has more length than 30.

Thanks

kiran

|||Hi Tej,

Sorry for the late reply.

Look like you're having permission/security problem. Please check out the following for some guidance.

Sqlagent security:
http://msdn2.microsoft.com/en-us/library/ms190926.aspx

Creating sqlagent proxies:
http://msdn2.microsoft.com/en-us/library/ms189064.aspx

Problem viewing the history of the job I ran manually

Hey guys. I've a job thta I ran manually and when i tried to look for the history, it doesn't show anything. How would I see why it failed. I also tried to look at the sysjobhistory table and nothing there. The thing is, if the agent runs the job, it shows it there but if I run it manually, it doesn't. I know that's not the case in SQL 2000.

Please advice, how to check that. Thank you.

Tej

As explicitly stated in book online,

"Contains information about the execution of scheduled jobs by SQL Server Agent.

This table is stored in the msdb database."

So, all sql job execution is logged into sysjobhistory. How did you invoke the job manually? Do make sure you haven't cleared the history info.

If need to, run sql profiler and see if the job is started and if history is written to sysjobhistory table.|||

Hey oj,

What I meant by manual execution is that I right clicked the job and ran it manually. When I do that and go to the Job activity Monitor, it would go to Step 0, which I think is the preparation phase and before even going to step one it finishes. And it doesn't get logged. I've captured the SP:Completed,SP:Starting,StmtCompleted,SP:StmtStarting,SQL:BatchCompleted,SQL:BatchStarting.

I see a call so sp_help_jobstep sp and then it calls the sp_sqlagent_log_jobhistory to log the failure.

I dont see it actually trying to run the jobstep.It's still failing. I had to restart the agent. When I did that, it started logging stuff but the problem is that, this job calls a SSIS package to be executed. It fails saying 'The package execution failed'. When I run the package with my account, it runs fine. When I right click the job and run the package, it runs as SQL Server service account which is also a local admin on the box. And it fails. What would the next step be in order to figure out where the problem is?

Thank you

Tej

|||

HI

I faced this type of issue with job history view. when we tried to view the job history, it runs some scripts in back ground(we can capture thru profile), there microsoft has defined servername variable as 30, but my server name has more than 30 charecters length. I fixed this issue by reducing the server name to 30 charecters.

my solution may help u if ur server name has more length than 30.

Thanks

kiran

|||Hi Tej,

Sorry for the late reply.

Look like you're having permission/security problem. Please check out the following for some guidance.

Sqlagent security:
http://msdn2.microsoft.com/en-us/library/ms190926.aspx

Creating sqlagent proxies:
http://msdn2.microsoft.com/en-us/library/ms189064.aspx

Problem viewing the history of the job I ran manually

Hey guys. I've a job thta I ran manually and when i tried to look for the history, it doesn't show anything. How would I see why it failed. I also tried to look at the sysjobhistory table and nothing there. The thing is, if the agent runs the job, it shows it there but if I run it manually, it doesn't. I know that's not the case in SQL 2000.

Please advice, how to check that. Thank you.

Tej

As explicitly stated in book online,

"Contains information about the execution of scheduled jobs by SQL Server Agent.

This table is stored in the msdb database."

So, all sql job execution is logged into sysjobhistory. How did you invoke the job manually? Do make sure you haven't cleared the history info.

If need to, run sql profiler and see if the job is started and if history is written to sysjobhistory table.|||

Hey oj,

What I meant by manual execution is that I right clicked the job and ran it manually. When I do that and go to the Job activity Monitor, it would go to Step 0, which I think is the preparation phase and before even going to step one it finishes. And it doesn't get logged. I've captured the SP:Completed,SP:Starting,StmtCompleted,SP:StmtStarting,SQL:BatchCompleted,SQL:BatchStarting.

I see a call so sp_help_jobstep sp and then it calls the sp_sqlagent_log_jobhistory to log the failure.

I dont see it actually trying to run the jobstep.It's still failing. I had to restart the agent. When I did that, it started logging stuff but the problem is that, this job calls a SSIS package to be executed. It fails saying 'The package execution failed'. When I run the package with my account, it runs fine. When I right click the job and run the package, it runs as SQL Server service account which is also a local admin on the box. And it fails. What would the next step be in order to figure out where the problem is?

Thank you

Tej

|||

HI

I faced this type of issue with job history view. when we tried to view the job history, it runs some scripts in back ground(we can capture thru profile), there microsoft has defined servername variable as 30, but my server name has more than 30 charecters length. I fixed this issue by reducing the server name to 30 charecters.

my solution may help u if ur server name has more length than 30.

Thanks

kiran

|||Hi Tej,

Sorry for the late reply.

Look like you're having permission/security problem. Please check out the following for some guidance.

Sqlagent security:
http://msdn2.microsoft.com/en-us/library/ms190926.aspx

Creating sqlagent proxies:
http://msdn2.microsoft.com/en-us/library/ms189064.aspx

Problem Viewing Reports on Server

Hello, we're having a bit of an issue getting Report Server to display reports. We've published via the web-interface and Visual Studio. After we publish, it gives an error and it looks as if it's trying to find the data source that we used to create the report. We've changed the datasource names to match that of the local machine too. Here's the error...

  • An error has occurred during report processing.

  • Cannot create a connection to data source 'LocalDataSourceName'.

  • Keyword not supported: 'driver'.

    Any help would be greatly appreciated. Thank you!

    What is the connection string and which data provider are you using? It looks like the data provider can't handle the connection string.|||Problem solved....we were using an invalid connection string. For some reason it was working on one server but not the other. Just tried a different string on both of them and it works great now.
  • Problem Viewing reports in Report Manager

    I have successfully installed the sql server reporting services on a windows
    2003 server. I have been able to deploy several reports to the report
    server. I have even been able to schedule a report to execute and send out
    via email every morning of the week.
    Here's the problem. When I try to view a report using the report manager I
    get a
    The page cannot be found
    HTTP 404 - File not found
    Internet Explorer
    error. I just don't get it. I can perform every other function using the
    report manager except view the report online. Which of course is a problem
    because I want to send my customers to the site to be able to view and run
    reports.
    Thanks for any help.
    --
    Jon Clayton
    Regions Financial CorporationSounds like a security issue or a malformed URL. It's very difficult (from
    here) to determine how you access report manager differently than the online
    version, but could you post a URL that worked, and a URL that failed?
    Dwayne|||Thanks for your help.
    Here is a link that works
    http://Servername/Reports/Pages/Folder.aspx
    This link of course brings up the default folders page
    Click on a folder and go to the following url, which work
    http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
    Click on a report in that folder to view the report using the following url
    fail
    http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
    The failure only occurs within the frame below. The header frame is still
    displayed, therefore I am able to:
    Click on the properties tab with the failed page displayed is successful
    using the following ur
    http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
    I have given full access permissions to the ASPNET account on the local
    machine to the two RS folders.
    I am convinced that it is a permissions issue. As a matter of fact I had an
    instance installed in my test invironment which is Windows 2000 which worked
    fine. But ever since the latest security updates that machine is having the
    same issue.
    Thanks again for your help.
    --
    Jon Clayton
    Regions Financial Corporation
    "Dwayne J. Baldwin" wrote:
    > Sounds like a security issue or a malformed URL. It's very difficult (from
    > here) to determine how you access report manager differently than the online
    > version, but could you post a URL that worked, and a URL that failed?
    > Dwayne
    >
    >|||"Jon" wrote:
    > Thanks for your help.
    > Here is a link that works
    > http://Servername/Reports/Pages/Folder.aspx
    > This link of course brings up the default folders page
    > Click on a folder and go to the following url, which works
    > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
    > Click on a report in that folder to view the report using the following url
    > fails
    > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
    > The failure only occurs within the frame below. The header frame is still
    > displayed, therefore I am able to:
    > Click on the properties tab with the failed page displayed is successful
    > using the following url
    > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
    > I have given full access permissions to the ASPNET account on the local
    > machine to the two RS folders.
    > I am convinced that it is a permissions issue. As a matter of fact I had an
    > instance installed in my test invironment which is Windows 2000 which worked
    > fine. But ever since the latest security updates that machine is having the
    > same issue.
    > Thanks again for your help.
    > --
    > Jon Clayton
    > Regions Financial Corporation
    >
    > "Dwayne J. Baldwin" wrote:
    > > Sounds like a security issue or a malformed URL. It's very difficult (from
    > > here) to determine how you access report manager differently than the online
    > > version, but could you post a URL that worked, and a URL that failed?
    > >
    > > Dwayne
    > >
    > >
    > >
    > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||It appears that the entries in the config files are correct. Thanks for the
    tip.
    --
    Jon Clayton
    Regions Financial Corporation
    "DLM" wrote:
    >
    > "Jon" wrote:
    > > Thanks for your help.
    > >
    > > Here is a link that works
    > > http://Servername/Reports/Pages/Folder.aspx
    > > This link of course brings up the default folders page
    > >
    > > Click on a folder and go to the following url, which works
    > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
    > >
    > > Click on a report in that folder to view the report using the following url
    > > fails
    > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
    > > The failure only occurs within the frame below. The header frame is still
    > > displayed, therefore I am able to:
    > >
    > > Click on the properties tab with the failed page displayed is successful
    > > using the following url
    > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
    > >
    > > I have given full access permissions to the ASPNET account on the local
    > > machine to the two RS folders.
    > >
    > > I am convinced that it is a permissions issue. As a matter of fact I had an
    > > instance installed in my test invironment which is Windows 2000 which worked
    > > fine. But ever since the latest security updates that machine is having the
    > > same issue.
    > >
    > > Thanks again for your help.
    > >
    > > --
    > > Jon Clayton
    > > Regions Financial Corporation
    > >
    > >
    > > "Dwayne J. Baldwin" wrote:
    > >
    > > > Sounds like a security issue or a malformed URL. It's very difficult (from
    > > > here) to determine how you access report manager differently than the online
    > > > version, but could you post a URL that worked, and a URL that failed?
    > > >
    > > > Dwayne
    > > >
    > > >
    > > >
    > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||Hi Jon,
    I have exactly the same problem. Please advise what I need to check/do?
    Thanks very much
    Khat.
    "Jon" wrote:
    > It appears that the entries in the config files are correct. Thanks for the
    > tip.
    > --
    > Jon Clayton
    > Regions Financial Corporation
    >
    > "DLM" wrote:
    > >
    > >
    > > "Jon" wrote:
    > >
    > > > Thanks for your help.
    > > >
    > > > Here is a link that works
    > > > http://Servername/Reports/Pages/Folder.aspx
    > > > This link of course brings up the default folders page
    > > >
    > > > Click on a folder and go to the following url, which works
    > > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
    > > >
    > > > Click on a report in that folder to view the report using the following url
    > > > fails
    > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
    > > > The failure only occurs within the frame below. The header frame is still
    > > > displayed, therefore I am able to:
    > > >
    > > > Click on the properties tab with the failed page displayed is successful
    > > > using the following url
    > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
    > > >
    > > > I have given full access permissions to the ASPNET account on the local
    > > > machine to the two RS folders.
    > > >
    > > > I am convinced that it is a permissions issue. As a matter of fact I had an
    > > > instance installed in my test invironment which is Windows 2000 which worked
    > > > fine. But ever since the latest security updates that machine is having the
    > > > same issue.
    > > >
    > > > Thanks again for your help.
    > > >
    > > > --
    > > > Jon Clayton
    > > > Regions Financial Corporation
    > > >
    > > >
    > > > "Dwayne J. Baldwin" wrote:
    > > >
    > > > > Sounds like a security issue or a malformed URL. It's very difficult (from
    > > > > here) to determine how you access report manager differently than the online
    > > > > version, but could you post a URL that worked, and a URL that failed?
    > > > >
    > > > > Dwayne
    > > > >
    > > > >
    > > > >
    > > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||I am also having this same exact problem. I can run everything without issue
    on our test server but production server is exhibiting this exact behavior?
    I can do everything but view the report. I can even run the report on the
    production server through code and through http://server/reportserver.
    Navigate to the folder/report and viola. I can enter parameters and run it.
    But not in the report manager gui' I get a 404 when I press the view
    report button. If I press it a second time I then get an error in the lower
    left hand corner of IE. If I open it up it states that on Line 50 permission
    denied and url = http://server/reportserver...blah...blah...blah
    Kevin
    "Khat Liko" wrote:
    > Hi Jon,
    > I have exactly the same problem. Please advise what I need to check/do?
    > Thanks very much
    > Khat.
    > "Jon" wrote:
    > > It appears that the entries in the config files are correct. Thanks for the
    > > tip.
    > > --
    > > Jon Clayton
    > > Regions Financial Corporation
    > >
    > >
    > > "DLM" wrote:
    > >
    > > >
    > > >
    > > > "Jon" wrote:
    > > >
    > > > > Thanks for your help.
    > > > >
    > > > > Here is a link that works
    > > > > http://Servername/Reports/Pages/Folder.aspx
    > > > > This link of course brings up the default folders page
    > > > >
    > > > > Click on a folder and go to the following url, which works
    > > > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
    > > > >
    > > > > Click on a report in that folder to view the report using the following url
    > > > > fails
    > > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
    > > > > The failure only occurs within the frame below. The header frame is still
    > > > > displayed, therefore I am able to:
    > > > >
    > > > > Click on the properties tab with the failed page displayed is successful
    > > > > using the following url
    > > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
    > > > >
    > > > > I have given full access permissions to the ASPNET account on the local
    > > > > machine to the two RS folders.
    > > > >
    > > > > I am convinced that it is a permissions issue. As a matter of fact I had an
    > > > > instance installed in my test invironment which is Windows 2000 which worked
    > > > > fine. But ever since the latest security updates that machine is having the
    > > > > same issue.
    > > > >
    > > > > Thanks again for your help.
    > > > >
    > > > > --
    > > > > Jon Clayton
    > > > > Regions Financial Corporation
    > > > >
    > > > >
    > > > > "Dwayne J. Baldwin" wrote:
    > > > >
    > > > > > Sounds like a security issue or a malformed URL. It's very difficult (from
    > > > > > here) to determine how you access report manager differently than the online
    > > > > > version, but could you post a URL that worked, and a URL that failed?
    > > > > >
    > > > > > Dwayne
    > > > > >
    > > > > >
    > > > > >
    > > > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.

    Problem viewing reports in Report Builder

    Hi.

    I get a problem when I want to preview a report in Report Builder. I just launch Report Builder by the url [1] (RS is on a server, and I work on a laptop). Then I choose a model and create a simple report. When I press "Run Report", I get an error message saying: "The permissions granted to user 'mydomain\myusername' are insufficient for performing this operation. (rsAccessDenied)". But my user are assigned to content manager...

    If I then save the report to the Report Server, I can access the report through e.g. the Report Manager without any problems.

    Why doesn't the preview functionality work for me? Are there some settings I need to set, or is it a bug in Report Builder?

    Regards, Tomsi

    [1] http://<servername>/reportserver/reportbuilder/reportbuilderlocalintranet.application

    Same problem for me. If I add myself to the local admin group it will work fine. Of course that is not a valid solution. What security piece are we missing?

    Is there a how to or step by step on the this part of the security for report builder?

    Thanks much

    Carl

    |||Do you have the system permission "Execute Report Definitions"? It is configurable from the Site Settings link in Report Manager.|||

    Thanks. Adding myself (NT user or group) to a "System Role Assignement" under "site-wide security" fixed it.

    |||

    Hello, I am supposed to be the administrator but I cant see system wide security.

    Problem viewing reports in Report Builder

    Hi.

    I get a problem when I want to preview a report in Report Builder. I just launch Report Builder by the url [1] (RS is on a server, and I work on a laptop). Then I choose a model and create a simple report. When I press "Run Report", I get an error message saying: "The permissions granted to user 'mydomain\myusername' are insufficient for performing this operation. (rsAccessDenied)". But my user are assigned to content manager...

    If I then save the report to the Report Server, I can access the report through e.g. the Report Manager without any problems.

    Why doesn't the preview functionality work for me? Are there some settings I need to set, or is it a bug in Report Builder?

    Regards, Tomsi

    [1] http://<servername>/reportserver/reportbuilder/reportbuilderlocalintranet.application

    Same problem for me. If I add myself to the local admin group it will work fine. Of course that is not a valid solution. What security piece are we missing?

    Is there a how to or step by step on the this part of the security for report builder?

    Thanks much

    Carl

    |||Do you have the system permission "Execute Report Definitions"? It is configurable from the Site Settings link in Report Manager.|||

    Thanks. Adding myself (NT user or group) to a "System Role Assignement" under "site-wide security" fixed it.

    |||

    Hello, I am supposed to be the administrator but I cant see system wide security.

    Problem viewing reports from report server

    Hi,
    I am new to Microsoft SQL Server Reporting Services.
    I followed the MSDN tutorial and successfully created a basic report.
    The preview of the report is fine within Business Intelligence
    Studio. I successfully deployed it to http://localhost/ReportServer.
    Look:
    -- Build started: Project: Report Project1, Configuration:
    Production --
    Build complete -- 0 errors, 0 warnings
    -- Deploy started: Project: Report Project1, Configuration:
    Production --
    Deploying to http://localhost/ReportServer
    Deploying report '/Report Project1/Sales Orders'.
    Deploy complete -- 0 errors, 0 warnings
    ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped
    ========== ========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
    But, when I tried to check it out from the Web browser (either IE or
    FireFox), the report is not displayed. Instead I saw the following
    error message:
    For security reasons DTD is prohibited in this XML document. To enable
    DTD processing set the ProhibitDtd property on XmlReaderSettings to
    false and pass the settings into XmlReader.Create method.
    However, the report is downloadable. If you click on "Export", I can
    export it to Excel or PDF.
    Question: In which file, do I set the ProhibitDtd property on
    XmlReaderSettings to false and pass it to XmlReader.Create method?
    Thank you!Were you able to solve your problem ? I am having same issues
    "antonyliu2002@.yahoo.com" wrote:
    > Hi,
    > I am new to Microsoft SQL Server Reporting Services.
    > I followed the MSDN tutorial and successfully created a basic report.
    > The preview of the report is fine within Business Intelligence
    > Studio. I successfully deployed it to http://localhost/ReportServer.
    > Look:
    > -- Build started: Project: Report Project1, Configuration:
    > Production --
    > Build complete -- 0 errors, 0 warnings
    > -- Deploy started: Project: Report Project1, Configuration:
    > Production --
    > Deploying to http://localhost/ReportServer
    > Deploying report '/Report Project1/Sales Orders'.
    > Deploy complete -- 0 errors, 0 warnings
    > ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped
    > ==========> ========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========> But, when I tried to check it out from the Web browser (either IE or
    > FireFox), the report is not displayed. Instead I saw the following
    > error message:
    > For security reasons DTD is prohibited in this XML document. To enable
    > DTD processing set the ProhibitDtd property on XmlReaderSettings to
    > false and pass the settings into XmlReader.Create method.
    > However, the report is downloadable. If you click on "Export", I can
    > export it to Excel or PDF.
    > Question: In which file, do I set the ProhibitDtd property on
    > XmlReaderSettings to false and pass it to XmlReader.Create method?
    > Thank you!
    >

    Problem viewing Reports from Network

    Hi,
    We have a network of XP Machines.
    When i try to view the reports in the application from the same
    machine itself it's coming up properly,but when i try to acess the
    reports in the application from another machine it's giving me the
    following error,
    ?The permissions granted to user ?OLDSERVER\Guest' are insufficient
    for performing this operation. (rsAccessDenied)
    As a solution to the problem of permissions in the help it's mentioned
    that we need to create roles in the SQL Server Report Manager for the
    users whom we need to give access to the reports.When we are accessing
    the reports from the network by default we are accessing the server as
    guests who doesn't have much rights.So I have created role (Browser )
    on SQL Server Report Manager for the guest user and tried accessing
    the server.
    Then it's giving the following error
    The Error Log description for the error was as follows,
    aspnet_wp!library!cd4!10/13/2004-21:48:41:: e
    ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    An internal error occurred on the report server. See the error log for
    more details., ;
    Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    An internal error occurred on the report server.
    See the error log for more details. -->
    System.InvalidOperationException: Computer name could not be obtained.
    at System.Environment.get_MachineName()
    at Microsoft.ReportingServices.Diagnostics.RunningJobContext..ctor(String
    jobId, String requestPath,
    JobActionEnum action, JobTypeEnum type, RunningJobList parentList,
    String userName, HttpContext
    optionalWebCtx)
    at Microsoft.ReportingServices.Diagnostics.RunningJobList.AddJob(String
    jobId, String requestPath,
    JobActionEnum action, JobTypeEnum type, String userName, HttpContext
    optionalCtx)
    at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase..ctor(String
    jobId, String requestPath,
    JobActionEnum action, JobTypeEnum jobType, String userName)
    at Microsoft.ReportingServices.Library.ProcessReportParametersCancelableStep..ctor(RSService
    rs,
    CatalogItemContext reportContext, Guid reportID, Guid linkID,
    DateTime historyDate, Int32 executionOption,
    ReportSnapshot compiledDefinition, ReportSnapshot snapshotData,
    String savedParametersXml,
    NameValueCollection values, JobTypeEnum jobType, String userName)
    at Microsoft.ReportingServices.Library.RSService.GetReportParametersForRendering(CatalogItemContext
    reportContext, Guid reportID, Guid linkID, DateTime historyDate,
    Int32 executionOption, ReportSnapshot
    compiledDefinition, ReportSnapshot snapshotData, String
    savedParametersXml, NameValueCollection values,
    JobTypeEnum jobType)
    at Microsoft.ReportingServices.Library.RSService._GetReportParameters(String
    report, String historyID, Boolean
    forRendering, NameValueCollection values,
    DatasourceCredentialsCollection credentials)
    at Microsoft.ReportingServices.Library.RSService.GetReportParameters(String
    report, String historyID, Boolean
    forRendering, NameValueCollection values,
    DatasourceCredentialsCollection credentials)
    -- End of inner exception stack trace --
    aspnet_wp!webserver!cd4!10/13/2004-21:48:41:: e ERROR:
    Reporting Services error
    Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    An internal error occurred on the report server. See the error log
    for more details. -->
    System.InvalidOperationException: Computer name could not be obtained.
    Thanks in Advance,
    RajeshTake a look at
    http://msdn.microsoft.com/library/en-us/rswork/htm/rms_security_v1_10bm.asp
    . Try using built-in accounts Everyone or Users instead of Guest.
    --
    -- "This posting is provided 'AS IS' with no warranties, and confers no
    rights."
    jhmiller@.online.microsoft.com
    "Rajesh" <rajeshkchandran@.gmail.com> wrote in message
    news:cad1e70a.0410201456.280c018f@.posting.google.com...
    > Hi,
    > We have a network of XP Machines.
    > When i try to view the reports in the application from the same
    > machine itself it's coming up properly,but when i try to acess the
    > reports in the application from another machine it's giving me the
    > following error,
    > 'The permissions granted to user 'OLDSERVER\Guest' are insufficient
    > for performing this operation. (rsAccessDenied)
    > As a solution to the problem of permissions in the help it's mentioned
    > that we need to create roles in the SQL Server Report Manager for the
    > users whom we need to give access to the reports.When we are accessing
    > the reports from the network by default we are accessing the server as
    > guests who doesn't have much rights.So I have created role (Browser )
    > on SQL Server Report Manager for the guest user and tried accessing
    > the server.
    > Then it's giving the following error
    > The Error Log description for the error was as follows,
    > aspnet_wp!library!cd4!10/13/2004-21:48:41:: e
    > ERROR: Throwing
    > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    > An internal error occurred on the report server. See the error log for
    > more details., ;
    > Info:
    > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    > An internal error occurred on the report server.
    > See the error log for more details. -->
    > System.InvalidOperationException: Computer name could not be obtained.
    > at System.Environment.get_MachineName()
    > at
    > Microsoft.ReportingServices.Diagnostics.RunningJobContext..ctor(String
    > jobId, String requestPath,
    > JobActionEnum action, JobTypeEnum type, RunningJobList parentList,
    > String userName, HttpContext
    > optionalWebCtx)
    > at Microsoft.ReportingServices.Diagnostics.RunningJobList.AddJob(String
    > jobId, String requestPath,
    > JobActionEnum action, JobTypeEnum type, String userName, HttpContext
    > optionalCtx)
    > at
    > Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase..ctor(String
    > jobId, String requestPath,
    > JobActionEnum action, JobTypeEnum jobType, String userName)
    > at
    > Microsoft.ReportingServices.Library.ProcessReportParametersCancelableStep..ctor(RSService
    > rs,
    > CatalogItemContext reportContext, Guid reportID, Guid linkID,
    > DateTime historyDate, Int32 executionOption,
    > ReportSnapshot compiledDefinition, ReportSnapshot snapshotData,
    > String savedParametersXml,
    > NameValueCollection values, JobTypeEnum jobType, String userName)
    > at
    > Microsoft.ReportingServices.Library.RSService.GetReportParametersForRendering(CatalogItemContext
    > reportContext, Guid reportID, Guid linkID, DateTime historyDate,
    > Int32 executionOption, ReportSnapshot
    > compiledDefinition, ReportSnapshot snapshotData, String
    > savedParametersXml, NameValueCollection values,
    > JobTypeEnum jobType)
    > at
    > Microsoft.ReportingServices.Library.RSService._GetReportParameters(String
    > report, String historyID, Boolean
    > forRendering, NameValueCollection values,
    > DatasourceCredentialsCollection credentials)
    > at
    > Microsoft.ReportingServices.Library.RSService.GetReportParameters(String
    > report, String historyID, Boolean
    > forRendering, NameValueCollection values,
    > DatasourceCredentialsCollection credentials)
    > -- End of inner exception stack trace --
    > aspnet_wp!webserver!cd4!10/13/2004-21:48:41:: e ERROR:
    > Reporting Services error
    > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
    > An internal error occurred on the report server. See the error log
    > for more details. -->
    > System.InvalidOperationException: Computer name could not be obtained.
    >
    > Thanks in Advance,
    > Rajesh

    Problem viewing report with Report Viewer

    Hi,

    I am using the Report Viewer Control to display the Reports. My query is generated dynamically so that output the query is a datatable. My application gives the user the flexibility to select the tables & the table-fields on which he wants to run the report. So I cannot have a fixed report file as I do not know what will the user select.

    I tried adding the result datatable as the datasource for the report dynamically.

    protected void RunReport_Click(object sender, EventArgs e){string constg ="server=localhost;Database=techapp;user id=sa;password=admin;";SqlConnection con =new SqlConnection(constg);//query is the query string that is generated at runtimeSqlDataAdapter da =new SqlDataAdapter(query,con);DataSet ds =new DataSet();da.Fill(ds,"ReportDataTable"); con.Close();ViewReport(ds.Tables["ReportDataTable"]);}protected void ViewReport(DataTable dt){ ReportViewer1.ProcessingMode = ProcessingMode.Local; ReportDataSource rd =new ReportDataSource(); rd.Name ="ReportData_Data"; rd.Value = dt; ReportViewer1.LocalReport.DataSources.Add(rd); ReportViewer1.DataBind();}

    My problem is that the entire code gets executed properly without any exception but the report is not displayed. I checked the ReportDataSource & it shows the proper value. In all the samples that I went through, I found that they have mentioned a report file. I don't know if this is the cause of the problem, but if it is then In mycase how can I create a report design file if I wouldn't know what to add in that file at design time.

    I do not have an expertise in this. can anyone please guide me through the right way & let me know what is it that I'm not doing correct?

    I guess its the problem with height of report

    Check whether you have set the height of report as 100%. Change that to some fixed size let say 800px.

    Let me know if you need any further help

    |||

    Hi Ashok,

    I tried adjusting the height of the report viewer . This is the changed code but it still doesn't show any thing.

     ReportViewer1.ProcessingMode = ProcessingMode.Local; ReportViewer1.Height = Unit.Pixel(500); ReportDataSource rd =new ReportDataSource(); rd.Name ="ReportData_Data"; rd.Value = ds.Tables["ReportDataTable"]; ReportViewer1.LocalReport.DataSources.Add(rd); ReportViewer1.DataBind();

    Could the problem be the absence of a report design file ie an rdlc file. I downloaded a sample code from net where the report file is created dynamically & it seemed to work this way.

    Is a report design file by default required for the report viewer control to display the report? What is the complexity involved in creating such design files on your own?? Can you shed some light on these points ?

    Thanks

    Problem viewing report based on analysis services

    I am using using some code which Implements IReportServerCredentials (see
    the object below) to pass credentials to a non local report server. This
    works fine and my reportviewer can get it's report from a non local server.
    When the report uses Analysis Services it displays the parameters part of
    the report viewer so I know it is getting as far as the report server but
    when I press view report I doesn't display anything, not even an error. I
    have tried adding the user I am logging as to the roles within the analysis
    Services project it is based on but with no luck. I have included the code
    in case anyone finds it helpful. Can anyone help?
    Dim cred As New ReportServerCredentials("username", "password", "domain")
    ReportViewer1.ServerReport.ReportServerCredentials = cred
    Imports Microsoft.VisualBasic
    Imports Microsoft.Reporting.WebForms
    Imports System.Net
    Public Class reportingservices
    End Class
    <Serializable()> _
    Public Class ReportServerCredentials
    Implements IReportServerCredentials
    Private _userName As String
    Private _password As String
    Private _domain As String
    Public Sub New(ByVal userName As String, ByVal password As String, ByVal
    domain As String)
    _userName = userName
    _password = password
    _domain = domain
    End Sub
    Public ReadOnly Property ImpersonationUser() As
    System.Security.Principal.WindowsIdentity Implements
    Microsoft.Reporting.WebForms.IReportServerCredentials.ImpersonationUser
    Get
    Return Nothing
    End Get
    End Property
    Public ReadOnly Property NetworkCredentials() As ICredentials Implements
    Microsoft.Reporting.WebForms.IReportServerCredentials.NetworkCredentials
    Get
    Return New NetworkCredential(_userName, _password, _domain)
    End Get
    End Property
    Public Function GetFormsCredentials(ByRef authCookie As System.Net.Cookie,
    ByRef userName As String, ByRef password As String, ByRef authority As
    String) As Boolean Implements
    Microsoft.Reporting.WebForms.IReportServerCredentials.GetFormsCredentials
    userName = _userName
    password = _password
    authority = _domain
    Return Nothing
    End Function
    End ClassIn this instance are you trying to access the report in the following
    situation:
    client accessing report (machine1) -> Report Server (machine 2) -> Analysis
    Services (machine 3)?
    If so then it is most likely a kerberos authentication issue due to the
    "double hop" you are experiencing.
    For more information on enabling this check the following article:
    http://support.microsoft.com/kb/917409/en-us
    SQL Server Developer Support Engineer
    "Fresno Bob" wrote:
    > I am using using some code which Implements IReportServerCredentials (see
    > the object below) to pass credentials to a non local report server. This
    > works fine and my reportviewer can get it's report from a non local server.
    > When the report uses Analysis Services it displays the parameters part of
    > the report viewer so I know it is getting as far as the report server but
    > when I press view report I doesn't display anything, not even an error. I
    > have tried adding the user I am logging as to the roles within the analysis
    > Services project it is based on but with no luck. I have included the code
    > in case anyone finds it helpful. Can anyone help?
    > Dim cred As New ReportServerCredentials("username", "password", "domain")
    > ReportViewer1.ServerReport.ReportServerCredentials = cred
    >
    > Imports Microsoft.VisualBasic
    > Imports Microsoft.Reporting.WebForms
    > Imports System.Net
    >
    >
    > Public Class reportingservices
    > End Class
    >
    > <Serializable()> _
    > Public Class ReportServerCredentials
    > Implements IReportServerCredentials
    > Private _userName As String
    > Private _password As String
    > Private _domain As String
    > Public Sub New(ByVal userName As String, ByVal password As String, ByVal
    > domain As String)
    > _userName = userName
    > _password = password
    > _domain = domain
    > End Sub
    > Public ReadOnly Property ImpersonationUser() As
    > System.Security.Principal.WindowsIdentity Implements
    > Microsoft.Reporting.WebForms.IReportServerCredentials.ImpersonationUser
    > Get
    > Return Nothing
    > End Get
    > End Property
    > Public ReadOnly Property NetworkCredentials() As ICredentials Implements
    > Microsoft.Reporting.WebForms.IReportServerCredentials.NetworkCredentials
    > Get
    > Return New NetworkCredential(_userName, _password, _domain)
    > End Get
    > End Property
    > Public Function GetFormsCredentials(ByRef authCookie As System.Net.Cookie,
    > ByRef userName As String, ByRef password As String, ByRef authority As
    > String) As Boolean Implements
    > Microsoft.Reporting.WebForms.IReportServerCredentials.GetFormsCredentials
    > userName = _userName
    > password = _password
    > authority = _domain
    > Return Nothing
    > End Function
    > End Class
    >
    >

    Problem Viewing Databases in Enterprise Manager

    I am using SQL Server 7.0 desktop version. I have a remote server registered in SQL Enterprise Manager. I can see the server itself and the main folders under it such as Databases, Management, Data Transformation Services, Security, and Support Services. However, when I click on the plus sign next to databases or try to view the databases it comes up "(No Items)". I am set up as a owner of one of the databases on this machine and I think I have access to all databases in this machine. Is there anything I can do to solve this problem?
    I am not having this problem with any other registered SQL servers.I made sure the Show system databases and system object box was checked. It is checked. I still can not see anything.
    -- anonymous@.discussions.microsoft.com wrote: --
    Not sure if this will solve your problem, but give it a
    try:
    Right click on server name, select Edit sql server
    registration properties and check "Show system databases
    and system objects" box.
    This should atleast show you master and other system
    databases, if nothing else is wrong.
    >--Original Message--
    >>I am using SQL Server 7.0 desktop version. I have a
    remote server registered in SQL Enterprise Manager. I can
    see the server itself and the main folders under it such
    as Databases, Management, Data Transformation Services,
    Security, and Support Services. However, when I click on
    the plus sign next to databases or try to view the
    databases it comes up "(No Items)". I am set up as a
    owner of one of the databases on this machine and I think
    I have access to all databases in this machine. Is there
    anything I can do to solve this problem?
    >>I am not having this problem with any other registered
    SQL servers.
    >.
    >