incubator-stonehenge-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Dewey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (STONEHENGE-79) DotNet Config Service doesn't support SQLExpress
Date Mon, 13 Jul 2009 17:49:14 GMT

    [ https://issues.apache.org/jira/browse/STONEHENGE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730422#action_12730422
] 

Ben Dewey commented on STONEHENGE-79:
-------------------------------------

Close, except the InstanceName would be a string not 1433 (default: SQLExpress).

The only issue to this is that you can't use the instance name with an IP address.  you'd
have to use 'localhost'

Do php, etc work with localhost instead of 127.0.0.1?

> DotNet Config Service doesn't support SQLExpress
> ------------------------------------------------
>
>                 Key: STONEHENGE-79
>                 URL: https://issues.apache.org/jira/browse/STONEHENGE-79
>             Project: Stonehenge
>          Issue Type: Bug
>            Reporter: Ben Dewey
>             Fix For: M2
>
>
> The new STONEHENGE-67 Config patch doesn't support SQLExpress as a named instance.  The
config service would need to be modified to support a named instance of the database.
> The current work-around is to enable TCP/IP on the SQLExpress instance using port 1433.
 See the PHP/WSAS Installation guide for more information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message