Skip to content
This repository was archived by the owner on Feb 24, 2019. It is now read-only.
This repository was archived by the owner on Feb 24, 2019. It is now read-only.

Collection jobs fail silently in SQL Server 2016 without doing anything constructive if you have spaces in the path #84

@NeoPangea

Description

@NeoPangea

Do you want to request a feature or report a bug?
bug

What is the current behavior?
If you have spaces in your path, SQL Server 2016 agent fails to run the powershell but does not fail the job.

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net
Install on SQL Server 2016 ensuring the powershell scripts are written to a folder with spaces in the path and run the jobs. Check the job history and find a powershell error

What is the expected behavior?
The Jobs should run as expected

Which versions of SQL Server and which OS are affected by this issue? Did this work in previous versions of our procedures?
SQL Server 2016 Windows server 2016

Possible fix
I have fixed this in my installation by surrounding the single quoted string with double quotes. So '' becomes "''" Note that the single quotes are still required within the double quotes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions