App Controller won't connect to SQL server on same server

Installing App Controller 2012 RTM on same server with SQL 2008 Developer (which I understand to be an extension of Enterprise). I already have SCVMM 2012 installed on another server and so far it is working fine.

When I try to install App Controller, I have no problem with the domain user account, port, certificate, all is well until I get to the database.

I enter the FQDN of the server, the instance (which is the same as running in services), and the name of the database I created. Now I get this error:

A network-related or instance-specific error 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 that SQL Server is configured to allow remote connections.

No other errors or codes given. Using SQL default port number 1433. SQL server and agent services are running. If I just use the hostname, then it says the specified SQL instance is not a supported version or edition. Is Developer not supported? I read it is just Enterprise with some additional features. I am able to connect to the SQL management studio fine.

Any suggestions?

May 21st, 2012 10:03pm

Hi,

The setup log may have a more detailed error message to show why it is not able to connect to a database. You can find it in %TEMP%\App Controller.

In order to install the App Controller server, you must be logged in as a domain user with membership in the local Administrators group, or equivalent, on the computer that you are configuring. This account must also have at least DBO permission on the database that will be used.

On the Configure the database page App Controller Setup will prepopulate the Server name with the name of the computer. If this is not happening it suggests that Setup is not able to correctly identify the SQL Server.

If you have a default database install then a value is not required for the Port field - entering 1433 also shouldn't cause any issues.

If App Controller Setup is able to connect to the SQL Server then after a short delay the list of available instances will be populated in the Instance name list. If this is not happening then it suggests that App Controller Setup is not able to query for the instances - either due to a connection or permissions issue.

For the Database name the account with which you are installing the App Controller server must have at least database owner (dbo) permissions in the specified database. If the specified database does not exist and the current user has the appropriate permissions, the App Controller setup wizard will create it for you.

Thanks

Richard

Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2012 9:41pm

My account appears to have dbo permissions. The SQL database and App Controller are on two different servers. I have my domain account set up as an authorizer user for SQL and it is the owner of the App Controller database. When I try to install it, I use my domain account, the FQDN of the SQL server, no port, it auto populates the instance and database just fine, then it says a network or instance specific error has occured, the server was not found or accessible.

But if the server was not found, how was it able to find populate those fields? This doesn't make any sense to me.

Sorry it too so long to reply. I was given another project for the past few weeks and SCVMM 2012 and App Controller had to wait.

June 26th, 2012 2:05am

Nevermind. The problem has been resolved.
Free Windows Admin Tool Kit Click here and download it now
June 27th, 2012 1:07am

Hi, How did you fix this, I have the same issue?
July 16th, 2012 6:13am


SQL Server

Free Windows Admin Tool Kit Click here and download it now
August 17th, 2012 3:37pm

i am having the same problem with the specified SQL instance is not a supported version or edition.

but SQL developer is meant to cover all SQL editions.

does anyone have any ideas on how to fix this?

November 9th, 2012 7:33pm

Hi Catherine

The setup for App Controller looks for specific editions of SQL Server which it recognizes as supported and Developer is not a supported edition.

The right to a supporting SQL Server Standard Edition runtime is included with all Client or Server Management Licenses for System Center 2012 so we recommend using SQL Server Standard rather than trying to use Developer.

The Developer edition of SQL Server allows developers to cost-effectively build and test and demonstrate applications based on SQL Server software.  

Kind Regards,

Richard

Free Windows Admin Tool Kit Click here and download it now
November 16th, 2012 3:22am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics