Sent not confirmed - move data error.

Issue: Files were sent to DMS and not confirmed.

Resolution: Need to see if the confirmation file can be re-created or if they need to be resent to Galaxy

Types: 4000 is manage, 4001 is teller

Steps:

Determine if the files where imported into DMS.

1. Look through existing log files for files still in the database.
1. This method will work if the files are less than 3 weeks old.
1. Galaxy holds logs for approximately 3 weeks.
2. Log into the DMS SFTP backend and into the CU folder.
3. Make note of the DateSend column in the log folder, or in the database.
4. Navigate to the Logs folder.
5. Log into SQL and expand the database that contains the files that need to be confirmed.
1. For CDPManage
1. Open the CDPManage4 database.
2. Expand the tables
3. Right click on the Document table and View All Rows.
4. Run this query:

Select documentid, datesend, dateconfirm, remoteid

From Document

Where DateSend < ‘DATESEND’ and RemoteID is null

       (NOTE: change ‘DATESEND’ to the actual DateSend +1 from the log)

             Ex. DateSend is 10/10/2013, use 10/11/2013

1. For CDPTeller
1. Open the CDPTeller4 Database
2. Expand the tables
3. Right click on Trans_Head and View All Rows.
4. Run this query:

Select Localid, datesend, dateconfirm, remoteid

From Trans_Head

Where DateSend < ‘DATESEND’ and RemoteID is null

                (NOTE: change ‘DATESEND’ to the actual DateSend +1 from the log)

                Ex. DateSend is 10/10/2013, use 10/11/2013

1. View a few days’ worth of DMS Master logs and look for some of the missing
1. You cannot view the .bak logs, because those are back-ups of logs that we downloaded, that did not contain confirmations.
2. If you can find the documents in the files, download the files to a folder on your computer.
3. Navigate to G:\CUFiles\Utils – CDP
4. Copy MasterLogMuncher.cmd to the same folder you copied the log files to
5. Run MasterLogMuncher.
1. This will re-create an import log for CDPMoveData.
6. Push the created log file to the server’s CDPMoveData\Input folder
7. Launch CDPMoveData
8. Run Confirmation.
9. Re-run the above queries to ensure that all has been confirmed.

1. If you cannot find files in any of the log files, look in the Aborted_Files folder in the DMS SFTP backend.
1. Sometimes, if imports take a long time, they will get moved into the Aborted_Files folder so that other imports can take place.
2. If files are there, the CU will need to contact Galaxy to get the files imported.
1. They can contact Galaxy and let them know that there are files in the “Aborted_Files” folder that need to be moved for import.

1. If the files are nowhere to be found in any of the DMS logs or folders, the files will need to be resent to DMS.
1. Log into SQL and expand the database that contains the files that need to be confirmed.
1. For CDPManage
1. Open the CDPManage4 database.
2. Expand the tables
3. Right click on the Document table and View All Rows.
4. Run this query:

Select documentid datesend, dateconfirm, remoteid

From Document

Where DateSend < ‘DATESEND’ and RemoteID is null

       (NOTE: change ‘DATESEND’ to the actual DateSend +1 from the log)

Ex. DateSend is 10/10/2013, use 10/11/2013

Once you have the result set, run the following query:

Update Document

Set DateSend = NULL

Where DateSend < ‘DATESEND’ and RemoteID is null

1. For CDPTeller
1. Open the CDPTeller4 Database
2. Expand the tables
3. Right click on Trans_Head and View All Rows.
4. Run this query:

Select Localid datesend, dateconfirm, remoteid

From Trans_Head

Where DateSend < ‘DATESEND’ and RemoteID is null

                       (NOTE: change ‘DATESEND’ to the actual DateSend +1 from the log)

Ex. DateSend is 10/10/2013, use 10/11/2013

       Once you have the result set, run the following query:

Update Trans_Head

Set DateSend = NULL

Where DateSend < ‘DATESEND’ and RemoteID is null