Re: Permissions Issue

From: Karl Levinson [x y] mvp (jamescagney90210@excite.com)
Date: 01/22/03 

From: "Karl Levinson [x y] mvp" <jamescagney90210@excite.com>
Date: Wed, 22 Jan 2003 11:12:25 -0500

If the problem is permissions, then enabling auditing should let you see the
problem. Running free tools such as RegMon, FileMon and/or Process Explorer
from www.sysinternals.com may also let you see something useful [and you can
change some hard to change permissions on some objects within Process
Explorer as well, I believe].

http://securityadmin.info/faq.htm#auditing

Since Power Users have the permissions necessary, you could also open up
GPEDIT.MSC and look at what permissions Power Users have there that other
users do not, and change the permissions there.

If the SQL client is running this application across the network using Named
Pipes or Multi-Protocol to connect to the SQL server with SQL authentication
selected instead of Windows authentication in the SQL server, then the
Windows account of the currently logged in user must have permissions to
authenticate to the SQL server over Netbios, before the SQL server can even
try SQL authentication. [e.g. if the logged in user can't get to a share
like \\sqlserver\c , then SQL authentication may fail]. Using a firewall or
IP filtering also breaks this authentication. For this reason, it may be
better to use TCP/IP in the SQL client instead of Named Pipes or
Multi-Protocol, so that pure SQL authentication can work without first
needing Netbios authentication. You can try to set this in the SQL connect
string in the web page code, but I believe you might also need to set this
within the SQL client software, and you might need to install the SQL client
software on the client to be able to specify this. [As far as I know.]

"MannyI" <eibrahim@nui.com> wrote in message
news:081401c2c226$281ab560$d7f82ecf@TK2MSFTNGXA14...
> I have published a custom VB application (6.0 with SQL
> Server 2000 DB) on an Advanced Server 2000 box. As the
> local admin, when I run the application it works fine.
>
> When another user (who is not the local admin to the 2000
> server)runs the same application, they get the Microsoft
> Visual C++ error stated above. When the user clicks the
> ignore button on the message box, the user is able to get
> into the application without any problems and the
> application runs fine afterwards.
>
> We put breakpoints in the code where the error comes up
> and it when the code tries to make an ADO connection to
> the SQL Server Database.
>
> I believe that the error is due to permissions but am not
> exacly sure how to resolve the issue. The reason I know
> it has to do with permissions is that when a user is added
> to the power users groups, the user does not get the above
> error.
>
> Does anyone have any ideas?"
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.443 / Virus Database: 248 - Release Date: 1/10/2003