Problem with BorderStyle while Exporting to PDF

Hi,
I have lines of BoderStyle: Dotted, BorderWidth: 0.5pt in my report
When I preview it and print it I get the dotted lines
But if I export the same report to PDF and then print I get Dashed lines
instead of Dotted Lines
It's very important that I get Dotted lines.
Can Someone Help me with this
Thanks in Advance
PonnurangamThis is a known issue that will be addressed in a future release.
Unfortunately I do not have a work around to suggest you.
Anyone else?
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ponnurangam" <ponnurangam@.trellisys.net> wrote in message
news:OL1Dft%23nEHA.744@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have lines of BoderStyle: Dotted, BorderWidth: 0.5pt in my report
> When I preview it and print it I get the dotted lines
> But if I export the same report to PDF and then print I get Dashed lines
> instead of Dotted Lines
> It's very important that I get Dotted lines.
> Can Someone Help me with this
> Thanks in Advance
> Ponnurangam
>

Problem with accessing stored procedure in the report

Hi,

I am new to Sql Server 2005 Reporitng Services. I created a report in BI and used stored procedure as a dataset. When I run the report in preview mode it works fine and when I run it in report server/report manager, I am getting the following error:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'dsetBranch'. (rsErrorExecutingCommand)

Could not find stored procedure 'stpBranch'.

But I have this procedure in the db and it runs fine in the query analyzer and the query builder window in report project. When I refresh the page in Report manager, I am getting this error.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.] System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753715 System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +102 Microsoft.Reporting.WebForms.ReportAreaPageOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +149 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

I have changed the dataset from procedure to a sql string and the report is working fine everywhere. But I have a business requirement that I need to use a stored procedure.

I am not sure why I am getting this error and I greatly appreciate any help.

Thanks

ngk,

I have seen this before. Are you using any schema namespaces in your stored procedure name.

Such as HumanResources.GetAllEmployees instead of the old default of dbo.GetAllEmployees.

If so are you also running your stored procedures in Query Analyser as the "SAME" user that your Report Datasource uses.
Pay close attention to these details...

I have seen where 1 sql user has the default schema set to HumanResources and the stored procedure call is made such as exec GetAllEmployees instead of
exec HumanResources.GetAllEmployees.

In this situation any user that makes the first call (exec GetAllEmployees ) and has the default schema of HumanResources will succeed.
Any user that does not have this default will return an error because it is looking for dbo.GetAllEmployees and this may not exist.

Hope this helps.. if not please provide more details on what users you are using and the exact call you are making for the stored procedure.

|||

Hi Bret,

Thanks for the info. I am not using any schema namespaces in my stored procedures. I actually got this error when I tried to connect to a remote sql server. Now I have installed developer editon on my local machine and I have reporting services also on my local machine. I have been able to connect to the strored procedures and deploy the reports to the local report server and view the reports without any problems. I am not sure whether I may have to face the same issue when the reports are deployed to the remote SQL DB and Reporting Services production servers.

Thanks

Problem with accessing stored procedure in the report

Hi,

I am new to Sql Server 2005 Reporitng Services. I created a report in BI and used stored procedure as a dataset. When I run the report in preview mode it works fine and when I run it in report server/report manager, I am getting the following error:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'dsetBranch'. (rsErrorExecutingCommand)

Could not find stored procedure 'stpBranch'.

But I have this procedure in the db and it runs fine in the query analyzer and the query builder window in report project. When I refresh the page in Report manager, I am getting this error.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.] System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753715 System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +102 Microsoft.Reporting.WebForms.ReportAreaPageOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +149 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

I have changed the dataset from procedure to a sql string and the report is working fine everywhere. But I have a business requirement that I need to use a stored procedure.

I am not sure why I am getting this error and I greatly appreciate any help.

Thanks

ngk,

I have seen this before. Are you using any schema namespaces in your stored procedure name.

Such as HumanResources.GetAllEmployees instead of the old default of dbo.GetAllEmployees.

If so are you also running your stored procedures in Query Analyser as the "SAME" user that your Report Datasource uses.
Pay close attention to these details...

I have seen where 1 sql user has the default schema set to HumanResources and the stored procedure call is made such as exec GetAllEmployees instead of
exec HumanResources.GetAllEmployees.

In this situation any user that makes the first call (exec GetAllEmployees ) and has the default schema of HumanResources will succeed.
Any user that does not have this default will return an error because it is looking for dbo.GetAllEmployees and this may not exist.

Hope this helps.. if not please provide more details on what users you are using and the exact call you are making for the stored procedure.

|||

Hi Bret,

Thanks for the info. I am not using any schema namespaces in my stored procedures. I actually got this error when I tried to connect to a remote sql server. Now I have installed developer editon on my local machine and I have reporting services also on my local machine. I have been able to connect to the strored procedures and deploy the reports to the local report server and view the reports without any problems. I am not sure whether I may have to face the same issue when the reports are deployed to the remote SQL DB and Reporting Services production servers.

Thanks

Problem with accessing stored procedure in the report

Hi,

I am new to Sql Server 2005 Reporitng Services. I created a report in BI and used stored procedure as a dataset. When I run the report in preview mode it works fine and when I run it in report server/report manager, I am getting the following error:

An error has occurred during report processing. (rsProcessingAborted)

Query execution failed for data set 'dsetBranch'. (rsErrorExecutingCommand)

Could not find stored procedure 'stpBranch'.

But I have this procedure in the db and it runs fine in the query analyzer and the query builder window in report project. When I refresh the page in Report manager, I am getting this error.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[FormatException: Input string was not in a correct format.]

System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753715

System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +102

Microsoft.Reporting.WebForms.ReportAreaPageOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +149

Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75

System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

I have changed the dataset from procedure to a sql string and the report is working fine everywhere. But I have a business requirement that I need to use a stored procedure.

I am not sure why I am getting this error and I greatly appreciate any help.

Thanks

ngk,

I have seen this before. Are you using any schema namespaces in your stored procedure name.

Such as HumanResources.GetAllEmployees instead of the old default of dbo.GetAllEmployees.

If so are you also running your stored procedures in Query Analyser as the "SAME" user that your Report Datasource uses.
Pay close attention to these details...

I have seen where 1 sql user has the default schema set to HumanResources and the stored procedure call is made such as exec GetAllEmployees instead of
exec HumanResources.GetAllEmployees.

In this situation any user that makes the first call (exec GetAllEmployees ) and has the default schema of HumanResources will succeed.
Any user that does not have this default will return an error because it is looking for dbo.GetAllEmployees and this may not exist.

Hope this helps.. if not please provide more details on what users you are using and the exact call you are making for the stored procedure.

|||

Hi Bret,

Thanks for the info. I am not using any schema namespaces in my stored procedures. I actually got this error when I tried to connect to a remote sql server. Now I have installed developer editon on my local machine and I have reporting services also on my local machine. I have been able to connect to the strored procedures and deploy the reports to the local report server and view the reports without any problems. I am not sure whether I may have to face the same issue when the reports are deployed to the remote SQL DB and Reporting Services production servers.

Thanks

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!
>