Failed SIM 5.1 sp1 install to remote MS-SQL

getting "Unable to get information from the specified database server" on database configuration page and fails to install to a remote SQL2005 db. both servers are same W2K3sp1 builds on HP DL hardware.

local facts: W2K3sp1 SIM to W2K3sp1 SQL2005 db, same VLAN, install domain account has both server admim group and SQL create/edit DB on remote db server. tested using sys DSN successfully over tcp port 1433 with install domain user/service account. Install domain accnt is domain admin. Remote db shows netstat connection from SIM server on port 1433. able to connect from SIM to SQL on remote server with SQL 2005 Server Mgt Studio/Tool using same install accnt. SQL Browsing service is enabled on remote db host, no firewalls running, AV or Windows. NSlookup is good, no other named SQL instances - straight SQL 2005 DB. Also failed install if changed tcp ports to 1453 or 1434. added hosts entry and restarted system after flushing dns didn't work and no change. password of user/service domain account only has ! exclamation mark in password. checked with switch admins and they confirm port 1433 is not blocked.

Re: Failed SIM 5.1 sp1 install to remote MS-SQL

if I let it default, it tried to install the MSDE version and if I select the 'other' option for remote SQL it still gives the 'can't find' time out error even though I can open a sql admin or ODBC connection to that remote SQL server. Thanks... I did try the steps you mention but I'm still getting the time out finding the remote SQL server (with no instance)...guess it's time to beat up on HP...

Re: Failed SIM 5.1 sp1 install to remote MS-SQL

Sounds like it.

The only other suggestion I might have is to use a copy of Wire Shark, and see what the traffic looks like. See if there is any response from the SQL server. Perhaps even get lucky and be able to inspect a SQL packet.

Re: Failed SIM 5.1 sp1 install to remote MS-SQL

We had this issue last week. I wanted to install my DB to a PolyServe Cluster. I left the DB name as 'Master' and the install creates its own DB. Make sure your service account has all the relevant DB permissions.