Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
peter_mauger
Starting Member
2 Posts |
 Posted - 2006-08-07 : 22:55:58
|
| Hi,This is a bit of a bizarre error that I am getting consistently for a certain subset of my customers (a small subset... in the order of 5-10 offices out 120).I'm using a custom MSDE instance to run my commercial client-server application against. As part of my security measures I'm using an SQL login for my licensing service (located on the same machine as the database) to update the user's monthly license. The problem I'm having (and that has me completely baffled) is that the specific login keeps disappearing from the database...I haven't written a single script that could possibly be removing a login from the database (the only scripts I have that modify the security at all are run during the installation process). During the course of my investigations it appears that the following may be having some effect.In all instances of the error occurring (that I have discovered so far) the database and service have been installed on a machine that is not the domain controller for the network (so essentially a client machine). One of the clients with the problem was working from a laptop that had a dodgy network cable (and therefore connection) that dropped out from time to time. Checking the server logs for another client indicated that the time of first failure (ie when the login dropped off the face of the planet) directly coincided with the day their domain controller last went down.I have at least two other SQL logins that haven't ever exhibited the same behaviour so I'm a bit lost. Has anyone out there ever had a similar problem?Cheers,Peter MaugerSenior Software EngineerGlobal iQ |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-08-23 : 14:16:28
|
| The database server not being a domain controller or being a domain controller has no effect on an account being dropped. The OS, service pack level, etc... also do not impact this. The only way for a login to disappear is for someone or something to be doing it. The someone would be a person with sysadmin/sa privileges or securityadmin fixed server role permission. The something would be an application that can do the drop and has the permission as mentioned before. To troubleshoot this issue, you'll need to figure out what accounts have the ability to do this. Restrict the access down to the bare minimum. Is your application using the sa account? Does the customer have the password?Tara Kizer |
 |
|
|
om
Starting Member
8 Posts |
Posted - 2006-09-01 : 16:00:09
|
| thanks for kind information |
|
|
|
|
|
|
Login dropping off database