CDR Tickets

Issue Number 4230
Summary Problem with CDR Loader Files when Switching Tiers
Created 2017-02-10 18:54:57
Issue Type Bug
Submitted By Juthe, Robin (NIH/NCI) [E]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2017-03-01 09:50:45
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.202825
Description

As discussed in our meeting yesterday, I encountered a problem last Friday (2/3) and was unable to open the CDR on PROD due to not having the correct CDR loader file. This happened after doing some testing on DEV and QA, so I had several loader files on my machine from those tiers and the older loader file from PROD (dated November 2016) had been deleted from my workstation (I think it only keeps 5--that's how many I had).

Comment entered 2017-02-10 18:55:36 by Juthe, Robin (NIH/NCI) [E]

Adding Volker as a watcher.

Comment entered 2017-02-28 10:25:56 by Osei-Poku, William (NIH/NCI) [C]

Linda and I ran into a somewhat similar problem yesterday after logging into QA and tried to log back into PROD. In both cases, the loader did not launch. I finally logged in by clicking on the loader from the file system.

Comment entered 2017-02-28 10:31:12 by Kline, Bob (NIH/NCI) [C]

Could you please post the CdrClient.log files for the three machines (Linda's, William's, and Robin's) to the ticket? It lives in %APPDATA%\SoftQuad\XMetaL\9.0.

Thanks!

Comment entered 2017-02-28 12:11:28 by Kline, Bob (NIH/NCI) [C]

I found the bug, and I have installed a fixed version of the loader on DEV. I'll install it on QA after lunch. Until Einstein lands on PROD, you may still run into the problem when you go back to PROD.

Comment entered 2017-02-28 17:08:59 by Osei-Poku, William (NIH/NCI) [C]

You probably don't need to see our log files anymore but I loaded them anyway. Sorry for the delay.

Comment entered 2017-03-07 19:50:32 by Osei-Poku, William (NIH/NCI) [C]

I ran into the same problem while switching from DEV to QA this evening. I have attached the cdrclient file with the logs for today only.

Comment entered 2017-03-09 07:56:08 by Kline, Bob (NIH/NCI) [C]

I see I actually introduced a bug instead of fixing one with my previous change. I backed that out, bumped up the number of loaders to be retained from five to ten, and added logic to make sure we weren't trying to delete the same program we were running. I installed this on DEV and QA, added it to the deployment set, and gave CBIIT a request to patch it onto STAGE.

Comment entered 2017-07-27 16:56:35 by Englisch, Volker (NIH/NCI) [C]

, I'm thinking this ticket related to the deleted loader files could probably be closed. Am I right?

Comment entered 2017-07-28 13:58:42 by Kline, Bob (NIH/NCI) [C]

Sure, as long as the users confirm they are no longer experiencing the problem.

Comment entered 2017-08-08 11:21:26 by Kline, Bob (NIH/NCI) [C]

Can this be closed, Robin?

Attachments
File Name Posted User
CdrClient.log 2017-02-28 17:08:09 Osei-Poku, William (NIH/NCI) [C]
CdrClient.log 2017-02-28 13:16:09 Osei-Poku, William (NIH/NCI) [C]
CdrClient.log 2017-02-28 10:42:21 Juthe, Robin (NIH/NCI) [E]
cdrClient.txt 2017-03-07 19:51:29 Osei-Poku, William (NIH/NCI) [C]

Elapsed: 0:00:00.001268