Skip to main content

Troubleshooting

Where to Look​

The output location is based on the -OutputDir parameter, which defaults to an 'Export-Permission' folder inside the $env:AppData folder.

Inside the output location, reports will be organized into folders by year, month, and individual report instance. Each report instance is identified by timestamp and guid.

"$OutputDir\yyyy\MM\$timestampAndGuid"

Inside the folder for the current report, the log file generated by the script can be found (Export-Permission.log)

Generating the log file is one of the last things the script does. If the script is interrupted, the log file may not be written to disk. In this case the PowerShell transcript can also be found in this folder (PowerShellTranscript.log).

If neither of these files was generated, check the console for output if possible. For more information, set $DebugPreference = 'Continue' and then run the script again.

Known Error 1​

Export-Permission : The term 'Export-Permission' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.

Cause​

Earlier versions of the PowerShellGet module did not offer to add the directories targeted by the Install-Script cmdlet to $env:PATH persistently. As of at least v2.2.4 they do; a prompt is presented the next time you call Install-Script to perform an actual installation.

Solution​

Use the latest version of the PowerShellGet module. In an elevated PowerShell window (running as an administrator):

Update-Module PowerShellGet

On old versions this may result in an error stating that because PowerShellGet module was not installed by Install-Module it cannot be updated by Update-Module. In this case we can force the installation anyway:

Install-Module PowerShellGet -AllowClobber -Force
Exit # Exit PowerShell to ensure the old module version is not loaded

Then install the script in a new elevated PowerShell window:

Install-Script Export-Permission

Then, answer Yes to the prompt to add the PowerShell Scripts folder to the PATH environment variable:

PATH Environment Variable Change
Your system has not been configured with a default script installation path yet, which means you can only run a script
by specifying the full path to the script file. This action places the script into the folder 'C:\Program
Files\WindowsPowerShell\Scripts', and adds that folder to your PATH environment variable. Do you want to add the script
 installation path 'C:\Program Files\WindowsPowerShell\Scripts' to the PATH environment variable?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"):

Then answer Yes to the prompt to install the script from PSGallery:

Untrusted repository
You are installing the scripts from an untrusted repository. If you trust this repository, change its
InstallationPolicy value by running the Set-PSRepository cmdlet. Are you sure you want to install the scripts from
'PSGallery'?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"):

Then any new powershell windows launched in the future will be able to run Export-Permission without specifying the full file path.