Summary
In the log file CommandAction.log, the powershell.exe command is returning a value of "1". While PowerShell is launching, the script is never invokedSymptoms
In the log file CommandAction.log, the powershell.exe command is returning a value of "1". While PowerShell is launching, the script is never invoked.Cause
This typically occurs due to the PowerShell Execution Policy which is set. By default, the Execution Policy is set to Restricted, which means that only signed PowerShell scripts are allowed to run.Resolution
To change the Execution Policy for Powershell, the following command line can be run from the PowerShell console window:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
Note: As AppPortal currently runs under a 32-bit application pool, it is necessary to set the Execution Policy for the 32-bit PowerShell. To launch the 32-bit PowerShell, use the following executable:
C:\windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
Additional Information
The following article describes the various Execution Policy options
Was this helpful?
Related Articles
FlexNet agent (ndtrack) may trigger a security software warning due to PowerShell script execution containing unusual char… 76Number of Views PowerShell script to monitor the process and folders used by the cloud metering process 73Number of Views Launching Powershell Script from Supportdir using installscript Customaction 16Number of Views Configps1 PowerShell script fails when non default SQL Server port is used 19Number of Views PowerShell script to delete the Snow MongoDB service 5Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago