To fix this problem, try these steps:

• If you did not restart your computer after installing DaFIS, reboot your computer now. Once the computer has re-started, try launching DaFIS again to see if you are still getting the error message.

• Rename C:\Oracle\ora81\bin\tnsping.exe to 'savetnsping.exe'. DaFIS TP uses TNSPING for a quick, simple test to see if your computer can locate the DaFIS TP database. If tnsping.exe isn't there, the test is skipped.

  Occasionally, a computer may have trouble running tnsping.exe, but no trouble running the actual DaFIS TP forms and queries. When you rename tnsping.exe, you allow DaFIS TP to skip the test and go straight to the DaFIS TP forms and queries.

  The disadvantage to this tactic is that if the production database is down, you will get an invalid usercode message at login instead of a "could not connect to the database" message.

• Most of the time if you get an error message with TNSPING and then rename tnsping.exe, you'll just move the failure point to the login phase (i.e., you'll still get an invalid page fault, illegal operation or access violation error message, but it will occur at the login). In this case, the solution is to uninstall and reinstall DaFIS TP. For more information, refer to the 'How can I uninstall DaFIS' FAQ on this page.

• If none of these suggestions help, please contact the DaFIS Help Desk.

If you can login on another machine, go back to the problem computer. Check the Caps Lock and Num Lock to make sure they are properly set.

If you know you have the correct login/password but cannot login, there may be a problem with the Oracle Net8 Client installation. In that case, the solution is to do a complete uninstall and reinstall of the Oracle Net8 Client. For more information, refer to the 'How can I uninstall' FAQ on this page.

If you are reluctant to do an uninstall/reinstall, here are a couple of other things to try first.

• Try a login to the Test database. If you can login to the Test database, you can be confident that the Net8 Client is working and the problem lies somewhere else.

  For instructions of how to login to the Test database, refer to the 'How can I test DaFIS TP' FAQ on this page.

• Copy in a fresh copy of the SQLNET.ORA file. The SQLNET.ORA file is used to locate the DaFIS database.

  Copy the SQLNET.ORA file from:
  Q:\DaFIS\Special\sqlnet.ora
  to
  C:\Oracle\ora81\network\admin
  C:\Oracle\ora81\network\admin\sample

  Note: If the Net8 Client is installed on a drive other than C:, copy the SQLNET.ORA file to that drive instead.

If the error continues, contact the DaFIS Help Desk with as many details as possible about the installation problem you are experiencing.

There are times when the Oracle Universal Installer is not sufficient for uninstall needs. For example, it may not recognize all of the installed components, it may not be able to uninstall old versions of Oracle components or it may crash when you try to run it. In these situations, the expert uninstall method is the only alternative.

Please use the following links for complete instructions.

• How to Uninstall DaFIS TP - Safe Method
• How to Uninstall DaFIS TP - Expert Method
• How to Reinstall DaFIS TP
• More Information About DaFIS TP Uninstall

DSL or Other High-Speed Connection

If your computer is located outside the ucdavis.edu network and you want to use the AFS Client method to map the Q: drive, you can request that your IP address be added to the authorized DaFIS access list, provided you have a static IP address, and the IP address is not to a home (policy prohibits home offices from being added to the IP allow list). To request this service, contact the I.E.T. AFS service team at afs-setup@ucdavis.edu; be sure to provide your static IP address.

Otherwise, you may be able to use the AFS proxy server method to map the Q: drive (the proxy server connection method is not subject to the same restrictions). However, many ISPs block the type of network traffic that the AFS proxy server method uses. If your ISP blocks that type of traffic, the proxy server mapping will not work.

Modem Connection

If you are connecting to DaFIS TP via a Citrix server, the authorization is based on the Citrix server's IP address. As long as the Citrix server can connect with DaFIS TP, you will be able to connect.

If you are dialing into one of the campus modem pools, you will automatically have the ability to run DaFIS Transaction Processing through this connection. Be aware that DaFIS TP will run extremely slowly over a modem. Note: You will not be able to install the DaFIS TP software over this modem connection because you will be timed out before the installation is complete.

You can use a test login to the Test database. This will exercise all of the DaFIS TP software that is used with the actual Production database. Of course, you cannot do real work in the Test database, it is only for testing.

To test the DaFIS TP install:

1. Select Start->Run

2. In the Open field, enter Q:\DaFIS\Test\util\dafis.exe

3. If you are prompted to do a SQLNET.ORA Update, in most cases you should click the Update button. Possible exceptions: If you use other Oracle databases, you may have a customized SQLNET.ORA file, in that case you may not want to click the Update button.

4. When you get to the login screen, enter these values (all upper case):

   User ID:		TEST
   Password:		TEST

   Click the OK button to login.

5. You should see the Welcome to the FIS menu screen. That means the login test was successful. Click Exit the FIS button.

To recover try these steps, in order:

• Patience: The installer can take as long as an hour to complete. The progress bar moves in increments of 10%. It may take 15 - 20 minutes before the progress bar moves at all. If the progress bar hasn't moved for an hour, you can be pretty sure that it has stalled and will not recover.
• If your patience has been exhausted, terminate the installer and restart the computer. Do a quick login test with DaFIS TP. Maybe the installer display got stuck, but the install progressed anyway.
• Try to run the installer again. In some cases, it will pick up where it left off and then complete normally. If one re-run of the installer doesn't do the trick, go on to the next step.
• Do a complete uninstall of the partially completed install. For uninstall instructions, refer to the 'How do I uninstall' FAQ on this page. After you do the uninstall, you can re-run the automated installer. As an alternative, you may want to try the manual install method. There are more steps to the manual install method, but you get more feedback along the way.

If you already have the AFS Client installed on your computer, check to make sure your Q drive is mapped according to the AFS Client instructions. We've had several people call that had the software installed, but their Q drive was still mapped to \\proxy-afs\desktop.

If you are working on a Macintosh, please contact the DaFIS Help Desk so that we can help you troubleshoot the problem. We haven't had any reports of extreme slowness on these machines, so we would need to investigate it further.

1. Click once on the DaFIS icon on your computer's desktop with your right mouse button and select "Create Shortcut" from the menu.
2. Rename your new DaFIS shortcut icon to "DaFIS Training".
3. Right-click on the new DaFIS Training icon and select "Properties" from the menu.
4. Select the "Shortcut" tab at the top of the properties screen.
5. Change the Target to Q:\DaFIS\Training\.....
6. Click OK to save your changes.

1. Run the DaFIS Installer following the regular instructions.
2. When you get to the screen that says "Select Items to Install" be sure to check the box next to DaFIS Training.
3. If you do not wish to install DaFIS Production on your computer, uncheck that box.
4. Follow the instructions to complete the installation.

The date of the file you copy should be at least 8/14/98.

The best way to see if the missing file is on your PC is to:

Click:

--->Start
--->Find
--->Files or Folders...

Then in the Named: box type in the name of the missing dll file, be sure to search all local hard drives and to include subfolders.

If you find it, then copy it to the directory specified in the error message.

If it is not on your PC, you will need to copy it from another PC using the same procedures. Be sure the computer you copy from has the same operating system. If you are unable to get a copy of the file, contact the DaFIS Help Desk to get a copy e-mailed to you.

AFS Servers - AFS Client
afs1.ucdavis.edu
afs2.ucdavis.edu
afs3.ucdavis.edu
afs4.ucdavis.edu

afsadmin4.ucdavis.edu
afsadmin5.ucdavis.edu
afsadmin6.ucdavis.edu
afsadmin7.ucdavis.edu
afsadmin8.ucdavis.edu
afsadmin9.ucdavis.edu

AFS Servers - AFS Proxy
proxy-afs.ucdavis.edu 169.237.105.130
mantis.ucdavis.edu 169.237.105.131
sydney.ucdavis.edu 169.237.105.132
sarajevo.ucdavis.edu 169.237.105.133

Database Servers
fis-tp.ucdavis.edu
fis-test.ucdavis.edu

Oracle Name Resolution
oranames1.ucdavis.edu
oranames2.ucdavis.edu

Uniface License Monitor
unfclic1.ucdavis.edu
unfclic2.ucdavis.edu
unfclic3.ucdavis.edu

Connection Timeout Values
Set a 30-minute timeout for the AFS Servers-AFS Client rules.

Set a 600-minute timeout value for the Database Servers rules.

If your firewall has an option to close idle TCP connections, this will affect DaFIS TP. DaFIS TP (actually the Net8 client) uses a single TCP connection (aka data stream) throughout the TP login. The TCP stream will be idle when the TP session is not in use.

Example: You have a one hour timeout on TCP sessions in your firewall. A client has DaFIS TP running, locks the workstation and goes to lunch. Upon return unlocks the workstation and starts using DaFIS TP again. The client enters a new DPO and then clicks OK. DaFIS TP gives an error messages that the DPO could not be saved: The save did not work because the Net8 TCP session was closed by the firewall.

Port Details
For finer control, add the ports listed below to your firewall rulesets. All connections intiated from the client side.

Type	Host	Port	Purpose
AFS Servers- AFS Client	afs1.ucdavis.edu afs2.ucdavis.edu afs3.ucdavis.edu afs4.ucdavis.edu afsadmin4.ucdavis.edu afsadmin5.ucdavis.edu afsadmin6.ucdavis.edu afsadmin7.ucdavis.edu	UDP 7001 - client port UDP 7000, 7003 - server port	Q: drive access - direct
AFS Servers- AFS Proxy	proxy-afs.ucdavis.edu mantis.ucdavis.edu sydney.ucdavis.edu sarajevo.ucdavis.edu	TCP 139 TCP 445	Q: drive access - via AFS proxy
Database Servers	fis-tp.ucdavis.edu fis-test.ucdavis.edu	TCP 1521	database access
Oracle Name Resolution	oranames1.ucdavis.edu oranames2.ucdavis.edu	TCP 1522 TCP 389 TCP 636	database host lookup
Uniface License Monitor	unfclic1.ucdavis.edu unfclic2.ucdavis.edu unfclic3.ucdavis.edu	TCP 7188 TCP 32774 and up	license compliance