installation woe(s)

[steve]

my app installs itself then msde with the securitymode=sql...the app
installs for "everyone" and not "just me". we've been installing while
logged into an admin account. most of the end devices (laptops) have only a
local configuration (not domain) and use wifi to consume web services that
support the app. these end devices have not had any problems and the single
user account that has access to the device(s) is in the admin group.

we recently setup a training computer that *is* on our domain network. we
went through the same setup process. the only difference is that the user
account we created on this pc is *not* in the admin group. for some reason,
user accounts can only connect to msde if they have admin privileges. we
went ahead and temporarily put that account in the admin group for the pc
until we (i) can figure out what the fix is...if you have any information
re. this, i'd appreciate you sharing the knowledge.

tia,

steve

[Adam Goossens]

Hi steve,

Are you connecting to MSDE from within your app using an SQL Username
and Password, or relying on Windows Authentication? I understand you
said that you're using SQL Server Security Mode, but that also allows
Windows Authentication too. I just want to clarify :)

If you give your local user direct permissions to the correct MSDE
database, does that change anything?

Regards,
-Adam.

steve wrote:

my app installs itself then msde with the securitymode=sql...the app
installs for "everyone" and not "just me". we've been installing while
logged into an admin account. most of the end devices (laptops) have only a
local configuration (not domain) and use wifi to consume web services that
support the app. these end devices have not had any problems and the single
user account that has access to the device(s) is in the admin group.

we recently setup a training computer that *is* on our domain network. we
went through the same setup process. the only difference is that the user
account we created on this pc is *not* in the admin group. for some reason,
user accounts can only connect to msde if they have admin privileges. we
went ahead and temporarily put that account in the admin group for the pc
until we (i) can figure out what the fix is...if you have any information
re. this, i'd appreciate you sharing the knowledge.

tia,

steve

[steve]

"Adam Goossens" <ad**********@users.sourceforge.net> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
| Hi steve,
|
| Are you connecting to MSDE from within your app using an SQL Username
| and Password, or relying on Windows Authentication? I understand you
| said that you're using SQL Server Security Mode, but that also allows
| Windows Authentication too. I just want to clarify :)
|
| If you give your local user direct permissions to the correct MSDE
| database, does that change anything?

crap!!! we had been using trusted connections in the connection string but
later changed that so we wouldn't have to manage sql/windows users. that
change was not reflected in cvs! no wonder they couldn't connect! anyway, i
changed the connection string to use the user account that setup creates in
msde on install...all is well. and, this time it has been cvs'd - and
everyone will "refresh" before committing! ;^)

cheers,

steve

[Adam Goossens]

lol, glad to hear you sorted it out :)

Regards,
-Adam.

steve wrote:

"Adam Goossens" <ad**********@users.sourceforge.net> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
| Hi steve,
|
| Are you connecting to MSDE from within your app using an SQL Username
| and Password, or relying on Windows Authentication? I understand you
| said that you're using SQL Server Security Mode, but that also allows
| Windows Authentication too. I just want to clarify :)
|
| If you give your local user direct permissions to the correct MSDE
| database, does that change anything?

crap!!! we had been using trusted connections in the connection string but
later changed that so we wouldn't have to manage sql/windows users. that
change was not reflected in cvs! no wonder they couldn't connect! anyway, i
changed the connection string to use the user account that setup creates in
msde on install...all is well. and, this time it has been cvs'd - and
everyone will "refresh" before committing! ;^)

cheers,

steve