|
|
|
FAQEvent Logs Client Won't Launch - Register Node Fail error message Standard User cannot launch program- folder permissions Program won't send or receive alerts Email not being sent Dropping profilesChanging Ports Hiding/Showing Icon in System Tray Event Logs There are basically three types of logs:
Server Events Log The communications with the server is logged on the server under an "events" tab. This provides a log of the set up of nodes and changes between the software client on the workstation and server such as when a new user was created, if there was a download of any changes in the button configuration, any error information and if there was any changes to the user information (like name or phone number). This is accessed through the server for viewing but at the moment we do do not have a "download" feature. However, you can copy and paste this data. Log of Alerts Received The log of alert messages is on the receiver software client of any receivers. This is located on each receiver's workstation. In the menu bar, you can click "Export" and it creates a log of all alerts and any user generated, associated notes as a text file. I have attached a sample titled ePanic_alerts_export.txt . Note, there is no log here of emails or text messages sent. This information will be stored on the receivers workstation until it is manually deleted from the receiver window. Log of Client Communications with Server and Messages Sent A log of communications with the server and of emergency messages is available on the sender's workstation and the file is Client.log. Note, while it confirms if the alert messages were successfully sent, it does not track if emails or text were actually received. Location: Log and config folder for XP C:\Documents and Settings\All Users\Application Data\ePanicButton Log and config folder for Windows 7/Vista C: \ProgramData\ePanicButton\Client
Admin user can install but next user (standard) can't launch the program
"Administrator can come in and load the program successfully but when the end user logs in, the program does not launch for them." The Solution: To solve this problem it is necessary give all users of that computer the access right to "Modify" and "Write" for the folder ePanicButton/Client.Go to the folder, Right Click and select properties, Choose the users and select Edit. Log and config folder for XP C:\Documents and Settings\All Users\Application Data\ePanicButton Log and config folder for Windows 7/Vista C: \ProgramData\ePanicButton\Client Client Won't Launch - Register Node Fail error message
Possible Issues Firewall / Anti-virus
This may be an issue with your anti-virus and/or firewall. You can test by turning off your firewall and then seeing if the client launches. Also try making exception in your anti-virus program: you want to allow the program: ePanicButton application reference file - appref.ms in the start up folders XP operating systems
Windows 7 and Vista
Vista Defender
Problem was with Defender program, which may block epanic 's start up. Need to disabled Defender - http://www.youtube.com/watch?v=D3WNHz99V8M Or in defender just turn on startup for epanic
Install Error after previous install by another user
Question: did you install as one user (maybe an administrative user), then later delete program and then try to re-install with another user? There is a specific Un-Install process and it might be an issue with remaining residual files. Make sure that you click Uninstall link in the ePanic Folder in the Program Menu of the Start Button. You can try checking these same Startup folders list above and delete any epanic button folders and files. XP operating systems
Windows 7 and Vista
Alerts and/or "Respond" Signal won't go through
Ensure that port 20160 is open for sending Ensure that port 20161 is open
for respond feature Firewall / Anti-virus Make exceptions for these programs: ePanicButton.exe ePanic_AlertReceiver.exe To find these programs to add to your exceptions list, open up Task Manager Under processes tab, search for epanicbutton programs Select the program and right click> Open File LocationCopy file location from window address bar or search from your anti-virus exception list browser window. You will find the location of both programs (ePanicButton.exe and ePanic_AlertReceiver.exe) Note: you may find other folders in the parent folders. These are for older versions of the client. You can find the correct, latest folder by searching through the task manager. Email not being sent It may be a smtp relay issue exchange server issue. If the email test fails, then it might be a configuration setting at the Exchange Server level. Make sure the user has permissions to relay through the server. You can also check on your Exchange server event log to see it is provides a reason for rejecting the test email. You may need to set up a SMTP Receive or Send Connector setup in your Exchange 2007 Server. To learn how- http://blogs.techrepublic.com.com/networking/?p=373 Solution to not opening relay to all workstations: If there are concerns about enabling Relaying on an Exchange server for all workstation, enabling the relay on a unknown sibling server on the same network reduces that exposure to just the PCs that were granted access to the SMTP Virtual Server. An important step is found on the Properties page for the Domains item, found below the Default SMTP Virtual Server in the IIS Management tool. A little Radio button and hostname field tells the server to forward all Email received to the designated Exchange server. It gets to where it needs to go and the Security hole is minimized to select users who probably won't be perpetrating any SPAM operations. In other words, Activate and configure the Server 2003 SMTP service on another box, grant rights to Relay thru it, and then defined on it to use your Exchange server as a "Smart Relay Host". The way it works is that ePanic sends the message to your SMTP (Simple Mail Transport Protocol - part of IIS) server, which then relays it to the Exchange server to propagate to the clients. This solution might introduce a bit of latency, but negligible. Dropping profiles Our system takes into account dynamic IP addresses but it does it by verifying with the mac address. Issues may occur if there was a change in their ISP connection or network card. Also, if you use WI-FI, there may be a change in the wi-fi adapter for this workstation. Turn off Wi-Fi adaptor. Changing Ports SMTP Port to change smtp port on server: put outgoing server address and then port number ex: email.secureserver.net:80 Pop Up Alerts "The default port number (20160) is used unless another one is specified. To specify another port number, append it to the recipient's name after a ':'. For example: SECSERVER_01:21170", On the Receiver Program, the port where the program "listens" for the alerts must be changed as well. Receiver Menu Bar > View > Options > Communication Port Note about Respond Feature: While the client program "sends" the alerts through port 20160, the "Respond" feature uses port 20161 to send back the signal that turns the little 'e' from white to green in the sender's epanic icon in the notification tray. Remove icon from Notification Tray Right now, there is no way to remove from the notification tray, unless we do some new development work. However, as you know, you can Rclick the task bar> Properties > Customize > Choose Hide Icons and Notifications for the epanic icon
|
||
|
|
|
|