|
|
You're in the
sql server reporting services
group:Service Pack 2 Experience?
sql server reporting services:
OK? Have you gotten the web parts working? Seen any *shudder* regressions in functionality? -- Brian Welcker Group Program Manager Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights.
[quoted text, click to view]
Brian Welcker wrote: > For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? Hi Brian, 1. Is it a straightforward upgrade applying the patch without having to worry about key management and backing up this or backing up that? 2. Have you been in touch with Microsoft to see about whatever fix is necessary that fixes Win2003 SP1 that broke Reporting Services? Thanks, GeoSynch
For any patch, I would recommend backing up your database and encryption
key, not matter how straightforward it is. What is the specific error you are getting on Win2K3 SP1? We have not gotten a consistent repro in-house. And what is the identity of the AppPool used for RS? Anything else unique about the box? -- Brian Welcker Group Program Manager Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "GeoSynch" <SpamSlayed@Casablanca.com> wrote in message news:%23FsZ82RSFHA.4028@tk2msftngp13.phx.gbl... > Brian Welcker wrote: > >> For those of you who have downloaded SP2, how is it going? Is print >> working OK? Have you gotten the web parts working? Seen any *shudder* >> regressions in functionality? > > Hi Brian, > > 1. Is it a straightforward upgrade applying the patch without having to > worry about > key management and backing up this or backing up that? > > 2. Have you been in touch with Microsoft to see about whatever fix is > necessary > that fixes Win2003 SP1 that broke Reporting Services? > > > Thanks, > > GeoSynch >
Brian hi,
I was waiting for the SP2 because of a web archive subscription e-mailing problem(because of the error data line too long for the e-mail server?),and now it seems that the problem is solved. We had a Windows 2003 SP1 authentication problem and this is overcome with basic authentication-normally windows authentication fails because of the use of proxy server to access the internet. I think the Windows 2003 authentication problem("The request failed with HTTP status 401: Unauthorized") must be resolved in some way. Reporting Services was good when it was first published and now it is becoming better everyday. Best regards,
Thanks for the feedback. Good to know that it has resolved some issues for
you. -- Brian Welcker Group Program Manager Microsoft SQL Server [quoted text, click to view] "Alpay UTKU" <alpayutku@hotmail.com> wrote in message news:d080ad3d.0504242227.5c18ada4@posting.google.com... > Brian hi, > I was waiting for the SP2 because of a web archive subscription > e-mailing problem(because of the error data line too long for the > e-mail server?),and now it seems that the problem is solved. > > We had a Windows 2003 SP1 authentication problem and this is overcome > with basic authentication-normally windows authentication fails > because of > the use of proxy server to access the internet. > I think the Windows 2003 authentication > problem("The request failed with HTTP status 401: Unauthorized") must > be > resolved in some way. > > Reporting Services was good when it was first published and now it > is becoming better everyday. > > Best regards, > > Alpay
We had no problems installing the service pack, but our reports did not print
as they had in PDF Format. Each page was slightly wider than intended (a page 8.5 x 11 portrait with .5 inch margins and a 7.5 in wide body did not print on one page). When we reduced the margins, it printed correctly. Am I doing something wrong with the page setup? David [quoted text, click to view] "Brian Welcker [MS]" wrote:
> Thanks for the feedback. Good to know that it has resolved some issues for > you. > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server > > "Alpay UTKU" <alpayutku@hotmail.com> wrote in message > news:d080ad3d.0504242227.5c18ada4@posting.google.com... > > Brian hi, > > I was waiting for the SP2 because of a web archive subscription > > e-mailing problem(because of the error data line too long for the > > e-mail server?),and now it seems that the problem is solved. > > > > We had a Windows 2003 SP1 authentication problem and this is overcome > > with basic authentication-normally windows authentication fails > > because of > > the use of proxy server to access the internet. > > I think the Windows 2003 authentication > > problem("The request failed with HTTP status 401: Unauthorized") must > > be > > resolved in some way. > > > > Reporting Services was good when it was first published and now it > > is becoming better everyday. > > > > Best regards, > > > > Alpay > >
Brian,
we did not encounter any problems during the SP2 install on our Win 2003 Server. I was waiting for this service pack because I needed a fix for the KB 875518 - Width of a list that contains an embedded matrix grows unexpectedly... The service pack seems to solve the problem but only if there is a single matrix embedded in the list. However, I have also a subreport embedded in the same list that shows the matrix totals; this subreport is nothing but another matrix. In this case the list still grows unexpectedly, producing one extra blank page for each report page. Any suggestions? Thanks, Alex Korygin. [quoted text, click to view] "Brian Welcker" wrote:
> For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
There may be slight differences between print (which is GDI based) and PDF.
One of the things is that printers have 'unprintable areas' that might cause some issues. Are you sure you don't have anything that grows horizontally? If you can repro it with a small sample, we can take a look. -- Brian Welcker Group Program Manager Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "David Siebert" <DavidSiebert@discussions.microsoft.com> wrote in message news:274F5104-9F31-4E32-BD4F-A40FB2F55B06@microsoft.com... > We had no problems installing the service pack, but our reports did not > as they had in PDF Format. Each page was slightly wider than intended (a > page 8.5 x 11 portrait with .5 inch margins and a 7.5 in wide body did not > print on one page). When we reduced the margins, it printed correctly. > Am I > doing something wrong with the page setup? > > David > > "Brian Welcker [MS]" wrote: > >> Thanks for the feedback. Good to know that it has resolved some issues >> for >> you. >> >> -- >> Brian Welcker >> Group Program Manager >> Microsoft SQL Server >> >> "Alpay UTKU" <alpayutku@hotmail.com> wrote in message >> news:d080ad3d.0504242227.5c18ada4@posting.google.com... >> > Brian hi, >> > I was waiting for the SP2 because of a web archive subscription >> > e-mailing problem(because of the error data line too long for the >> > e-mail server?),and now it seems that the problem is solved. >> > >> > We had a Windows 2003 SP1 authentication problem and this is overcome >> > with basic authentication-normally windows authentication fails >> > because of >> > the use of proxy server to access the internet. >> > I think the Windows 2003 authentication >> > problem("The request failed with HTTP status 401: Unauthorized") must >> > be >> > resolved in some way. >> > >> > Reporting Services was good when it was first published and now it >> > is becoming better everyday. >> > >> > Best regards, >> > >> > Alpay >> >> >>
Brian we are having a problem with client side printing feature printing
blank page at end of all reports. I'm not the only one as I noticed someone else had already posted regarding this issue. [quoted text, click to view] "Brian Welcker" wrote:
> For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
Okay, here's the simplest example I can come up with:
I create a new document, set the body to be 6.5in wide by 2in tall. The page size is 8.5in wide by 11in tall. I set all margins (top, bottom, left, right) to 1in. So, we now have a blank page. The print preview in VS displays the report as 1 blank page. When deployed and exported to PDF, it is one blank page. However, when you click the print button and preview or print the document using the sp2 client-side printing tool, it displays/prints 2 blank pages. Thanks for looking into this, and hopefully I'm just missing something basic. Please let me know if you find anything [quoted text, click to view] "Brian Welcker [MSFT]" wrote:
> There may be slight differences between print (which is GDI based) and PDF. > One of the things is that printers have 'unprintable areas' that might cause > some issues. Are you sure you don't have anything that grows horizontally? > If you can repro it with a small sample, we can take a look. > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "David Siebert" <DavidSiebert@discussions.microsoft.com> wrote in message > news:274F5104-9F31-4E32-BD4F-A40FB2F55B06@microsoft.com... > > We had no problems installing the service pack, but our reports did not > > as they had in PDF Format. Each page was slightly wider than intended (a > > page 8.5 x 11 portrait with .5 inch margins and a 7.5 in wide body did not > > print on one page). When we reduced the margins, it printed correctly. > > Am I > > doing something wrong with the page setup? > > > > David > > > > "Brian Welcker [MS]" wrote: > > > >> Thanks for the feedback. Good to know that it has resolved some issues > >> for > >> you. > >> > >> -- > >> Brian Welcker > >> Group Program Manager > >> Microsoft SQL Server > >> > >> "Alpay UTKU" <alpayutku@hotmail.com> wrote in message > >> news:d080ad3d.0504242227.5c18ada4@posting.google.com... > >> > Brian hi, > >> > I was waiting for the SP2 because of a web archive subscription > >> > e-mailing problem(because of the error data line too long for the > >> > e-mail server?),and now it seems that the problem is solved. > >> > > >> > We had a Windows 2003 SP1 authentication problem and this is overcome > >> > with basic authentication-normally windows authentication fails > >> > because of > >> > the use of proxy server to access the internet. > >> > I think the Windows 2003 authentication > >> > problem("The request failed with HTTP status 401: Unauthorized") must > >> > be > >> > resolved in some way. > >> > > >> > Reporting Services was good when it was first published and now it > >> > is becoming better everyday. > >> > > >> > Best regards, > >> > > >> > Alpay > >> > >> > >> > >
Brian,
here is another problem with SP2. We have a report that contains two matrixes: one after another. These two must really look like a single table, so we set the height of header rows to "0in" manually in rdl file for the second matrix. It used to work with SP1, but now if I render report as HTML using URL access I can see these hidden rows (note that GDI+ and PDF rendering look fine). Another odd behavior is that the second matrix gets suppressed (that is, I can only see 3 columns out of 7) the first time I render the report, but after I click Refresh button on the viewer's toolbar it renders all the columns. :( Is there any way to hide the matrix headers now? Regards, Alex Korygin. [quoted text, click to view] "Brian Welcker" wrote:
> For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
Brian,
we used to hide matrix headers by setting the row hight to '0in' manually in rdl files. It worked pretty well until SP2 installation and now it is broken. If I render report as HTML via URL access I can see all hidden rows (note that GDI+ and PDF renderings still work fine). So, how do we hide the matrix rows now? Thanks, Alex Korygin. [quoted text, click to view] "Brian Welcker" wrote:
> For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
I'm logged on from home so I don't have a server handy. I wonder if it is a
rounding error. Can you set your margins to be 1.9" wide and see if you see this? And can you try exporting to TIFF and see if it repros? Finally, maybe try another printer and see if it repros. -- Brian Welcker Group Program Manager Microsoft SQL Server This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "David Siebert" <DavidSiebert@discussions.microsoft.com> wrote in message news:B8D570A9-16E8-4277-89A6-9869714699F1@microsoft.com... > Okay, here's the simplest example I can come up with: > > I create a new document, set the body to be 6.5in wide by 2in tall. The > page size is 8.5in wide by 11in tall. I set all margins (top, bottom, > left, > right) to 1in. So, we now have a blank page. The print preview in VS > displays the report as 1 blank page. When deployed and exported to PDF, > it > is one blank page. However, when you click the print button and preview > or > print the document using the sp2 client-side printing tool, it > displays/prints 2 blank pages. > > Thanks for looking into this, and hopefully I'm just missing something > basic. Please let me know if you find anything > > "Brian Welcker [MSFT]" wrote: > >> There may be slight differences between print (which is GDI based) and >> PDF. >> One of the things is that printers have 'unprintable areas' that might >> cause >> some issues. Are you sure you don't have anything that grows >> horizontally? >> If you can repro it with a small sample, we can take a look. >> >> -- >> Brian Welcker >> Group Program Manager >> Microsoft SQL Server Reporting Services >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> "David Siebert" <DavidSiebert@discussions.microsoft.com> wrote in message >> news:274F5104-9F31-4E32-BD4F-A40FB2F55B06@microsoft.com... >> > We had no problems installing the service pack, but our reports did not >> > as they had in PDF Format. Each page was slightly wider than intended >> > (a >> > page 8.5 x 11 portrait with .5 inch margins and a 7.5 in wide body did >> > not >> > print on one page). When we reduced the margins, it printed correctly. >> > Am I >> > doing something wrong with the page setup? >> > >> > David >> > >> > "Brian Welcker [MS]" wrote: >> > >> >> Thanks for the feedback. Good to know that it has resolved some issues >> >> for >> >> you. >> >> >> >> -- >> >> Brian Welcker >> >> Group Program Manager >> >> Microsoft SQL Server >> >> >> >> "Alpay UTKU" <alpayutku@hotmail.com> wrote in message >> >> news:d080ad3d.0504242227.5c18ada4@posting.google.com... >> >> > Brian hi, >> >> > I was waiting for the SP2 because of a web archive subscription >> >> > e-mailing problem(because of the error data line too long for the >> >> > e-mail server?),and now it seems that the problem is solved. >> >> > >> >> > We had a Windows 2003 SP1 authentication problem and this is >> >> > overcome >> >> > with basic authentication-normally windows authentication fails >> >> > because of >> >> > the use of proxy server to access the internet. >> >> > I think the Windows 2003 authentication >> >> > problem("The request failed with HTTP status 401: Unauthorized") >> >> > must >> >> > be >> >> > resolved in some way. >> >> > >> >> > Reporting Services was good when it was first published and now it >> >> > is becoming better everyday. >> >> > >> >> > Best regards, >> >> > >> >> > Alpay >> >> >> >> >> >> >> >> >>
I'll see if we can repro this here.
-- Brian Welcker Group Program Manager Microsoft SQL Server This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Alex Korygin" <AlexKorygin@discussions.microsoft.com> wrote in message news:21BD9AD7-0C31-4562-8A6C-EB6AC9E29D10@microsoft.com... > Brian, > > here is another problem with SP2. We have a report that contains two > matrixes: one after another. These two must really look like a single > table, > so we set the height of header rows to "0in" manually in rdl file for the > second matrix. It used to work with SP1, but now if I render report as > HTML > using URL access I can see these hidden rows (note that GDI+ and PDF > rendering look fine). Another odd behavior is that the second matrix gets > suppressed (that is, I can only see 3 columns out of 7) the first time I > render the report, but after I click Refresh button on the viewer's > toolbar > it renders all the columns. :( > > Is there any way to hide the matrix headers now? > > > Regards, > > Alex Korygin. > > > > > > "Brian Welcker" wrote: > >> For those of you who have downloaded SP2, how is it going? Is print >> working >> OK? Have you gotten the web parts working? Seen any *shudder* regressions >> in >> functionality? >> >> -- >> Brian Welcker >> Group Program Manager >> Microsoft SQL Server Reporting Services >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >>
Brian,
I tried printing my previous example on another printer, and obtained the same results (2 blank pages printed). I also exported it to TIFF and it displayed as 1 page (just like PDF and VS print preview). Changing the margins to 1.9in wide made all formats show 2 pages as it was an increase to the margins. If I change them to .9in, all formats (including client-side printing) show 1 page. This has been my solution to work around the problem for the time being. I am running RS sp2 (developer) on XP Pro sp1 with SQL 2003 sp3 (developer) all on the same machine. We've reproduced the same problem on another desktop running the same software configuration. People in this thread (http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=6cf61737-73a7-42ca-8b49-b2a488ed80ed) seem to be having similar problems. One person had all margins set to 0in but had the body set to the exact width of the page. This printed an extra page but was resolved by decreasing the width of the body to something less than the width of the printed page. Thanks so much for your help and concern. David Siebert [quoted text, click to view] "Brian Welcker [MS]" wrote:
> I'm logged on from home so I don't have a server handy. I wonder if it is a > rounding error. Can you set your margins to be 1.9" wide and see if you see > this? And can you try exporting to TIFF and see if it repros? Finally, maybe > try another printer and see if it repros. > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "David Siebert" <DavidSiebert@discussions.microsoft.com> wrote in message > news:B8D570A9-16E8-4277-89A6-9869714699F1@microsoft.com... > > Okay, here's the simplest example I can come up with: > > > > I create a new document, set the body to be 6.5in wide by 2in tall. The > > page size is 8.5in wide by 11in tall. I set all margins (top, bottom, > > left, > > right) to 1in. So, we now have a blank page. The print preview in VS > > displays the report as 1 blank page. When deployed and exported to PDF, > > it > > is one blank page. However, when you click the print button and preview > > or > > print the document using the sp2 client-side printing tool, it > > displays/prints 2 blank pages. > > > > Thanks for looking into this, and hopefully I'm just missing something > > basic. Please let me know if you find anything > > > > "Brian Welcker [MSFT]" wrote: > > > >> There may be slight differences between print (which is GDI based) and > >> PDF. > >> One of the things is that printers have 'unprintable areas' that might > >> cause > >> some issues. Are you sure you don't have anything that grows > >> horizontally? > >> If you can repro it with a small sample, we can take a look. > >> > >> -- > >> Brian Welcker > >> Group Program Manager > >> Microsoft SQL Server Reporting Services > >> > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> "David Siebert" <DavidSiebert@discussions.microsoft.com> wrote in message > >> news:274F5104-9F31-4E32-BD4F-A40FB2F55B06@microsoft.com... > >> > We had no problems installing the service pack, but our reports did not > >> > as they had in PDF Format. Each page was slightly wider than intended > >> > (a > >> > page 8.5 x 11 portrait with .5 inch margins and a 7.5 in wide body did > >> > not > >> > print on one page). When we reduced the margins, it printed correctly. > >> > Am I > >> > doing something wrong with the page setup? > >> > > >> > David > >> > > >> > "Brian Welcker [MS]" wrote: > >> > > >> >> Thanks for the feedback. Good to know that it has resolved some issues > >> >> for > >> >> you. > >> >> > >> >> -- > >> >> Brian Welcker > >> >> Group Program Manager > >> >> Microsoft SQL Server > >> >> > >> >> "Alpay UTKU" <alpayutku@hotmail.com> wrote in message > >> >> news:d080ad3d.0504242227.5c18ada4@posting.google.com... > >> >> > Brian hi, > >> >> > I was waiting for the SP2 because of a web archive subscription > >> >> > e-mailing problem(because of the error data line too long for the > >> >> > e-mail server?),and now it seems that the problem is solved. > >> >> > > >> >> > We had a Windows 2003 SP1 authentication problem and this is > >> >> > overcome > >> >> > with basic authentication-normally windows authentication fails > >> >> > because of > >> >> > the use of proxy server to access the internet. > >> >> > I think the Windows 2003 authentication > >> >> > problem("The request failed with HTTP status 401: Unauthorized") > >> >> > must > >> >> > be > >> >> > resolved in some way. > >> >> > > >> >> > Reporting Services was good when it was first published and now it > >> >> > is becoming better everyday. > >> >> > > >> >> > Best regards, > >> >> > > >> >> > Alpay > >> >> > >> >> > >> >> > >> > >> > >> > >
Should we anticipate any emergency releases to the service pack?
Has anyone run across the "Excel Missing Rows" issue?
[quoted text, click to view] "Alex Korygin" wrote:
> Brian, > > we used to hide matrix headers by setting the row hight to '0in' manually in > rdl files. It worked pretty well until SP2 installation and now it is broken. > If I render report as HTML via URL access I can see all hidden rows (note > that GDI+ and PDF renderings still work fine). So, how do we hide the matrix > rows now? > > Thanks, > > Alex Korygin. > > "Brian Welcker" wrote: > > > For those of you who have downloaded SP2, how is it going? Is print working > > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > > functionality? > > > > -- > > Brian Welcker > > Group Program Manager > > Microsoft SQL Server Reporting Services > > > > This posting is provided "AS IS" with no warranties, and confers no rights. > > > >
Brian,
Thank you for looking into this. After playing for sometime this morning I have been able to fix the problem. This behavior seems to occur if the matrix width exceeds the width of the report. In this case the matrix looks suppressed on the right side, but only the first time report is rendered. If I zoom in and out, or expand / collapse a report section, or go to a next page of the report – it renders correctly. So, I was able to fix my problem by reducing the matrix width. Nevertheless, I am still not able to hide the header rows. Thanks, Alex korygin. [quoted text, click to view] "Brian Welcker [MS]" wrote:
> I'll see if we can repro this here. > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Alex Korygin" <AlexKorygin@discussions.microsoft.com> wrote in message > news:21BD9AD7-0C31-4562-8A6C-EB6AC9E29D10@microsoft.com... > > Brian, > > > > here is another problem with SP2. We have a report that contains two > > matrixes: one after another. These two must really look like a single > > table, > > so we set the height of header rows to "0in" manually in rdl file for the > > second matrix. It used to work with SP1, but now if I render report as > > HTML > > using URL access I can see these hidden rows (note that GDI+ and PDF > > rendering look fine). Another odd behavior is that the second matrix gets > > suppressed (that is, I can only see 3 columns out of 7) the first time I > > render the report, but after I click Refresh button on the viewer's > > toolbar > > it renders all the columns. :( > > > > Is there any way to hide the matrix headers now? > > > > > > Regards, > > > > Alex Korygin. > > > > > > > > > > > > "Brian Welcker" wrote: > > > >> For those of you who have downloaded SP2, how is it going? Is print > >> working > >> OK? Have you gotten the web parts working? Seen any *shudder* regressions > >> in > >> functionality? > >> > >> -- > >> Brian Welcker > >> Group Program Manager > >> Microsoft SQL Server Reporting Services > >> > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> > >> > >
No, we have not found anything yet that would warrant this. Most of the
printing issues seem to be related to report settings or printer settings. I have not seen a specific case that I have been able to repro here. If someone has a simple repro that they think results in an error, we can give it a try. -- Brian Welcker Group Program Manager Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "Luke" <lukeguerrant@gmail.com> wrote in message news:1114524210.672333.129150@f14g2000cwb.googlegroups.com... > Should we anticipate any emergency releases to the service pack? >
I have the Windows 2003 authentication
problem("The request failed with HTTP status 401: Unauthorized") when calling a webservice from an asp.net application. Is there a resolution to this. -- Regards Toby Riley [quoted text, click to view] "Alpay UTKU" wrote:
> Brian hi, > I was waiting for the SP2 because of a web archive subscription > e-mailing problem(because of the error data line too long for the > e-mail server?),and now it seems that the problem is solved. > > We had a Windows 2003 SP1 authentication problem and this is overcome > with basic authentication-normally windows authentication fails > because of > the use of proxy server to access the internet. > I think the Windows 2003 authentication > problem("The request failed with HTTP status 401: Unauthorized") must > be > resolved in some way. > > Reporting Services was good when it was first published and now it > is becoming better everyday. > > Best regards, > > Alpay
If the Report Server is on a different server than your ASO.NEt application,
you are probably running into "double hop" issues. You can't marshal credentials from one server to another in Windows security without Kerberos delegation. -- Brian Welcker Group Program Manager Microsoft SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "TobyRiley" <TobyRiley@discussions.microsoft.com> wrote in message news:9B3B0A5D-8BA0-4537-B394-DEF876BDC06A@microsoft.com... >I have the Windows 2003 authentication > problem("The request failed with HTTP status 401: Unauthorized") when > calling a webservice from an asp.net application. > > Is there a resolution to this. > > -- > Regards > > Toby Riley > > > "Alpay UTKU" wrote: > >> Brian hi, >> I was waiting for the SP2 because of a web archive subscription >> e-mailing problem(because of the error data line too long for the >> e-mail server?),and now it seems that the problem is solved. >> >> We had a Windows 2003 SP1 authentication problem and this is overcome >> with basic authentication-normally windows authentication fails >> because of >> the use of proxy server to access the internet. >> I think the Windows 2003 authentication >> problem("The request failed with HTTP status 401: Unauthorized") must >> be >> resolved in some way. >> >> Reporting Services was good when it was first published and now it >> is becoming better everyday. >> >> Best regards, >> >> Alpay >>
Our SRS blew up on SP2. After installing, we started getting this:
"The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.6.54'. The expected version is 'C.0.6.51'. To continue, update the version of the report server database and verify access rights. (rsInvalidReportServerDatabase)" We found information at this link http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSerrors/htm/Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings.resources.Strings_rsInvalidReportServerDatabase.asp But couldn't figure out how to use rs.exe to upgrade the database. We've tried uninstalling SRS and dropping the databases and going back to a standard, non-SP2 install and are still getting errors - but with different version numbers this time. Any ideas? [quoted text, click to view] "Brian Welcker" wrote:
> For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
We recently installed SP2 in order to resolve some of the issues with
matrices and Excel exporting. Although some of the issues were addressed, it looks like it wasn't fully resolved: For instance: I have a report that has a header table with two matrices (one placed on top of the other) that check a parameter passed in from the stored proc to determine which matrix to show/hide. Ex: (in matrix properties) Visibility.Hidden = First(Fields!ShowMatrix1.Value, "MyDataSet") ------------------------------------------------------------------------ In Service Pack 1, the web screen looks correct (showing the correct matrix and hiding the other), however when I choose to export to Excel, Reporting Services displayed both matrices. In Service Pack 2, when I export to Excel, and the first matrix is displayed, everything's great (the first shows and the second is hidden). Unfortunately, when the second matrix is displayed (second meaning the matrix that lies on top of the first in the design view), there is this huge blank row between the header and values. [quoted text, click to view] "Brian Welcker" wrote:
> For those of you who have downloaded SP2, how is it going? Is print working > OK? Have you gotten the web parts working? Seen any *shudder* regressions in > functionality? > > -- > Brian Welcker > Group Program Manager > Microsoft SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |