Unable to connect to database sts_config.mdf 1

[ddickers]

This is a new install of SBS 2003 R2, all went well with no error messages during install, but right from the start, I am unable to open

http://companyweb.

Any hints would be appreciated.

Thanks,
Don

 

[ShackDaddy]

Which of the main Wizards have you run/not run? Are the SQL services running in the Services list?

 

[ddickers]

So far, I have run all the wizards on the to do list. I have stopped and restarted several times the MS$SQLSharepoint, SPtimer, and IIS. Plus, going into the IIS under Web sites, going to the mycompany web site and starting and stopping it too; all with no joy.

One other thing that I didn't mention to open this thread, is that you can't open

http://companyweb.

It gets an runtime error screen that talks about putting some lines into the config.web file. Not sure what it is talking about yet.

Thanks,
Don

 

[ShackDaddy]

Can you post those errors? That will take us closer to the heart of the matter.

 

[ddickers]

Here is what it looks like: this is in the browser window in response to

http://companyweb/default.aspx:

Server Error in '/_layout' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

 

[ShackDaddy]

Find errorlog.txt and search it for the word: "failed" and see if you find any lines that deal with DNS, SharePoint or SQL.

Look for errors in the App Log from the MsiInstaller service.

A common cause for the SharePoint install to fail is a problem creating proper DNS records, but the information you find may give us other ideas as well.

ShackDaddy

http://www.shackelfordconsulting.com

 

[ddickers]

The problem is now solved. Thanks for your help.
Not sure what fixed the problem, but, after a while, the DNS record for sharepoint was removed, and when put back in, it came up and is now working good.

 

[ShackDaddy]

Great, glad to hear it!

ShackDaddy

http://www.shackelfordconsulting.com