Difference between revisions of "Corrupted Install Repair"
(New page: {{Template:MainTOC}} This guide is for reseting and repairing a corrupted installation that cannot be repaired by other means. You will not loose any data if you follow the procedure bel...) |
(→Upgrade to The Latest Version) |
||
(23 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{Template:MainTOC}} | {{Template:MainTOC}} | ||
− | This guide is for reseting and repairing a corrupted installation that cannot be repaired by other means. | + | This guide is for reseting and repairing a corrupted installation that cannot be repaired by other means. Warning: you may lose some data. |
==Preparation== | ==Preparation== | ||
− | # Batch out all outstanding transaction, if you can. | + | # '''Batch out all outstanding transaction, if you can.''' |
− | # If you cannot, attempt to [[CreditLine_Import/Export#Export|Export]] and/or print the batch report for the outstanding transactions | + | # If you cannot, attempt to [[CreditLine_Import/Export#Export|Export]] and/or print the batch report for the outstanding transactions. Later you can delete the journal and [[CreditLine_Import/Export#Import|Import]] the transactions. |
# Select all drives to be checked for errors and to automatically fix them. | # Select all drives to be checked for errors and to automatically fix them. | ||
# Restart the computer | # Restart the computer | ||
# Check the machine for viruses. You can use a free service such as [http://housecall.trendmicro.com Housecall Virus Scan]. | # Check the machine for viruses. You can use a free service such as [http://housecall.trendmicro.com Housecall Virus Scan]. | ||
− | # | + | # '''Stop all CreditLine applications (Manager and Server), including [[CreditLine Service]] (if installed) |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
+ | ===Stopping CreditLine Applications=== | ||
+ | {{Stop CreditLine}} | ||
+ | ===Backup=== | ||
+ | Backup the entire '''911''' directory to a safe location. | ||
+ | ==Basic Repair== | ||
+ | ===Upgrade to The Latest Version=== | ||
+ | → Try to batch out all outstanding transactions before upgrading. Upgrading a version with unbatched transactions may lead to journal corruption. | ||
+ | |||
+ | Run the the latest version installation on top of the existing install. You will not lose any data (but see the warning above). '''If this fails to resolve the issue''', continue with the steps below. | ||
+ | |||
+ | ===Clean Up=== | ||
+ | If you have successfully batched everything, remove '''ccv_jor.dat''' files from the '''911/data''' directory to clean up the journals (all unbatched data in those journals will be deleted). Sometimes there are corrupted transactions hanging around the journal. | ||
+ | |||
+ | ==Advanced Repair== | ||
+ | ===Uninstall=== | ||
+ | # Uninstall the software through the control panel (if installed this way) | ||
+ | # Delete the entire '''911''' directory. If any files are locked by the operating system or a CreditLine application is active, it will prevent the deletion of the directory. | ||
− | + | ===Restoration And Repair=== | |
− | == | + | # [[CreditLine_Download|Download]] and Install the latest version of the software. |
− | + | # From the backed up '''911''' directory copy and overwrite the following in the corresponding new folders: | |
− | # | + | ## From '''911/data''' folder, '''911_ccv.ini'''. |
− | # | + | ## From '''911/data''' folder, the following files: ccv_info.dat, ccv_jor.dat, ccv_log.dat; and for multiple merchant installs: ccv_info?.dat, ccv_jor?.dat, ccv_log?.dat (where '''?''' is any number, back up everything that fits that pattern) |
+ | ## From '''911''' folder, the following directories: JOR, LOG; and for multiple merchant installs: JOR?, LOG? (where '''?''' is any number, back up everything that fits that pattern) | ||
− | |||
− | + | ===Final Clean Up=== | |
+ | After everything is batched out '''completely'', it is recommended to remove ccv_jor.dat files since they may contain residiual corruption. | ||
− | |||
− | + | =Appendix A= | |
+ | The following info may help you with the repair. | ||
{{Template:CreditLine Directory Structure}} | {{Template:CreditLine Directory Structure}} |
Latest revision as of 19:20, 4 August 2008
This article is part of the Payment Processing Software Library |
|
Get it... | |
Install it... | |
Connect to it... | |
Set it up... | |
Learn to use it... | |
→ Manual & User Guide | |
Fix it... | |
→ Errors & Troubleshooting | |
Get Help... | |
More Info ... | |
See also... | |
This guide is for reseting and repairing a corrupted installation that cannot be repaired by other means. Warning: you may lose some data.
Contents
Preparation
- Batch out all outstanding transaction, if you can.
- If you cannot, attempt to Export and/or print the batch report for the outstanding transactions. Later you can delete the journal and Import the transactions.
- Select all drives to be checked for errors and to automatically fix them.
- Restart the computer
- Check the machine for viruses. You can use a free service such as Housecall Virus Scan.
- Stop all CreditLine applications (Manager and Server), including CreditLine Service (if installed)
Stopping CreditLine Applications
- If the CreditLine Service is installed, verify the Services list in Windows Advanced Computer Management Console
If you are running CreditLine Credit Card Software Service and are upgrading remotely, you can use the following commands to stop and start the service:
sc \\hostname stop CreditServer sc \\hostname start CreditServer
- Search the Task Manager for CreditLine Server and Manager and end the process. Make sure to click Image Name to sort by name
Backup
Backup the entire 911 directory to a safe location.
Basic Repair
Upgrade to The Latest Version
→ Try to batch out all outstanding transactions before upgrading. Upgrading a version with unbatched transactions may lead to journal corruption.
Run the the latest version installation on top of the existing install. You will not lose any data (but see the warning above). If this fails to resolve the issue, continue with the steps below.
Clean Up
If you have successfully batched everything, remove ccv_jor.dat files from the 911/data directory to clean up the journals (all unbatched data in those journals will be deleted). Sometimes there are corrupted transactions hanging around the journal.
Advanced Repair
Uninstall
- Uninstall the software through the control panel (if installed this way)
- Delete the entire 911 directory. If any files are locked by the operating system or a CreditLine application is active, it will prevent the deletion of the directory.
Restoration And Repair
- Download and Install the latest version of the software.
- From the backed up 911 directory copy and overwrite the following in the corresponding new folders:
- From 911/data folder, 911_ccv.ini.
- From 911/data folder, the following files: ccv_info.dat, ccv_jor.dat, ccv_log.dat; and for multiple merchant installs: ccv_info?.dat, ccv_jor?.dat, ccv_log?.dat (where ? is any number, back up everything that fits that pattern)
- From 911 folder, the following directories: JOR, LOG; and for multiple merchant installs: JOR?, LOG? (where ? is any number, back up everything that fits that pattern)
Final Clean Up
After everything is batched out 'completely, it is recommended to remove ccv_jor.dat files since they may contain residiual corruption.
Appendix A
The following info may help you with the repair.
Directory Structure
NOTE: in version 3.01.07 and older the software ALWAYS looks for \911\bin from the root of the drive regardless of the installation path or working directory set. The working directory only points out the root drive.
Directory Name | Contains |
---|---|
C:\911\BIN | Executables |
C:\911\DATA | Data |
C:\911\JOR | Historical Journal, automaticly created. For multiple merchant setups it is JOR? where ? is the merchant index. |
C:\911\LOG | Historical Log, automaticly created. For multiple merchant setups it is LOG? where ? is the merchant index. |
C:\911\MESSAGES | Text-Based Communication Files |
Important Files
Encryption Keys
The following two files must always accompany the #Transaction Journal: 911\data\DataEncryptingKey.ini and \911\data\KeyEncryptingKey.ini
Transaction Journal
The journal of all transactions is under the 911\data directory in ccv_jor.dat (or ccv_jor?.dat where ? is merchant index if you are using a multiple merchant setup. Make sure that the encryption keys 911\data\DataEncryptingKey.ini and \911\data\KeyEncryptingKey.ini always follow any moves of the data to and from the system or permanent corruption of the Transaction Journal File may result.
→Deleting this file will remove all unbatched transactions.
Setup
The merchant and other setup is under the 911\data directory in ccv_info.dat file(or ccv_info?.dat where ? is merchant index if you are using a multiple merchant setup.
BIN Ranges
The card number BIN ranges are the starting 6 digits of the card numbers that help us to identify the card types. \911\data\ccv_range.ini contains the defined BIN ranges for the setup
Terminal Registration File
The following file is used to register Terminals/Lanes manually, when required by processor compliance (e.g. Elavon 5/3rd Bank): 911\data\POSREGISTRATION.ini
Log
- Server Activity Log
- The log is stored under the 911\data directory in ccv_log.dat file (or ccv_log?.dat where ? is merchant index if you are using a multiple merchant setup. The log can be viewed in CreditLine Manager by using CreditLine View Log Dialog. Older logs can be viewed by using the CreditLine Log Archive List Dialog.
- Error Statistic File
- The error statistic file can be used for reliability testing and is stored under the 911\data directory in ccv_error.csv. The header for the file describes the fields, separated by '|', e.g. "DATE|TIME|MERCHANT NAME|ERROR DESCRIPTION|ERROR TYPE|TRANS TYPE|PROCESSOR NAME|COMM TYPE|COMM PARAMETER"
Advanced Configuration
The advanced configuration is under the 911\data directory in 911_ccv.ini. See CreditLine Advanced Setup for more info.
Connection Configuration
The connection settings for various processors and modems is under the 911\data directory in ccv_link.ini.
Important File Summary
File Name | Function |
---|---|
C:\911\BIN\CCV_MANAGER.EXE | Manager Program |
C:\911\BIN\CCV_SERVER.EXE | Server Program |
C:\911\DATA\CCV_INFO.DAT | Site Configuration - this file contains all the merchant specific information → multiple merchant setups use multiple files of format C:\911\DATA\CCV_INFO?.DAT where ? is the merchant index. |
C:\911\DATA\CCV_JOR.DAT | Current Day Journal - deleting this file will remove all authorized transactions → multiple merchant setups use multiple files of format C:\911\DATA\CCV_JOR?.DAT where ? is the merchant index. |
C:\911\DATA\CCV_LOG.TXT | Current Day Log |
C:\911\DATA\911_CCV.INI | Program Configuration |
C:\911\DATA\CCV_LINK.INI | Connection Configuration |
Backups
Batches (Journals)
You can view and manipulate the Journal Backups in the CreditLine Batch Archive Dialog
→In some extreme cases the transactions that you are looking for can only be found by clicking the Radio Buttons "Before Batch" and "Daily Backup" in the CreditLine Batch Archive Dialog
The number of days that the journals are backed up is specified in CreditLine Business Configuration Dialog. To restore the journal/batch you can rename the desired journal backup file to ccv_jor.dat and move it to 911\DATA directory. Don't forget to reload the configuration to apply the changes.
→ For multiple merchant setups replace JOR below with JOR? where ? is the merchant index.
File Name | Function |
---|---|
C:\911\JOR\b<time_stamp>.?? | "BEFORE" BACKUP. Backup of the journal before the batch was run |
C:\911\JOR\j<time_stamp>.?? | "BATCH" BACKUP. Backup of the journal that was batched |
C:\911\JOR\d<time_stamp>.?? | "DAY" BACKUP. Incremental Backup of the journal for a business day appended at the time of the batch |
C:\911\JOR\u<time_stamp>.?? | "UN-BATCHED" BACKUP. Backup of un-batched transactions that were carried over to the next batch (for instance un-finalized Auths) |
Logs
You can view the Log Backups in the CreditLine Log Archive List Dialog
The number of days that the logs are backed up is specified in CreditLine Business Configuration Dialog.
→ For multiple merchant setups replace LOG below with LOG? where ? is the merchant index.
File Name | Function |
---|---|
C:\911\LOG\l<time_stamp>.?? | Backup of the logs |
Setup Files
To restore the setup file you can rename the desired setup backup file to ccv_info.dat and move it to 911\DATA directory. Don't forget to reload the configuration to apply the changes.
→ For multiple merchant setups replace JOR below with JOR? where ? is the merchant index.
File Name | Function |
---|---|
C:\911\JOR\n<time_stamp>.?? | Backup of CreditLine Setup File - generated after every batch |
C:\911\JOR\i<time_stamp>.?? | Backup of CreditLine Setup File - generated before every batch |
Encryption Keys
The encryption keys are backed up in the 911\Backup directory.
There are two keys: DataEncryptingKey.ini (backup file starting with d), KeyEncryptingKey.ini (backup file starting with k)
To restore the keys:
- Batch out any outstanding accessible transactions
- Backup current DataEncryptingKey.ini and KeyEncryptingKey.ini in 911\Data directory, by renaming them to DataEncryptingKey.ini.bad and KeyEncryptingKey.ini.bad
- Enter 911\Backup directory and sort by Date Modified';
- Pick the desired pair of keys, copy them to 911\Data directory and rename to DataEncryptingKey.ini and KeyEncryptingKey.ini respectively.
- Restart the CreditLine server/service and CreditLine Manager
- Attempt to view the journal
- If unsuccessful, try the next pair in the list.