![]() |
![]() |
|
|
|
| 1 |
What is the purpose of this site? This site is for the secure exchange of CAD and Engineering related data with Visteon worldwide. |
| 2 |
How do I register for access? Visit the web site http://datax.visteon.com and fill out the Registration Form. Your request will be reviewed and you will receive an e-mail message containing your user ID and password when your access has been configured. |
| 3 |
How long does it take to get registered? Registrations are generally processed the same day they are received. After you receive your ID and password via e-mail, you can begin exchanging files. If you require immediate assistance, you can call the Visteon help desk at 734-710-5555 (Route to DATAX). |
| 4 |
How much does it cost? There is no charge for the use of this site. You are responsible for your own Internet/Network connection costs from your ISP. |
| 5 |
What software is required for access? An SSL capable web browser is required. Most recent versions will work. Development is done using the latest versions of Internet Explorer, Firefox and Google Chrome. DataX is Currently Certified up to the Following Web Browser Versions: Internet Explorer: Version 10.0.12 Firefox: Version 26.0 Google Chrome: Version 31.0.1650.63 m You may also need Adobe Acrobat Reader to view some of the (PDF format) Engineering Specifications and information on the system. And you may also want a free JT File Viewer like JT2Go. |
| 6 |
How secure is this site? Access is restricted to http/https. Once you enter the site, you will be using SSL (Secure Socket Layer). An encryption method is established with a unique session key and secure transmission begins. True 256-bit SSL Certificates enable every site visitor to experience the strongest SSL encryption available. How Secure Sockets Layer (SSL) Works. |
| 7 |
I can't log in. What's wrong? It could be several things. User ID and password are case sensitive. Check your caps lock key too. If you still can't get logged in, contact the Visteon Help Desk at 734-710-5555 (Route to DATAX) and they can assist you in resolving the problem. |
| 8 | When I pick "Business Partners Enter Here" all I get is an hourglass and a timeout. Something is preventing you from doing SSL (Secure Socket Layer). It can be that your browser is not SSL capable; or that SSL is turned off on it. More likely, you are going through a proxy server or firewall that is not allowing port 443 (the port SSL uses) to pass through. You usually need to contact your internal systems support people. |
| 9 | How long do files remain on the system? Files remain on the system for at least 10 days. Disk space permitting, they remain longer. |
| 10 | I'm having trouble printing my receipt page. Check your cache settings. If you are not caching the receipt page, you may have trouble printing it. In Netscape, go to Edit -> Preferences -> Advanced -> Cache. Set the disk cache (8192 kbytes is good), the memory cache (1024 kbytes is good), the cache folder (generally your .netscape/cache folder) and make sure you compare the document to the cache at least once per session. You may need to restart (close completely and reopen) your browser for these settings to take effect. |
| 11 | I'm having trouble uploading large files. There can be several causes for this. The more common causes: A) You are low on temporary disk space. Because of the way browsers work, they require "temporary" space to convert the binary file that you want to upload into something more "web friendly". This can require up to 3 times the original file size to be available free in your temporary area. (i.e. sending a 250MB file can require 750MB of free space). The cure, if you're low on space, is to either clean house or buy a bigger house. Unix users can check the /tmp partition with the command "df -k /tmp". Windows users can display drive properties under "My Computer>C Drive" B) Browser temporary files are overloaded For a good cure, nothing works better than deleting "Temporary Internet Files". This temporary directory should be cleaned out regularly and always if you're experiencing any possible browser issue. Also see Q.10 on printing receipt pages. On Internet Explorer, you can find it under "Tools>Internet Options>General". In Netscape, "Edit>Preferences>Advanced>Cache" and clear both disk and memory cache. C) Networking (data source not the local system) If you are having troubles and the source for the data is not the local system (e.g. it is on a network/shared drive) try copying it to the local system first before sending. We have seen local network issues cause transfer problems. D) Power Saving or Timeout. If you are having an issue where transfers stop after a certain length of time (consistently) you might want to check if one of your system devices may be either timing out, or going to "sleep". This is more an issue with PCs than unix hardware. Frequently, power saving and timeout settings, particularly on network devices (modems, Ethernet cards) and disk drives can interrupt transfers. Screen savers can also interrupt things. Unfortunately, some of these settings are not readily obvious to the casual user (e.g. certain S-Register settings on modems can cause this problem). If you suspect this type of issue, you probably want to bring in local PC support. E) Check the connection, firewall or ISP. This is the difficult part. All internet web connections can time out - which is the usual reason why file uploads fail. You should understand how long a transmission should take, the type and quality of your internet connection, and the probability that the transfer will actually complete. Dial-up analog connections are the most troublesome. 56k dial-up modems, even under good conditions can be problematic. They also pose problems in tracing, since their IP address is usually dynamic. In general, you can expect 5-7 minutes per 1MB of data. This translates to a 10MB file taking over an hour to transfer. If you're located outside the US, holding a continuous connection for over an hour without timing out can be difficult. If you will regularly transfer files that take that much time, the best option would be to move to a better type of internet connection. The next step up would be some type of digital dial-up. This would usually be ISDN, typically 56k or 64k. You can still expect times of 4-6 minutes per 1MB of data, but the higher quality dial-up reduces line problems. If you have a direct (always on) high speed connection to the internet, then the quality of the line should not be the first place to check. Ask your local support about proxies and firewalls. Often they can check logs and look for and strange network events ("Connection reset by peer" is the typical suspicious error message - its computer speak for timeout). As a last resort (ISPs can be reluctant to do a deep technical dive), have your ISP monitor your connection for issues. Most of the time they can turn on (by request) monitoring the same way firewalls and proxies can monitor. |
| 12 | Is there a file size limit? For most people the effective answer is no. But before sending any large file, make sure you read question 11. The technical answer is that DataX does not support unix "large" files, which means it does not support the upload of a single file that is 2GB and over in size. Large files should always be compressed to reduce their size before uploading to DataX. 7-Zip is a good Open Source software solution for file compression and is now included in the Visteon standard software load. If the file is still over 2GB in size after compression then it will need to be spilt into smaller files before uploading to DataX. We recommend that the split-up files be less then 1GB in size and under 500MB when the sending or receiving sites have slow network connections. 7-Zip and GSplit are both good Open Source software solutions for file splitting and GSplit can optionally create a self uniting executable. A text file containing instructions for reuniting the files should be included with each set of uploaded files. |
| 13 | Google Chrome reports the following error: "Duplicate headers received from server" The response from the server contained duplicate headers. This problem is generally the result of a misconfigured website or proxy. Only the website or proxy administrator can fix this issue. Error 349 (net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION): Multiple distinct Content-Disposition headers received. This is disallowed to protect against HTTP response splitting attacks. This Error Occurs when the file you are trying to download has a comma (,) in it's Name Solution: Use Internet Explorer (IE) or Firefox to download the file. Prevention: Do Not Upload Files Into DataX With Commas (,) In Their Names. |
| Home | Registration Form | Password Reset |
|
|
|
|
![]() |
![]() |