Issue Number | 3663 |
---|---|
Summary | [CTGov] Unable to open CTGovProtocols Processing Status Report on Prod |
Created | 2013-09-11 09:46:33 |
Issue Type | Bug |
Submitted By | Osei-Poku, William (NIH/NCI) [C] |
Assigned To | Kline, Bob (NIH/NCI) [C] |
Status | Closed |
Resolved | 2013-09-18 14:49:58 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.113059 |
We are unable to open the CTGovProtocols Processing Status Report. I have attached the error message.
I am unable to reproduce this failure. Can you confirm that you're still getting the error message?
yes. I just got the message again.
Could you have at least one other user test so when I report the problem to CBIIT I'll be able to tell them whether it's just your account? Thanks!
It's three of us getting the same error message.
Not sure why I can't enter the dependency from the other end. JIRA baffles me.
The problem appears to affect reports that display in MS Excel spreadsheet. The same error comes up when you run the Media Caption and Content report.
Since this is something that is keeping CIAT from doing their work, and needs to be addressed soon, shoudl I move this up in the agile board to the Iteration 1? I don't have a clear understanding of how priorities work in terms of addressing issues in the release vs high priority issues that get entered like this one. Thanks.
On our end, we're doing as much as we could do if this were in iteration 1, so I wouldn't bother with that (though you can if you want). Unfortunately, JIRA doesn't let us set the priority of the ticket I filed with CBIIT (who are the only ones able to fix the problem), but I have told them that this is something which needs to be resolved as soon as possible. I'll continue to prod (politely).
Thanks Bob. That answers my question, and I will let Ning know that we are trying to get CBIIT to address this. Let me know if you think we need to try and elevate this (not sure how, but I guess I could go and talk to Erika).
Erika would be the right person. Let's see how they respond to my most recent nudge.
From issue WEBTEAM-1237:
I am unable to duplicate this error, even logged into the bastion. It seems like it may be related to add-ins or COM settings. Please have a user try the following:
1. Log off and log back on to bastion session (don't just disconnect,
actually log off).
2. Start Excel from the Start menu
3. In Excel, click the File menu, the click Options and go to the
Add-Ins sheet
4. In the "Manage:" dropdown, choose "COM Add-ins" and click
"Go..."
5. Check if there are any add-ins, and clear the checkbox to disable
them if so.
6. Retry the problematic XLS
I tried this in Bastion Host using my laptop without success. I did
not see any add-ins.
I am going to try again on another laptop to see if it will work.
It didn't work on the second laptop I tried it on. There were no add-ins just like mine.
This is a very awkward approach to coordinating communication between the two universes, but I gather in JIRA it's the best we can do. Here's the latest from the CBIIT world:
Robert Chen added a comment - Monday, 16 Sep 2013 04:33 PM
Here is what I've found:
Workaround #1: cdr.cancer.gov is accessible outside the bastion host
environment (NIH-net facing subnet), so you can open the Excel file from
your NCI machine
Workaround #2: Firefox on the bastion host is able to download and open
the excel file successfully
Workaround #3: The error message "An error occurred and this feature is
no longer functioning properly..." keeps popping up. However, there is
an Excel error pop-under that says "The language DLL 'VBE7INTL.DLL'
could not be found". If you close the DLL error message, or if you OK
through the first error enough times, the excel page shows up.
Workaround #4: I took the liberty to set Add/Remove Programs > Office
2010 > Office Shared Features > Visual Basic for Applications to
"Installed on first use". I can now open the excel file from IE without
getting prompted. However, this change requires a reboot to tie off
loose ends. The reboot can be scheduled, or deferred to the next
maintenance.
At least #1 works for us.
The problem appears to have been resolved. We are now able to open excel reports without getting any error messages.
Closing issue.
File Name | Posted | User |
---|---|---|
CGov Processing Status Report error.docx | 2013-09-11 09:46:33 | Osei-Poku, William (NIH/NCI) [C] |
Elapsed: 0:00:00.001833