Microsoft Acknowledgement?

Can I please, at least, get an acknowledgement from someone at
Microsoft that they have seen this posting? Without a response
whatsoever in a month's time, I'm wondering if it was posted at all.
Hopefully I can get some sort of input as well as a viable workaround
or plans for this bug to be fixed in a future release. This is quite
a large bug. I appreciate anyone's time on this issue. Thanks.
FrankThere is no guarantee that MS will answer a post here. If this newsgroup can
get to be part of the msdn managed newsgroup then if you had a msdn
subscription (not sure what level is required) then you could be guaranteed
an answer (but not necessarily by MS). Right now this is peer supported and
MS people drop in when they can. There is no-one whose job at MS is to
answer these posts (again, if it becomes one of the msdn managed newsgroups
then that would change).
I suggest reposting with the subject of your concern.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0410061158.a903962@.posting.google.com...
> Can I please, at least, get an acknowledgement from someone at
> Microsoft that they have seen this posting? Without a response
> whatsoever in a month's time, I'm wondering if it was posted at all.
> Hopefully I can get some sort of input as well as a viable workaround
> or plans for this bug to be fixed in a future release. This is quite
> a large bug. I appreciate anyone's time on this issue. Thanks.
> Frank|||Um, might help if you posted the bug description. A little arrogant don't
you think, that you expect us to dig through the group looking for an old
post?
For large bugs, I usually use a large shoe. Does that help?
Jeff
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0410061158.a903962@.posting.google.com...
> Can I please, at least, get an acknowledgement from someone at
> Microsoft that they have seen this posting? Without a response
> whatsoever in a month's time, I'm wondering if it was posted at all.
> Hopefully I can get some sort of input as well as a viable workaround
> or plans for this bug to be fixed in a future release. This is quite
> a large bug. I appreciate anyone's time on this issue. Thanks.
> Frank|||It may appear that I'm arrogant and for that I am sorry, this was
supposed to be a reply to my original message. I should not be held
responsible for the Google technology not doing what it is supposed to
do. I also don't think it's arrogant to wait patiently for a month
for a reply and then ask again. So no digging was expected I just
didn't want to have the same message 2x on the same board. So please
ask before assuming. At least you replied though. So here is a copy
of my original post so that you don't think I'm lazy nor arrogant:
Message 1 in thread
From: Stoma_Kalos (fzuma@.yahoo.com)
Subject: Subscription BUG...Please place this on the fix list...
View this article only
Newsgroups: microsoft.public.sqlserver.reportingsvcs
Date: 2004-09-16 14:53:35 PST
This was a bit frustrating to figure out. Here's the problem, if you
create a subscription for a Linked Server on the MS Report Server
everything seems fine. If you decide to custom build your own Report
Server and use the CreateSubscription method and pass all the normal
property values for Reports everything seems to be fine. But if you
use the CreateSubscription method for a Linked Report, then you'll
receive an error (* - you can see this error on one of my other
postings).
After much deliberation and hair pulling I have come to the following
two conclusions about creating subscriptions:
1) When using the MS provided tool it will create a Linked Report
subscription, but it appears to leave out certain vital
ExtensionSettings like CC, BCC, etc. If you try creating a custom
subscription without these settings you will receive the error shown
in my previous posting*. So it is my assumption that MS is somehow
getting around this problem behind the scenes.
2) When creating any subscription, the ExtensionSettings, although its
datatype in the SQL Server database is ntext, will only be 256
characters or less. This tells me that a method or property behind
the scenes of the CreateSubscription method is truncating the
ExtensionSettings before it reaches the database.
Examples of the full ExtensionSettings column value in the
Subscription table. Notice the cutoffs at the ends and the missing
settings in the Linked Report value compared to the Regular Report
value.
Linked Report value:
<ParameterValues><ParameterValue><Name>TO</Name><Value>Frankxxxxx</Value></ParameterValue><ParameterValue><Name>IncludeReport</Name><Value>True</Value></ParameterValue><ParameterValue><Name>RenderFormat</Name><Value>MHTML</Value></ParameterValue><Parameter
Regular Report value:
<ParameterValues><ParameterValue><Name>TO</Name><Value>Frank
JFMAJJASN</Value></ParameterValue><ParameterValue><Name>CC</Name><Value
/></ParameterValue><ParameterValue><Name>BCC</Name><Value
/></ParameterValue><ParameterValue><Name>ReplyTo</Name><Value /><
* You may search for this posting to view the subscription error:
From: Stoma_Kalos (fzuma@.yahoo.com)
Subject: Saving Linked Reports In Subscriptions?
Please let me know if you need any more clarification.
Frank
"Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message news:<#4lv2c#qEHA.3760@.TK2MSFTNGP09.phx.gbl>...
> Um, might help if you posted the bug description. A little arrogant don't
> you think, that you expect us to dig through the group looking for an old
> post?
> For large bugs, I usually use a large shoe. Does that help?
> Jeff
> "Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
> news:e876e3c8.0410061158.a903962@.posting.google.com...
> > Can I please, at least, get an acknowledgement from someone at
> > Microsoft that they have seen this posting? Without a response
> > whatsoever in a month's time, I'm wondering if it was posted at all.
> > Hopefully I can get some sort of input as well as a viable workaround
> > or plans for this bug to be fixed in a future release. This is quite
> > a large bug. I appreciate anyone's time on this issue. Thanks.
> >
> > Frank|||"Stoma_Kalos" wrote:
> It may appear that I'm arrogant and for that I am sorry, this was
> supposed to be a reply to my original message. I should not be held
> responsible for the Google technology not doing what it is supposed to
> do. I also don't think it's arrogant to wait patiently for a month
> for a reply and then ask again. So no digging was expected I just
> didn't want to have the same message 2x on the same board. So please
> ask before assuming. At least you replied though. So here is a copy
> of my original post so that you don't think I'm lazy nor arrogant:
> Message 1 in thread
> From: Stoma_Kalos (fzuma@.yahoo.com)
> Subject: Subscription BUG...Please place this on the fix list...
>
> View this article only
> Newsgroups: microsoft.public.sqlserver.reportingsvcs
> Date: 2004-09-16 14:53:35 PST
>
> This was a bit frustrating to figure out. Here's the problem, if you
> create a subscription for a Linked Server on the MS Report Server
> everything seems fine. If you decide to custom build your own Report
> Server and use the CreateSubscription method and pass all the normal
> property values for Reports everything seems to be fine. But if you
> use the CreateSubscription method for a Linked Report, then you'll
> receive an error (* - you can see this error on one of my other
> postings).
> After much deliberation and hair pulling I have come to the following
> two conclusions about creating subscriptions:
> 1) When using the MS provided tool it will create a Linked Report
> subscription, but it appears to leave out certain vital
> ExtensionSettings like CC, BCC, etc. If you try creating a custom
> subscription without these settings you will receive the error shown
> in my previous posting*. So it is my assumption that MS is somehow
> getting around this problem behind the scenes.
> 2) When creating any subscription, the ExtensionSettings, although its
> datatype in the SQL Server database is ntext, will only be 256
> characters or less. This tells me that a method or property behind
> the scenes of the CreateSubscription method is truncating the
> ExtensionSettings before it reaches the database.
> Examples of the full ExtensionSettings column value in the
> Subscription table. Notice the cutoffs at the ends and the missing
> settings in the Linked Report value compared to the Regular Report
> value.
> Linked Report value:
> <ParameterValues><ParameterValue><Name>TO</Name><Value>Frankxxxxx</Value></ParameterValue><ParameterValue><Name>IncludeReport</Name><Value>True</Value></ParameterValue><ParameterValue><Name>RenderFormat</Name><Value>MHTML</Value></ParameterValue><Parameter
> Regular Report value:
> <ParameterValues><ParameterValue><Name>TO</Name><Value>Frank
> JFMAJJASN</Value></ParameterValue><ParameterValue><Name>CC</Name><Value
> /></ParameterValue><ParameterValue><Name>BCC</Name><Value
> /></ParameterValue><ParameterValue><Name>ReplyTo</Name><Value /><
>
> * You may search for this posting to view the subscription error:
> From: Stoma_Kalos (fzuma@.yahoo.com)
> Subject: Saving Linked Reports In Subscriptions?
>
> Please let me know if you need any more clarification.
> Frank
>
> "Jeff Dillon" <jeff@.removeemergencyreporting.com> wrote in message news:<#4lv2c#qEHA.3760@.TK2MSFTNGP09.phx.gbl>...
> > Um, might help if you posted the bug description. A little arrogant don't
> > you think, that you expect us to dig through the group looking for an old
> > post?
> >
> > For large bugs, I usually use a large shoe. Does that help?
> >
> > Jeff
> > "Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
> > news:e876e3c8.0410061158.a903962@.posting.google.com...
> > > Can I please, at least, get an acknowledgement from someone at
> > > Microsoft that they have seen this posting? Without a response
> > > whatsoever in a month's time, I'm wondering if it was posted at all.
> > > Hopefully I can get some sort of input as well as a viable workaround
> > > or plans for this bug to be fixed in a future release. This is quite
> > > a large bug. I appreciate anyone's time on this issue. Thanks.
> > >
> > > Frank
>