Comments
7 comments
-
Good Afternoon @gbargsley thank you for your post!
I have noted 2 things from this error, the first is that you're running an older version of Data Masker (major version 5.6 with Redgate licensing) and the second that you're using the older command line executable.
For automation purposes, in v6+ a new command line feature was added that would allow you to circumvent this error and run normally.
If you update to, at the very least, v6.0 but preferably the newest version and then utilise the PARFILE based cmdline to call your masking set, you should find that this solves your problems - the documentation for this can be found here: https://documentation.red-gate.com/dms6/data-masker-help/version-6-tech-tips/running-data-masker-from-the-command-line and you'll note the usage of this is: 'DMSCmdLine.exe PARFILE=C:\MaskingSets\SamplePARFILE.txt'
Please let me know how you get on and if you have any further questions.
Thank you very much. -
I have 6 installed, but I do not have the time to make the changes needed to work with my existing 5.x data masks.
-
Thanks @gbargsley - Is the file format a .dmsmaskset?
If so, Then you should be able to open this in v6 without any issues.
If not and it is the older format, then there is a handy Masking Set Converter in the Tools tab of Data Masker v6 which should help you convert the file to be compatible.
This would then allow you to utilise the cmdline and PARFILE capabilities to get around the above error.
Thank you very much. -
Thanks for the input. I will revisit upgrading and getting my DMSets migrated.
-
Thank you @gbargsley - let me know how you get on and if you have any problems.
Just to be on the safe side I would recommend trying to convert a copy of the set separately, just to be sure.
Happy to help where I can! -
Ok, so I converted my dmset to a v6 file. I ran it through DataMasker GUI manually to make sure all worked with no errors. That is fine. I just created a PARFILE and am trying to figure out how to execute via PowerShell but the docs appear to only reference command line as DOS.
I used to use: Start-Process "C:\Program Files\Red Gate\Data Masker for SQL Server\DataMasker.exe" "D:\DBA\DataMasker\Masking Sets\Elastic_DataMasking_08152018.DMSSet -R -X" -NoNewWindow -Wait
But: Start-Process "C:\Program Files\Red Gate\Data Masker for SQL Server 6\DataMaskerCmdLine.exe" "PARFILE=D:\DBA\DataMasker\Masking Sets\v6\PARFILE_Elastic_DataMasking_01312019.txt -R -X" -
Thanks for coming back on this @gbargsley - I believe when calling the command line from PowerShell you can use the ‘&’ call operator (docs here: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_operators?view=powershell-6)
This should then run the process.
Let me know how you get on - thank you very much.
Add comment
Please sign in to leave a comment.
Error: