Hi,
I have changed my Reporting services from Windows Security to Forms Security. When I deploy reports on the local SQL server, a windows pops up. This windows requires my username and password for the report server. After I input them, everything works fine.
However, When I deploy reports to the above server from the different SQL server located on a different computer, the windows always pops up, although I type the same username and same password. Any ideas
Thanks a lot.

Forms security deploy problem and email-subscription
Jing
Thanks in advance!
xRuntime
edison_torres
The Forms extension failed to read its configuration settings from the RSReportServer.config configuration file. The extension is not available to users."
Any ideas
Thanks
Ingrid Vangkilde
Lamb
Thanks
Tudor
Murbro
Yes, I have already changed them on the computer where my reporting server is located. In fact, I have succeeded in implementing Forms security locally. Like what I described in my question post, after my inputing username and password, local deploying is fine. But when I deploy from another computer, after my inputer the same username and password, the poped-up windows is still there.
Moreover, I also encountered another problem. When email-subscription works under windows security, but it doesn't work under forms security. The error is "Object reference not set to an instance of an object."
Any ideas about them
Thanks a lot.
McWhirter
Hi ,
I have configured SMTP server and i have done email subscription to particular customer called "tbs".The report generates daily at 9:00pm and report will be sent to customer's email.But,if the report doesnot contain any Records,the report should not be delivered to Customer.
Could you be able to guide me and suggest me .
Thanks,
Jayaram
archangel82
Check whether the error comes from the (modified) sample code. For instance the sample implementation of GetUserInfo checks for the existence of the HttpContext and returns null if it's not present.
If you have changed that, it would be possible that it could fail when running the report as part of a subscription.
Thanks
Tudor