dsccommunity / dsccommunity/SqlServerDsc
SqlServerDscHelper: Connect-SQL: Fails to connect to a named instance if browser service is not started and instance is listening on non-standard port
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 385
- Forks
- 224
- PR merge metrics
- No merged PRs in 30d
Description
Details of the scenario you try and problem that is occurring:
I have a named instance with named pipes disabled and the port forced to 1433. In this scenario, Connect-SQL does not know how to connect to an instance on a specific port.
The DSC configuration that is using the resource (as detailed as possible):
Any configuration will be affected after the port is set.
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Server 2012 R2, SQL Server 2014, PowerShell v5.0
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
4.0.0.0 & dev
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Connect-SQL entry point and reproducing the named-instance scenario with SQL Server Browser stopped, named pipes disabled, and port 1433 forced. Compare the connection behavior with the browser service available; done means Connect-SQL can connect to the named instance without relying on the browser service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100