SQL Server 2005

We're trying to implement the application role for Microsoft
Forecasting. We've gone through the steps, but it isn't connecting.
We can connect easily when using a network login which has rights to
the database. We ran the "permissions" script and have a Forecaster
app role (and schema); we inserted the password into table Z_HLM3.

Once the Forecaster administrator has signed on, that password is no
longer in that table. At this point, we try logging in as another
network login(who does not have rights in the database), expecting
Forecaster to use the app role. Forecaster tries to authenticate with
the network login, rather than the app role.

Any insight? Did we miss a switch or some obvious step?

You most probably need to tak this to a group for your app (Forecasting), since it is the app that
need to execute the correct commands in order to use and app role. I did noticed some
misconceptions, though, which I suggest you clear up first:

> Forecaster tries to authenticate with
> the network login, rather than the app role.

The authentication to SQL server is always done using some login. This can be a SQL Server login or
a windows login. A windows login can be created either for a specific Windows account or a group in
Windows. One do *not* authenticate (login) using some app role.


> We can connect easily when using a network login which has rights to
> the database.

What is a "network Login"? A windows login? Or something else?


> We ran the "permissions" script and have a Forecaster
> app role (and schema); we inserted the password into table Z_HLM3.

All above are application specific, which you should troubleshoot with experts for the Forecaster
app.

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"JOH" <JOHolloway@gmail.com> wrote in message
news:d7565c8a-c15b-4bfb-b5a4-2f2586d4e25e@x41g2000hsb.googlegroups.com...
> SQL Server 2005
>
> We're trying to implement the application role for Microsoft
> Forecasting. We've gone through the steps, but it isn't connecting.
> We can connect easily when using a network login which has rights to
> the database. We ran the "permissions" script and have a Forecaster
> app role (and schema); we inserted the password into table Z_HLM3.
>
> Once the Forecaster administrator has signed on, that password is no
> longer in that table. At this point, we try logging in as another
> network login(who does not have rights in the database), expecting
> Forecaster to use the app role. Forecaster tries to authenticate with
> the network login, rather than the app role.
>
> Any insight? Did we miss a switch or some obvious step?

On Jun 17, 6:58 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@hotmail.nomail.co m> wrote:
> You most probably need to tak this to a group for your app (Forecasting), since it is the app that
> need to execute the correct commands in order to use and app role. I did noticed some
> misconceptions, though, which I suggest you clear up first:
>
> > Forecaster tries to authenticate with
> > the network login, rather than the app role.
>
> The authentication to SQL server is always done using some login. This can be a SQL Server login or
> a windows login. A windows login can be created either for a specific Windows account or a group in
> Windows. One do *not* authenticate (login) using some app role.
>
> > We can connect easily when using a network login which has rights to
> > the database.
>
> What is a "network Login"? A windows login? Or something else?
>
> > We ran the "permissions" script and have a Forecaster
> > app role (and schema); we inserted the password into table Z_HLM3.
>
> All above are application specific, which you should troubleshoot with experts for the Forecaster
> app.
>
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
>
> "JOH" <JOHollo...@gmail.com> wrote in message
>
> news:d7565c8a-c15b-4bfb-b5a4-2f2586d4e25e@x41g2000hsb.googlegroups.com...
>
> > SQL Server 2005
>
> > We're trying to implement the application role for Microsoft
> > Forecasting. We've gone through the steps, but it isn't connecting.
> > We can connect easily when using a network login which has rights to
> > the database. We ran the "permissions" script and have a Forecaster
> > app role (and schema); we inserted the password into table Z_HLM3.
>
> > Once the Forecaster administrator has signed on, that password is no
> > longer in that table. At this point, we try logging in as another
> > network login(who does not have rights in the database), expecting
> > Forecaster to use the app role. Forecaster tries to authenticate with
> > the network login, rather than the app role.
>
> > Any insight? Did we miss a switch or some obvious step?

Thanks for the clarifications.