I am trying to track down an error I am getting while trying toconnect to a table in a named instance of SQL server 2005 using ILM"2" RC0I have put the same database on several different servers for testingpurposes including a default instance of SQL 2005 and SQL2008.SQL MAs connect to the default instances without any problem butconnection attempts to the named instance result in the follwiongerror: "Failed to retrieve the schema. Cannot connect to the databaseyou have specified."SQL MA configuration is as follows:Server: testdata10\ilminstanceDatabase: testdataTable/View: largesetcredentials are the same for all of my configurationsIs this a known issue or should I look for other issues with my setup?

Can you connect remotely to the named instance with other tools than MIIS and the SQL MA?What type of credentials are you using? Database only ormixed ?Which rights & permissions did you set for the connection account?Which OS are you running the SQL server on?Kind regards,PeterPeter Geelen - Sr. Consultant IDA (http://www.traxion.com)

Yes, I can connect to the named instance using SQL SMS I am using Windows integrated authentication using the same account info as used with SQL SMS Right now the user has dbowner role while I am tracking this down. The SQL Server is running SQL server 2005 (enterprise) on Windows server 2003 (enterprise) Thanks

I haven't tried it, but I know I ran into all sorts of issues early on (with the betas) that affected the connect string (essentially). For instance, the handling of "localhost" or "." changed over time with the SQL MA, so I wouldn't be surprised if this is a bug with the RC0 SQL MA. I would search Connect to see if someone has reported this before and if not, log the error for testing anyway.Brad Turner, ILM MVP - Ensynch, Inc - www.identitychaos.com

We have seen this issue being reported once before on Connect but couldn't repro the issue:https://connect.microsoft.com/feedback/ViewFeedback.aspx?SiteID=433&FeedbackID=384849&wa=wsignin1.0In this post there are also some other hints on why you might see this. /Andreas

Thanks, using an alias solved the problem