2012-07-11 12:05 AM
we've recently updated the Powershell API to v2.0 and got the following error on our 64bit systems running the 32-bit Powershell (SYSWOW64):
Import-Module : The following error occurred while loading the extended type da
TAP\DataONTAP.Type.ps1xml : File skipped because of the following validation ex
ception: File C:\Windows\system32\WindowsPowerShell\v1.0\Modules\DataONTAP\Data
ONTAP.Type.ps1xml cannot be loaded. The file C:\Windows\system32\WindowsPowerSh
ell\v1.0\Modules\DataONTAP\DataONTAP.Type.ps1xml is not digitally signed. The s
cript will not execute on the system. Please see "get-help about_signing" for m
TAP\DataONTAP.C.Type.ps1xml : File skipped because of the following validation
exception: File C:\Windows\system32\WindowsPowerShell\v1.0\Modules\DataONTAP\Da
taONTAP.C.Type.ps1xml cannot be loaded. The file C:\Windows\system32\WindowsPow
erShell\v1.0\Modules\DataONTAP\DataONTAP.C.Type.ps1xml is not digitally signed.
The script will not execute on the system. Please see "get-help about_signing"
for more details...
We could, till now, just solve the Problem by setting the ExecutionPolicy to "Bypass" instead of "RemoteSigned".
However the 64-Bit Powershell (system32) imports the Module without any Problems.
Systems are W2k8 R2 Enterprise Edition 64Bit. (We could reproduce the error on different Systems)
Could you Please correct that behavior in a future- (or bugfix-) Release?
2012-07-11 06:04 AM
The Toolkit should work fine in the 32 bit (aka SysWow64) PowerShell runtime. I suspect that your toolkit may not be installed correctly, in particular make sure that the module files aren't blocked. See this post for more info: https://communities.netapp.com/message/74639#74639
You probably want to unblock the zip file before extracting the contents to the 32bit module dir: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\Modules
Note that recent versions of the installer script (Install.ps1, available in the download section) should do the unblocking step automatically.
Edit: Also, please double check your execution policy in 32bit powershell with Get-ExecutionPolicy.
2012-07-16 01:42 AM
sorry for my late answer. (Had some free days)
You were absolutely correct.
After downloading the package again and extracting it to the 32bit mod folder everything works smooth in the "RemoteSigned" Policy.
But i've also tried the install.ps1 script. Which seems to work just in the mode it is started (32bit ISE for 32bit folder and 64bit ISE for 64bit folder).
Would be cool to have one handling both if running under 64bit.
-> Also it extracted the files to the 64bit folder but not to the 32bit one. It just deleted the old version there but no new were shown up.