I'm already using SQL authentication in my app, and I'm using the exact same connection string, just modified to name localhost explicitly as mentioned earlier. I've already enabled TCP/IP and restarted the SQL instance. I also tried the firewall mods even though this is a purely local operation.
Mono seems to connect to the instance, but it times out after exactly 30 seconds when executing a command (presumably when fetching the schema or something). I've even granted the user I'm connecting with complete access to the db, ie. granted all server roles and all permissions to the specific database to connect to, thinking it was perhaps a permission issue, to no avail: DbLinq Database mapping generator 2008 version 0.20 for Microsoft (R) .NET Framework version 3.5 Distributed under the MIT licence (http://linq.to/db/license) >>> Reading schema from SqlServer database sqlmetal: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> Mono.Data.Tds.Protocol.TdsTimeoutException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at Mono.Data.Tds.Protocol.Tds.CheckForData (Int32 timeout) [0x00000] in <filename unknown>:0 at Mono.Data.Tds.Protocol.Tds.ExecuteQuery (System.String sql, Int32 timeout, Boolean wantResults) [0x00000] in <filename unknown>:0 at Mono.Data.Tds.Protocol.Tds80.Execute (System.String commandText, Mono.Data.Tds.TdsMetaParameterCollection parameters, Int32 timeout, Boolean wantResults) [0x00000] in <filename unknown>:0 at System.Data.SqlClient.SqlCommand.Execute (Boolean wantResults) [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at System.Data.SqlClient.SqlCommand.Execute (Boolean wantResults) [0x00000] in <filename unknown>:0 at System.Data.SqlClient.SqlCommand.ExecuteReader (CommandBehavior behavior) [0x00000] in <filename unknown>:0 I'll try the newest DbLinq the next time I have a chance, unless you have some other suggestion. Thanks for all the help. Sandro On Oct 4, 2:54 pm, Jonathan Pryor <[email protected]> wrote: > All I can suggest is two things: > > 1. Use -c "CONNECTION_STRING" instead of /user, /password, etc. > 2. You may need to configure SQL Server to allow access. Here's the > handy dandy "omfg that's gigantically long are you kidding me" > tutorial I wrote for getting a Mono-hosted NerdDinner app to > connect to a Windows-hosted SQL Server instance: > > http://www.jprl.com/Blog/archive/development/mono/2009/May-14.html#ne... > > Hopefully that's not entirely obsolete... > > I imagine you'll need (5)(C), (5)(D), and (5)(E). > > - Jon -- You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/dblinq?hl=en.
