When you configure a PowerShell-based inventory connection, the connection form may be incomplete, or the application may throw a PowerShell connection exception when you try to create a new connection.
Missing connection form
Error when trying to create a new PowerShell connection
Error stack trace
System.Exception: PowerShell connection exception, possible reasons include malformed config file.
at ManageSoft.Compliance.Beacon.Controls.DialogSavePowerShellConnection.connectionTypeComboBox_SelectedIndexChanged(Object sender, EventArgs e)
at DevExpress.XtraEditors.Repository.RepositoryItemComboBox.RaiseSelectedIndexChanged(EventArgs e)
at DevExpress.XtraEditors.ComboBoxEdit.UpdatePopupEditValueIndex(Int32 prevIndex)
at DevExpress.XtraEditors.ComboBoxEdit.set_EditValue(Object value)
at DevExpress.XtraEditors.PopupBaseEdit.SetPopupEditValueOnClose(Object value, Boolean isAccept)
at DevExpress.XtraEditors.PopupBaseEdit.AcceptPopupValue(Object val)
This issue typically occurs when the regional settings on the Beacon server change, which can affect how numeric values are interpreted. The steps below help you correct the regional settings so the PowerShell connection can be created successfully.
- Open the Region settings on the Beacon server
- Open Control Panel.
- Search for Region, and then select it.
- Check the regional format
- In the Format dropdown, make sure the format is set to an English locale, such as English (United States) or English (United Kingdom).
- Do not leave the format set to Match Windows display language (recommended).
- Verify the decimal symbol
- Select Additional settings.
-
- In the Numbers tab, check the Decimal symbol field.
- Make sure the value is a period (.).
- Do not use a comma (,) or a single quote (').
- Apply changes and restart the Beacon application
- Select OK to save any changes.
- Restart the Beacon application to ensure the new settings take effect.
After confirming that the decimal symbol is set to a period and the regional format is set to an English locale, you should be able to create and update PowerShell connections without errors. The PowerShell connection form should display all required fields, and the connection should save successfully.
Related Articles
Web proxy values configured for PowerShell connection beacon UI are not used when clicking the "Test Connection" button 12Number of Views Powershell Connection Creation Fails with 'Powershell Connection Exception, possible reasons include malformed config file' 8Number of Views FlexNet agent (ndtrack) may trigger a security software warning due to PowerShell script execution containing unusual char… 78Number of Views Handshake failed. Cannot connect to server. No endpoint can establish a connection to the server. 284Number of Views Error in Amazon Web Services (AWS) PowerShell Connection When Using a Proxy 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
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. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago