SQL Server 2008 Install – Second Try

The SQL Server install didn’t go well. I tried to install the full suite and four of the five services failed.

So I reverted and thought I’d explore a different track.

First of all, I was trying to use the free SQL Server Developer Edition x64 that I got from the Heroes Happen Here Road Show. I know that version expires in 180 days but it was in hand and I had used it successfully before.

For this second try, I was considering alternatives. Microsoft offers this download that’s also good for 180 days. It’s a 1gb+ download so I started it and went to get some coffee.

Once it’s completed downloading, I run the setup.exe program. I check my prerequisites and it warns me about installing on a domain controller. Then I check the Installation tab and select New Installation. It runs the setup configuration check and I pass seven of seven. I click OK.

I specify Enterprise Evaluation and click Next.

I accept the terms and click Next and then Install.

Again, it warns me about the domain controller. It also mentions firewall rules saying:

..make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/fwlink/?LinkID=94001 for information about ports to open for each feature.

Since I’m not looking for remote access at this point, I click Next.

I get a Setup Role page. It wants me to setup Analysis Services with SharePoint Integration. I’ll forego that for now, hoping just to get the database engine to start. I may have to retrace my steps to get this to work later. I click Next.

On the Feature Selection page, I just check the Database Engine Services, Full Text Search and the client tools and click Next.

The Installation Rules page tells me nothing will be blocked. This time, I pass five out of five. I click Next.

I leave the default instance checked and click Next.

It tells me I’ve got enough disk space and click Next.

I tell it to use the same account for all services. I enter the user name and password of the service account I created earlier which is a domain admin account. I click OK on the username box and then I click Next.

I select Mixed Mode authentication, enter an SA password. I add the current user as a SQL Server admin and click Next.

I let it send whatever it wants to Microsoft and click Next.

The Installation Configuration Rules page tells me I’ve passed four out of four. I click Next.

I get a summary and I click Install.

@Success (tipping my hat to my Domino programmer buddies)

I open SQL Server Management Studio, watch the progress lights and I get the SQL Server login window.

I try MyNewDomainController.MyNewDomain.com: No Good.

I try the IP address: No Good

My error, in both cases is:

Cannot connect to 192.168.1.20

A network-related or instance specific effor occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and then SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a conection to SQL Server)(Microsoft SQL Server, Error 5)

I found this from our new best friend Pinalkumar. At his suggestion, I check the services in the Configuration Manager. The SQL Browser and SQL Agent weren’t running so I started them both. Still no luck but, also at his suggestion, I try to connect to LocalHost. Again @Success. I can also connect to MyNewDomainController which is the computer name but not the FQDN which is MyNewDomainController.MyNewDomain.com. I noticed that the Browser service and the FT Scheduler Daemon were set to manual startups. I changed them to Automatic.

I look deeper into the Configuration Manager and I see that the SQL Server Network Configuration has a Protocols for MSSQLSERVER and, among those protocols, TCPIP and Named Pipes are disabled. I enable them and restart the services.

Also, I realize my network adapter was told to use external DNS so IP will not be looking to MyNewDomainController to resolve host names. So I added MyNewDomainController and MyNewDomainController.MyNewDomaincom to my hosts file pointing to the LAN IP address.

Finally, @Success one last time. I can connect to my SQL Server using computer name, FQDN, IP address and localhost.

Pinalkumar also has some help with the Firewall settings but his screenshots show Windows Vista. One day, I’ll have to figure this one out.

I’ll restart and take a snapshot here before I backtrack to install Report Services and Analysis Services. Then we can try the SharePoint 2010 install.

HTH

-robot


Tags:

 
 
 

Comments are closed.