SqlScript: When this resource is used directly after an SQL Server install it fails #659
Assignees
Labels
bug
The issue is a bug.
Comments
johlju
added
bug
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Jun 24, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Jul 8, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Jul 12, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Jul 13, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Aug 13, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Aug 17, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Aug 19, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Aug 19, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Sep 8, 2017
Now it correctly loads the correct assemblies when SqlServer module is present (issue dsccommunity#649). Now SQLPS module will be correctly loaded (discovered) after installation of SQL Server (issue dsccommunity#659). Previously resources depending on SQLPS module could fail because SQLPS was not found after installation because the PSModulePath environment variable in the (LCM) PowerShell session did not contain the new module path.
johlju
changed the title
|
I do believe this issue is resolved since a while back. Closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Details of the scenario you tried and the problem that is occurring:
When this resource is used directly after an SQL Server install it fails.
This is because the PowerShell session has not yet updated the environment variable PSModulePath to include the new path to SQLPS module. Unless target node was restarted after SQL Server installation.
The DSC configuration that is using the resource (as detailed as possible):
Any configuration using xSQLServerScript resource, and target node is not restarted after SQL Server installation.
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
All
What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
SQLPS
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev
The text was updated successfully, but these errors were encountered: