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 |
|
cjp
Yak Posting Veteran
69 Posts |
 Posted - 2012-01-26 : 03:11:15
|
| After a computer repair, I re-installed SQLS 2008 and updated it to SP 3. This was a standalone installation using Windows authentication; it took the computer name as the name for the server. Let's call this abc123; I deliberately did not set a password at this point.Recently, my employer's IT department set the computer up on our network, using my University username and password as my Windows logon details; let's call this def456. Now, Sql Server won't let me connect to a database because it says 'login failed for username': in effect, def456 + password has replaced abc123 + no password and it doesn't know who I am.I have ferreted through various Microsoft helps on this but I could find nothing that treats this particular issue. Inevitably, the IT guy says he doesn't know how to fix this.I have tried logging in as administrator but this doesn't work. It seems to me that the change to Windows login details has created this impasse. Is there any way I can get it to log me in successfully to the original installation? Failing this, I will have to get our IT people to reload the OS and put me on to the intranet, and then I will reinstall SQL Server from scratch.Thanks.Chris |
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-01-26 : 07:01:40
|
| May be I am oversimplifying the issue, but shouldn't you be able to log into your local computer (using abc123) instead of logging into the University domain as the domain user and then access the server? Once you log into the local computer, you can then add the UniversityDomain\def456 as a user. |
 |
|
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2012-01-26 : 08:19:34
|
| Sunita is correct. Atleast to say there will be no connection with SQL with the University user account, unless this account was added with permissions before it was added to the domain (in which, wouldn't have been able to find that user in the first place.(No domain authentication))Your SQL install should have a local SA account, and when I say should, I mean it DOES have this account. Another thing; because you went from a local account to a domain account, the SID's wouldn't even match for either of the users. Just a few pieces of info....let me know if you have any questions about what I said. Hopefully it wasn't too confusing.Steve |
|
|
|
cjp
Yak Posting Veteran
69 Posts |
Posted - 2012-01-26 : 10:25:03
|
| Thanks for the advice. Following what you both said, I have managed to find my original identity and hack this so that it is presented at the logon window. Lo and behold - it works and I have recovered SQL Server. So - two lots of good news: I can use SQLS and I have plugged a gaping hole in my basic knowledge...Many thanks to you both.Chris |
|
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-01-26 : 10:42:18
|
| You are very welcome - glad it worked out! |
|
|
|
steve_r18
Yak Posting Veteran
59 Posts |
Posted - 2012-01-27 : 15:09:50
|
| Excellent to hear. These forums are by far one of the best resources for SQL!!Steve |
|
|
|
|
|
|
|
|
LOGIN DIFFICULTY