Thank you Microsoft for making this an unbelievable whipping. Your VB
provided version of the sample doesn't work. I have spent countless hours
trying to get it working and out of desperation I tried the C# version.
Hmmm, it worked on the first try. Why do you ship a defective version for
VB.NET? What is the deal Microsoft? You push VB.NET in Reporting Services,
but not in the forms authentication model. What is the deal? Is there an
ulterior motive to this? I have read and posted several questions related to
this error. How about you don’t provide a VB.NET example for anything that
doesn’t work. This is just mind boggling that you would provide an example
that didn’t work and delay implementing your product, in my case, for over
six months. DON’T provide a VB.NET sample if it doesn’t work! Do you get
the feeling that I am unhappy? Funny thing is that if MS was reading this
board, surely they wouldn’t have led so many people down this road. So
thanks for absolutely nothing MS. For anybody that reads this, the answer is
use the C# version of the sample.
In conclusion, MS has intentionally misled their developers with this
deception. Hey, I work for a MS Gold Partner and this isn’t a just for fun
project that I’m working on.
[quoted text, click to view] "Chris_CamSoft" wrote:
> I have completed the sample twice. I can validate from the /reportserver
> login, but not the /reports login (Report Manager). I get the error "Key
> cannot be null. Parameter name: key". I have seen this error in other post,
> but no solution. Does anybody know how to resolve this problem? I can
> create other users that can login without the error, but they have no access
> to the report server.
>
> Any help is very appreciated!
>
> Thanks.
