• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 637
  • Last Modified:

Going Nuts Here...SQL SERVER 2008 is installed but not being recognized as installed by other applictations

Here is what I have installed on my Windows 2008 Server Standard:
SQL SERVER 2008 R2 which was installed first. I selected all of the options like SQL Full Text Search FOR EACH INSTALLATION which does not show up in the Add Remove Programs. See Image. I get the following showing that the system health check has detected a problem some of which are

1. A compatible version of SQL Server is not installed.  NO NO NO ..... THEY ARE INSTALLED

Workaround / Remedy
SQL Server installation is a prerequisite for Visual Studio Team Foundation Server 2008. Install a supported version of SQL Server and then install any required service packs. For more information about supported versions of SQL Server, download the most recent version of the Team Foundation Installation Guide, which is available from the Microsoft Web site.

2. SQL Server is not listening for remote TCP/IP connections.  I DO NOT KNOW WHAT THIS ONE IS

Workaround / Remedy
Use the SQL Server Surface Area Configuration tool to enable remote TCP/IP connections.

3. The SQL Full Text Search service is not installed.  I CHECKED THIS ON BOTH INSTALLS AND IT DOES NOT SEEM TO SHOW UP IN THE LIST OF INSTALLED PROGRAMS.

Workaround / Remedy
The SQL Full Text Search service is not installed. To install this service, you must run Microsoft SQL Server setup and install this component.
SQLInstalled2008Server.png
0
ruavol2
Asked:
ruavol2
11 Solutions
 
Paul JacksonCommented:
Open SQL Server Configuration manager
Expand SQL Server Network Configuration
Select Protocols for MSSQLSERVER
Right-click TCP/IP and select enable
Select SQL Server Services
Right-click SQL Server (MSSQLSERVER) and select restart.

In Sql Server MAnagement Studio
right click the instance name and select properties
In the left pan click connections and check 'Allow remote connections' in the right hand pane.
click ok.
0
 
Alpesh PatelAssistant ConsultantCommented:
Have you tried to connect SQL Server using SSMS?

Please check Firewall settings, REmote connection enabled of SQL Server etc.

0
 
ruavol2Author Commented:
Jacko72 & Patel

Here is what I have done. I went in to the SQL Server Configuration Manager and for some Reason even though it shows up in the Services Section. The MSSQLSERVER does not show up in the SQL Server Configuration Manager or the SQL Server Management Studio. Even thought you can plainly see it in the Administrator Tools SERVICES. This makes no sense to me. Any other thoughts.

Also I noticed some items that did not get removed for some reason like the MICROSOFT##SSEE. I removed it before from the previous installs now it is back. Any thoughts.....? Please advise. Thank you.
SQLServerConfigurationManager.png
ConnectSQLServer.png
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Brendt HessSenior DBACommented:
Okay, I took a quick look at the images you provided, and saw nothing specific.  However, there are a few things to do.

1)  Have you loaded up the Surface Area Configuration tool for the new HOSTRPTS2008 instance?  If so, what is the result.  Please activate TCP/IP on that instance if you have not already done so.

However, I thought to dig a bit farther, and here's what I found:

Team Foundation Server 2008, by itself, will not work with SQL Server 2008. You’ll receive an error message that your SQL Server instance is not compatible, as well as other error messages such as Full Text not being installed.

Abdelhamid’s blog post at http://blogs.msdn.com/aabdou/archive/2008/05/13/team-foundation-server-sp1-beta-now-available.aspx gives instruction that should let you finish installing this.
0
 
BLipmanCommented:
It is that first one, the name of the server.  Based on your services.msc screen shot, your instance name is mssqlserver which is a default instance.  To access a default instance you use the server name or IP.  Alternately, type (local) and try that (this only works from the SQL server, not remote machines).  The SQL browser service can be helpful for applications to find the proper instance name and port but with a default instance I would guess the service would listen on 1433 (the default).  If you are using the Windows Firewall or an internal firewall/vlan, make sure 1433-tcp and 1434-udp are allowed inbound to the server (check this after your other attempts have not panned out).  Looks like you just about have it right though (the first two comments are the first two things I would have suggested).
0
 
arnoldCommented:
SSEE is the setup for WSUS
You have default instance MSSQLSERVER is this the one you installed?

Can you check what you have running from services
mssql (MSSQLSERVER> (default instance servername\)
mssql (SQLEXPRESS) (servername\sqlexpress)

etc.
If you are installing the application on a differnet server, you need to make sure to add the firewall rules to allow the remote system access via TCP/IP to this one on port 1433 or the port referneced under the TCP/IP settings for the connection/sql instance.

0
 
ruavol2Author Commented:
Gentlemen. I just do not know what to do?  I have gone into the SQL Server Management Studio and it launches the Window showing the SQL Server 2008 R2 and I have to pick a Server.

I am confused and just do not know what to do. I get the same darn errors.
I have every service started even the SQL Server agent. See images above. I have gone in and added ports for TCP and UDP for 1433 calling them the SQL Browser Service

I have even turned the Firewall completely off. Then tried to reinstall. Nothing has worked. Do you have any more thoughts otherwise I am going to have to take this offline and get someone to help me. I am in pretty desperate situation as development is halted and one of the top experts on EE is my business partner (mlmcc) and we cannot get started. I have about $50 dollars I can spare and that is about it to resolve this. Does anyone else have any thoughts....

One thing I am confused about is why do I have different SQL Server names listed on the SQL Server Configuration Manager and not under Services..... They seem different like something is missing.

Please advise I am all in......what can I do.....?
0
 
arnoldCommented:
open taskmanager, you should have four sqlserver instances running based on the number of SQL installs.
Instead of the server name you use "HOSTRPTS2008" use "(local)" and see if you have a different behavior.  Your HOSTRPTS2008 might only be resolving a specific IP while that is not that IP to which the sql instance you are having an issue with is bound to.
0
 
ruavol2Author Commented:
I opened the TaskManager and took the following screenshots. See images below.


I then went in to try to install team foundation server and typed in local. I then got the  following message.
Is this what you meant for me to do?
TaskManagerServices.png
TaskManagerProcesses.png
TFS-Installation.png
0
 
arnoldCommented:
(local)\instance
127.0.0.1\instance

Which SQL 2008 instance did you setup for this?
Use the sql server configuration manager which should also list the various instances you have and double check whether tcp IP is enabled and if it is enabled to what ip/port did you bind them?

I see two instances on your system, the default MSSQLSERVEr and the RPTMGRPRO to which are you trying to connect?

(local)
(local)\RPTMGRPRO

0
 
ruavol2Author Commented:
I tried (local)\RPTMGRPRO
(local)\MSSQLSERVER
(local)\SQLEXPRESS
None worked.

I went back to HOSTRPTS2008\RPTMGRPRO and got these same exact errors again.

The System Health Check has detected a problem that will cause Setup to fail.  
Description
A compatible version of SQL Server is not installed.
Workaround / Remedy
SQL Server installation is a prerequisite for Visual Studio Team Foundation Server 2008. Install a supported version of SQL Server and then install any required service packs. For more information about supported versions of SQL Server, download the most recent version of the Team Foundation Installation Guide, which is available from the Microsoft Web site.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that may cause Setup to fail.
Description
SQL Server Analysis Services is not installed.
Workaround / Remedy
SQL Server Analysis Services is a prerequisite for Visual Studio Team Foundation Server 2008. Install a supported version of SQL Server Analysis Services. For more information about supported versions of SQL Server and Team Foundation Server prerequisites, download the most recent version of the Team Foundation Installation Guide, which is available from the Microsoft Web site.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that may cause Setup to fail.
Description
The SQL Server Analysis Services service is stopped.
Workaround / Remedy
The SQL Server Analysis Services service is stopped. In Control Panel on the Analysis Services server, double-click Administrative Tools, double-click Services, and then look for the SQL Server Analysis Services service. If the service is not running, start it by right-clicking the service and then clicking Start.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that may cause Setup to fail.
Description
The SQL Server Analysis Services service is not set to start automatically.
Workaround / Remedy
The SQL Server Analysis Services service is not set to start automatically. In Control Panel on the Analysis Services server, double-click Administrative Tools, double-click Services, and then look for the SQL Server Analysis Services service. Double-click the service to view the service properties. In the Startup type list, click Automatic, and then click OK.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that will cause Setup to fail.  
Description
The SQL Server Analysis Services instance was unavailable for querying instance information.
Workaround / Remedy
The SQL Server Analysis Services instance was unavailable for querying instance information. Please check to make sure the instance is running and available.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that may cause Setup to fail.
Description
Windows Firewall is not enabled.
Workaround / Remedy
Windows Firewall is not enabled on this computer. Team Foundation setup will not add exceptions to Windows Firewall to install and use this product. If you enable Windows Firewall at a later time, or you are using a third-party software or hardware firewall product, you must add these exceptions manually. For more information on required ports, see the Team Foundation Installation Guide.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that will cause Setup to fail.  
Description
The SQL Full Text Search service is not installed.
Workaround / Remedy
The SQL Full Text Search service is not installed. To install this service, you must run Microsoft SQL Server setup and install this component.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that will cause Setup to fail.  
Description
The SQL Full Text Search service is stopped.
Workaround / Remedy
The SQL Full Text Search service is in a stopped state. In Control Panel, double-click Administrative Tools, double-click Services, and then look for the service. If the service is not running, start it by right-clicking the service and then clicking Start.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 
 The System Health Check has detected a problem that will cause Setup to fail.  
Description
The SQL Full Text Search service is not configured to start automatically.
Workaround / Remedy
The SQL Full Text Search service is not configured to start automatically when the computer starts. In Control Panel, double-click Administrative Tools, double-click Services, and then look for the service. Double-click the service to view the service properties. In the Startup type list, click Automatic, and then click OK.
More information
For additional information and help please refer to: http://go.microsoft.com/fwlink/?LinkId=79226 


Then I tried this as well HOSTRPTS2008\MSSQLSERVER and got the error below.
TFS-InstallationProblem.png
0
 
arnoldCommented:
When using Sql server management studio (SSMS), are you able to connect to HOSTRPTS2008?
MSSQLSERVER is a placeholder for the default instance and does not need to be included as an instance reference.

It is not clear to me what the version that the foundation app you are installing is looking for.
Using the SSMS make sure you are able to connect and then run
select @@version.
See whether the instance to which you are connecting has the correct version of SQL server tha is required for what you are installing.
0
 
ruavol2Author Commented:
Yes I am connecting to SQL Server Management Studio to HOSTRPTS2008.

I was told that TFS 2008 would take SQL Server 2008 R2 So I installed it.

When you say " SSMS make sure you are able to connect and then run select @@version " I am not quite following you sorry...?

Should take SQL 2008 R2.

Why is it in Services it says RPTMGRPRO as the name of the database and the connection in SQL Server 2008 R2 says REPORTMANAGERPRO...? Am I on to something here....?
ConnectingToSQLServerMgrStudio.png
ConnectingToREPORTMANAGERPRO.png
0
 
arnoldCommented:
What is the name of the instance that you installed.

One you connect to the sql 2008 R2 that you installed using SSMS.
There is no reportmanagerpro instance based on the services entry from the taskmanager you posted. You have a rptmngrpro instance. http:#a35816455 the image http://filedb.experts-exchange.com/incoming/2011/05_w22/461877/TaskManagerServices.png

Did you check the sql server configuration tool to make sure that TCP/IP is enabled on the SQL 2008 R2 instance you installed? And check the port configuration.
0
 
ruavol2Author Commented:
I am going to have to apologise for my ignorance.
When you say this:"What is the name of the instance that you installed." I thought I originally set this up to use MSSQLSERVER then I do remember Since I could not get it to work. I tried intsalling it was either RPTMGRPRO or REPORTMANAGERPRO as the database name. Now I am not so sure what it was I called it or if a previous installation kept one of the names I gave and did not erase it upon uninstallation.

I will check this tomorrow:
"Did you check the sql server configuration tool to make sure that TCP/IP is enabled on the SQL 2008 R2 instance you installed? And check the port configuration."

I thought I had done this but I am not so sure now. I created a UDP and the other ??? for 1433 and completely turned off the firewall. Where do I go to do that?
0
 
ruavol2Author Commented:
I am going to e working on this server and attempting to install the Team Foundation Server this weekend. I think this question was scheduled for deletion. I may still need this question open. Else I will repost. The problem is still the same and I have not been able to get it installed.
0
 
ruavol2Author Commented:
Nothing worked. Had two different guys supposedly senior tech at Geek Squad. Neither could make it happen so that asked if I would consider reformatting ................the standard I have seen on all the machines I took to Geek Squad. So far nothing I have sent them could be fixed. 3 out of 3 machines the concluded simply had to be rebuilt..............what a disappointment............!

No one could get team foundation server installed. Spent weeks on it, No one could get Windows 7 Pro SP1 to update. etc.

I will reward points on effort and leave it for you to tell me whether it should be sent to the knowledge base.......your thoughts appreciated.
0
 
arnoldCommented:
During setup did you setup/grant the administrator access to the sql server/instance?
Try using the sql server 2008 surface area configuration tool connect to the correct instance and try to add administrator.
This might be what prevents you using windows authentication from gaining access.
See if the add administator option helps.
Did you set the sa for sql login and did you try using that.  Been a while so do not remember if this was tried and did not go through the whole thread.
0
 
ruavol2Author Commented:
I have a brand new install of 2008 Server and I do not think that when it was installed that the guy that did it actually did what you said above. I will try that tonight and see if it helps. You are saying that the thread is above......?
0
 
arnoldCommented:
SQL on pre Vista would auto allow the administrator account access to SQL.
After vista the Administrative account has to be added during the install or if you setup SQL auth and windows auth, you would need to login with the sa account and add the logins into the security section of the database configuration and then add the windows login to allow it access to the database or via defining it with a specific role i.e. sysadmin/dbowner, etc.
0
 
ruavol2Author Commented:
Valiant effort. I still could not get the Team Foundation Server to install. Nor could the best guy they had at the Geek Squad at the National call center support or the local one I had. I do not know what stopped us but we did all we could. That much I know. Thank you for all your help.

Maybe Microsoft wants to make it a mystery to everyone too. Never seen anything so hard to setup or configure in my life. Ever
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now