MSCOMCT2.ocx error: Difference between revisions
Ttenbergen (talk | contribs) m →Fix: m |
Ttenbergen (talk | contribs) m m |
||
| Line 4: | Line 4: | ||
== Fix == | == Fix == | ||
The fix is to navigate to | *The fix is to navigate to | ||
**Regional Server (RegionWRHA)\Maintenance | |||
right-click copy | *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) | *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 | |||
right-click copy the file on the desktop | *navigate to | ||
**C:\Windows\SysWOW64 | |||
navigate to | * 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. ''' | '''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. ''' | ||
Revision as of 11:40, 17 March 2016
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.
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.