I am using the ReportViewer control for Windows Forms, and I would like to be able let my users copy text from the report. Is there any way to configure this? At the moment, the text is not selectable.
Thanks,
Erick
I understand, thanks. I've been getting a lot of pushback from users on this issue, so I'm glad to hear it's on your radar screen.
Thanks,
Erick
Ok, I have this up and running thanks to the help of lots of users in this forum (Thank You again)
I deployed some reports, and everything looks fine, however to add another twist to this, I would like the website to look prettier, by adding something like a welcome page,and some folders and such.
Does anyone have any ideas on how to do that ? DO you have any material or a website, where I can get some info ?
Thanks
Which site? The Report Manager? It supports limited costomization through CSS styles (see C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\Styles)
We have report server installed for intranet use only. We are using actice directory users for role assignments.
New requirement is to allow access to reports via internet (www.xyz.com) and we are not going to use Microsoft Active Directory Users Account.
What would we need to do to accomplish the above? What additional steps would you recommend?
Thanks
Did you check Tudor's blog article (http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx) and its MSDN links?
-- Robert
|||Is there any BLOG for SQL Server 2000? If we install Report Manager facing internet then should we must do forms authentication? or is there any alternative to this?
Thanks,
I'm a developer at a medium-sized installation using ReportServer 2005. There's a problem that occurs for some users and not others. After the ReportServer 2005 report has been generated, the user clicks the Print icon. The print dialog comes up; when they click the OK button on the Print dialog, the screen goes black and their machine reboots.
We've then gone to install the latest Microsoft updates on their machine, to no avail.
After the reboot, they can print from, e.g., Microsoft Word or other applications, but they crash the OS when they print from the ReportServer 2005 report.
I know the first time you print from ReportServer, it installs some software on your machine. I don't know if the problem is related to this.
Any ideas would be appreciated.
Charlie
Hi,
I got the same problem on 1 paticular machine ! Everytime you click the print-button --> os blue screen crash !?
|||Probably you've installed Microsoft Patch KB925902.
Remove it from your system and retry...
I've had the same problem printing with Reporting Service 2000.
Bye
--
|||Fabius...
Thanks for the hint about KB925902. However, this doesn't seem to apply to Report Server 2005. All our users have this patch, but some workstations abort on the Report print and some don't. But it was a good suggestion.
Thanks,
Charlie
|||Are you printing to HP printers that have a PCL6 driver installed?
We have noted the same issue, based on testing the PCL5 driver may work better, as a temporary fix.
|||MLane...
This was a great idea. Most of the printers here are HP. There's one Xerox printer. Report Server always prints correctly to the Xerox, but fails with the HP printers for some users and not others. Still doesn't explain why some users work and some don't, but it's a start and a good workaround.
Charlie
|||I had a number of calls on this problem too. The KB925902 patch seems to be logical, due to the timing of it all, but did you remove it from clients or from the server?
|||Mike...
We never actually removed KB925902 from any machines. ALL of our machines have this patch. Report Server printing crashes only on some client machines and not on others.
There also seems to be a correlation as to which printer driver is used. HP printer drivers seem to crash; Xerox printer drivers seem to be OK.
This problem seems to be client-side since some machines never crash and some always crash. I've opened a problem ticket with Microsoft on this.
Thanks,
Charlie
|||I just received this hotfix information from Microsoft.
WARNING: This fix is not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing.If you would like confirmation that this fix is designed to address your specific problem, or if you would like to confirm whether there are any special compatibility or installation issues associated with this fix, you are encouraged to speak to a Support Professional in Product Support Services.
The package is password protected so be sure to enter the appropriate password for each package.To ensure the right password is provided cut and paste the password from this mail.
NOTE: Passwords expire every 7 days so download the package within that period to insure you can extract the files.If you receive two passwords it means you are receiving the fix during a password change cycle.Use the second password if you download after the indicated password change date.
Package:
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%202000/sp5/Fix200463/2195/free/307588_ENU_i386_zip.exe)
Password: c3A@.XrLB@.
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%20XP/sp3/Fix200284/2600/free/307536_ENU_i386_zip.exe)
Password: #m6#s5SJT
Password Changes On: 04/18/2007
Next Password: 7@.^V[*O
NOTE: Be sure to include all text between '(' and')' when navigating to this hot fix location!
|||Did you report this to the SQL Server feedback center? (https://connect.microsoft.com/SQLServer)
What is the ID of the ticket, I'd like to keep track of what MS have to say.
|||Yes, I just reported it. Case number is SRX 070 416 601 142. It's not yet resolved as I write this.
Charlie
|||Mike...
Thanks for this hotfix info. I downloaded the two files. I can't seem to find information about KB935843 at Microsoft or Google. I can't just install these files without more information about what they do. But I'll hold on to them.
Thanks,
Charlie
|||I have a Case number also SRX070416602399.
It seems that the cause was applying Windows Update patch KB925902 and if the client has a HP PCL6 printer driver configured. We were successful in duplicating this error on a VM running XP, applied the XP hotfix and it corrected the stop error from happening.
|||The problem with ReportServer crashing the client box while printing did indeed appear to be associated with the PCL6 printer drivers. When they were uninstalled from the client box and replaced with the PCL5 drivers, all seems OK. Something with PCL6 and ReportServer 2005.
Charlie
|||Check out this for discussion on the problem, hot fixes do work....as well as changing back to PCL5
http://support.microsoft.com/kb/935843
Denver
I'm a developer at a medium-sized installation using ReportServer 2005. There's a problem that occurs for some users and not others. After the ReportServer 2005 report has been generated, the user clicks the Print icon. The print dialog comes up; when they click the OK button on the Print dialog, the screen goes black and their machine reboots.
We've then gone to install the latest Microsoft updates on their machine, to no avail.
After the reboot, they can print from, e.g., Microsoft Word or other applications, but they crash the OS when they print from the ReportServer 2005 report.
I know the first time you print from ReportServer, it installs some software on your machine. I don't know if the problem is related to this.
Any ideas would be appreciated.
Charlie
Hi,
I got the same problem on 1 paticular machine ! Everytime you click the print-button --> os blue screen crash !?
|||Probably you've installed Microsoft Patch KB925902.
Remove it from your system and retry...
I've had the same problem printing with Reporting Service 2000.
Bye
--
|||Fabius...
Thanks for the hint about KB925902. However, this doesn't seem to apply to Report Server 2005. All our users have this patch, but some workstations abort on the Report print and some don't. But it was a good suggestion.
Thanks,
Charlie
|||Are you printing to HP printers that have a PCL6 driver installed?
We have noted the same issue, based on testing the PCL5 driver may work better, as a temporary fix.
|||MLane...
This was a great idea. Most of the printers here are HP. There's one Xerox printer. Report Server always prints correctly to the Xerox, but fails with the HP printers for some users and not others. Still doesn't explain why some users work and some don't, but it's a start and a good workaround.
Charlie
|||I had a number of calls on this problem too. The KB925902 patch seems to be logical, due to the timing of it all, but did you remove it from clients or from the server?
|||Mike...
We never actually removed KB925902 from any machines. ALL of our machines have this patch. Report Server printing crashes only on some client machines and not on others.
There also seems to be a correlation as to which printer driver is used. HP printer drivers seem to crash; Xerox printer drivers seem to be OK.
This problem seems to be client-side since some machines never crash and some always crash. I've opened a problem ticket with Microsoft on this.
Thanks,
Charlie
|||I just received this hotfix information from Microsoft.
WARNING: This fix is not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing.If you would like confirmation that this fix is designed to address your specific problem, or if you would like to confirm whether there are any special compatibility or installation issues associated with this fix, you are encouraged to speak to a Support Professional in Product Support Services.
The package is password protected so be sure to enter the appropriate password for each package.To ensure the right password is provided cut and paste the password from this mail.
NOTE: Passwords expire every 7 days so download the package within that period to insure you can extract the files.If you receive two passwords it means you are receiving the fix during a password change cycle.Use the second password if you download after the indicated password change date.
Package:
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%202000/sp5/Fix200463/2195/free/307588_ENU_i386_zip.exe)
Password: c3A@.XrLB@.
--
KB Article Number(s): 935843
Language: English
Platform: i386
Location: (http://hotfixv4.microsoft.com/Windows%20XP/sp3/Fix200284/2600/free/307536_ENU_i386_zip.exe)
Password: #m6#s5SJT
Password Changes On: 04/18/2007
Next Password: 7@.^V[*O
NOTE: Be sure to include all text between '(' and')' when navigating to this hot fix location!
|||Did you report this to the SQL Server feedback center? (https://connect.microsoft.com/SQLServer)
What is the ID of the ticket, I'd like to keep track of what MS have to say.
|||Yes, I just reported it. Case number is SRX 070 416 601 142. It's not yet resolved as I write this.
Charlie
|||Mike...
Thanks for this hotfix info. I downloaded the two files. I can't seem to find information about KB935843 at Microsoft or Google. I can't just install these files without more information about what they do. But I'll hold on to them.
Thanks,
Charlie
|||I have a Case number also SRX070416602399.
It seems that the cause was applying Windows Update patch KB925902 and if the client has a HP PCL6 printer driver configured. We were successful in duplicating this error on a VM running XP, applied the XP hotfix and it corrected the stop error from happening.
|||The problem with ReportServer crashing the client box while printing did indeed appear to be associated with the PCL6 printer drivers. When they were uninstalled from the client box and replaced with the PCL5 drivers, all seems OK. Something with PCL6 and ReportServer 2005.
Charlie
|||Check out this for discussion on the problem, hot fixes do work....as well as changing back to PCL5
http://support.microsoft.com/kb/935843
Denver
sql
but we have already solved the problem by adding missed <identity impersonate="true" /> line to C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\web.config. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetAP05.asp for details.
Hi,
I have a very weird and frustrating problem at a customer. Since two months we are busy developing a report model, so users are able to create their own reports using the reportbuilder.
Suddenly the 1:n relations seem to be screwed! If I have a simple relation between entities, like a customer can have optional multiple invoices and a invoice has always one customer..
When in reportbuilder I select the customername, invoicenumber and #Invoices, then I expect there is only one invoice per invoicenumber. (When I select this in a query myself it is the truth...) But, the reportbuilder gives 2 as a result. This suddenly happens to all my 1:n roles.
It's not only in the #invoices fields, even when i select invoice amount this amount is being multiplied by 2.
I opened a backup of my project from one month ago, with the same relation in it and try to make the same report and it gave me the right results. But ofcourse I don't want to waste a month works, so I need to get this model working!
HELP!!!!
Thanks in advance
Julian
My fault... If i selected the relation entity and tested the results I would have seen each relation is mentioned twice.