Web Integrated Solutions

Transcription

1 1: Receiving Error 4008 Web Integrated Solutions SOLUTION: This is a label extensions error for template files not available. This usually means that the path for the label template files was not provided or an incorrect path to the files was provided. By default, the template files are installed in the labels directory under the API installation directory. 2: Receive the following error when trying to start ATOM: Exception in thread "main" java.lang.noclassdeffounderror: Main/Atom SOLUTION: Incorrect start up command or using start up command for an older version of ATOM. The latest version of ATOM uses the following startup command: Win32: <javapath>/javaw" -Xrs -cp.;.\atom.jar;.\validate.jar;.\jsafeobf.jar;.\sslj.jar;.\certj.jar com.fedex.api.atom Solaris/Linux: <jvmpath>/java -DATOM=1 -mx132m -classpath.:./ Atom.jar:./Validate.jar:./certj.jar:./jsafeObf.jar:./sslj.jar com.fedex.api.atom & Where <jvmpath> is the complete path to the JVM you wish to execute. 3: When trying to view an XML reply with Internet Explorer the following error is returned: Invalid at the top level of the document. Error processing resource file:///a:/ (filename) Line, Position. AFFECTS: WIN32 SOLUTION: This error can occur when the file name contains/includes spaces or symbols. Save the file with a new name that doesn t include any spaces or symbols. 4: Trouble viewing a PNG label with Linux Red Hat 8 Kernal AFFECTS: LINUX SOLUTION: Some home-brewed CTS Tag parsing algorithms cause embedded commas in a tag s value to be thrown away. The comma character (0x2c) can not be omitted from the PNG file. FSMAPI FAQ v1.0 06/15/04 Page 1 of 6

2 5: Receiving Error 2202 Using an invalid IP Address or port for the ATOM you are trying to connect with, or the ATOM you are trying to connect with is not running. SOLUTION: Verify the IP address of the server where ATOM is installed, then check to see if ATOM is running. For Win32, use the AtomView utility from the Start->Programs menu, select Settings-> Comm/System, click the update button (The default password is ATOM). An error dialog indicates ATOM is not running. For Solaris/Linux, use the Aatom utility in the Atom directory under the API installation directory. The command Aatom status will return the current status for ATOM. 6: When trying to generate a SignatureProofOfDelivery png label the following error occurs: Object handle is out of date. SOLUTION: Verify that the spodpng.html template exists in the labels directory and that permissions are set appropriately for the application to access the label and template directory. 7: Time out errors connecting to gateway.fedex.com SOLUTION: In the ATOM config.ini file the server= line should be pointed to a DNS name configuration rather than pointing to a specific ip address. See also FAQ : Receive the following error when printing a label, Java Runtime Exception System.LoadLibrary(LBLEXTS)Failed. AFFECTS: SOLARIS/LINUX, WIN32 SOLUTION: The Jlblexts.jar file uses JNI to access the C library lblexts.dll or liblblexts.so. For WIN32: The lblexts.dll file must be located in a directory defined in the system PATH variable. For Solaris/Linux: JNI libraries must be in the path defined by the Java property "java.library.path" to be loaded with the System.loadLibrary("libname") method. To extend the java.library.path, define the environment variable DYLD_LIBRARY_PATH with the additional directories, and the FedEx Ship Manager API shared libraries (.so files) should be copied into that directory. You can override the java.library.path in the Java 2 SDK from the command line. For example, the following command starts up a program Foo which needs to load a native library in the c:\mylibs directory: java -Djava.library.path=c:\mylibs Foo FSMAPI FAQ v1.0 06/15/04 Page 2 of 6

3 9: Atom stops communicating for unknown reason, but is still running. Re-starting Atom clears the problem. SOLUTION: This could be due to: Inet IP Address Caching in the JVM (Sun bug tracking # ). Occasionally, one or more of the physical IP's behind the FSMAPI Gateway goes down or is taken out of service. When that happens a situation occurs where some number of customers will now be unable to communicate with the gateway. The JVM, for performance purposes, caches the DNS resolved IP internally and by default maintains it for the duration of the instance of the JVM. In ATOM's case, as long as ATOM continues to run it never again tries another DNS lookup, even though a connection failure might be reported. Re-starting the JVM (ATOM) clears the problem. The InetAddress class has a cache to store successful as well as unsuccessful host name resolutions. The positive caching is there to guard against DNS spoofing attacks; while the negative caching is used to improve performance. By default, the result of positive host name resolutions are cached forever, because there is no general rule to decide when it is safe to remove cache entries. The result of unsuccessful host name resolution is cached for a very short period of time (10 seconds) to improve performance. Under certain circumstances where it can be determined that DNS spoofing attacks are not possible, a Java security property can be set to a different Time-to-live (TTL) value for positive caching. Likewise, a system admin can configure a different negative caching TTL value when needed. A Java security property controls the TTL value used for successful host name resolution caching: networkaddress.cache.ttl (default: -1) Indicates the caching policy for successful name lookups from the name service. The value is specified as as integer to indicate the number of seconds to cache the successful lookup. A value of -1 indicates "cache forever". Since: JDK1.0 Apparently this value did not function properly prior to JDK1.4 Set this value to a positive integer in the java_home_directory>/lib/security/java.security file. (java.home indicates the directory into which the JRE was installed.) This will cause ATOM to refresh the FSMAPI Gateway address within the specified interval. 10: I am unable to stop ATOM from the Control Panel->Services (Win32) or via the Aatom script (Solaris/Linux). How else can I stop ATOM? FSMAPI FAQ v1.0 06/15/04 Page 3 of 6

4 SOLUTION: 1. open a telnet session to on port 8189 telnet type in the following: 0,"77"1040,"ATOM"99,"" 3. press return, the reply should be: 0,"177"99,"" if you get a "invalid password" reply, look in the pw.fil file and use that password in place of the ATOM string in the trans above. 4. when you disconnect the telnet session ATOM will shutdown. 11: When using the FSMAPI with my VB, ASP, or C++ COM application, I sometimes get a return error code from the FSMAPI that I cannot find in the error listing. The error is a large negative number, example SOLUTION: This is a Windows COM object error code. The large negative number returned from a COM call to the API is a raw HRESULT error code. A raw HRESULT is usually a 10 digit number. This is the expected return code from a COM object thrown by an exception within the object. Some coding on the part of the customer is necessary to convert this HRESULT to the error return code listed in the API error code list. Here's how to do it with a scientific calculator: 1. Enter the number as a negative decimal number. 2. Convert to hex. 3. Take the 4 rightmost digits of that result and re-enter them as a hex number 4. Convert to decimal to get the converted error code. The code to do this is in each of the FSMAPI COM examples. 12: ATOM stops for unknown reason. AFFECTS: WINNT, WIN2K, XP The issue could be that the JVM will stop functioning if a customer logs off their operating system and then logs back on later. The JVM stops when they log off, but does not re-start when they log back on. Currently customers will have to either re-start ATOM manually, or restart the operating system. This is due to the following: FSMAPI FAQ v1.0 06/15/04 Page 4 of 6

5 The Java virtual machine shuts down in response to two kinds of events: * The program exits normally, when the last non-daemon thread exits or when the exit (equivalently, System.exit) method is invoked, or * The virtual machine is terminated in response to a user interrupt, such as typing ^C, or a system-wide event, such as user logoff or system shutdown. SOLUTION: FSMAPI contains this fix. Download the latest FSMAPI, or previous versions can be fixed as follows. 1. Change the windows registry as follows: HKEY_LOCAL_MACHINE\SOFTWARE\FedEx\Atom\JavaOptions Add a -Xrs at the start of the value (before the -cp statement). 2. Restart the API service. This effects all flavors of WIN32 that support services: NT, 2K, and XP, running SUN JVM 1.3.x and above (the later versions of the API). The work around appears to resolve the problem without causing any noticeable side effects. 95, 98, ME, Unix & Linux are not effected. 13: Unable to upgrade to latest version of Java with atom installed. AFFECTS: WIN32 SOLUTION: When FSMAPI is installed it configures itself for whatever version of Java is present at that time. When you upgrade to a different version of Java, FSMAPI is still configured to use the path of the older java version. Either uninstall and then reinstall FSMAPI, or change the configuration in the registry manually as follows: 1. Stop the FedExAPIService. 2. Edit the registry key HKEY_LOCAL_MACHINE\SOFTWARE\FedEx\Atom\JavaDir 3. Change the key value to the path for the new installation of Java. 4. Restart the FedExAPIService 14: Error compiling C sample code using Sun Solaris 2.6 SOLUTION: In Order to compile the follow must be available and properly configured. 1. The appropriate C++ library must be on the system (ie..libstdc++.a ) for the API code to access. 2. The library must be included in the Unix User (Path/Environment) with appropriate priviledges. 3. Verify extracted API makefile exists and is correctly used. (installed location, priviledges, pathing, environment, and proper naming) so that necessary resources are available at the time of compile. FSMAPI FAQ v1.0 06/15/04 Page 5 of 6

6 15: Error 4027 Specified Windows printer name not found in Printers folder. (Unable to generate a label using the lblexts.dll.) AFFECTS: WIN32 SOLUTION: This inability to print to a named printer attached to another computer on the network is a known issue acknowledged by Microsoft. Therefore the printer must be attached to the local machine. FSMAPI FAQ v1.0 06/15/04 Page 6 of 6