Warning message that keeps repeating in error log

This topic has 4 replies, 5 voices, and was last updated 14 years, 3 months ago by Ed Mastascusa.

Creator

Topic
December 15, 2009 at 7:03 pm #51426

Robert Denny
Participant

I am working on cleaning up our error logs.

In our pacs process we are getting many warnings that read

12/15/2009 00:09:04 [msg :RecP:WARN/0: Pacs_xlate] [0.0.10803661] The # 2 segment encountered ‘PV1’ is not defined for message type ‘ORU_R01’. Segment ignored.

12/15/2009 00:11:02 [msg :RecP:WARN/0: Pacs_xlate] [0.0.10803826] The # 2 segment encountered ‘PV1’ is not defined for message type ‘ORU_R01’. Segment ignored.

12/15/2009 00:12:54 [msg :RecP:WARN/0: Pacs_xlate] [0.0.10803966] The # 2 segment encountered ‘PV1’ is not defined for message type ‘ORU_R01’. Segment ignored.

I am not able to find any messages with the ORU_R01 text in any messages.

Any suggestions on what might be causing these warnings?
Creator

Topic

Viewing 3 reply threads

Author

Replies
- December 15, 2009 at 7:17 pm #70239
  
  Jim Kosloskey
  Participant
  
  Did you find any messages with MSH-9 of ORU anything?
  
  email: jim.kosloskey@jim-kosloskey.com
- December 15, 2009 at 8:07 pm #70240
  
  Sam Craig
  Participant
  
  Search the SMAT file for the message ID listed in the error message and see what is in MSH-9. Is it setup as a Wildcard for ORU in Thread config?
- December 16, 2009 at 1:13 pm #70241
  
  Gary Atkinson
  Participant
  
  Also, check your variant and make sure the PV1 is in the schema and in the order of the inbound message.
- December 28, 2009 at 1:51 pm #70242
  
  Ed Mastascusa
  Participant
  
  Hi Robert,
  
  Since the warning is saying that the #2 segment is the PV1 it looks like the root cause of the warnings is that you are receiving some messages where an MSH is followed by a PV1 instead of a PID segment.
Author

Replies

Viewing 3 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.