Andreas Jordan
Andreas Jordan
I am very sorry, but I don't remember what part of the code needs another change. So we have to start from the beginning. Please run your code with the...
OK, I can reproduce the issue now and want to document my findings: I only use `Copy-DbaCredential` in a brand new powershell session. While the command is running, the DAC...
If we use Connect-DbaInstance with -DedicatedAdminConnection we prevent the Cache from beeing filled. But we also return the server SMO which is used later in the command again with Connect-DbaInstance....
I don't see this as a bug and would like to close the issue.
`$Serverslist=DXXXX1W9262,DXXXX1W9261` is incorrect PowerShell syntax. If you use `$Serverslist='DXXXX1W9262', 'DXXXX1W9261'`, the command should work fine, because `$Serverlist` is an array containing two strings. If you use `$Serverslist='DXXXX1W9262,DXXXX1W9261'`, then this is...
Sorry, still not correct. Please have a look at the other parameter tests.
#9352 has all the needed changes, so we should close this one.
As it is a local instance - do you run the command from an elevated PowerShell session? This should be needed to get to the registry.
`Import-DbaCsv` has the same problems - because it uses `Connect-DbaInstance` with ` -StatementTimeout 0`. That forces a `.ConnectionContext.Copy()` and that does not work with a token. Will try to find...
No, it's `$connContext.GetDatabaseConnection($Database)` that is the problem. Will have to test if this is needed...