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 |
|
sqlteam01
Starting Member
5 Posts |
 Posted - 2007-11-20 : 08:52:08
|
| I posted this in the developement forum accidentally. Hopefully I can get more helps from here.I have SQL Server 2000 on a Windows 2003 Sserver, configured as auto-start as when OS starts, using domain account as Startup Service Account. This win2003 is not a domain controller. It worked before but now the SQL 2000 does not start up automatically. If I manually start the SQL server immediately after the OS starts, error 1057 occured. It says "The account name is invalid or does not exist or the password is invalid for the account name specified." Every time, I have to wait for about 10 minutes and then start it successfully. Any helps will be highly appreciated. |
|
|
evilDBA
Posting Yak Master
155 Posts |
Posted - 2007-11-20 : 08:56:37
|
| Just a guess, is your Primary Domain controller installed on the same server? |
 |
|
|
sqlteam01
Starting Member
5 Posts |
Posted - 2007-11-20 : 11:17:32
|
evilDBA, the DC is on a w2k box, which is always on. Any other ideas? Thanks.quote:
Originally posted by evilDBA
Just a guess, is your Primary Domain controller installed on the same server?
|
|
|
|
Van
Constraint Violating Yak Guru
462 Posts |
Posted - 2007-11-20 : 11:29:17
|
| I've had very little if any experience with domain controllers and all but here's something that I used to run into. At a pervious job when we would have DR tests at the DR site, sometimes when the line was up between the company and the DR site and they were doing "stuff" with the domain controller switching it over to the DR site or whatever, I'd have issues connecting to or starting sql and would have to wait several min for it to connect. DTS packages that connected to other servers would take 10 min or so as well. Seems like it would time out and then use the other controller at the company rather than the DR site or something like that and then be able to work. Just something to look into. I bet your SQL server is trying for 10min or so to use one domain controller then switching to another or something like that. I'm no network admin so that may sound stupid. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-11-22 : 22:23:50
|
| Ensure sql server can access domain controller properly, let you win admin check it. |
|
|
|
|
|
|
SQL Server 2000 cannot start