I've got a table with a header, group, and detail row. The detail row
is collaspable however when it's collasped there is several lines of
white space between the parent groups. How do I get rid of this white
space?
Thanks in advance for the helpIs it possible that the white space is really the detail row, and it is
not shrinking as expected? (I've had this same problem before...) If
you are supressing just a column or two, but not hiding the entire
detail row (such as setting visibility --> hidden property based upon
conditional expression) then you will get the spacing issue as
described.|||Thanks Matt
That was the problem. I was setting the visibility at the cell level
when i should have been setting it on the over all row. thanks for the
help
Mathiassql
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Tuesday, March 27, 2012
External stored procedures and sockets
I hope this is the right group for this question.
I am trying to deliver a UDP multicast data stream as a notification method
using an extended stored procedure. The multicast message, however, is not
making it out on the network. (At least not in a form that I can recognize.
)
- I can make the multicast work from a stand-alone console application using
the same procedure with dummy data, so I think I'm setting up the multicast
properly.
- I have verified that the extended stored procedure receives the parameters
from the trigger that calls it successfully, so the external stored procedur
e
is being called properly.
- I have verified that there are no error returns from any of the socket (or
other) API calls in the extended stored procedure, so the procedure thinks
it's doing what it ought to.
My conclusion is that there is something in the execution environment that
is keeping the extended stored procedure from working as expected (i.e., as
it does as a simple subroutine in the console application). On the other
hand, I know I've seen people write about using sockets in their extended
stored procedures.
Any ideas as to what I'm doing wrong?
Thanks.
Ed Hoch
--
GEDDS Manager
Geophysical Institute
University of Alaska FairbanksHi
Have you checked that there is not a firewall blocking this port? Also make
sure that your account has the correct access to do this.
John
"Edward Hoch" wrote:
> I hope this is the right group for this question.
> I am trying to deliver a UDP multicast data stream as a notification metho
d
> using an extended stored procedure. The multicast message, however, is no
t
> making it out on the network. (At least not in a form that I can recogniz
e.)
> - I can make the multicast work from a stand-alone console application usi
ng
> the same procedure with dummy data, so I think I'm setting up the multicas
t
> properly.
> - I have verified that the extended stored procedure receives the paramete
rs
> from the trigger that calls it successfully, so the external stored proced
ure
> is being called properly.
> - I have verified that there are no error returns from any of the socket (
or
> other) API calls in the extended stored procedure, so the procedure thinks
> it's doing what it ought to.
> My conclusion is that there is something in the execution environment that
> is keeping the extended stored procedure from working as expected (i.e., a
s
> it does as a simple subroutine in the console application). On the other
> hand, I know I've seen people write about using sockets in their extended
> stored procedures.
> Any ideas as to what I'm doing wrong?
> Thanks.
> Ed Hoch
> --
> GEDDS Manager
> Geophysical Institute
> University of Alaska Fairbanks|||Hi John,
I am assuming that since I can run the same code successfully from a console
application, that it is not a firewall issue. I don't think it's possible t
o
"firewall" a specific process (like SQL Server), is it? Also, I have logged
in to the console as the user that SQL Server runs under. The console
application still works. So, unless SQL Server is somehow managinig to
affect the permissions of that account, I don't think it's an access
problem, either.
Feel free to correct me if any of my assumptions are wrong. Thanks very
much for your response.
Ed
"John Bell" wrote:
> Hi
> Have you checked that there is not a firewall blocking this port? Also mak
e
> sure that your account has the correct access to do this.
> John
> "Edward Hoch" wrote:
>
I am trying to deliver a UDP multicast data stream as a notification method
using an extended stored procedure. The multicast message, however, is not
making it out on the network. (At least not in a form that I can recognize.
)
- I can make the multicast work from a stand-alone console application using
the same procedure with dummy data, so I think I'm setting up the multicast
properly.
- I have verified that the extended stored procedure receives the parameters
from the trigger that calls it successfully, so the external stored procedur
e
is being called properly.
- I have verified that there are no error returns from any of the socket (or
other) API calls in the extended stored procedure, so the procedure thinks
it's doing what it ought to.
My conclusion is that there is something in the execution environment that
is keeping the extended stored procedure from working as expected (i.e., as
it does as a simple subroutine in the console application). On the other
hand, I know I've seen people write about using sockets in their extended
stored procedures.
Any ideas as to what I'm doing wrong?
Thanks.
Ed Hoch
--
GEDDS Manager
Geophysical Institute
University of Alaska FairbanksHi
Have you checked that there is not a firewall blocking this port? Also make
sure that your account has the correct access to do this.
John
"Edward Hoch" wrote:
> I hope this is the right group for this question.
> I am trying to deliver a UDP multicast data stream as a notification metho
d
> using an extended stored procedure. The multicast message, however, is no
t
> making it out on the network. (At least not in a form that I can recogniz
e.)
> - I can make the multicast work from a stand-alone console application usi
ng
> the same procedure with dummy data, so I think I'm setting up the multicas
t
> properly.
> - I have verified that the extended stored procedure receives the paramete
rs
> from the trigger that calls it successfully, so the external stored proced
ure
> is being called properly.
> - I have verified that there are no error returns from any of the socket (
or
> other) API calls in the extended stored procedure, so the procedure thinks
> it's doing what it ought to.
> My conclusion is that there is something in the execution environment that
> is keeping the extended stored procedure from working as expected (i.e., a
s
> it does as a simple subroutine in the console application). On the other
> hand, I know I've seen people write about using sockets in their extended
> stored procedures.
> Any ideas as to what I'm doing wrong?
> Thanks.
> Ed Hoch
> --
> GEDDS Manager
> Geophysical Institute
> University of Alaska Fairbanks|||Hi John,
I am assuming that since I can run the same code successfully from a console
application, that it is not a firewall issue. I don't think it's possible t
o
"firewall" a specific process (like SQL Server), is it? Also, I have logged
in to the console as the user that SQL Server runs under. The console
application still works. So, unless SQL Server is somehow managinig to
affect the permissions of that account, I don't think it's an access
problem, either.
Feel free to correct me if any of my assumptions are wrong. Thanks very
much for your response.
Ed
"John Bell" wrote:
> Hi
> Have you checked that there is not a firewall blocking this port? Also mak
e
> sure that your account has the correct access to do this.
> John
> "Edward Hoch" wrote:
>
Monday, March 26, 2012
External images
I'm having problems getting external images to show up in a report. As
suggested in other posts in this group - the resource is linked to a fully
qualified server name.
The reporting services is locked down to authenticated users. The image url
is to the same server and I've tried setting access to both anonymous access
and authenticated users. I don't believe it is a permissions problem
because I can paste the url in a browser and view the image with no problem.
When I right click on the red x (where the image should be) and go to
properties and look at the url - it only shows the server name and not the
rest of the url (folder and file name.) When I review the data that provides
the url for the external image - the correct url is in there. I copy and
paste to the browser - the image comes up fine.
This really has me stumped - because everything seems to be right. I have
this running in three sites with no problem and don't see what I'm doing
different here. The only difference is that this is running in a tightly
locked down hospital setting. Is there some browser setting that can be set
in a policy that would restrict a web page from pulling info from multiple
sources or something?
Thanks,
DavidHi David,
Welcome to the MSDN newsgroup.
As for the image displaying problem, based on my experience, we could
troubleshoot from two aspects, the client-side browser and the server-side
report deisgn. Have you try visisting the report page from other client
machines to see whether the image can display well? If also suffering the
problem, it is likely the report or the image part is not correctly
rendered. Also, as you mentioned that when you right click the "X" and view
URL, it doesn't point to the correct image file path ,yes? I suggest you
also use the browser's "View Source" menu item to check the HTML source of
the report page, if the <img> element is not assigned the correct "src"
attribute, it is likely the server report's design has some thing incorrect
that cause this problem.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||I looked at the source code and it says this for the image <IMG class="r1"
SRC="">
I verified the data in the dataset and it is coming back with the correct
url for the image.
When I look at the source for a page that is rendering correctly (in a
different location) it's coming back with the following
<IMG class="r1"
SRC="</DIV></TD><TD">http://hvsql01/ReportServer?%2fCardioDx%2fNuclear&EncounterID=22004&rs%3aFormat=HTML4.0&rs%3aImageID=189"></DIV></TD><TD
ROWSPAN="3" style="WIDTH:3.18mm">
I'm a little suprised at the url for the image source. Looks like it's
coming from the reportserver instead of directly from the source. Makes
sense I guess having to generate the pictures in other formats would require
pulling it through the rendering engine.
Everything looks the same as the source running successfully in another
environment.
Thanks for helping narrow this down however - not sure what to do at this
point.
I'm running SQLRS with service pack 2. One of the fixes I tried to apply was
to add an unattended mode user with the rsconfig app. Nothing changed but
it accepted it.
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:5X1KGl1QGHA.1592@.TK2MSFTNGXA03.phx.gbl...
> Hi David,
> Welcome to the MSDN newsgroup.
> As for the image displaying problem, based on my experience, we could
> troubleshoot from two aspects, the client-side browser and the server-side
> report deisgn. Have you try visisting the report page from other client
> machines to see whether the image can display well? If also suffering the
> problem, it is likely the report or the image part is not correctly
> rendered. Also, as you mentioned that when you right click the "X" and
> view
> URL, it doesn't point to the correct image file path ,yes? I suggest you
> also use the browser's "View Source" menu item to check the HTML source of
> the report page, if the <img> element is not assigned the correct "src"
> attribute, it is likely the server report's design has some thing
> incorrect
> that cause this problem.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Thanks for your respone David,
I've also performed some further tests on my side and did found some clues.
Actually, what you have seen (I'm a little suprised at the url for the
image source. Looks like it's coming from the reportserver instead of
directly from the source) is the expected behavior because SQL Reporting
service does not directly simply put the external image's address in the
report's rendered html. Instead, the report server will first retrieve the
image stream itself than provide a url point to the image stream from the
report server. Therefore, this make it important that we need to make sure
our report server application can correct access that image under its
running security account. See the below note in BOL:
====================External Images
You can include stored images in a report by specifying a URL to the image.
When you use an external image in a report, the image source is set to
External and the value for the image is the URL address to the image (for
example, http://<servername>/images/image1.jpg).
When the report is previewed in Report Designer, preview uses the
credentials of the user to display the image. When the report is run on the
report server, the report server uses the unattended execution account to
retrieve the image. If the unattended execution account is not specified,
the image is retrieved using no credentials (anonymous user account). If
either of these accounts have insufficient rights to access the image, the
image will not be displayed in the report. For more information about the
unattended execution account, see Configuring an Account for Unattended
Report Processing.
====================
And based on my test, when I specify an invalid url ( or a url the report
server can not access). the "src" attribute of the <img> tag will be empty
, just like <img ... src="http://pics.10026.com/?src=" /> , and this conforms to what you'r
encountering also, correct? So I think the problem is possibly caused by
the web url based image is not correctly accessed by the report server
application.
So far I think there're two things we can check:
1. security, whether the images are protected by any authentication which
require certain security context(account) to access
2. web proxy setting , since you can visit the image in browser, is there
any proxy setting in browser which is not utilized by the report server
appliation that cause the image unaccessible?
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thanks Steven,
As I mentioned in my last post - I had already set up the system for
unattended execution and permissions were set for Domain Admin.
That leaves me with your second suggestion which I don't understand. Can
you explain a little further what I'm supposed to be looking for? When RS
processes the image - does it use the proxy server to get the image? Is
that what you are saying?
Thanks,
David
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:sSZ3o1ARGHA.7144@.TK2MSFTNGXA03.phx.gbl...
> Thanks for your respone David,
> I've also performed some further tests on my side and did found some
> clues.
> Actually, what you have seen (I'm a little suprised at the url for the
> image source. Looks like it's coming from the reportserver instead of
> directly from the source) is the expected behavior because SQL Reporting
> service does not directly simply put the external image's address in the
> report's rendered html. Instead, the report server will first retrieve the
> image stream itself than provide a url point to the image stream from the
> report server. Therefore, this make it important that we need to make
> sure
> our report server application can correct access that image under its
> running security account. See the below note in BOL:
> ====================> External Images
> You can include stored images in a report by specifying a URL to the
> image.
> When you use an external image in a report, the image source is set to
> External and the value for the image is the URL address to the image (for
> example, http://<servername>/images/image1.jpg).
> When the report is previewed in Report Designer, preview uses the
> credentials of the user to display the image. When the report is run on
> the
> report server, the report server uses the unattended execution account to
> retrieve the image. If the unattended execution account is not specified,
> the image is retrieved using no credentials (anonymous user account). If
> either of these accounts have insufficient rights to access the image, the
> image will not be displayed in the report. For more information about the
> unattended execution account, see Configuring an Account for Unattended
> Report Processing.
> ====================> And based on my test, when I specify an invalid url ( or a url the report
> server can not access). the "src" attribute of the <img> tag will be empty
> , just like <img ... src="http://pics.10026.com/?src=" /> , and this conforms to what you'r
> encountering also, correct? So I think the problem is possibly caused by
> the web url based image is not correctly accessed by the report server
> application.
> So far I think there're two things we can check:
> 1. security, whether the images are protected by any authentication which
> require certain security context(account) to access
> 2. web proxy setting , since you can visit the image in browser, is there
> any proxy setting in browser which is not utilized by the report server
> appliation that cause the image unaccessible?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>|||Hi David,
The proxy I means is the proxy your webclient (like browser) need to visist
external internet resources. For example, when you use IE to visit some
certain resources, maybe you're configured to use some proxy server in IE's
connection setting(or you've used any proxy client which automatically
configure this for you). However, for report server application ,it may not
utilize the same setting as IE, thus, there may occur some issue when
report server application try visit some external resources. So I'm not
sure whether your network environment is something like this.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||I just came back from the installation and there are no proxy servers set
up.
Do you have any other suggestions? I really do not have any idea what
could be wrong here.
Thanks - David
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:ypy%23J4oRGHA.6492@.TK2MSFTNGXA03.phx.gbl...
> Hi David,
> The proxy I means is the proxy your webclient (like browser) need to
> visist
> external internet resources. For example, when you use IE to visit some
> certain resources, maybe you're configured to use some proxy server in
> IE's
> connection setting(or you've used any proxy client which automatically
> configure this for you). However, for report server application ,it may
> not
> utilize the same setting as IE, thus, there may occur some issue when
> report server application try visit some external resources. So I'm not
> sure whether your network environment is something like this.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Just spent 4.5 hours on the phone and an open ticket with Microsoft and
determined that there is a bug in IIS that doesn't pass permissions on to
local virtual directories.
Finally - the work around for this is to put a file path in where the url is
supposed to go for the image. This worked great - bypassed problems iis is
having and seems to run a little faster too.
Here's a "for instance" sent by the tech at MS. Put whatever path to your
image.
file:///c:/WINNT/Zapotec.bmp
David
<drchips@.nospam.nospam> wrote in message
news:%23lj9EowQGHA.1328@.TK2MSFTNGP10.phx.gbl...
> I'm having problems getting external images to show up in a report. As
> suggested in other posts in this group - the resource is linked to a
> fully qualified server name.
> The reporting services is locked down to authenticated users. The image
> url is to the same server and I've tried setting access to both anonymous
> access and authenticated users. I don't believe it is a permissions
> problem because I can paste the url in a browser and view the image with
> no problem.
> When I right click on the red x (where the image should be) and go to
> properties and look at the url - it only shows the server name and not the
> rest of the url (folder and file name.) When I review the data that
> provides the url for the external image - the correct url is in there. I
> copy and paste to the browser - the image comes up fine.
> This really has me stumped - because everything seems to be right. I have
> this running in three sites with no problem and don't see what I'm doing
> different here. The only difference is that this is running in a tightly
> locked down hospital setting. Is there some browser setting that can be
> set in a policy that would restrict a web page from pulling info from
> multiple sources or something?
> Thanks,
> David
>|||Thanks for your followup David,
So the problem still be caused by the IIS side, really a bit surprising.
Anyway, glad that you've got it working now.
If there's anything else we can help, please feel free to post here.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
suggested in other posts in this group - the resource is linked to a fully
qualified server name.
The reporting services is locked down to authenticated users. The image url
is to the same server and I've tried setting access to both anonymous access
and authenticated users. I don't believe it is a permissions problem
because I can paste the url in a browser and view the image with no problem.
When I right click on the red x (where the image should be) and go to
properties and look at the url - it only shows the server name and not the
rest of the url (folder and file name.) When I review the data that provides
the url for the external image - the correct url is in there. I copy and
paste to the browser - the image comes up fine.
This really has me stumped - because everything seems to be right. I have
this running in three sites with no problem and don't see what I'm doing
different here. The only difference is that this is running in a tightly
locked down hospital setting. Is there some browser setting that can be set
in a policy that would restrict a web page from pulling info from multiple
sources or something?
Thanks,
DavidHi David,
Welcome to the MSDN newsgroup.
As for the image displaying problem, based on my experience, we could
troubleshoot from two aspects, the client-side browser and the server-side
report deisgn. Have you try visisting the report page from other client
machines to see whether the image can display well? If also suffering the
problem, it is likely the report or the image part is not correctly
rendered. Also, as you mentioned that when you right click the "X" and view
URL, it doesn't point to the correct image file path ,yes? I suggest you
also use the browser's "View Source" menu item to check the HTML source of
the report page, if the <img> element is not assigned the correct "src"
attribute, it is likely the server report's design has some thing incorrect
that cause this problem.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||I looked at the source code and it says this for the image <IMG class="r1"
SRC="">
I verified the data in the dataset and it is coming back with the correct
url for the image.
When I look at the source for a page that is rendering correctly (in a
different location) it's coming back with the following
<IMG class="r1"
SRC="</DIV></TD><TD">http://hvsql01/ReportServer?%2fCardioDx%2fNuclear&EncounterID=22004&rs%3aFormat=HTML4.0&rs%3aImageID=189"></DIV></TD><TD
ROWSPAN="3" style="WIDTH:3.18mm">
I'm a little suprised at the url for the image source. Looks like it's
coming from the reportserver instead of directly from the source. Makes
sense I guess having to generate the pictures in other formats would require
pulling it through the rendering engine.
Everything looks the same as the source running successfully in another
environment.
Thanks for helping narrow this down however - not sure what to do at this
point.
I'm running SQLRS with service pack 2. One of the fixes I tried to apply was
to add an unattended mode user with the rsconfig app. Nothing changed but
it accepted it.
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:5X1KGl1QGHA.1592@.TK2MSFTNGXA03.phx.gbl...
> Hi David,
> Welcome to the MSDN newsgroup.
> As for the image displaying problem, based on my experience, we could
> troubleshoot from two aspects, the client-side browser and the server-side
> report deisgn. Have you try visisting the report page from other client
> machines to see whether the image can display well? If also suffering the
> problem, it is likely the report or the image part is not correctly
> rendered. Also, as you mentioned that when you right click the "X" and
> view
> URL, it doesn't point to the correct image file path ,yes? I suggest you
> also use the browser's "View Source" menu item to check the HTML source of
> the report page, if the <img> element is not assigned the correct "src"
> attribute, it is likely the server report's design has some thing
> incorrect
> that cause this problem.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Thanks for your respone David,
I've also performed some further tests on my side and did found some clues.
Actually, what you have seen (I'm a little suprised at the url for the
image source. Looks like it's coming from the reportserver instead of
directly from the source) is the expected behavior because SQL Reporting
service does not directly simply put the external image's address in the
report's rendered html. Instead, the report server will first retrieve the
image stream itself than provide a url point to the image stream from the
report server. Therefore, this make it important that we need to make sure
our report server application can correct access that image under its
running security account. See the below note in BOL:
====================External Images
You can include stored images in a report by specifying a URL to the image.
When you use an external image in a report, the image source is set to
External and the value for the image is the URL address to the image (for
example, http://<servername>/images/image1.jpg).
When the report is previewed in Report Designer, preview uses the
credentials of the user to display the image. When the report is run on the
report server, the report server uses the unattended execution account to
retrieve the image. If the unattended execution account is not specified,
the image is retrieved using no credentials (anonymous user account). If
either of these accounts have insufficient rights to access the image, the
image will not be displayed in the report. For more information about the
unattended execution account, see Configuring an Account for Unattended
Report Processing.
====================
And based on my test, when I specify an invalid url ( or a url the report
server can not access). the "src" attribute of the <img> tag will be empty
, just like <img ... src="http://pics.10026.com/?src=" /> , and this conforms to what you'r
encountering also, correct? So I think the problem is possibly caused by
the web url based image is not correctly accessed by the report server
application.
So far I think there're two things we can check:
1. security, whether the images are protected by any authentication which
require certain security context(account) to access
2. web proxy setting , since you can visit the image in browser, is there
any proxy setting in browser which is not utilized by the report server
appliation that cause the image unaccessible?
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thanks Steven,
As I mentioned in my last post - I had already set up the system for
unattended execution and permissions were set for Domain Admin.
That leaves me with your second suggestion which I don't understand. Can
you explain a little further what I'm supposed to be looking for? When RS
processes the image - does it use the proxy server to get the image? Is
that what you are saying?
Thanks,
David
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:sSZ3o1ARGHA.7144@.TK2MSFTNGXA03.phx.gbl...
> Thanks for your respone David,
> I've also performed some further tests on my side and did found some
> clues.
> Actually, what you have seen (I'm a little suprised at the url for the
> image source. Looks like it's coming from the reportserver instead of
> directly from the source) is the expected behavior because SQL Reporting
> service does not directly simply put the external image's address in the
> report's rendered html. Instead, the report server will first retrieve the
> image stream itself than provide a url point to the image stream from the
> report server. Therefore, this make it important that we need to make
> sure
> our report server application can correct access that image under its
> running security account. See the below note in BOL:
> ====================> External Images
> You can include stored images in a report by specifying a URL to the
> image.
> When you use an external image in a report, the image source is set to
> External and the value for the image is the URL address to the image (for
> example, http://<servername>/images/image1.jpg).
> When the report is previewed in Report Designer, preview uses the
> credentials of the user to display the image. When the report is run on
> the
> report server, the report server uses the unattended execution account to
> retrieve the image. If the unattended execution account is not specified,
> the image is retrieved using no credentials (anonymous user account). If
> either of these accounts have insufficient rights to access the image, the
> image will not be displayed in the report. For more information about the
> unattended execution account, see Configuring an Account for Unattended
> Report Processing.
> ====================> And based on my test, when I specify an invalid url ( or a url the report
> server can not access). the "src" attribute of the <img> tag will be empty
> , just like <img ... src="http://pics.10026.com/?src=" /> , and this conforms to what you'r
> encountering also, correct? So I think the problem is possibly caused by
> the web url based image is not correctly accessed by the report server
> application.
> So far I think there're two things we can check:
> 1. security, whether the images are protected by any authentication which
> require certain security context(account) to access
> 2. web proxy setting , since you can visit the image in browser, is there
> any proxy setting in browser which is not utilized by the report server
> appliation that cause the image unaccessible?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>|||Hi David,
The proxy I means is the proxy your webclient (like browser) need to visist
external internet resources. For example, when you use IE to visit some
certain resources, maybe you're configured to use some proxy server in IE's
connection setting(or you've used any proxy client which automatically
configure this for you). However, for report server application ,it may not
utilize the same setting as IE, thus, there may occur some issue when
report server application try visit some external resources. So I'm not
sure whether your network environment is something like this.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||I just came back from the installation and there are no proxy servers set
up.
Do you have any other suggestions? I really do not have any idea what
could be wrong here.
Thanks - David
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> wrote in message
news:ypy%23J4oRGHA.6492@.TK2MSFTNGXA03.phx.gbl...
> Hi David,
> The proxy I means is the proxy your webclient (like browser) need to
> visist
> external internet resources. For example, when you use IE to visit some
> certain resources, maybe you're configured to use some proxy server in
> IE's
> connection setting(or you've used any proxy client which automatically
> configure this for you). However, for report server application ,it may
> not
> utilize the same setting as IE, thus, there may occur some issue when
> report server application try visit some external resources. So I'm not
> sure whether your network environment is something like this.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Just spent 4.5 hours on the phone and an open ticket with Microsoft and
determined that there is a bug in IIS that doesn't pass permissions on to
local virtual directories.
Finally - the work around for this is to put a file path in where the url is
supposed to go for the image. This worked great - bypassed problems iis is
having and seems to run a little faster too.
Here's a "for instance" sent by the tech at MS. Put whatever path to your
image.
file:///c:/WINNT/Zapotec.bmp
David
<drchips@.nospam.nospam> wrote in message
news:%23lj9EowQGHA.1328@.TK2MSFTNGP10.phx.gbl...
> I'm having problems getting external images to show up in a report. As
> suggested in other posts in this group - the resource is linked to a
> fully qualified server name.
> The reporting services is locked down to authenticated users. The image
> url is to the same server and I've tried setting access to both anonymous
> access and authenticated users. I don't believe it is a permissions
> problem because I can paste the url in a browser and view the image with
> no problem.
> When I right click on the red x (where the image should be) and go to
> properties and look at the url - it only shows the server name and not the
> rest of the url (folder and file name.) When I review the data that
> provides the url for the external image - the correct url is in there. I
> copy and paste to the browser - the image comes up fine.
> This really has me stumped - because everything seems to be right. I have
> this running in three sites with no problem and don't see what I'm doing
> different here. The only difference is that this is running in a tightly
> locked down hospital setting. Is there some browser setting that can be
> set in a policy that would restrict a web page from pulling info from
> multiple sources or something?
> Thanks,
> David
>|||Thanks for your followup David,
So the problem still be caused by the IIS side, really a bit surprising.
Anyway, glad that you've got it working now.
If there's anything else we can help, please feel free to post here.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Friday, March 23, 2012
external access - the definitive solution?
ok, I know this topic has been covered COUNTLESS times in this group,
yet the solution is still very, very hard to come by. Has anybody
successfully published their reports (through a custom .net web
application using URL access to the report server) to an external
network / internet?
If so, how... Custom security extension? Handing out network logins
(with very restricted rights) to the report server?
A final, solid solution would be greatly appreciated...Yes, we did do it and it and there are compromises. A custom security
extension is painful but is probably most secure. The simplest way for an
Internet solution is to -
1. Permit "annonymous" accesss to a low privelege account on the
ReportServer virtual directory.
2. Everything must be https and you will need a registered FQDN server side
cert.
3. However, one still needs to authenticate the user which needs to be done
by your application. Otherwise you have to go custom+Forms authentication or
handing out network logins .. ugh!
4. In order to secure reports, we used a sessionkey generated by our app and
passed it as a hidden parameter from an embedded IE browser using url access.
5. The RDLs execute SPs and the session check is done at this point. With a
custom solution one would do the check prior to allowing access to the
ReportServer.
6. You then need to follow MBSA guidelines to lock down your IIS server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod104.asp
P.S ... the last part is nuts & you'll wonder why not have all clients
connect over IPSec and be done with it.
"Gearoid" wrote:
> ok, I know this topic has been covered COUNTLESS times in this group,
> yet the solution is still very, very hard to come by. Has anybody
> successfully published their reports (through a custom .net web
> application using URL access to the report server) to an external
> network / internet?
> If so, how... Custom security extension? Handing out network logins
> (with very restricted rights) to the report server?
> A final, solid solution would be greatly appreciated...
>
yet the solution is still very, very hard to come by. Has anybody
successfully published their reports (through a custom .net web
application using URL access to the report server) to an external
network / internet?
If so, how... Custom security extension? Handing out network logins
(with very restricted rights) to the report server?
A final, solid solution would be greatly appreciated...Yes, we did do it and it and there are compromises. A custom security
extension is painful but is probably most secure. The simplest way for an
Internet solution is to -
1. Permit "annonymous" accesss to a low privelege account on the
ReportServer virtual directory.
2. Everything must be https and you will need a registered FQDN server side
cert.
3. However, one still needs to authenticate the user which needs to be done
by your application. Otherwise you have to go custom+Forms authentication or
handing out network logins .. ugh!
4. In order to secure reports, we used a sessionkey generated by our app and
passed it as a hidden parameter from an embedded IE browser using url access.
5. The RDLs execute SPs and the session check is done at this point. With a
custom solution one would do the check prior to allowing access to the
ReportServer.
6. You then need to follow MBSA guidelines to lock down your IIS server
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secmod/html/secmod104.asp
P.S ... the last part is nuts & you'll wonder why not have all clients
connect over IPSec and be done with it.
"Gearoid" wrote:
> ok, I know this topic has been covered COUNTLESS times in this group,
> yet the solution is still very, very hard to come by. Has anybody
> successfully published their reports (through a custom .net web
> application using URL access to the report server) to an external
> network / internet?
> If so, how... Custom security extension? Handing out network logins
> (with very restricted rights) to the report server?
> A final, solid solution would be greatly appreciated...
>
Friday, March 9, 2012
expression sum and iif help?
Hi All,
SUM(IIF(Fields!NO.Value >= 1, Fields!tsHours.Value,0))
i write this expression inside the group footer row, it give a #error when generating report.
please help
Cheers
Nick
Hi Nick,
The possible reason for this error is that the Sum function can only add fields of the same data type. It is quite possible in this case that the data types of the fields in the TRUE and FALSe part of the If statement is different. Try making the data types same of both the fields by usinf the Conversion functions available.
Hope this helps.
Regards,
Pradeep
|||Hi,
I think ure iif() is returning varying datatypes. 0 being a integer and Fields!tsHours.Value returning some other datatype.
Use a conversion function such as CDbl() on both fields.For eg: CDbl(Fields!tsHours.Value) and CDbl(0).This makes either of the values returned as Double.
eg:
Sum(IIf(Fields!NO.value>=1,CDbl(Fields!tsHours.Value),Cdbl(0)))
Somiya
|||Thanks Chaubey and Somiya,
You guys are right, after i explicitly convert to same type , then it works.
Cheers
Nick
Friday, February 24, 2012
Expose SQL Meta Data via ASP
Hi,
Apologies if this is better posted in an ASP group, but here goes
anyway ...
Is it possible to work out what parameters a stored procedure expects,
using ASP?
I would like to take the name of a stored procedure, work out what
input parameters it has and build a form based on them in ASP.
Thanks,
MB.Tools (mbrocklehurst@.hotmail.com) writes:
> Apologies if this is better posted in an ASP group, but here goes
> anyway ...
> Is it possible to work out what parameters a stored procedure expects,
> using ASP?
> I would like to take the name of a stored procedure, work out what
> input parameters it has and build a form based on them in ASP.
You can use the .Refresh method for a command object. That will populate
a parameter collection for you.
Now, how you actually access that from ASP, you will have to ask someone
else. I don't know ASP.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||or you can run a query against INFORMATION_SCHEMA.PARAMETERS
"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns959DF15265D4AYazorman@.127.0.0.1...
> Tools (mbrocklehurst@.hotmail.com) writes:
> > Apologies if this is better posted in an ASP group, but here goes
> > anyway ...
> > Is it possible to work out what parameters a stored procedure expects,
> > using ASP?
> > I would like to take the name of a stored procedure, work out what
> > input parameters it has and build a form based on them in ASP.
> You can use the .Refresh method for a command object. That will populate
> a parameter collection for you.
> Now, how you actually access that from ASP, you will have to ask someone
> else. I don't know ASP.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techin.../2000/books.asp
Subscribe to:
Posts (Atom)