PacsOne system not working, don't know why

martijnp · Post by **martijnp** » Thu Feb 09, 2012 8:46 pm

We are running 2 PacsOne servers for one of our customers.

The first should be forwarding all images to the second PACS when it receives them.
Since a coupleof weaks we have some issues with this.

When I try to echo from PACS2 to PACS1 everything is OK.
The other way around it is gicing me the error: Verify() failed: error = Association request rejected

When i want to store images to gives me an 'out of resources' error.

I suspect that the license is not running properly, we had this before.
How can I check this? I've checked the PACS2 port (:1234, with Putty), and it's opened

We've attached another Disk Array, but afterwoods i figure that problem was existing before these disks were attached...

The ipconfig output is as following:

C:\PacsOne>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : PACS2
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0C-29-3B-33-7D
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5c28:2149:3a3c:a229%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.76.28(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.76.193
DHCPv6 IAID . . . . . . . . . . . : 234884137
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-B8-50-11-00-0C-29-3B-33-7D

DNS Servers . . . . . . . . . . . : 192.168.76.2
192.168.76.3
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{28CA439D-9CCB-4BD5-AD79-73C769461DB1}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:28fb:1ab:3f57:b3e3(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::28fb:1ab:3f57:b3e3%13(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\PacsOne>

Post by **pacsone** » Fri Feb 10, 2012 2:02 am

Did you check the PacsOne Server logs on PACS2 and see what error got logged that correspond to the C-ECHO/C-STORE requests sent from PACS1?

martijnp · Post by **martijnp** » Fri Feb 10, 2012 8:04 am

When I try to ECHO from PACS1 to PACS2 I get the following messages in the log:

Fri Feb 10 09:02:01 2012 INFO - Session: started from SCU: 192.168.76.28
Fri Feb 10 09:02:01 2012 INFO - Receiving A-ASSOCIATE-RQ PDU
Fri Feb 10 09:02:01 2012 INFO - 1 record found in [applentity] table
Fri Feb 10 09:02:01 2012 INFO - A-ASSOCIATE-RQ received successfully
Fri Feb 10 09:02:01 2012 INFO - Sending A-ASSOCIATE-AC PDU
Fri Feb 10 09:02:01 2012 INFO - A-ASSOCIATE-AC PDU sent successfully
Fri Feb 10 09:02:01 2012 INFO - Receiving P-DATA-TF PDU
Fri Feb 10 09:02:01 2012 INFO - C-ECHO [1] command received in P-DATA-TF PDU
Fri Feb 10 09:02:01 2012 INFO - A-ASSOCIATE-RELEASE-RQ PDU received
Fri Feb 10 09:02:01 2012 INFO - Sending A-ASSOCIATE-RELEASE-RSP PDU
Fri Feb 10 09:02:01 2012 INFO - A-ASSOCIATE-RELEASE-RSP PDU sent successfully
Fri Feb 10 09:02:01 2012 INFO - Session: disconnected for client: 192.168.76.28

Post by **pacsone** » Fri Feb 10, 2012 7:51 pm

According to the logs on PACS2, PacsOne has accepted the C-ECHO request sent from PACS1, so it seems that maybe PACS1 was echoing something else?

Try stopping PacsOne Server on PACS2, then have PACS1 send another C-ECHO request to PACS2 and see if it's accepted or rejected. The expected result should be that PACS1 would NOT be able to connect to PACS2 since PacsOne Server is not running. So if you get either a Success or Rejection error when PACS1 is trying to C-ECHO PACS2, then it's definitely sending the request to the wrong host/IP address/TCP port.