Hello,
We user SCVMM 2012 R2 UR 13 in combination with Netapp 3.0 shares. To make the shares available we have a seperate server running with the Netapp SMI-s agent.
For the last few days the SMI-s storage provider is showing status 'not responding' in the console and it fails to refresh or rescan with the following error:
2901: The operation did not complete successfully because of a parameter or call sequence that is not valid. Ensure that the parameters are valid, and then try the operation again.
On the smi-s agent server everything seems to be working alright. I can query the storage system without problems.
I have restarted both the SCVMM server and the SMI-S server, but this did not help.
I also tried to create a trace file on the SCVMM server for the storage provider which shows this error:
[0]04E0.13C0::2019-08-06 14:01:55.732 [Microsoft-VirtualMachineManager-Debug]14,4,ImgLibOM.cs,326,Update DB Row of StorageFileServer object netapp-svm with ID
d3e0bfd9-e1ac-49b3-a30b-91ab167430cd,{b8aa5894-0664-4797-a624-3ada50553e68}
[0]04E0.13C0::2019-08-06 14:01:55.733 [Microsoft-VirtualMachineManager-Debug]4,4,ImgLibOM.cs,308,Failing LibObjectBase.UpdateDB
[s#275616 6ms] [ex#14f9] New exception = [[(CarmineException#a891) { Microsoft.VirtualManager.Utils.CarmineException:
The operation did not complete successfully because of a parameter or call sequence that is not valid.
Ensure that the parameters are valid, and then try the operation again. at Microsoft.VirtualManager.DB.SqlRetryCommand.AddParameter
(String name, SqlDbType type, Boolean nullable, Int32 size, String typeName, Object value) at Microsoft.VirtualManager.DB.SqlRetryCommand.AddParameter
(String name, SqlDbType type, Boolean nullable, Int32 size, Object value) at Microsoft.VirtualManager.DB.ImageLibrary.StrgFileServerDBAccess.
SetStorageFileServerParameters(SqlRetryCommand cmd, StorageFileServerData data) at
Microsoft.VirtualManager.DB.ImageLibrary.StrgFileServerDBAccess.ExecuteSetStorageFileServerSP(String spName, StorageFileServerData stData, ImgLibCat
Has anyone ever seen this problem and/or knows how to fix this?
thanks!