Newbie Question: Setting Permissions correctly

[nshenry03]

Using MS SQL Server 2005 and MS Visual Web Development to Report information.

CoWorker set everything up and sent me a backup of the database and a .zip of the website. I am able to open database and view tables/info using MS SQL Server management tool.

When using Username/password he supplied I get error:
An error has occurred during report processing.
Exception has been thrown by the target of an invocation.
Login failed for user 'OII'.

When using Username/password I made I get error:
An error has occurred during report processing.
Exception has been thrown by the target of an invocation.
EXECUTE permission denied on object 'NewSelectCommand', database 'dev1', schema 'OII'.

from web.config
<connectionStrings>
<add name="dev1ConnectionStr" connectionString="Data Source=desktop_8sy3bb1\sqlexpress;Initial Catalog=dev1;Persist Security Info=True;User ID=nhenry;Password=*****"
providerName="System.Data.SqlClient" />
<add name="ReportConnectionString" connectionString="Data Source=desktop_8sy3bb1\sqlexpress;Initial Catalog=dev1;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="ShiftConnectionString" connectionString="Data Source=desktop_8sy3bb1\sqlexpress;Initial Catalog=dev1;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="dev1ConnectionString" connectionString="Data Source=desktop_8sy3bb1\sqlexpress;Initial Catalog=dev1;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="dev1ConnectionString2" connectionString="Data Source=desktop_8sy3bb1\sqlexpress;Initial Catalog=dev1;Integrated Security=True"
providerName="System.Data.SqlClient" />
<add name="dev1ConnectionString3" connectionString="Data Source=desktop_8sy3bb1\sqlexpress;Initial Catalog=dev1;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>

 

[sodakotahusker]

I would say you need to grant exec rights to that user(nhenry).
I have not worked with schema's so I am not sure about this. My guess is that you can grant exec rights to the stored procedure being called by the report. If that does not work, you'd have to grant the priviliges to the schema itself.