Looks like SQL Browsing is on but we can't connect without the port number still. Is the port number something that can really trip up the installation? Thanks! Sami

It turned out to be an issue on the SQL side--the port was not being accepted by the portal service installer when it tried to access the SQL Agent. This is a test environment for SQL shared across multiple applications in the organization, so we're not really sure what the precise problem was as we created a new instance of SQL and used the default instance and that installed. Thanks for your help! Sami

Hi, We are trying to install the FIM service connecting to a sql database on another server. We have given sys ad and admin rights to the installing account. We have run the installer with the verbose logging and are receiving this message: " Invoking remote custom action. DLL: C:\Users\SRV_FI~1\AppData\Local\Temp\2\MSI230.tmp, Entrypoint: CheckSQLServerAgent MSI (c) (C0!A8) [16:11:34:786]: PROPERTY CHANGE: Adding SQLSERVICENAME property. Its value is 'MSSQL$AGLSQ01,49634'. MSI (c) (C0!A8) [16:11:34:786]: PROPERTY CHANGE: Adding SQLAGENTEXIST property. Its value is '0'. MSI (c) (C0!A8) [16:11:34:786]: PROPERTY CHANGE: Adding IS_SQL_AGENT_RUNNING property. Its value is '0'. Action ended 16:11:34: CheckSQLServerAgent. Return value 1. Action 16:11:34: ErrorSQLAgentNotFoundDlg. Dialog created" We have checked that the account can log into SQL, create Agent jobs, and start SQL agent jobs. (The error message in the dialog says that SQL Server Agent is not running or the account does not have permissions to access it.) Does the MSSQL$ in the SQLSERVICENAME property indicate it could be trying to create something locally? Has anyone encountered this before? The server name for the database we gave SERVERDB1.domain.com/instance,port. But it looks like it is using MSSQL$instance,port. Thanks for any help. Sami

just a note the syntax you must specify SQLSERVER\INSTANCENAME not SQLSERVER/INSTANCENAME ... when using named instance the MSSQL$INSTANCE is the SQL server service name running in windows services (not the display name: SQL Server (InstanceName) this is for SQL 2008 R2 ). try to use the syntax SQLSERVER\INSTANCENAME without the port and make sure the SQL browser service is running to automatically provide the correct port based on the instance name. It's never too late in life ... to start living

Hi Amer, Thank you so much for your suggestion (and apologies for my typo--long day). We aren't able to get past the configuration scrren without the port number, but the DBA is not around to verify that the SQL Browser Service is running, so we will see if he can check that out soon. Thank you again! Sami