Home Dashboard Directory Help
Search

SQL Server 2012 RTM PowerShell provider fails loading Microsoft.SqlServer.Management.Dac by Bob Beauchemin


Status: 

Active


4
0
Sign in
to vote
Type: Bug
ID: 731782
Opened: 3/17/2012 3:33:15 PM
Access Restriction: Public
0
Workaround(s)
view
3
User(s) can reproduce this bug

Description

When using the SQL Server PowerShell provider, attempts to navigate into the DAC folder fail when attempting to navigate to the default instance with the following error message:

WARNING: 'DEFAULT' not available: Could not load file or assembly 'Microsoft.SqlServer.Management.Dac,
Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find
the file specified.

This is in the RTM version of the product.
Details
Sign in to post a comment.
Posted by Microsoft on 4/19/2013 at 6:38 PM
Hey Bob,

The team has taken a look at this issue and in light of our other in-flight work and priority backlog, we are not pursuing a fix at this time. You should continue to use the SSMS context menu DAC-verbs as well as the DacServices API to leverage DACFx functionality. We still have this item tracking this issue should it come up for future consideration.

Thanks for reporting the issue,
Adam Mahood
Program Manager
SQL Server Database Systems
Posted by Bob Beauchemin on 4/1/2013 at 9:21 PM
The bug is that there is functionality in the SQL Server PowerShell provider that use to work in SQL Server 2008 R2 that doesn't work now and errors out. This shouldn't happen.

The DAC folder was originally there because of DAC's relationship with the SQL Server Utility feature. DAC and Utility provider "pseudo-directories" were added at the same time, SQL Server 2008 R2. The SQL Server Utility feature has not been removed from the product, nor has DAC's integration with it been changed. The DAC metadata is still in the same system tables and there is more DAC integration in SSMS than there used to be, regardless of folder layout.

If you want to make the SQL Server PowerShell provider equivalent to SSMS folders, then remove the DAC folder from the PowerShell provider entirely. And possibly move the DAC functionality under the SMO Database object to reflect what SSMS now looks like. Or leave it out of the provider entirely, since it is more of a standalone component, a la the SMO scripter.

Cheers, Bob
Posted by Microsoft on 4/1/2013 at 5:51 PM
Hey Bob,


If you are targeting SQL Server 2012, to what are you trying to navigate? There is no longer a DAC folder visible in the SSMS object tree, only the DACFx well-known install location in the filesystem.

Any clarification you might have would be awesome!

Thanks,
Adam Mahood
Program Manager
SQL Server DAtabase Systems
Posted by Bob Beauchemin on 4/1/2013 at 3:19 PM
No, I'm using a SQL Server 2012 instance, nothing earlier installed. To repro:

>Import-Module sqlps // this also cause cd to SQLServer: psdrive
>cd dac //works
>cd my2012 //works
>dir // produces error about Microsoft.SqlServer.Management.Dac v11 which doesn't exist because of name change

Cheers, Bob
Posted by Microsoft on 4/1/2013 at 2:40 PM
Bob,

Are you trying to use the SQL Server 2012 PowerShell Provider to navigate to the DAC folder of an instance of an older version of SQL Server (i.e. 2008R2 where a DAC folder is present)?

Thanks,
Adam Mahood
SQL Server Database Systems
Posted by Erik Bitemo on 3/23/2012 at 10:42 PM
Same symptom for named instance.
Sign in to post a workaround.