***** Deployment error: Connection closed ******

c:\Report1.rdl The underlying connection was closed: An unexpected error
occurred on a send.
When i deploy I get this error sometimes. It gets resolved on its own. Its
like a hit and trial thing, sometimes it runs, sometimes it doesnt. Wonder
what am I doing wrong?
ThanksThis could be is an IIS timeout issue. You can change this value in IIS
manager.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"NI" <NI@.discussions.microsoft.com> wrote in message
news:673C1CD2-8511-4585-8193-83A52AF2DB62@.microsoft.com...
> c:\Report1.rdl The underlying connection was closed: An unexpected error
> occurred on a send.
> When i deploy I get this error sometimes. It gets resolved on its own. Its
> like a hit and trial thing, sometimes it runs, sometimes it doesnt. Wonder
> what am I doing wrong?
> Thanks
>

(very) basic security questions

I'm almost ready to deploy my web application onto a shared server at my ISP, the application uses SQL Server 2000.

I am using paramaterised queries for all read operations and stored procs for all of the updates. While developing, I have been using a trusted connection to connect to SQL server.

Now that i'm about to deploy, what steps do I need to take to ensure that there is a single user which has basic read permissions plus execute permissions on the stored procs. The main things that i'm confused about are:-

1. What, typically do I need to set up? A new role? A new user group?
2. Trusted connections - I notice from my own connection string that I am not passing in a password. Why is that? If I continue to use a trusted connection to the server at the ISP, do I need to ask the ISP for any login information? Wil I need a password on the connection string (from what i've read so far, trusted connections are preferred becasue no password is transferred - how can that be?)

I know these are very basic questions, but all of the material i've read so far seems to assume some basic prior knowledge, (which as you can tell I don't have!)

Appreciate any help,

Thanks
BernieIn all the situations I have seen from remote hosting, you will need to change your connection string from trusted to one that has the uid=suppliedbyhost;pwd=suppliedbyhost;
If you look over your sp's check to see if dbo is the owner. This will limit the access on the remote host.