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 |
|
nossie
Starting Member
2 Posts |
 Posted - 2011-04-11 : 11:09:07
|
Hello.I'm a software engineer tasked with upgrading a SQL Server 2000 to 2008r2. So I'm very software savvy but not a SQL Admin by any means. I've installed SQL server here and there in the past but never under these conditions: The SQL Server is live and running about 50 databases for websites on a co-hosted win 2003 server.I keep failing on the upgrade with this message:The service is not starting due to logon failure. Make sure you are using the right combination of login name and password for the SQL Server service account. #1: What is the "service account"?#2: Can I run the upgrade against the 2000 server while it's running? Didn't see it saying I can't anywhere? Do I have to stop the 2000 service?During the install wizard it asks me for a account for the SQL Full-text Filter Daemon launcher. I've tried with a new account and a current account. If I put in a wrong user/pass combo it lets me know immediately. So I think that must be error free.When I view and browse the database in Microsoft SQL Management Studio (2008r2) it shows me Server=CDG Connection=CDG\admin-cdg. Useful information. Tells me I have he right password combo or not?Am stumped here. Any help appreciated.Thank you. |
|
|
dinakar
Master Smack Fu Yak Hacker
2507 Posts |
Posted - 2011-04-12 : 07:59:58
|
| (1) Service account is the account under which SQL Server is running. Go to Administrative Tools >Services and look for Microsoft SQL Server service > right click > Properties and find the account under which its running.(2) You dont (and shouldnt) stop the service. Just make sure there is no one using the system while you are doing the upgrade. On a side note, do run the SQL Server 2008 R2 Upgrade Advisor analysis to see if there is any code/feature that will break once you do the upgrade. Typically this should be done on a test system and not live.Dinakar Nethi************************Life is short. Enjoy it.************************http://weblogs.sqlteam.com/dinakar/ |
 |
|
|
raghuveer125
Constraint Violating Yak Guru
285 Posts |
Posted - 2011-04-12 : 08:12:06
|
| Yep the thing is true You should need to first try this on test server.Ok one more alternative solution is you can install named instance which is also known as side by side installation.Here You need to install new sql 2008 R2 with named instance. once installation is done you have to move your database one by one (or you can detach from 2000 and attache on 2008) to named instance and you have to find orphan database user and correct it. Once you moved all database next you can uninstall mssql 2000 from that server.Note: to find orphan users of each databaseuse [YourDatabaseName]gosp_change_users_login @Action = 'Report'Raghu' S |
|
|
|
nossie
Starting Member
2 Posts |
Posted - 2011-04-12 : 09:31:11
|
| Hi guys. I have it working.Since an engineer left the company we changed the webserver's password. When we rebooted the webserver SQL server 2000 wouldn't start until we reset the password in the Services panel to match the computer password. Everything seemed fine. THEN we tried the update. Then we got the "login failure" problem. So I just had a thought to put the computer and sqlserver password back to the old password and give it a go... guess what?... it has installed flawlessly. So there must be a 3rd location for a password that the install wizard was using. Honestly though I couldn't make a guess at it where.It's working now but I'm missing a full understanding of the problem.Thanks for the help :) |
|
|
|
|
|
|
Upgrading from 2000 to 2008 install problems.