Remember that you can always contact Customer Service for assistance.
Common Issues
SCENARIO: When I run locally it works, but not not if I run as a Windows Service. This is almost ALWAYS the same thing: User Rights for the logon ID running the MS Windows Service. The CORE HL7 Sender has 5 Windows Service executable files (.exe) which you can find in the Installation Folder (click Open the Installation Folder in the Tools menu of the Main Window) . They are:
•COREHL7SenderService1.exe •COREHL7SenderService2.exe •COREHL7SenderService3.exe •COREHL7SenderService4.exe •COREHL7SenderServiceX.exe
The first 4 files are your primary windows services (Service1, 2, 3, and 4) and COREHL7SenderServiceX.exe is the program that runs your private services in multiple instances.
When you install any Windows Service using the CORE HL7 Sender, by default, that service will use the built-in Windows account LocalSystem to run. When you are Running Locally, you are running as YOU (whatever logon Id you used to log into the server) with all of the user rights and privileges, and login scripts, gifted to you by your Network Administrator. When a Windows Service runs, it is running, by default, as LocalSystem which has no such privileges.
There is a very easy way to test if this is in fact the problem. Click the
 Open the MS Windows Services
Right-Click on the service you want to test and select Properties. In the properties window go to the Log On tab.
 Log On Tab
Check This Account and then enter YOUR Windows Logon ID and Password. Then click Ok or Apply.
We use YOUR account because we KNOW that it works when YOU run it locally. Now if you start the service and it WORKS, you will know that the initial problem was caused by insufficient User Rights for the Windows Service. This is usually caused either by a Global Security policy, OR because you are using Network Shared folders or Mapped Drives in the Data Folder property of your Sender Profile.
|
button on the toolbar in the
This is a very common support call for us and it is almost always (99% of the time) the same thing, FIREWALLS or VPNs.
SCENARIO: I can connect and send messages to a HL7 Listener running on the same computer. It fails to connect and send to a HL7 Listener running at a remote IP address. Try these steps in this order.
1.Go to a COMMAND prompt and try to PING the remote IP address. Does that work? IF no, fix that. If yes, continue. 2.VERIFY with your Trading Partner that their HL7 Listener is up AND listening on the port number in your profile. Then click the 3.Verify that your firewall is not blocking outbound TCP traffic for the PORT number selected in your Sender Profile. If it's not blocking the port make sure that it will allow ALL of the .exe files you can see in the Installation folder (click Open the Installation Folder in the Tools menu of the Main Window) to send outbound TCP traffic. You may have to create firewall exception rules to do this, so work closely with your Network Administrator.
|
PING button on the toolbar in the main window when you have the profile selected. Does THIS Succeed. If yes then your CORE HL7 Sender Should work AT LEAST when running locally. If it doesn't work when running as a service refer to the FIRST troubleshooting scenario on this page. If it doesn't work, continue.
See this discussion about installing and removing the Windows Services.
|
