Page 1 of 1
Install successful. Ping/Verify issues.
Posted: Thu Apr 16, 2015 3:15 pm
by djoyce
Install seems successful but when I configure my sonogram machines to send images to the server, the ping is good, but verify isn't. I'm using the standard port 104. I went through the install a few times initially using the default port "1234". After a few unsuccessful attempts, I uninstalled PACS only (leaving wamp intact), rebooted and reinstalled using port 104. That seemed to work. So to ensure it wasn't a fluke, I restored the snapshot (this is a virtual environment) and installed WAMP (using the same configuration files for php and apache I created earlier which worked) and PACSONE, this time using port 104. So essentially, it was mostly the same setup as the previous install that worked but was done from scratch. But the ping is good, no verify from the machine. All firewalls are down. Any ideas what it may be?
Thanks.
Install details:
This is a VMware ESX 5.1 VM
Windows Server 2008 R2
WAMP
Re: Install successful. Ping/Verify issues.
Posted: Thu Apr 16, 2015 4:21 pm
by pacsone
It seems the some other application may already be using port 104 on this server/VM instance? To find out for sure, you can stop PacsOne Server first, then open a local command shell and run the following command at the shell prompt:
Then check the 2nd column in the output from the command above, and see if you see a row like "0.0.0.0:104" and if you do, then the 5th column will tell you the Process ID (PID) of the application currently using that port 104.
Re: Install successful. Ping/Verify issues.
Posted: Thu Apr 16, 2015 6:43 pm
by djoyce
pacsone wrote:It seems the some other application may already be using port 104 on this server/VM instance? To find out for sure, you can stop PacsOne Server first, then open a local command shell and run the following command at the shell prompt:
Then check the 2nd column in the output from the command above, and see if you see a row like "0.0.0.0:104" and if you do, then the 5th column will tell you the Process ID (PID) of the application currently using that port 104.
It's a clean Windows install with nothing much else but WAMP, PACSONE, Microsoft Visual C++ 2012, Firefox and Notepad++.
The PID maps to pacsone.exe:
Code: Select all
C:\>netstat -aon -p tcp
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 2532
TCP 0.0.0.0:104 0.0.0.0:0 LISTENING 2680
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 672
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 2784
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1296
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 388
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 760
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 808
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 484
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 1332
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING 492
TCP 127.0.0.1:3306 127.0.0.1:49605 ESTABLISHED 2784
TCP 127.0.0.1:49605 127.0.0.1:3306 ESTABLISHED 2680
TCP 127.0.0.1:49616 127.0.0.1:49617 ESTABLISHED 2452
TCP 127.0.0.1:49617 127.0.0.1:49616 ESTABLISHED 2452
TCP 192.168.50.232:139 0.0.0.0:0 LISTENING 4
TCP 192.168.50.232:3389 192.168.50.167:65504 ESTABLISHED 1296
C:\>query process /ID:2680
USERNAME SESSIONNAME ID PID IMAGE
system services 0 2680 pacsone.exe
I managed to get it working again somehow by going through the same process I got it working the first time; installing PacsOne, then uninstalling it (and leaving WAMP alone), rebooting and installing. Might licensing be the culprit? I decommissioned my PACSONE servers a few years back for another system that did reporting and recently needed PACSONE for archiving only. I applied one of the old licenses (which seemed to work) but it's an entirely new VM.
Re: Install successful. Ping/Verify issues.
Posted: Thu Apr 16, 2015 7:10 pm
by djoyce
I found the problem. Invalid license.
Code: Select all
Thu Apr 16 15:06:01 2015 INFO - <9> Sending A-ASSOCIATE-RJ PDU
Thu Apr 16 15:06:01 2015 INFO - <9> A-ASSOCIATE-RJ PDU sent successfully
Thu Apr 16 15:06:01 2015 INFO - Session: <9> disconnected for client: 192.168.50.59
Thu Apr 16 15:07:53 2015 INFO - Session: <10> started from SCU: 192.168.50.59
Thu Apr 16 15:07:53 2015 INFO - <10> Receiving A-ASSOCIATE-RQ PDU
Thu Apr 16 15:07:53 2015 INFO - 1 record found in [applentity] table
Thu Apr 16 15:07:53 2015 ERROR - Invalid license information or license has expired
Thu Apr 16 15:07:53 2015 INFO - <10> Sending A-ASSOCIATE-RJ PDU
Thu Apr 16 15:07:53 2015 INFO - <10> A-ASSOCIATE-RJ PDU sent successfully
Thu Apr 16 15:07:53 2015 INFO - Session: <10> disconnected for client: 192.168.50.59
I guess I have to update my licensing. Thanks for the help! Still unsure how it worked the other times.