My organization recently upgraded the Labmanager from v3.0 to v4.0. The methods what we exposed through C# .net assembly started failing after upgrade of labmanager while it worked perfectly in previous versions (both v2.5 and v3.0). Please advice immediately since this is very critical.
The exceptions are thrown in Labmanager SOAP methods like ListConfigurations(), GetSingleConfigurationByName() and probably others too.
(Exception: Could not find Bucket in database given the parameters--->)
Sample code which worked in v3.0 while it fails in v4.0 :
binding = new LabManagerSoap.LabManagerSOAPinterface();
binding.Url = sLabManagerSOAPUrl;
binding.Timeout = 10 * 300 * 1000;
binding.AuthenticationHeaderValue = new LabManagerSoap.AuthenticationHeader();
binding.AuthenticationHeaderValue.username = sUsername;
binding.AuthenticationHeaderValue.password = sPassword;
ServicePointManager.CertificatePolicy = new CertificateAccepter();
//** Get Configurations in Workspace and see if the connection could be established
int configurationType = 1; //** 1=Workspace
LabManagerSoap.Configuration[] WSconfigurations = binding.ListConfigurations(configurationType); <---- exception is thrown here.
Thanks.
The exceptions are thrown in Labmanager SOAP methods like ListConfigurations(), GetSingleConfigurationByName() and probably others too.
(Exception: Could not find Bucket in database given the parameters--->)
Sample code which worked in v3.0 while it fails in v4.0 :
binding = new LabManagerSoap.LabManagerSOAPinterface();
binding.Url = sLabManagerSOAPUrl;
binding.Timeout = 10 * 300 * 1000;
binding.AuthenticationHeaderValue = new LabManagerSoap.AuthenticationHeader();
binding.AuthenticationHeaderValue.username = sUsername;
binding.AuthenticationHeaderValue.password = sPassword;
ServicePointManager.CertificatePolicy = new CertificateAccepter();
//** Get Configurations in Workspace and see if the connection could be established
int configurationType = 1; //** 1=Workspace
LabManagerSoap.Configuration[] WSconfigurations = binding.ListConfigurations(configurationType); <---- exception is thrown here.
Thanks.