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 |
Anthony Casey
Starting Member
4 Posts |
Posted - 2010-06-01 : 12:12:32
|
Hello all,I have a problem whereas, as of last week Tuesday users in my company (about 8 of them) can no longer gain access to a database program which is linked to SQL Server Express Edition.Before logging into the software from the client machines, there is a setup utility to configure and test connection to the database. This configuration uses an account setup in SQL Management Studio (Security > Logins) to authenticate the database...."Connected to OLEDB: DHSSVR01\TRISYS.TriSys (Db:TriSys) Successfully.Licensed for 12 users to 'Company'."After confirming the connection, I exit the setup utility and return to the software login screen and attempt to login but am given this message every time..."Incorrect login as '*username*' into database DHSSVR01\TRISYS.TriSysPlease try again."I have spent hours researching and cautiously trying a few things but nothing has worked so far.It seems that the 'programs' user accounts are managed from within the software itself which is 0% useful if you cant access the software in the first place.PLEASE PLEASE HELP.Many thanks in advance.Anthonyanthonycasey@dhs.org.uk |
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-06-01 : 12:51:58
|
If the user accounts are managed from within the software, then you'll need to contact the vendor of the software for assistance. I imagine that there is a users table (or similarly named) that you can query in SQL Server Management Studio. I would hope that the passwords are encrypted, but perhaps they are not. Check the users table to see if the records seem correct. Did anyone accidentally clear the table?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
|
|
Anthony Casey
Starting Member
4 Posts |
Posted - 2010-06-02 : 04:12:00
|
Thank you for the reply tkizer.Unfortunately, the software vendor charges extortionate prices for their support contracts and my boss is neither willing to pay the one-off support charge of £300 for a 2 hour phone call to which there is no guarantee of a fix.There is also the possibility that this is primarily an SQL issue so contacting the vendor could possibly be a waste of time depending on where their expertise lie. Either way, I need to do all I can to resolve this myself before taking things further.This 'Users table' you talk of is exactly what I am looking for and Yes, I am looking for a way to query this via the SQL Server Management Studio just like you say. Unfortunately, I am new to SQL and not yet versed with the SQL language.Can you (Or anyone else reading) kindly provide some suggestions on how to query this 'Users table' please?Further to your post, the passwords are not encrypted and I have a record of them all.Nobody had access to the server on the day of the occurrence so I'm quite sure the user table was not accidentally deleted although, I cannot be certain as I was not in the office that day.It does seem more than likely that the user table has somehow been cleared as we can confirm connection to the database from the client machines but then the error message states that the user names are invalid.Thank you again, I greatly appreciate your help!Anthony |
|
|
Anthony Casey
Starting Member
4 Posts |
Posted - 2010-06-02 : 12:24:51
|
Hello again,After having played around with this all day I've discovered the users table which does still has all of the users listed with 'user id', 'login name', 'password', 'name', etc. I just wish I could identify where the problem lies!!I have done much research today and tried a few things to see if I could resolve this.One of the things I noticed is that backups had not been done for some time and because of this the main log file on the HDD had grew to 42GB.In case this was somehow effecting the database, I ran a 'Full' and 'Transaction Log' log backups in an attempt to truncate the log files. Although this did not work first time round I was eventually able to truncate the transaction log file using the 'Shrink > Files' tool but unfortunately there has been no change to the logging in situation.I have the full backups before running the shrink in case there are adverse effects to data but my only concern right now is to get into the database software.Please, if there is anything else you can suggest to look into, I would be very grateful.What can you tell me about the resource locking statistics?Thank you,Anthony |
|
|
|
|
|
|
|