JSON Parsing Error while validating ticket during ServiceNow Ticketing Integration

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

JSON Parsing Error while validating ticket during ServiceNow Ticketing Integration

L1 Bithead

Hi Experts,

 

I am getting JSON Parsing Error while validating the ticket for ServiceNow Ticketing Integration, would appreciate if anyone can give some pointers on how to troubleshoot this.

 

024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] RestConnector::GetResponse()->END || || 

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] RestConnector::ConnectAndRetriveTicketInformation()->END || || 

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] ConnectionLogic::SubmitRequest()->Parsing response. || || 

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] ConnectionLogic::SubmitRequest()->END || || 

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] Response::SerializeResponse()->START || || 

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] Response::SerializeResponse()->Before replacing result with empty string <html lang="en" class=" ltr" dir="ltr"><head><title>ServiceNow</title><meta http-equiv="X-UA-Compatible" content="chrome=1"></meta><meta http-equiv="cache-control" content="public"></meta><link href="favicon.ico?v=5" rel="shortcut icon"></link><link type="text/css" rel="stylesheet" href="/styles/css_includes.cssx?v=01-03-2024_0751&amp;c=03/18/2021_01:01:48 PM_38353d181bd00a1005e3b99f034bcb61&amp;theme="></link><script type="text/javascript" data-description="globals population">

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] Response::SerializeResponse()->Parsing Response from web service || || 

2024-02-07 07:53:55,664 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] JSONResponse::ParseResponse()->START || || 

2024-02-07 07:53:55,680 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [ERROR] JSONResponse::ParseResponse()->Parsing Json response failed || || 

2024-02-07 07:53:55,689 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [ERROR] TicketValidator::ValidateTicket()->Exception: System.Exception: Parsing Json response failed ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

  at Newtonsoft.Json.JsonTextReader.ParseValue()

  at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)

  at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)

  at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)

  at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)

  at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)

  at CyberArk.TicketingSystemUtils.JSONResponse.ParseResponse(String response)

  --- End of inner exception stack trace ---

  at CyberArk.TicketingSystemUtils.JSONResponse.ParseResponse(String response)

  at CyberArk.ServiceNow.Response.SerializeResponse(String webServiceResponse, String ticketNotExistErrorMessage)

  at CyberArk.ServiceNow.TicketValidator.ValidateTicket(IValidationParametersEx parameters, ITicketOutput& ticketingOutput) || || 

2024-02-07 07:53:55,689 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] CommonFunctions::RemoveSpecialCharacters()->START || || 

2024-02-07 07:53:55,689 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] CommonFunctions::RemoveSpecialCharacters()->END || || 

2024-02-07 07:53:55,690 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] TicketValidator::ValidateTicket()->Ticket was rejected || || 

2024-02-07 07:53:55,690 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || EXXXXXXX [Ticketing system ServiceNow] [INFO] TicketValidator::ValidateTicket()->END || || 

2024-02-07 07:53:55,690 || DEBUG  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || a end | ReturnObjectType: System.Boolean || || akn

2024-02-07 07:53:55,706 || TRACE  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || PASWS001I Starting method GeneralExceptionAttribute::OnException || || 

2024-02-07 07:53:55,706 || ERROR  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || PASWS001E Error occurred: PASWS090E Input parameter for [TicketID] value is invalid. Parsing Json response failed || || 

2024-02-07 07:53:55,706 || DEBUG  || 33 || PLXXXXX || 0555A || 29a7a417-ac88-4c49-a2fb-246a720aaa85 || CyberArk.PasswordVault.WebServices.Infra.Exceptions.ValidationParameterException: PASWS090E Input parameter for [TicketID] value is invalid. Parsing Json response failed ---> ak4: Parsing Json response failed

  at am3.a(RetrievePasswordData A_0, PVPassword A_1, Boolean A_2)

  at Castle.Proxies.Invocations.atc_a_56.InvokeMethodOnTarget()

  at Castle.DynamicProxy.AbstractInvocation.Proceed()

  at bej.a(IInvocation A_0)

  at Castle.DynamicProxy.AbstractInvocation.Proceed()

  at Castle.Proxies.atcProxy.a(RetrievePasswordData A_0, PVPassword A_1, Boolean A_2)

  at CyberArk.PasswordVault.PASWebServices.Controllers.AccountsController.SetPasswordContentToResponse(String accountId, AccountContentPrerequsites accountContentPrerequisites, Boolean isSecret)

  --- End of inner exception stack trace ---

  at CyberArk.PasswordVault.PASWebServices.Utils.PasswordRetrieveErrorHandler.HandleContentTicketingException(Exception ex)

  at CyberArk.PasswordVault.PASWebServices.Utils.PasswordRetrieveErrorHandler.HandleContentException(Exception ex)

  at CyberArk.PasswordVault.PASWebServices.Controllers.AccountsController.SetPasswordContentToResponse(String accountId, AccountContentPrerequsites accountContentPrerequisites, Boolean isSecret)

  at CyberArk.PasswordVault.PASWebServices.Controllers.AccountsController.Content(String accountId, AccountContentPrerequsites accountContentPrerequisites)

  at CyberArk.PasswordVault.PASWebServices.Controllers.AccountsController.Retrieve(String accountId, AccountContentPrerequsites accountContentPrerequisites)

  at lambda_method(Closure , Object , Object[] )

  at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)

  at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)

5 REPLIES 5

L7 Applicator

Hi @sunny ajmera​ 

 

Is this issue happening only with a specific ticket type or all the ticket types ?

 

 

L1 Bithead

Its happening for both incident and change request types.

L1 Bithead

any other pointers to resolve this issue?

L7 Applicator

Hi @sunny ajmera​ 

 

Just to confirm are you able to open ServiceNow URL on the PVWA server ?

L1 Bithead

Hello @sunny ajmera​ ,

 

Not sure if this is resolved for you or not. I had a similar error and it turns out the SNOW URL that I was using included an extra "/login.do" in the URL. Removed that and it worked fine. So please check your SNOW URL.

  • 486 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!