MSCOMCT2.ocx error: Difference between revisions
Ttenbergen (talk | contribs) m →Fix: m |
TOstryzniuk (talk | contribs) m →Fix: OCX fix - uncheck reference to system file |
||
| Line 19: | Line 19: | ||
**2016-08-22 - seems they forget to do this when you get new computer set up, therefore contact ehealth. | **2016-08-22 - seems they forget to do this when you get new computer set up, therefore contact ehealth. | ||
*** They forgot in Trish's case because setting up her PC does not follow data collector setup instructions. We will need to remind eHealth when main office PCs get updated. | *** They forgot in Trish's case because setting up her PC does not follow data collector setup instructions. We will need to remind eHealth when main office PCs get updated. | ||
* January 2, 2017 - HSC_3/D4 laptop: error message: MSCOMCTL.OCX | |||
**[[Herman Aubel]] uncheck the reference to this windows system file on this laptop. | |||
***We still need to try and understand why this happens to. [[Louise Lemoine]] did not have this issue Dec 29.16 before vacation and When [[Con Marks]] logged in to use it Jan 2.17, CCMDB would not work. | |||
== Causes == | == Causes == | ||
Not sure what would have caused this, but essentially this file is for some reason present on Tina's laptop and not on the data collection laptops. None of the changes in [[CCMDB.mdb_Change_Log_2016#2016-Mar-16]] had any active steps that should have started a new referral to this, or triggered a delete of the file, so it's not clear why this became an issue at that point. | Not sure what would have caused this, but essentially this file is for some reason present on Tina's laptop and not on the data collection laptops. None of the changes in [[CCMDB.mdb_Change_Log_2016#2016-Mar-16]] had any active steps that should have started a new referral to this, or triggered a delete of the file, so it's not clear why this became an issue at that point. | ||
Revision as of 16:40, 4 January 2017
After update CCMDB.mdb_Change_Log_2016#2016-Mar-16 all collectors were getting following error:
Your Microsoft Access Database or Project contains a missing or broken reference to the file 'MSCOMCT2.ocx' version 2.0.
Fix
- The fix is to navigate to
- Regional Server (RegionWRHA)\Maintenance
- right-click copy
- MSCOMCT2.OCX
- go back to the desktop, paste the file there (for some reason Windows 7 doesn't like to copy files directly from network to a system location)
- right-click copy the file on the desktop
- navigate to
- C:\Windows\SysWOW64
- paste the file.
This will only be possible with admin rights to the laptop. eHealth will give us admin rights to do this copy later today (12:37, 2016 March 17 (CDT)) and they will be present for a week unless we are done sooner with all fixes.
- April 5.16 - Ehealth fixed this up on the four main office computers. (inc# 2309932)
- 2016-06-23 added this to the updated laptop setup instructions, sent to Brandon Deamel
- 2016-08-22 - seems they forget to do this when you get new computer set up, therefore contact ehealth.
- They forgot in Trish's case because setting up her PC does not follow data collector setup instructions. We will need to remind eHealth when main office PCs get updated.
- 2016-08-22 - seems they forget to do this when you get new computer set up, therefore contact ehealth.
- January 2, 2017 - HSC_3/D4 laptop: error message: MSCOMCTL.OCX
- Herman Aubel uncheck the reference to this windows system file on this laptop.
- We still need to try and understand why this happens to. Louise Lemoine did not have this issue Dec 29.16 before vacation and When Con Marks logged in to use it Jan 2.17, CCMDB would not work.
- Herman Aubel uncheck the reference to this windows system file on this laptop.
Causes
Not sure what would have caused this, but essentially this file is for some reason present on Tina's laptop and not on the data collection laptops. None of the changes in CCMDB.mdb_Change_Log_2016#2016-Mar-16 had any active steps that should have started a new referral to this, or triggered a delete of the file, so it's not clear why this became an issue at that point.