I just tested the new Config Service with TCP/IP disabled and it doesn't work for SQLExpress with a named instance.
I've created a ticket for this. In the meantime follow the PHP/WSAS install instructions to enable TCP/IP and it will work. -Ben Dewey -----Original Message----- From: Ben Dewey [mailto:[email protected]] Sent: Thursday, July 09, 2009 6:53 PM To: '[email protected]' Cc: 'Satish Nikam (Persistent Systems Ltd.)' Subject: RE: Setup Issues with new config? Drew, I had to change the config service app.config file. But, I'll going to double check the configuration in regards to the DBConfig table results. It may be a bit of a catch-22, because if a use has SQLExpress installed without TCP/IP setup then they may get an error. Although if a user is interested in the interoperability aspect then they would have followed the PHP/WSAS instructions to enable TCP/IP on port 1433, essentially enabling SQLExpress on namedpipes localhost\SQLExpress and tcpip on localhost. I'll test the config by disabling TCP/IP and see what happens. This would account for users running the .NET Stack solo, and may be the issue you're experiencing. Do you have TCP/IP enabled on your SQLExpress instance? -Ben Dewey -----Original Message----- From: Drew Baird (Volt) [mailto:[email protected]] Sent: Thursday, July 09, 2009 6:50 PM To: Drew Baird (Volt); [email protected] Cc: Satish Nikam (Persistent Systems Ltd.) Subject: RE: Setup Issues with new config? Just re-read the commit email Hi Avantika. Please send me and Satish (v-sanika) the new install document. Thanks! Drew -----Original Message----- From: Drew Baird (Volt) Sent: Thursday, July 09, 2009 3:47 PM To: '[email protected]' Subject: Setup Issues with new config? Do we need a ticket to update the setup documents? Satish and I are bringing up a new system from scratch with SQLEXPRESS and we cannot get past the login. Do we need to edit the dbconfig table when we use SQLEXPRESS? Thanks! Drew
