Error "Plan or Snap Name should not be empty." by using Sagent Webservice RunPlan

Product Feature: Sagent WebService
Operating System: Windows 2008 64bit
 

Issue

When "save as snap" is set to TRUE and a valid Snap name is provided, running a plan through Sagent Webservice displays following error:

Plan or Snap Name should not be empty.

Cause

Problem reported on Sagent Version 6.8, Build 0355.0, Windows-64bit. Problems with the interface Sagent Web Service for the method runPlan. The attempt to run a plan and save as snap not works.

Following soap request provided:
<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<RunPlan xmlns="http://www.sagent-pbbi.com/sagent-schema">
<request xmlns="">
<token>{CBC5ECE5-3DD8-4817-A4AF-0DFB4090BA8E}</token>
<planName>test_akm_automation</planName>
<notificationEmailAddress>email.address@example.com</notificationEmailAddress>
<smtpServer>smpt.server</smtpServer>
<saveResultsAsSnap>true</saveResultsAsSnap>
<snapName>Carbapenemase_month_2013-07-26</snapName>
</request></RunPlan>
</soap:Body>
</soap:Envelope>

As answer was sent:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://www.sagent-pbbi.com/sagent-schema">
<SOAP-ENV:Body>
<ns:RunPlanResponseContainer>
<responseObject>
<err>SAWS-NOERR</err>
<errorString>Plan or Snap Name should not be empty</errorString> </responseObject> </ns:RunPlanResponseContainer> </SOAP-ENV:Body> </SOAP-ENV:Envelope>

The snap was not saved. The planName exists in the Repository and it shown with the Webservice method ListAvailablePlans in the Response. In the Design Studio is it possible to run the plan and save it as snap. The error message has to do with the parameter saveResultsAsSnap.

With the same request with saveResultsAsSnap = false the following respond received:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns="http://www.sagent-pbbi.com/sagent-schema">
<SOAP-ENV:Body>
<ns:RunPlanResponseContainer>
<responseObject>
<requestID>{961C296A-5A3A-4920-A303-08F56A987C62}</requestID>
<err>SAWS-NOERR</err></responseObject>
</ns:RunPlanResponseContainer>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Receiving also the same respond by using saveResultsAsSnap = false and as planName a nonexistent plan.

Resolution

UPDATED: April 4, 2017
This issue has been resolved in Sagent Patch 6.8.5.