December 26, 2008 at 2:26 pm
Hi everyone! We were upgrading one of our databases to Sql Server 2008 Enterprise Edition. We ran a mock migration to a virtual machine and it ran flawlessly, so naturally we went to town on the production machine. During the install I got an odd error (don't remember the wording off the top of my head).
Full Text Indexing, and Data Migration failed. I figured that wasn't a big deal -- seeing as I could import the data and repair full text indexing later. Upon trying to login to SSMS 2008 however, I was scared to say the least. I can't login. Went back to SSMS 2005, can't login. Tried admin login via command line. Can't login..
Is this a regular problem? I have been on Google for about a half an hour now and can't find a solid solution. Any ideas?
December 26, 2008 at 2:43 pm
Just an update. After reviewing the error logs I have found the cause of the error.
We have renamed our 'sa' account to something else which apparently causes the install scripts to fail.
mssqlserver /f /T3608 is responding with error code 126 so i can't rename the account. Anyone have any ideas? We have 23 million records MIA right now :sick:
December 26, 2008 at 5:52 pm
Did you check out this kb article? http://support.microsoft.com/kb/959077
Is there anything else in he logs besides the error 126?
December 26, 2008 at 6:16 pm
Just got an email and it reminded me of the thread! I actually figured out the problem!
I killed the system, and it seems the failed install left a few services running that kept the mssqlserver /f /T3608 from running properly. After a reboot and a quick look through task manager I killed the services, and renamed the sa user.
Following that I killed the mssqlserver and started the setup again. On the setup menu I went to maintenance and repaired the installation, it seemed to fix everything just fine. I'm doing a dbcheck to make sure everything is in it's place -- but really an odd issue. Failure to install because of sa name changes?
Hope if anyone else freaks out like I did they catch this in the archive!
December 26, 2008 at 6:19 pm
Thats quite a common problem.
Might be worth creating a new account with sysadmin permissions and taking all rights away from sa
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply