<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Cambria;
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>OK, after TOO many hours of looking at this thing I think I’ve got it sorted out. The kicker is, I don’t know how it got broken!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Over the years that SharePoint has been running in our environment I’ve never altered the core server configuration since I got it up and running. However, I’ve always been curious about the number of databases that seem to be related to SharePoint but that I didn’t know why they were there or how they got there (deep magic, I’m sure). From time to time I’ve had to correct permissions related issues by manually deleting users from the SharePoint users database that weren’t showing up in the web GUI. So, I knew where the active SharePoint database was. I just figured that the other databases had some other role I didn’t understand and – as long as it worked – I didn’t care!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Then, this problems occurs. I STILL don’t know what triggered it. I followed the procedure at the article posted but was getting the response “</span><span style='font-family:"Courier New";color:#1F497D'>Value does not fall within the expected range”</span><span style='color:#1F497D'> when running it against the database specified as the content database in the SharePoint Central Administration console under Virtual Server Management. I didn’t see that in the list of normal responses so I thought it must mean that there wasn’t a problem with this database.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>After a long conversation with a “SharePoint expert” technician where he told me he would have to go off and research it and come back with an answer tomorrow, I decided to take your advice, Dayron, and do the procedure again. So I started with the same database in the CLI as before with the same result. I continued to follow the procedure, removing and adding back the configuration database. Still no joy. But, I couldn’t help but wonder, why did that database have no “sites” in it? The other database, the one with the user content, had a site and it was appropriately named. What if I run the CLI command on it? Viola! The result described in the article!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Now what? Well, it’s already broken, let’s get crazy. What would happen if I substituted the database with the user data in it for the configuration database in the administration console? Drum roll, please! TA-DA!!! Back to the browser, reload the page and all appears to be well. A big sigh of relief!<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>The moral of the story is, “Weird stuff happens!”<i><o:p></o:p></i></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Side note: If it hadn’t been for SQL Server Enterprise Manager, I’d still be puzzling at it. LONG LIVE Enterprise Manager (or its current equivalent)! It’s helped me greatly with Shelby too.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#1F497D'>Bobby<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> discuss-bounces@itdiscuss.org [mailto:discuss-bounces@itdiscuss.org] <b>On Behalf Of </b>Danny Ybarra<br><b>Sent:</b> Monday, February 22, 2010 2:47 PM<br><b>To:</b> IT Discussion Forum<br><b>Subject:</b> Re: [itdiscuss] SharePoint Gurus?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Start with event logs on the wss server and the sql server. The usual suspects of these type of problems are password changes for service accounts. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Since you said it was remote use telnet for checking that the ports are still open over the firewall.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>After that on the wss management make sure that wss is pointing to the db server.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-family:"Cambria","serif";color:black'>Danny Ybarra</span><span style='font-family:"Cambria","serif";color:#1F497D'> </span><span style='font-size:13.5pt;font-family:"Cambria","serif";color:#A6A6A6'>|</span><span style='font-family:"Cambria","serif";color:#1F497D'> </span><b><span style='font-family:"Cambria","serif";color:#7030A0'>Viant</span></b><b><span style='font-family:"Cambria","serif";color:black'>Solutions</span></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><b><i><span style='font-size:10.0pt;font-family:"Cambria","serif";color:black'>IT Consultant<o:p></o:p></span></i></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Cambria","serif";color:#7F7F7F'><a href="mailto:DannyY@viantsolutions.com"><span style='color:#7F7F7F'>mailto:DannyY@viantsolutions.com</span></a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Cambria","serif";color:#7F7F7F'>office: 678.889.6089 x103</span><span style='font-size:10.0pt;color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Cambria","serif";color:#7F7F7F'>mobile: 678.358.4603</span><span style='font-size:10.0pt;color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> discuss-bounces@itdiscuss.org [mailto:discuss-bounces@itdiscuss.org] <b>On Behalf Of </b>Bobby Stewart<br><b>Sent:</b> Monday, February 22, 2010 3:27 PM<br><b>To:</b> IT Discussion Forum<br><b>Subject:</b> [itdiscuss] SharePoint Gurus?<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve got a sticky SharePoint problem. We use WSS 2.0 on Win 2003 R2 with SQL 2000 on a remote server. This weekend, after working almost flawlessly for years, we started getting the message "The Web site that is referenced here is not in the configuration database" when browsing to the SharePoint site.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Anyone got any pointers?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bobby Stewart<br>Network Analyst<br>Brentwood Baptist Church<br>Brentwood, TN<br><a href="http://WWW.BrentwoodBaptist.com">WWW.BrentwoodBaptist.com</a><br>(615) 324-6149 office<o:p></o:p></p><p class=MsoNormal>(615) 830-0012 cell<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>