Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Issue with DLP API incidentDetail request

Created: 15 Jan 2013 • Updated: 15 Jan 2013 | 3 comments
This issue has been solved. See solution.

I am using the following C# code to implement the Data Loss Prevention API and finding that on an incidentDetail request i get the below exception:
code:
string client_username = "[username]";
string client_password = "[password]";

string url = "https://[server_name]/ProtectManager/services/v2011/incidents?wsdl";

ReportingApi.ReportingServiceClient client = new ReportingApi.ReportingServiceClient(url, client_username, client_password);

try
{
client.connect();
IncidentListRequest request = new IncidentListRequest();
request.savedReportId = 84;

//request.incidentCreationDateLaterThan = DateTime.Now.AddYears(-1);
List ids = new List();
ids.AddRange(client.getPortClient().incidentList(request));

if (ids != null)
{
IncidentDetailRequest incidentDetails = new IncidentDetailRequest();
incidentDetails.incidentId = ids.ToArray();
incidentDetails.includeHistory = true;
incidentDetails.includeViolations = true;
incidentDetailResponse response = new incidentDetailResponse(client.getPortClient().incidentDetail(incidentDetails));
}
}
catch (Exception ex)
{
Console.WriteLine(ex.ToString());
}
finally
{
client.disconnect();
}

exception: "System.ServiceModel.FaultException`1[Symantec_DLP.IncidentService.BasicFault]: com.vontu.v2011.enforce.webservice.incident.ServiceErrorFault (Fault Detail is equal to Symantec_DLP.IncidentService.BasicFault)."

Pulled from Soap log:
-- 15/Jan/2013:07:20:33:868 -0800 [10.12.220.59] [inbound] ["incidentList"]
<?xml version='1.0' encoding='UTF-8'?>

84
0001-01-01T00:00:00

-- 15/Jan/2013:07:20:34:225 -0800 [10.12.220.59] [outbound] ["incidentList"]
<?xml version='1.0' encoding='UTF-8'?>

345

-- 15/Jan/2013:07:20:34:301 -0800 [10.12.220.59] [inbound] ["incidentDetail"]
<?xml version='1.0' encoding='UTF-8'?>

3
4
5

-- 15/Jan/2013:07:20:34:418 -0800 [10.12.220.59] [outbound] ["incidentDetail"]
<?xml version='1.0' encoding='UTF-8'?>

S:Servercom.vontu.v2011.enforce.webservice.incident.ServiceErrorFaultUnable to service Incident Detail request

Simple question what am I doing wrong?

Comments 3 CommentsJump to latest comment

Justin Schuhmann's picture

below is the xml that was auto-formatted

-- 15/Jan/2013:07:20:33:868 -0800 [10.12.220.59] [inbound] ["incidentList"]
<?xml version='1.0' encoding='UTF-8'?>

84
0001-01-01T00:00:00

-- 15/Jan/2013:07:20:34:225 -0800 [10.12.220.59] [outbound] ["incidentList"]
<?xml version='1.0' encoding='UTF-8'?>

345

-- 15/Jan/2013:07:20:34:301 -0800 [10.12.220.59] [inbound] ["incidentDetail"]
<?xml version='1.0' encoding='UTF-8'?>

3
4
5

-- 15/Jan/2013:07:20:34:418 -0800 [10.12.220.59] [outbound] ["incidentDetail"]
<?xml version='1.0' encoding='UTF-8'?>

S:Servercom.vontu.v2011.enforce.webservice.incident.ServiceErrorFaultUnable to service Incident Detail request

Justin Schuhmann's picture

To resolve this issue I had to go into the generated code for the service:

then editted IncidentDetailRequest and made:

includeViolations

includeHistory

 

both not be default values anymore...

 

Issue resolved, Symantec should update their API to correctly generate.

SOLUTION
Yaron Halperin's picture

Thank you Justin for reporting the issue. It is a known issue (ID  2967946) and we are planning to fix it in the upcoming 11.6.2 release.