incubator-stonehenge-dev mailing list archives

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

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

Avantika Agrawal commented on STONEHENGE-79:
--------------------------------------------

I think that sounds like a reasonable workaround. I am not too familiar with SQLExpress so
can you give an example of this?
so HostName would be 127.0.0.1 and if the user is using SQLExpress (i.e. InstanceName is not
null) then we append \1433 to it??

> 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