Thursday, March 29, 2012
Error Rendering trough Web Service to WebArchivo format
We are using the Reporting Services Web Service, in order to expose some
reports in our Web Application, right now I am trying to enable exporting the
report to the available formats in Reporting Services, and altough everything
seems to be working fine, when I try to render as Web Archive, I get the
following exception:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. --> The parameter is incorrect.
first I tough it was because of the device info configuration I was using,
since it was the same of the html format (which had things like turning off
the toolbar), thus I instead didnt pass any deviceinfo(null), in both cases
it works fine in all formats but it doesnt in Web Archive.
I have been searching for info about the error, but I havent found any ...
if anyone knows what is happening, I will be thankfull :) ... in the mean
time, I will keep trying, and if I find anything I will post it here.I have continued digging on the problem, I havent found anything on the
internet, and I have cleared out some things about the problem ...
so, here are some aditional info about the problem:
- it isnt only happening when I try to render the report trough the Web
Service, it also happens when I use url access.
- it is happening specifically in this report, there are other reports that
works well
- I am not using any totals/subtotals formulas (I say this, since I have
read this might cause trouble in certain rendering extensions)
- I just found something else (I have 3 reports):
- the report that is working doesnt receive any parameter
- the 2 reports that doesnt work receive 1 parameter, and additionaly have
a list of valid values ...
it looks like it were a bug, something along the lines that rendering
extension either ignores the parameters, or gets confused where there is a
list of valid values ...
Any help will be greatly appreciated ... in the mean time, I will be playing
with the reports definition, in order to find what is exactly happening, if I
dont find a solution soon I will restrict that rendering extension from being
used :(:(:( ...|||I am done with this, I am pretty certain is a bug, just not the type of bug I
tough ...
it is really weird, I played with the parameter options in the report and
the error kept happening, then I decided playing with the report design ...
well, whenever I put a third column in my report, the error happens when I
try to export it to web archive ... I put all types of definition in the
third column, to see if I managed to see anything making it fail, but didnt
arrive to anything, I tried from the simplest one (static text + no
formatting) all trough a "complex" one (formatting + dinamic text ...)
Monday, March 26, 2012
Error opening PDF files exported from Reporting Services
When I try exporting reports from Reporting Services to a PDF format, I
get the following error:
"There was an error opening this document. The file is damaged and
could not be repaired."
This has started to happen all of a sudden. There were no problems
with pdf exports before. I have checked and there have been no recent
changes to adobe reader version(5.01) on the user's machine.
Any ideas or guidance on this would be appreciated.
Thanks & Regards,
Hemil.Did you ever find a solution to this? I'm all of a sudden having the same
problem with a report that worked fine earlier.
"hemil.deshmukh@.gmail.com" wrote:
> Hi,
> When I try exporting reports from Reporting Services to a PDF format, I
> get the following error:
> "There was an error opening this document. The file is damaged and
> could not be repaired."
> This has started to happen all of a sudden. There were no problems
> with pdf exports before. I have checked and there have been no recent
> changes to adobe reader version(5.01) on the user's machine.
> Any ideas or guidance on this would be appreciated.
> Thanks & Regards,
> Hemil.
>|||If anyone knows the answer to this . . .
I believe it may have something to do with the version of Adobe Reader. I
just updated to 7.0.5 and started having the same problem. Does reporting
services have a patch or do I need to drop back a version on Adobe Reader?
--
gwf
"ryan" wrote:
> Did you ever find a solution to this? I'm all of a sudden having the same
> problem with a report that worked fine earlier.
> "hemil.deshmukh@.gmail.com" wrote:
> > Hi,
> >
> > When I try exporting reports from Reporting Services to a PDF format, I
> > get the following error:
> >
> > "There was an error opening this document. The file is damaged and
> > could not be repaired."
> >
> > This has started to happen all of a sudden. There were no problems
> > with pdf exports before. I have checked and there have been no recent
> > changes to adobe reader version(5.01) on the user's machine.
> >
> > Any ideas or guidance on this would be appreciated.
> >
> > Thanks & Regards,
> > Hemil.
> >
> >|||I am having a similar issue like the one I found on TechNet (at the bottom of
this email).
There are 4 emails generated by Reporting Services for this particular
report, two go to our customers in the â'To:â' area of the email and two in the
â'Bcc:â' area. The two going to the â'To:â' area can not open the PDF file. They
get the error â?¦
Adobe Reader could not open 'Dealer Report FI Only [1].pdf because its
either not a supported file type or because the file has been damaged (for
example, it was sent as an email attachment and wasnt correctly decoded).
(note that the above message was typed by our customer and may not be
exactly what was issued)
The customer says that they have the latest version of Adobe Reader. The
curious thing is that when they forward the email to me I can open it just
fine. Very strange.
Can anyone in the Microsoft world help with this issue?
Thanks,
Larry
"hemil.deshmukh@.gmail.com" wrote:
> Hi,
> When I try exporting reports from Reporting Services to a PDF format, I
> get the following error:
> "There was an error opening this document. The file is damaged and
> could not be repaired."
> This has started to happen all of a sudden. There were no problems
> with pdf exports before. I have checked and there have been no recent
> changes to adobe reader version(5.01) on the user's machine.
> Any ideas or guidance on this would be appreciated.
> Thanks & Regards,
> Hemil.
>
Monday, March 19, 2012
Error on CONVERT(Datetime,'2000-01-01')
Hello,
We have several stored procedure which convert literal strings to date in the format off: CONVERT(Datetime,'2000-01-01') or such.
Those procedures are working well on our development server as well as on several other servers we installed at our customers.
However, on an MSSQL server that was install in Germany, we get an error on those convert line. The error the MSSQL return is: "Bei der Konvertierung eines char-Datentyps in einen datetime-Datentyp liegt der datetime-Wert au?erhalb des gültigen Bereichs." which more or less translate too:
"During the conversion of a char data type into a DATE time data type lies DATE-TIME-WORTH outside of the valid range."
I managed to manually fix this by changing the convert line to the following: CONVERT(Datetime,'20000101') , but I still have few questions:
1. I would be happy to know what is the reason for the inconsistent behavior of the CONVERT(Datetime,'2000-01-01') and if there is a way to solve it without changing the stored procedure (maybe configuring something in the MSSQL setting or regional setting of the server itself).
2. Can I be assured that the CONVERT(Datetime,'20000101') will work properly on each and every instance of MSSQL, or can this format might also fail on different machines.
Thanks in advance.
Run this in Query Analyzer
SELECT CONVERT(Datetime,'2000-12-13')
SET DATEFORMAT dmy
SELECT CONVERT(Datetime,'2000-12-13')
The second one will fail because SQL server expects a date in yyyyddmm format, un Europe they use the ddmmyyyy format
Lookup SET DATEFORMAT in BOL
Denis the SQL Menace
http://sqlservercode.blogspot.com/
|||Forgot to answer you question ;-(
YYYYMMDD (no dashes) is the safe ISO dateformat to use
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Sunday, February 26, 2012
Error Message. Please help
--=_NextPart_000_0006_01C6531E.93D6CCD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I have 7 SQL Servers
They all sync once every hour.
One of my servers shows 2 Views (while the others show 4). SO I tried to = create the missing view's and I get this error message
"ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]There is = already an object named <name> already exists"
Thank You
--=_NextPart_000_0006_01C6531E.93D6CCD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I have 7 SQL Servers
They all sync once every = hour.
One of my servers shows 2 Views (while = the others show 4). SO I tried to create the missing view's and I get this error message
"ODBC error: [Microsoft][ODBC = SQL Server Driver][SQL Server]There is already an object named already = exists"
Thank You
--=_NextPart_000_0006_01C6531E.93D6CCD0--Try refreshing enterprise manger.
Regards
Amish Shah|||I used the right mouse button and clicked REFRESH.
and nothing happened.
Anything else I can try?
Thanks
"amish" <shahamishm@.gmail.com> wrote in message
news:1143649651.420463.246200@.v46g2000cwv.googlegroups.com...
> Try refreshing enterprise manger.
>
> Regards
> Amish Shah
>|||I have found disconnecting from the server and/or shutting down EM helps.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Shayaan Siddiqui" wrote:
> I used the right mouse button and clicked REFRESH.
> and nothing happened.
> Anything else I can try?
> Thanks
> "amish" <shahamishm@.gmail.com> wrote in message
> news:1143649651.420463.246200@.v46g2000cwv.googlegroups.com...
> > Try refreshing enterprise manger.
> >
> >
> > Regards
> > Amish Shah
> >
>
>|||How do you do this?
Do you click the "X" or is there another process?
Shayaan
"jrpm" <jrpm@.discussions.microsoft.com> wrote in message
news:9576EDFF-5EF4-4944-8B59-EF4422D1A05F@.microsoft.com...
>I have found disconnecting from the server and/or shutting down EM helps.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "Shayaan Siddiqui" wrote:
>> I used the right mouse button and clicked REFRESH.
>> and nothing happened.
>> Anything else I can try?
>> Thanks
>> "amish" <shahamishm@.gmail.com> wrote in message
>> news:1143649651.420463.246200@.v46g2000cwv.googlegroups.com...
>> > Try refreshing enterprise manger.
>> >
>> >
>> > Regards
>> > Amish Shah
>> >
>>|||This is a multi-part message in MIME format.
--=_NextPart_000_0008_01C653E0.B89F5FB0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Any suggestions?
Thanks
"Shayaan Siddiqui" <givethis@.mac.com> wrote in message =news:e2hL$h0UGHA.5884@.TK2MSFTNGP14.phx.gbl...
I have 7 SQL Servers
They all sync once every hour.
One of my servers shows 2 Views (while the others show 4). SO I tried =to create the missing view's and I get this error message
"ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]There is =already an object named <name> already exists"
Thank You
--=_NextPart_000_0008_01C653E0.B89F5FB0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Any suggestions?
Thanks
"Shayaan Siddiqui"
I have 7 SQL Servers
They all sync once every =hour.
One of my servers shows 2 Views =(while the others show 4). SO I tried to create the missing view's and I get this error message
"ODBC error: [Microsoft][ODBC =SQL Server Driver][SQL Server]There is already an object named =already exists"
Thank =You
--=_NextPart_000_0008_01C653E0.B89F5FB0--