Exporting login produces empty file - Githubissues

dataplat / dbatools

🚀 SQL Server automation and instance migrations have never been safer, faster or freer

https://dbatools.io

MIT License

2.43k stars 794 forks source link

Exporting login produces empty file #4604

Closed alevyinroc closed 5 years ago

alevyinroc commented 5 years ago

Before submitting a bug report:

[X] Ensure you are able to reproduce it on the latest released version (we release often)
[X] Verified this bug is not already reported in an issue
[X] Verified errors are not related to permissions
[ ] Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)

Steps to Reproduce

Produced on dbatools 0.9.519

get-dbalogin -ServerInstance $prod | where-object {-not $_.isDisabled} | select-object -first 1 | ForEach-Object {Export-DbaLogin -login $_ -path (join-path -path e:\tmp\2016upgrade\Logins -childpath "$($_.name.replace('\','$')).sql") -SqlInstance $prod -verbose}

Expected Behavior

File output listing login details, database permissions, roles, etc. for the first enabled user on the instance to a file named using the login name

Actual Behavior

Resulting file contains only GO

Environmental data

PowerShell: 5.1.17134.407
- SQL Server: Microsoft SQL Server 2008 R2 (SP3) - 10.50.6220.0 (X64) & Microsoft SQL Server 2016 (SP2-CU2-GDR) (KB4293807) - 13.0.5161.0 (X64)

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. If you would like this issue to remain open:

Verify that you can still reproduce the issue in the latest version of dbatools
Comment that the issue is still reproducible and include:
- What version of dbatools you reproduced the issue on
- What OS and version you reproduced the issue on
- What steps you followed to reproduce the issue