Not recognizing cmdlets from newly imported module
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
-
- Posts: 107
- Last visit: Thu Apr 29, 2021 8:47 am
Not recognizing cmdlets from newly imported module
Imported the MSOL modules without error and they work just find in PSS. However they are is still being flagged as 'unknown'. How can I get PSS to recognize these new cmdlets?
Mike
- SAPIEN Support Forums
- Posts: 945
- Last visit: Thu Oct 22, 2015 1:10 pm
Not recognizing cmdlets from newly imported module
This is an automated post. A real person will respond soon.
Thank you for posting, StupidSexyFlanders.
Did you remember to include the following?
*** Make sure you do not post any licensing information ***
Thank you for posting, StupidSexyFlanders.
Did you remember to include the following?
- 1. Product, version and build (e.g. Product: PowerShell Studio 2014, Version & Build: 4.1.71. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
2. Specify if you are running a 32 or 64 bit version
3. Specify your operating system and if it is 32 or 64 bit.
4. Attach a screenshot if your issue can be seen on the screen
5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
*** Make sure you do not post any licensing information ***
Re: Not recognizing cmdlets from newly imported module
If you installed this module after installing PowerShell Studio, you will need to rebuild the cache.
The module must be in a discover-able location. For example:
C:\Users\<username>\Documents\WindowsPowerShell\Modules
PowerShell must be able to find it automatically.
David
The module must be in a discover-able location. For example:
C:\Users\<username>\Documents\WindowsPowerShell\Modules
PowerShell must be able to find it automatically.
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: Not recognizing cmdlets from newly imported module
Also make sure you have the correct platform selected. Some modules are 64 bit only or support a specific version of PowerShell.
David
David
David
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
-
- Posts: 107
- Last visit: Thu Apr 29, 2021 8:47 am
Re: Not recognizing cmdlets from newly imported module
Thanks David. Are those steps required just to get the UI to recognize the new cmdlet names? I ask because the new cmdlet functionality is 100% working through PSS. I just installed version 4.2.81 yesterday but they are still not being recognized.
I am rebuilding the cache now, so that will take a while. Then I will tinker with the platform settings. The default is x64 and I am pretty sure these MS cmdlets are as well. I'll let you know how it goes.
Update: Well, in the time it took me to write this post the cache rebuild completed. Now everything is copacetic again.
I am rebuilding the cache now, so that will take a while. Then I will tinker with the platform settings. The default is x64 and I am pretty sure these MS cmdlets are as well. I'll let you know how it goes.
Update: Well, in the time it took me to write this post the cache rebuild completed. Now everything is copacetic again.
Mike