our PHINMS 2.9 receiver log no envelope error

38 views
Skip to first unread message

Christina Crawford

unread,
Feb 13, 2018, 10:41:24 AM2/13/18
to PHINMS User Community
We have our PHINMS 2.9 setup as a receiver for the first time. We are working with another lab as a new sender.
We have sent the sender our service action pair and our URL and to sent as http on first try. The sender can put our URL in their IE and see our info.
I did not send out new public cert to them yet to be used for encryption. I just updated it for another year. They did send us their CPA file but we have not imported it into our PHINMS yet.

I have the service action pair set to a receiver sql server database.

The user sent a text file. But they said it was a 500 error in their side. Our receiver log said there was no receiver envelope.


Here is the log. What have I missed.

RE: Philly Receiver Log
DM

Dittman, Mark
Tue 2/13/2018 10:14 AM
Inbox
To:
Liddick, Troy;
Cc:
Crawford, Christina;
16. Service Map for the Worker Queue Configuration

Each message has an envelope with addressing information tags referred to as a Service and Action pair. They are character strings logically mapped to a Worker Queue (asynchronous messaging). The service and action pair determines the location of the delivery. The Service Map and the Worker Queue are configured on the Receiver. Refer to Step 14. The Service Map also includes the type of Message Handler which is Servlet, Worker Queue, and Error Queue.

PHIN MS Release 3.0.00 – PHIN MS 3.0.00 Implementation GuideSee Page 54

From: Liddick, Troy
Sent: Tuesday, February 13, 2018 9:58 AM
To: Dittman, Mark <mdit...@pa.gov>
Cc: Crawford, Christina <ccra...@pa.gov>
Subject: Philly Receiver Log

Mike reporting a 500 error, here is the log,

--1518533536898
Content-ID: <ebxml-e...@hip.phila.gov>
Content-Type: text/xml


--1518533536898
Content-ID: <patest.txt.1...@hip.phila.gov>
Content-Type: Application/Octet-Stream
Content-Transfer-Encoding: base64
Content-Disposition: attachment; name="patest.txt.1518530379105"

dGVzdCBmaWxl
--1518533536898--
|
http-apr-5088-exec-18|02/13|09:54:25|created mime message successfully|
http-apr-5088-exec-18|02/13|09:54:25|PF2: Content-type=multipart/related; type="text/xml"; boundary="1518533536898"; start="ebxml-e...@hip.phila.gov"|
http-apr-5088-exec-18|02/13|09:54:25|Multi part found|
http-apr-5088-exec-18|02/13|09:54:25|Part:0, content-type=text/xml|
http-apr-5088-exec-18|02/13|09:54:25|done reading input stream, length=0|
http-apr-5088-exec-18|02/13|09:54:25|text/xml, converting bos to string|
http-apr-5088-exec-18|02/13|09:54:25|done converting string|
http-apr-5088-exec-18|02/13|09:54:25|Part:0, inps|
http-apr-5088-exec-18|02/13|09:54:25|Part:0, inps|
http-apr-5088-exec-18|02/13|09:54:25|set text part ok|
http-apr-5088-exec-18|02/13|09:54:25|Part:1, content-type=Application/Octet-Stream|
http-apr-5088-exec-18|02/13|09:54:25|done reading input stream, length=12|
http-apr-5088-exec-18|02/13|09:54:25|Part:1, inps app/oct|
http-apr-5088-exec-18|02/13|09:54:25|payload part has been set|
http-apr-5088-exec-18|02/13|09:54:25|HttpMultiPartParser: parseMimeMessage done|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet: created message processor|
http-apr-5088-exec-18|02/13|09:54:25|Error - no envelope found in message received|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet, envelope=null|
http-apr-5088-exec-18|02/13|09:54:25|RecieveFileServlet, payload=dGVzdCBmaWxl|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet, text=|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet, filename=patest.txt.1518530379105|


Christina

Lowe, Phillip (DOH)

unread,
Feb 13, 2018, 11:01:31 AM2/13/18
to phi...@googlegroups.com
You NEED to import their CPA.
In the handshake process, the shared secret is exchanged with encryption. That shared secret is part of the CPA file. If you don't respond to them with the shared secret they can't authenticate your end.


Phill Lowe – 360 236-4261
http-apr-5088-exec-18|Content-type=multipart/related; type="text/xml";
http-apr-5088-exec-18|boundary="1518533536898";
http-apr-5088-exec-18|start="ebxml-e...@hip.phila.gov"|
http-apr-5088-exec-18|02/13|09:54:25|Multi part found|
http-apr-5088-exec-18|02/13|09:54:25|Part:0, content-type=text/xml|
http-apr-5088-exec-18|02/13|09:54:25|done reading input stream,
http-apr-5088-exec-18|length=0| 02/13|09:54:25|text/xml, converting bos
http-apr-5088-exec-18|to string| 02/13|09:54:25|done converting string|
http-apr-5088-exec-18|02/13|09:54:25|Part:0, inps|
http-apr-5088-exec-18|02/13|09:54:25|Part:0, inps| 02/13|09:54:25|set
http-apr-5088-exec-18|text part ok| 02/13|09:54:25|Part:1,
http-apr-5088-exec-18|content-type=Application/Octet-Stream|
http-apr-5088-exec-18|02/13|09:54:25|done reading input stream,
http-apr-5088-exec-18|length=12| 02/13|09:54:25|Part:1, inps app/oct|
http-apr-5088-exec-18|02/13|09:54:25|payload part has been set|
http-apr-5088-exec-18|02/13|09:54:25|HttpMultiPartParser:
http-apr-5088-exec-18|parseMimeMessage done|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet: created message
http-apr-5088-exec-18|processor| 02/13|09:54:25|Error - no envelope
http-apr-5088-exec-18|found in message received|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet, envelope=null|
http-apr-5088-exec-18|02/13|09:54:25|RecieveFileServlet,
http-apr-5088-exec-18|payload=dGVzdCBmaWxl|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet, text=|
http-apr-5088-exec-18|02/13|09:54:25|ReceiveFileServlet,
http-apr-5088-exec-18|filename=patest.txt.1518530379105|


Christina

--

---
You received this message because you are subscribed to the Google Groups "PHINMS User Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phinms+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Francis de Wet

unread,
Feb 13, 2018, 11:27:53 AM2/13/18
to phi...@googlegroups.com
Also, "Error - no envelope" can sometimes indicate that the sender needs to stop PHINMS, delete the cache on their side, and restart PHINMS:

Typically:
<PHINMS Install Folder>\shared\requeueCache

Frans

--
Thanks,
Frans de Wet
Founder and Chief Technology Officer, Uber Operations LLC
Mobile -  (850) 445-7696

Christina Crawford

unread,
Feb 13, 2018, 7:29:23 PM2/13/18
to PHINMS User Community
What does a 500 error mean on the sender side.
The sender changed the port to 5088 for http in their route map and exported cap file for us to import. Restarted phinms. Still no envelope error on our side.
We are using sql server db worker queue with action pair. Nothing in 5th table.
So we need to send our public cert to sender to import to their phinms. Do we need their public cert to import.

We have receiver uncheck payload and text to disk.

Is there anything else we need to receive file to put into sql server db table.

Any file can go to the db table payload right. Does it put the file bane there too.
Does phinms use any internal file folder when receiving files before putting to sql server.
If use payloadcto disk on receiver service map what file folder does it go to. Do we have to use some payloadtodiak plugin or message handler plugin to use pay to load disk feature.
Does anyone use an error table in receiver service map beside worker queue.

I feel we are missing and prefer to receive a file and go to sql server db table.

Christina

Lowe, Phillip (DOH)

unread,
Feb 13, 2018, 8:14:52 PM2/13/18
to phi...@googlegroups.com
500 error means the server couldn't understand what was sent.
Check payload to disk and look in ...\PHINMS\shared\receiverincoming
Once you are communicating, you can worry about the destination routing. Divide and conquer!

When we set up to receive from a new sender, We send our public certificate for them to import and the instructions for filling in a route map to us and how to send a CPA back.
We import their public cert and CPA then tell them to send a test message without encryption.
When that is working, we have them send up a message that is encrypted.

It doesn't matter what port PHINMS is running on as long as the data arrives there.
We used a non-standard port for PHINMS since we had another web server on 8080 and IIS on port 80. That ran fine for years.
We set up an error table once but it has never been helpful.


We did have one person who drove us nuts. He finally gave up and a colleague tried and got a connection on the first try. There was something messed up with his login.
He deleted the logon from the system and created a new one and everything was fine. My bet is that there was something screwy with permissions.

Phill Lowe – 360 236-4261


-----Original Message-----
From: phi...@googlegroups.com [mailto:phi...@googlegroups.com] On Behalf Of Christina Crawford
Sent: Tuesday, February 13, 2018 4:29 PM
To: PHINMS User Community <phi...@googlegroups.com>

Christina Crawford

unread,
Feb 13, 2018, 9:55:58 PM2/13/18
to PHINMS User Community
I found.your email with the cdc documents. I read over again.

With PHINMS 2.9 and setting up the sender to send to cdc and setting up the receiver to receive files stuff that should be it besides the public cert and cos files.

Do we have to install a message handler executable or plugin to receive files also. This should be already built into phinms 2.9 right.

Christina Crawford

unread,
Feb 13, 2018, 10:10:31 PM2/13/18
to PHINMS User Community
Also what db tables are needed for.a receiver. Just the worker queue?
Is there a transportq used as a receiver.

Lowe, Phillip (DOH)

unread,
Feb 14, 2018, 12:27:48 PM2/14/18
to phi...@googlegroups.com
You don't need to install anything else except the JDBC driver if you are using an external database (we run MS SQL).
When we shifted to the 64 bit version we could only get it to work with the driver the PHINMS helpdesk has. We couldn't get it to work with the drivers that are posted on the web.


Phill Lowe – 360 236-4261

-----Original Message-----
From: phi...@googlegroups.com [mailto:phi...@googlegroups.com] On Behalf Of Christina Crawford
Sent: Tuesday, February 13, 2018 6:56 PM
To: PHINMS User Community <phi...@googlegroups.com>

Ray Humphrys

unread,
Feb 14, 2018, 12:31:28 PM2/14/18
to phi...@googlegroups.com
Rats. How do you get those SS drivers?

Lowe, Phillip (DOH)

unread,
Feb 14, 2018, 12:31:50 PM2/14/18
to phi...@googlegroups.com
WorkerQueue tables for the receiver. We run 6 or 7 so we can split traffic at the SERVICE/action pair level.
Sender uses TransportQ_out. We have not given access to the database so only run a single table though PHINMS can run multiple.
We have also created a PARTYID_MAP table to translate PARTYIDs to a SHORTNAME for ease of use in queries.
I have a tool that lets me look at a lot of PHINMS data flow by just reading the database and SHORTNAME really helps!


Phill Lowe – 360 236-4261


-----Original Message-----
From: phi...@googlegroups.com [mailto:phi...@googlegroups.com] On Behalf Of Christina Crawford
Sent: Tuesday, February 13, 2018 7:11 PM
To: PHINMS User Community <phi...@googlegroups.com>

Lowe, Phillip (DOH)

unread,
Feb 14, 2018, 1:31:44 PM2/14/18
to phi...@googlegroups.com

They can be found on all of our PHINMS servers  J

 

 

Phill Lowe – 360 236-4261

Reply all
Reply to author
Forward
0 new messages