|
Other Errors
|
|||
|
|
|||
|
|
|||
|
Local errors are errors that are the result of problems with the local computer or Modem.
For local errors, check the following
quick tips:
· Make sure the modem is properly connected and turned on. · Verify your modem selection, advanced settings, and other modem options are correct in Communications Setup. · Check to see if any other communications program is currently using your modem or hasn’t properly disconnected from it. ·
Reset or power down your modem.
If it is an internal modem, power your system down and reboot.
|
(1104) Local Error: Could not access modem
11XX, 1104, 1105 |
|
Error 1104 indicates that the InfoRad Wireless software tried to open the Com Port (or Modem) and could not get an OK response back from the Modem. The trick to fixing this problem is that you need to get the InfoRad software communicating again with the Modem.
If it is an external Modem, it’s more obvious that the
Modem is turned on and working properly. Make sure the lights are working as
they should and make sure that the Modem’s serial cable is properly seated at
both ends (at the Modem itself and at the PC). Also, make sure that the phone
line is plugged into the Line side of the Modem and that (if a phone is
plugged into the Modem) the phone is plugged into the Phone side of the
Modem. If all this checks out ok, then
continue on below.
|
|
|
|
This means that the line device
selected for sending pages is unavailable to the system. Usually this means
that the line is in use by some other application. ·
Make sure that the phone line is
plugged into the Line side of the Modem and that (if a phone is plugged into
the Modem) the phone is plugged into the Phone side of the Modem. · Connect a phone to the modem's phone port so that you can listen in on the call made by the InfoRad software. Make sure that there is a dial tone prior to sending a message. |
|
Remote errors
happen when the remote system (the wireless messaging service) reports a
specific error or when there is difficulty communicating with the wireless
messaging service. These errors happen after a connection with the messaging
service has been established. |
||||
(1201) Remote Error: Could
not handshake with Service
12XX, 1201, 1202, 1203, 1204, 1205, 1206 |
||||
|
InfoRad Wireless software was able to
CONNECT to the answering modem, but is receiving no further response from the
messaging service. ·
Check to insure the messaging service
modem access number is correct. Note that it may also be called the Terminal
phone number, Alpha Port phone number, Access number, or PCS short messaging
service (SMS) phone number. ·
Check the messaging service
communication parameters – Baud Rate, Data Bits, Parity, and Stop Bit. (Note:
Most wireless messaging services are 1200 Baud, sometimes 2400 or 300; and
are almost always 7 data bits, even parity, 1 stop bit.) ·
Check the modem selection in the
Communications Setup. ·
Select "Override" in the
Modem Configuration dialog, and then click on the Create button to build a
unique initialization string for your modem. ·
Reference your modem’s manual
(reference AT command section) to construct a modem initialization string for
your modem. · Check with your modem manufacturer to insure your modem supports the wireless messaging service Baud Rate and data settings (Ex: 1200, 7, even 1). |
||||
|
|
||||
|
The wireless messaging service did not
return any response code after the InfoRad Wireless software sent a data
block; generally a result of a poor connection, or can be a problem at the
messaging service. ·
Retry sending the message(s).
· If received when sending multiple messages, check with your wireless messaging service for any limit on the number of messages that can be sent in a single dial-up session. |
||||
|
|
||||
|
The messaging service responded to a
data block with the NAK code. ·
Retry sending the message.
·
Remove the area code from the wireless
receiver ID number (text pagers). ·
Check the maximum message size, lower
the message size setting to 80 characters and retry. ·
Verify the proper wireless receiver ID
number is entered. · Use the wireless receiver’s PIN number. |
||||
|
|
||||
|
The wireless messaging service
responded to a data block with the abandon code. This means the wireless
messaging service is rejecting the data block outright. It is most likely
that either the Receiver's ID is entered
incorrectly or the pager is not
setup for "UVB" with your paging company.
·
Make sure that you've entered
the correct ten-digit phone number (sometimes the seven-digit phone or some
PIN number provided by your paging company), no dashes, parentheses, or
spaces. · If you're certain you've entered the correct phone number, then check with your local paging representative to make sure that the pager is programmed for "UVB".
If you have Arch (USA Mobility) pagers and you know that you’ve entered the correct phone number, call your local Arch representative and verify that the pager(s) are setup for UVB. Other Helpful Tips: ·
A "[P" in error messages in
the Failed Messages error screen indicates that the program is starting to
send the message – if disconnects occur at this point it usually indicates an
invalid wireless receiver ID number. ·
Verify that the proper wireless
receiver number is entered. Sometimes wireless receivers are assigned two
numbers. One number for numeric messaging from a phone and another for the
wireless receiver identifier when remote messaging (PIN number). Verify with
your wireless messaging service which number to use. ·
You may need to verify with the
wireless messaging service that the wireless receiver number is activated on
the messaging service being called, is programmed for text or short messaging
(not numeric-only messaging), and that you are using the correct service
number for text messaging. ·
Verify that there is no area code in
the pager number. ·
Verify that you are dialing the correct
service number for your wireless receiver—messaging companies sometimes have
multiple service numbers, and your wireless receiver ID number must be valid
on the system to which you are connecting. · Some messaging companies will reject messages if the message is too long. Try sending a short message. If it successfully sends, verify the allowable message length with your wireless messaging service, and then set the message size in the wireless messaging service setup. |
||||
|
|
||||
|
The wireless messaging service sent the
InfoRad Wireless software a disconnect code. This can happen when the service
does not accept InfoRad Wireless software’s response to the login prompt. ·
Check that any password is valid in the
Wireless Messaging Service setup advanced properties. (Note that most
wireless messaging services do not require a password.) ·
A "[P" in error messages in
the Failed Messages error screen indicates that the wireless receiver ID # is
incorrect—try and use the PIN number and not the wireless receiver phone
number in the receiver’s ID Number field. Double-check the receiver ID to
make sure it was correctly entered. ·
Some messaging companies will reject
messages if the message is too long. Try sending a short message. If it
successfully sends, verify the allowable message length with your messaging
company, and then set the message size in the wireless messaging service.
·
Make sure the wireless receiver has been
activated or not disconnected by the messaging company. Optionally, try
messaging it from your phone as a numeric pager. · Verify that you are dialing the correct access number for your receiver—wireless messaging services sometimes have multiple systems, and your wireless receiver number must be valid on the system to which you are connecting. |
||||
|
|
||||
|
The messaging service did not
properly respond after the InfoRad Wireless software’s login. ·
Retry sending the message.
·
Check the data bits and parity settings
(Messaging Service Advanced Settings). ·
Check that any password is valid.
Remove the password if it is not required by the messaging service.
·
Try changing the baud rate (Messaging
Service Advanced Settings). ·
Check the modem selection in the
Communications Setup to ensure that the proper modem is selected.
·
Select "Override" in the
modem configuration, and click on the Create button to build a custom
initialization string for your modem. ·
Reference the ‘Using High Speed and Fax
modems’ section of the manual or on-line Help and your modem’s manual
(reference AT command section) to construct a modem initialization string for
your modem. · Check with your modem manufacturer to insure your modem supports the messaging service Baud Rate and data settings (Ex: 1200, 7, even, 1). |
|
Communication
errors report problems establishing or maintaining the link between the
wireless messaging service and the local computer, whether the source of the
problem is the wireless messaging service, the software Server, the phone
network, or anything else. |
(1301) Communication Error: Could not connect with remote modem
13XX, 1301, 1303, 1304, 1399 |
|
This appears
when the phone was successfully dialed, but no "CONNECT" message
was received. Common causes are bad service phone numbers, bad modem
initialization strings, bad modems (on either end), incorrectly installed
modems (no dial tone) and so on. ·
Verify that you correctly entered your
messaging service phone number and parameters such as baud rate, data parity,
and stop bits. You should always hear a high-pitched modem connection tone
when dialing the correct number. ·
Verify your modem selection or custom
init string. If you are using a Fax or high-speed modem disable the data
compression and error correction features; see Using High Speed and Fax
Modems section for more information. ·
Verify that you are dialing the correct
service number for your wireless receiver—messaging services sometimes have
multiple service numbers, and your wireless receiver number must be valid on
the number you are dialing. ·
Verify your dialing location settings
and selection. ·
Check if the messaging service requires
a password, and if so, verify that password (normally, messaging services
don’t use a password). ·
Double-check the custom modem
initialization string, if the "override" option was used during
modem setup. ·
Make sure the modem isn’t attempting to
connect to a fax number. · The wireless messaging system may be experiencing technical difficulties. Check with your messaging service. |
|
(1303) Communication Error: There was no dial tone on the dialing line |
|
This appears
when the local modem could not detect a dial tone, and so could not begin
dialing. ·
Verify the modem is correctly
installed. ·
Check to see if the phone line is in
use or is working properly. ·
Verify that your modem has power, that
you have dial tone at your modem, and that your phone line is plugged into
the modem jack labeled "line." ·
Verify that your dialing location and
options are correct (Windows "Telephony" or "Modems"
control panels). ·
Verify your modem selection.
· If you have a digital phone system, you may need to use a special jack to access an analog phone line. Plugging your modem directly into a digital phone system will not work, and may damage the modem or the phone system. |
|
(1304) Communication Error: The called number was busy |
|
This appears when the program has already redialed the service provider the specified number of times, and received a busy signal every time. · Verify that there is an "outside line" access number in the Dialing Properties if required. · Verify the messaging service access number is correct. · Check if the messaging service is busy or experiencing problems. · Increase the re-dial on busy setting in Communications Setup, Advanced Modem Settings, Dialing Options. |
|
|
|
The generic
communications error that appears when there is some problem reading data
from the communications port. ·
Check for any device conflicts. · Try decreasing the baud rate of the modem to 1200 baud and set the initial port settings of the modem to 7 data bits, even parity, and 1 stop bit. How? |
|
1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
TAPI errors report problems setting up
and using the Windows telephony interface. These errors should represent
problems that are specific to TAPI, and not to the process of sending pages
in general. For TAPI errors, unless specified
below, check the following: ·
Check other programs that utilize TAPI
for a similar problem. ·
Verify the TAPI setup/installation for
the operating system. ·
Verify that your system is using TAPI
1.4 or above. ·
Verify that you modem is setup properly
in the operating system. ·
Check for any device conflicts.
·
Check for any software conflicts.
·
Try deleting the current modem
configuration in the Modems Control Panel and then adding it back.
· Check your TAPI location selection and settings (dialing options) in the Windows "Telephony" or "Modems" control panels. |
(1400) TAPI Error: TAPI initialization failed
14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
To start up TAPI, the program must load
some TAPI / operating system DLLs. If the DLLs cannot be loaded, this error
will appear. 9/10 cases show that rebooting the PC fixes the problem. If not,
then try updating your version of Window's TAPI by downloading the latest
service pack for Windows. |
|
(1401) TAPI Error: Could not negotiate common API version 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
There are different versions of TAPI
available. Windows 95 shipped with TAPI 1.4 and Windows NT 4.0 shipped with
TAPI 2.0. InfoRad Wireless tells the system that it can support TAPI 1.4 and
the system responds by enabling only the features available in that version.
If there is some problem with this process (for example, if the system only
supports TAPI 1.3 or lower), you may see this error. Try updating your
version of Window's TAPI by downloading the latest service pack for Windows.
|
|
(1402) TAPI Error: Unable to query TAPI address
capabilities 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
Before placing a call on a device, the
program queries TAPI about the line’s capabilities. This message shows up
when TAPI will not or can not respond to the request. |
|
(1405) TAPI Error: Selected device does not
support data calls 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
TAPI devices include modems, fax
boards, ISDN telephones, and other devices, not all of which can transfer
data the way modems can. Before sending messages, InfoRad Wireless checks to
be sure that the device the user selected is in fact a data modem, and not
some other TAPI device. |
|
(1410) TAPI Error: Could not open line device 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
Before placing a call, InfoRad Wireless
checks to be sure that the line is available (and shows error 1105 if it is
not), but if there is some problem opening the line (even if TAPI claimed the
line was available) this is the error message. |
|
(1415) TAPI Error: Could not specify status
messages to monitor 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
After opening a line device, the
InfoRad Wireless software informs TAPI which status messages are important
for the call. If there is a problem doing this, this error appears.
|
|
(1425) TAPI Error: Could not specify port
settings prior to opening port 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
Before placing a call, the InfoRad
Wireless software attempts to set the baud rate, data bits, stop bits, flow
control, error correction and data compression settings specified for the
modem and messaging service in use. If there is a problem doing this, this
error appears. · Verify with your modem manufacturer that your modem supports the baud rate and data settings required by your messaging service (usually 300, 100, or 2400 baud with 7 Data Bits, Even parity, 1 Stop Bit). |
|
(1435) TAPI Error: Could not create call
parameters 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
This error appears if the data structure
containing parameters for TAPI cannot be created. This would only happen if
the computer ran out of memory. |
|
(1440) TAPI Error: Call to lineMakeCall()
failed 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
InfoRad wireless uses the
lineMakeCall() function of TAPI, which opens the serial port. This error
appears when this call fails. |
|
(1450) TAPI Error: No response to
lineMakeCall() 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
After placing a phone call with TAPI,
the InfoRad Wireless software expects to get some responses back from TAPI,
including an announcement that the modems have either connected or
disconnected. If those responses don’t arrive within 60 seconds, this error
appears. |
|
(1455) TAPI Error: Could
not get port handle from TAPI 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
After placing the phone call, the
InfoRad Wireless software asks TAPI for direct access to the COM port,
through which it can send and receive data. If the port handle is unavailable
for some reason, this error appears. |
|
(1460) TAPI Error: Could not change call
parameters 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
After dialing a call in Override mode
(Modem Configuration), the InfoRad Wireless software attempts to switch back
to standard TAPI mode to actually send pages, then hang up. If the switch
back to standard TAPI mode does not work, this error appears.
|
|
(1499) TAPI Error: Unexpected TAPI Error 14XX, 1400, 1401, 1402, 1405, 1410, 1415, 1425, 1435, 1440, 1450, 1455, 1460, 1499 |
|
This is error message used in cases
where the InfoRad Wireless software is able to detect that something has gone
wrong with TAPI, but the error is not one of the above listed errors.
|
|
Errors specific to the InfoRad Wireless
software File Processor (AFP) module. (These errors will typically only be
seen if you are using custom file processing.) |
(4001) AFP Error: Name does not exist in pager
or group list
4XXX, 4001, 4002, 4003 |
|
The AFP was
able to read an ASCII file, but the word or words interpreted as the name of
a pager or a group of pagers did not match any pager or pager group in the
InfoRad Wireless software database. ·
Check for correct spelling of the name
or group name in InfoRad Wireless software or in the application generating
the message. · Remove any excess spaces in the name in InfoRad Wireless software. |
|
|
|
This means that the line device
selected for sending pages is unavailable to the system. Usually this means
that the line is in use by some other application. |
|
|
|
The AFP did not
find all of the mandatory entries (header, recipient, and message contents)
in the ASCII message file. · Check the application generating the message file for proper formatting. |
|
Errors specific to the software Server
report problems creating ASCII files for the InfoRad Wireless software server
or problems retrieving message status information from the server status
files. For all APC Server errors ·
Reference the LAN Problems section
concerning network access rights. · Check for proper path specified for the ‘messages’ directory. The path should be the same in the InfoRad Wireless Pro Client and Server. |
(5001) APC Process Error:
Could not write message file
5XXX, 5001, 5002, 5003, 5004, 5005 |
|
The client was able to open or create a
file to place its message in, but there was an error writing to the file.
Possibly this could happen as an access rights problem, but more commonly,
access rights problems will show up as 5002. |
|
|
|
The client was not able to open or
create a file to place a message in. Usually this is either the result of
network access rights problems or a problem with the message path. · Log into the PC where the InfoRad Service application is installed, browse to the InfoRad Enterprise NT/SV Service folder and change the permissions for the Share to Full Control for all PC's or Users that need to operate the Client application. |
|
(5003) APC Process Error: Could not get message file number from
control file |
|
The client was not able to open the control file. Usually this is either the result of network access rights problems or a problem with the message path. · Check the Messages path on both the client and server applications. Another probable cause is the registry value for the ClientInfo folder that contains the Message Number that the Client application must be able to increment. Prior to performing these steps, InfoRad Tech Support advises that you backup your current Windows Registry. Please refer to your copy of Microsoft Windows to do so. Once your Windows Registry is properly backed up, you may be able to fix this error 5003 by the following: · Login to the PC as Administrator if needed · Click Start · Click Run · Enter "regedt32" or "regedit" in the Open: text box · Click OK · If you've installed the Client for "All Users", then select the HKEY_LOCAL_MACHINE registry. Otherwise, select the HKEY_CURRENT_USER registry · Browse to the following path: SOFTWARE, InfoRad, 2018-001, 9.X, Client · Right click on the ClientInfo folder and select Permissions or click Edit at the top, then Permissions · Make sure that the Users (Ie. Domain Users) for this computer have Full Control to this registry value, then click OK · Logout and Log back into Windows as the User that was receiving error 5003 and send a test page using the InfoRad Client. Error 5003 should no longer occur. You may now close your Registry Editor. Run the Client and send a test page. The test page should now go through for this Client application. |
|
(5004) APC Process Error: Could not read error information from AFP status file |
|
When a message fails, the client
attempts to extract the explanation from the resulting status file, in which
case the error from the server appears. If there is a problem opening or
reading from the status file, this error appears. |
|
|
|
Client installs using same client ID - re-run Client Setup for users receiving this error. If multiple users are logging on to a workstation, then each user (login) must run the Client Setup before using the Client program. From the description it sounds like a Client is sending a message and exiting without waiting for "sent". Another client that is using the same Client ID sends messages and "cleans" up the the status files from the original send. When the original client brings up the Client to send a mew message, it looks for the previously sent message, but the status file is not there and it pops the 5005 error. If they select to resend, then the original message is sent a 2nd time. |
|
Network errors are errors that are
usually the result of problems with the local network (Antivirus/Firewall
software) or with a network connection to the host computer. Here’s a good place to start: If you’re new to
InfoRad and have not already setup techsupport@inforad.com as a
Receiver, then CLICK HERE. Otherwise, continue troubleshooting
below.
For local errors, check the following:
· Make sure the Computer with InfoRad software installed has an available Internet connection and any Antivirus/Firewall software (Ie Norton, McAfee) or hardware (Ie. Router) is not blocking the InfoRad software from reaching the Internet. Start Troubleshooting
· Check with your Internet Service Provider to make sure that you are connecting to an allowed email server. Start Troubleshooting · Make sure that you have a valid Messaging Service selected for your Receiver. Click here to use our website to check your Messaging Service setup.
· If you belong to an organization where security is strict, then refer to your local IS/IT department for options Start Troubleshooting
|
(6002) Network Error: Could not connect to host
6XXX, 6002, 6101, 6201, 6202, 6203, 6301 |
|
INTERNET EMAIL (SMTP)
Firewall/Antivirus software such as Norton and McAfee both are known to either initially block InfoRad software from sending text messages via Internet email (SMTP) or block InfoRad software later on unexpectedly.
Either disable or configure your Firewall/Antivirus (sometimes both if Antivirus and Firewall software are separate) from blocking InfoRad software or scanning outgoing email, then send another test page. If you feel comfortable with leaving your Firewall/Antivirus software in that state, then do so. We have included the following links to assist you with setting up or configuring Antivirus and Firewall software.
McAfee Desktop Firewall version 8.0McAfee
VirusScan Enterprise 8.0 (Viruscan Console)
Some Internet Service Providers do not allow you to connect to email servers other than their own. For example, if you are an AOL customer, it’s understood that AOL does not allow you to connect to email servers other than their own. Therefore, you have to setup AOL’s email server to be used as a Messaging Service in the InfoRad software. This may be true for other Internet Service Providers such as Comcast, RoadRunner, Earthlink, etc. Contact your local Internet Provider’s representative to find out for certain.
If you know who your Internet Service Provider is, then find it in our listing of Messaging Services and set it up to be used as a Messaging Service in the InfoRad software (Make sure to click on the ShowMe button): http://www.inforad.com/techsupport/MessagingServices/MessagingServicesIndex.php3?showonly=ANY
If you work for an organization such as a hospital where network security is strict, then your organization may have its own email server that you can setup as a Messaging Service using the InfoRad software. Contact your local IS/IT department to find out for sure. The email server must be able to send to an email address outside of its own domain. Some Exchange servers, for instance, are not set up to send to a 10-digit-phone-number@vtext.com (Verizon Cell email address) because it does not belong to the email domain of myemail@myhospital.org. Therefore, in order to use your hospital’s email server, the email server (or network security) would have to allow email to be forwarded to the appropriate email server that handles the vtext.com domain. Possible Cause #4: Otherwise, if your Internet Service Provider is not listed, let us know so that we can update our website. Email us at techsupport@inforad.com.
INTERNET SNPP
Verify that you have a working Internet connection. If you're certain that you have an Internet connection, then check to see if the Messaging Server address or IP number is correct under Edit, Messaging Services. Compare your Messaging Service to our list of SNPP Messaging Services. Otherwise, make sure that you're able to send messages via SNPP across port 444 and that a firewall is not blocking this connection. For more information about firewalls, refer to the following URLs: · Windows XP Firewall: http://www.microsoft.com/windowsxp/using/networking/learnmore/icf.mspx · Norton Antivirus/Firewall: http://www.symantec.com/techsupp/consumer.html · McAfee Firewall: http://ts.mcafeehelp.com/?siteID=1 For further, in-depth troubleshooting, you can generate a log file called inetlog.txt using the following steps: · Click Setup and select Internet Settings
(C:\Program Files\InfoRad\Wireless Enterprise for Enterprise and C:\Program Files\InfoRad Enterprise SV Service for Enterprise NT/SV) You may also find this inetlog.txt file by right clicking on the shortcut to your InfoRad Wireless software, click on Properties, then click on the Find Target button.
(Error 6002) Network Error - Could not connect to host (Here I disabled the Internet connection and sent a test page to mimic the loss of an Internet connection) 08/31/2005 11:58:18 stat:Log
opened Successful Connection 04/06/2005 15:04:25 stat:Log
opened |
(6101) Network Error: Socket I/O operation
failed
6XXX, 6002, 6101, 6201, 6202, 6203, 6301 |
|
Some unexpected error occurred while sending or receiving data.
Many cases show that either some Antivirus/Firewall software is blocking the connection to the appropriate server (normally an email SMTP server) or sending text messages to email addresses via Internet email has caused the sender (either the IP number of the PC sending the text messages or the ReplyTo email address being used in the InfoRad software under Setup, Internet Settings, ReplyTo/Email SMTP tab) to be placed on a SPAM Block List. Another case shows that the messages were not going through simply because there was no ReplyTo Address entered at all. Even though text messages were being accepted for other pagers and/or cell phones, messages sent via email to some (Ie. Verizon cell phones) would terminate with error 6101. |
|
|
|
The remote host (the SNPP server, or possibly the telnet proxy server, if one is configured) disconnected without warning. |
|
|
|
SMTP Once Case appeared when sending text messages to via Internet email to TMobile phones. The customer changed the timeout from 30 to 40 Seconds and the Max Message Length from 80 to 140 Characters. The thought was that the timeout (increasing it to 40 Seconds) may have been preventing the connection by not allowing enough time for the connection to be established between the Customer’s PC and TMobile’s Email Server. SNPP The timeout for the paging service (set up in the paging service properties screen) elapsed with no response from the SNPP server. This problem can sometimes be rectified by increasing the timeout, but it may indicate something wrong with the SNPP server or with the network connection. Also can be sent from an SMTP server. |
|
|
|
When sending via Internet (email) SMTP Messaging Service
Many cellular companies currently require text messages to be sent via email. This error can occur when sending messages via Internet (email) SMTP.
· Sometimes, an email server will tell you that the email address you entered is incorrect. For instance, setup a Receiver to send to XXX5551212@vtext.com and select Verizon PCS – Internet SMTP for the Service (make sure that you also have your own email address entered under Setup, Internet Settings, ReplyTo Address). Send a test text message and you’ll get error 6203 indicating that XXX5551212@vtext.com is not a valid Verizon (vtext) email address. To fix, correct the email address and try again. · One instance can be caused by not having a ReplyTo Email Address entered under Setup, Internet Settings, ReplyTo Address tab (or Email (STMP) tab for versions 9.6.X). This normally occurs when an email server is being used that does not require authentication (with a username and password).
· Another occurrence is caused by an email server (Messaging Service) that requires authentication but either the InfoRad Wireless software does not have SMTP Authentication enabled or an incorrect username and password is entered (under Edit, Messaging Services for version 9.7.X and higher. Version 9.6.X does not support SMTP Authentication. You will need to upgrade your software. Call (800) 228-8998 for upgrade options).
When sending via Internet SNPP Messaging Service SNPP server responded to an SNPP protocol command with a failure code. When this error happens, the explanation text sent by the SNPP server will be included on the error screen along with this error message. That explanation should provide more detail on why the transaction failed. The explanation might be, for example, "550 Error, pager ID must be 10 digits" or "550 Error, pager ID cannot be identified" and so on. ·
Verify that you have entered the correct pager ID,
normally using the ten-digit phone number of the pager, no dashes or spaces. Have user read responses from hardware or remote system. Chances are the cause of failure was captured there. If nothing appears, have them generate the inetlog.txt file as described in the 6002 error above.
How to fix: If the user is behind a proxy or firewall, have them contact there IS manager. They need to know: Is the proxy a telnet proxy? If so, get the server address and port number for the telnet proxy. Start a telnet session to the proxy and find out what the command prompt is. Also find out what the connect command is. All of this information needs to be entered into the user’s InfoRad product under Telnet Proxy to work around the proxy.
Have the IS manager create an exception to allow connections going to the paging server hosted by the paging company to go through. This occurs when a connection could not be made to the WCTP gateway. Probable causes are either the server being down, or the user needs to connect to a proxy in order to page.
|
|
(6301) Network Error: Target address or URL appears to be invalid |
|
The URL address for the Messaging Service could not be parsed in order to attempt a connection. Check the Messaging Service address. |
|
WCTP errors – the result of problems with the transaction between the
InfoRad sending messages to the WCTP Server computer(s). |
(7000) WCTP Error: Could not read WCTP response
7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
Message to a
WCTP gateway was able to POST, but the WCTP gateway response was unreadable.
Attempt to re-send. |
|
(7001)
WCTP Error: WCTP response was garbled, invalid, or unrecognized 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
The WCTP gateway reply to a message was OK, but the text of the reply cannot be read or is unrecognized. This can happen when a valid web page URL is entered in the Messaging Service WCTP address instead of a valid WCTP gateway address. (Any web server will send a reply back to an HTTP POST operation, but the reply will be HTML and not XML. XML is the expected format of a reply from a WCTP gateway.) This error seldom occurs (if ever). |
|
(7002) WCTP Error:
Could not POST WCTP message to gateway 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
Could not connect to the WCTP gateway. This is a common error for InfoRad customers. · First, Do you have a Working Internet Connection? Simply browsing the Internet is enough to check that InfoRad has an Internet connection that is useful for sending messages using the WCTP Internet Protocol. If you are not sure that you’re paging company supports this Internet protocol, then Click Here to check out our List of Messaging Services. This could also mean that the Internet
or Network connection to the WCTP Server is being blocked or is not found.
Other common causes for this error are: ·
Is a Firewall
blocking the Internet connection? You may try
momentarily disabling the firewall or configure the firewall to allow
connections to the WCTP Server computer via port 80. 1.
Windows XP Firewall, Visit http://www.microsoft.com/windowsxp/using/networking/learnmore/icf.mspx. 2. McAfee Desktop Firewall version 8.0 3.
McAfee
VirusScan Enterprise 8.0 (Viruscan Console) · Do you have a Proxy Server that prompts you to log on before connecting to the Internet using Internet Explorer? InfoRad software supports HTTP Proxy Server Authentication for the WCTP protocol. Click here for the steps to setup the InfoRad software to use a Proxy Server. · Click Edit, then select Messaging Services. Scroll to the Messaging Service being used for this particular receiver (Ie. Arch - Internet WCTP), click to select the name of the Messaging Service and click Edit. Check the Server Address and make sure that all letters and punctuation are correct according to our website http://www.inforad.com/techsupport/MessagingServices/MessagingServicesIndex.html |
|
(7003)
WCTP Error: Bad HTTP status code 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
Make sure that you have the correct
WCTP Server Address entered under Edit, Messaging Services (Ie. http://wctp.arch.com/wctp) ·
Click here to view the list of Internet WCTP
Messaging Services on our website to verify. |
|
(7004)
WCTP Error: HTTP 407 Proxy Authentication Required 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
The HTTP
session returned a Proxy Authentication error. This can happen when the
Internet Connection uses a Proxy Server and you have not turned on Proxy
Authentication in the program Internet Setup options. ·
Turn on Proxy Authentication in the
Setup Menu by selecting Setup, Internet Settings. Enter your Username and
Password.
|
|
(7005)
WCTP Error: HTTP 407 Proxy Authentication - bad username/password 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
The HTTP
session returned a Proxy Authentication error. This can happen when your
Proxy Authentication setup contains an incorrect Username or Password. Edit the
Proxy Authentication Username and Password in the Setup Menu . Internet
Settings. Check with your Network Administrator for the correct Username and
Password for Proxy Authentication.
|
|
(7401)
WCTP Error: Invalid Subscriber ID 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
Just anything in the authentication
fields will no longer work. Customers who want to use Verizon WCTP must go
to: http://wctp.myairmail.com/wctpRegistration/jsRegistration.jsp ·
Make sure to register on-line
for your own username and password. ·
Make sure to confirm the
registration using the email sent to you by Verizon. ·
The username and password
registered with Verizon is then entered in the Messaging Service (Verizon
Paging - Internet WCTP) in the WCTP Authentication fields.
|
|
(7403)
WCTP Error: Invalid Subscriber ID 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
· Make sure to use the 10 digit phone number of the pager. Do not use dashes, spaces, or parentheses. · If you are certain that you have the correct 10 digit phone number entered (no dashes, spaces, or parentheses) and if you have an Arch or USA Mobility pager, then call your local paging representative and make sure that your pager(s) are setup for "UVB". |
|
(7440) WCTP Error: miscInfo is a required field 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
This
one is a real meaningful error hah? Right now, InfoRad Customers who are
sending text messages to Verizon pagers may get this error, and here’s why…
Customers who want to use Verizon WCTP must go to: http://wctp.myairmail.com/wctpRegistration/jsRegistration.jsp and register on-line for their own username and password. Refer to the screenshots below:
The username and password is then entered in the Messaging Service (Verizon Paging - Internet WCTP) in the WCTP Authentication fields.
|
|
(7602)
WCTP Error: Too Many Messages 7XXX, 7000, 7001, 7002, 7003, 7004, 7005, 7401, 7403, 7440, 7602 |
|
Wait a few moments before sending
another message and try again. Also, try to sending less messages or arrange
to send more messages with your paging company. |
|
When a system error occurs in the NT version of InfoRad Wireless
Enterprise and InfoRad Wireless Watch-IT ASCII/Serial, the service controller
application will display a dialog listing the Windows NT error number and
description of the error. |
System Code 5; System error 997 (2000 & XP):
Access is denied
System codes: X, 5, 53, 1060 |
|
You don’t have administrator rights on
the machine you are attempting to connect to. To use the service controller,
you have to log in to an account that the service machine will recognize as
having administrative rights. If your computers are part of a network domain,
log in as the domain administrator. |
System Code 53: The network path was not
found
|
|
No computer with the name you typed is
visible from your computer. It’s possible that the computer you want to
connect to is turned off or not logged in to the network, or maybe you made a
typo when you typed the name. |
System Code 1060: The specified service does not exist as an installed
service
|
|
The service program is not installed on
the computer you connected to. If you are sure you installed the service
before running the service controller, check to be sure you typed the correct
computer name. |
|
Modems, Phone Lines, Pagers, Winpage.exe, NT/SV Service Issue, Client(s) Could Not Obtain License, Controller Could Not Obtain License File, InfoRad Not Logging, Corrupt Installation Detected, Messages Stay in Waiting, Message Goes But Never Received, TAPI Failed, Must Use 1.4 or Higher, My Serial Number Shows As Question Marks (Ie. 2001-079-????-???????) |
|
Many other errors can occur when trying to send a message using a
Modem or sending via the Internet. InfoRad Tech Support provides you with
many of the common errors as shown below. |
Modem is Not Dialing
|
|
·
Check to see if any other application
is using the modem. ·
Make sure that the phone line is
plugged into the "Line" jack of the modem, and not the
"Phone" jack. ·
To rule out software conflicts, turn
off any fax receive software, communications software, or remote control
software before trying to send a message. ·
Verify your modem selection
· Check for possible device conflicts. |
After dialing, a voice or a ring and a beep is
heard
|
|
|
"Tone Only" or a
blank message, only numbers are sent, or message is garbled or incomplete. |
|
|
|
|
|
|
|
|
|
If the messages from the Client application are sent but remain in the waiting state without an error message, then the Service may be stuck on a particular message. This issue is usually in result of the Phone and Modem Options property not having a default location. Even if there is no modem in the PC and you're not planning on using a modem: Create a default Modem Dialing Properties under your Phone and Modems Options: o Click Start o Click Settings o Click Control Panel o Double Click on Phone and Modem Options o Under the Dialing Rules tab, if there is no default location entered (or "My Location"), Click New o Enter a Location name (Ie. My Location) o In the Area Code box, enter your Area Code o Click OK o Click OK o Click X in the upper right hand corner to close Control Panel |
|
|
|
It’s likely that you need to add Domain Users to the permissions of the Shared folder coming from the Server (or PC that is acting as the Server). |
|
|
|
Click OK and browse into the Service folder (Normally, the Service folder is located under C:\Program Files\InfoRad Enterprise SV Service). Once you’re in the Service folder, just click the Open button. You should now be back at the Controller, the Service Status should be running (or you can Start the Service) and you can finally add Receivers under Edit, Receivers. |
|
|
|
· Log out of the PC and log back in as Administrator · Browse to the InfoRad Wireless folder. For Office, Pro, eText, and AlphaPage First Responder, this directory is normally located under C:\Program Files\InfoRad Wireless · For Enterprise and Enterprise SV Users, browse to the affected Client's local working directory. You can find out where the directory is located by right clicking on the shortcut to the Client (normally on the Desktop), click Properties and take note of the Start In folder/directory. · Go to the Properties of the working folder and select the Permissions tab. Make sure that you add All Users or the Everyone group and allow them Full Control to the folder or at least Write permission in this case. If the users log onto a domain, you'll then have to add Domain Users or some domain group and give them Full Control or Write permission. |
|
|
|
· Log out of the PC and log back in as Administrator · Install the InfoRad software |
|
|
|
· Check the Clients message path and make sure that it is correct. We recommend to use the UNC path ("\\ServerName\Shared InfoRad Folder\MSG\") rather than some mapped drive. This way, the Controller's message directory and all Clients can share the same message path/directory and it is consistent across the board for all. The only thing left to do then would be to make sure that the appropriate permissions are set for all users who need access to the Client. If users log onto a domain, make sure to add Domain Users or some similar domain user/group and allow Full Control permissions to the shared folder. · Another case shows that if there is no Area Code entered under Control Panel's Phone and Modem Options, then the Service may not be sending messages for the Clients. This can occur even if you are not planning on using a dialup modem to send messages. |
|
Message goes away without error, but is never received at device (pager or cell) |
|
· Normally, this problem occurs when messages are sent via Internet email to some cell phone (could also be a pager or regular email address) that uses an email address for the Receiver's ID and there is no ReplyTo Email Address entered under Setup, Internet Settings, ReplyTo Address tab (or Email SMTP tab). Enter a ReplyTo Email Address under Setup, Internet Settings, ReplyTo Address tab (or Email SMTP tab) and click OK. Send another test page to see if the message gets to the device (or email address). If not, then there may be some other underlying issue. Check to make sure the email address is entered correctly, letter for letter. If there is one digit or character incorrect, this may cause the message to not get to the device. The Receiver's ID must be precise! · Another occurrence is that the message was never sent in the first place. Check under List, Logged Messages to verify that the message for that particular Receiver was actually sent. If not, then investigate the following possibilities:
|
|
|
|
Install or update TAPI. This normally comes with the Windows operating system. Installing the latest Windows Service Pack should fix the problem. This is necessary even if you are not planning on use InfoRad software to send text messages using the dialup Modem. |
|
My
Serial Number Shows up as Question Marks (Ie. 2001-079-????-???????) |
|
You may find this information located under the Help menu at the top of the Inforad Wireless software, then select About. The serial number and version is located near the bottom of the window. If you are unable to retrieve your Serial Number as directed - Ie. the serial number shows up as question marks - please try the following steps: · Right Click on the InfoRad Wireless shortcut located on your Desktop · Left Click on Properties · Left Click on the Find Target button · Open Double Left Click the file called INSTALL.LOG It may also be called INSTALL - being a type LOG file · Left Click to Select Edit at the very top of the INSTALL.LOG - Notepad Window · Left Click to Select Select All · Left Click to Select Edit once again · Left Click to Select Copy · Reply To the email sent From InfoRad Tech Support · Right Click, then Left Click on Paste in order to insert the contents of the INSTALL.LOG into the body of the email response To fix this problem, you can reinstall the InfoRad software for “All Users.” You are prompted with the option to install for All Users during the installation. Prior to reinstalling, you may want to backup the information you’ve entered into your InfoRad software by selecting File, Save Program Files, select a location to which you can save this information such as your “My Documents” folder, then Click Save. |
Copyright © 2000 - 2005 InfoRad, Inc.
All Rights Reserved.
Makers of AlphaPage® Wireless Messaging Products since 1985.