blob: 2cb671567c714848f08aab756e1783b10f4727ae (
plain)
1 SQL 2008 Reinstall Errors
2 =========================
3 :author: Aaron Ball
4 :email: nullspoon@iohq.net
5
6
7 == {doctitle}
8
9 Hello again all, Recently, after the server build was 'finished', I discovered
10 that the SQL install was not configured to use the proper authentication method
11 or service accounts (oops) and without mixed mode authentication enabled,
12 windows authentication could not be used to log in to sql to fix these things.
13 That being said, I had to uninstall SQL 2008 (standard edition) and do a
14 reinstall to correct these issues. Time to grab some popcorn and a drink and
15 sit back to watch that entertaining progress bar as it slowly creeps across the
16 tiny 800x600 virtual console window.
17
18 I configured the SQL install and ran into an ambiguous error (how typical).
19
20 ----
21 This access control list is not in canonical form and therefore cannot be modified.
22 ----
23
24 How quaint. Thankfully, after searching for a few minutes with our friend
25 Google, I stumbled upon a Microsoft feedback article that seemed to contain my
26 answer.
27
28 Here's what needs to be done.
29
30 Navigate in an explorer window to
31
32 C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
33
34 The link at the end of this post to the Microsoft feedback article says that
35 from there you open up the "**details.txt**" file. I found that that folder
36 actually contained 11 folders (from the current install and the previous
37 install) and a file called "summary.txt". I found the right "**details.txt**"
38 file in the most recently created folder.
39
40 Once you've located the right "details.txt" file, open it up in notepad (or
41 your editor of choice) and scroll to the end of the file (it's pretty big so
42 use the scroller bar). Near the end, you should see some text that looks
43 similar to...
44
45 ----
46 2009-05-30 18:02:40 Slp: Sco: Attempting to set directory full path
47 2009-05-30 18:02:40 Slp: Sco: Attempting to normalize directory path C:Program FilesMicrosoft SQL Server100COM
48 2009-05-30 18:02:40 Slp: Sco: Attempting to check if directory C:Program FilesMicrosoft SQL Server100COM exists
49 2009-05-30 18:02:40 Slp: Sco: Attempting to set security descriptor for directory C:Program FilesMicrosoft SQL Server100COM, security descriptor D:(A;OICI;FRFX;;;S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582)
50 2009-05-30 18:02:40 Slp: Sco: Attempting to check if directory C:Program FilesMicrosoft SQL Server100COM exists
51 2009-05-30 18:02:40 Slp: Sco: Attempting to normalize security descriptor D:(A;OICI;FRFX;;;S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582)
52 2009-05-30 18:02:40 Slp: Sco: Attempting to replace account with sid in security descriptor D:(A;OICI;FRFX;;;S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582)
53 2009-05-30 18:02:40 Slp: ReplaceAccountWithSidInSddl -SDDL to be processed: D:(A;OICI;FRFX;;;S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582)
54 2009-05-30 18:02:40 Slp: ReplaceAccountWithSidInSddl -SDDL to be returned: D:(A;OICI;FRFX;;;S-1-5-80-3263513310-3392720605-1798839546-683002060-3227631582)
55 2009-05-30 18:02:40 Slp: Prompting user if they want to retry this action
56 ----
57
58 The text you're looking for is the directory path listed after the text
59
60 ----
61 Attempting to normalize directory path
62 ----
63
64 Open up another explorer window and navigate to (not inside) the directory that
65 is specified after the previous quote. Right click the directory (in this case,
66 the directory is COM within the directory 100) and select "*" tab. Windows
67 should give you an error that says something along the lines of the permissions
68 being out of order and might not be effective (sorry...I forgot to copy that
69 error).
70
71 Click "*" window to close it out as well.
72
73 Go back to your installer now and click "*" on the error window.
74
75 I had to fix two directories. The guy in the Microsoft feedback article said he
76 had to fix five directories. That being said, this may need to be done more
77 than once.
78
79 That about sums this up. The article I found that helped me get started fixing
80 this can be found here:
81
82 http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=355216
83
84 Dirk
85
86
87 Category:Microsoft
88 Category:MsSQL
89
90
91 // vim: set syntax=asciidoc:
|
