Windows 8 upgrade windows 7 premium to windows 8 pro fails, see error message, what about BRIDGEMIG and how to

pdeleege

New Member
Joined
Nov 5, 2012
Messages
1
[0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: CBrgUnattend::CollectBridgeSettings failed: 0x1, 0
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:05:48, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:06:23, Error CONX ConX::Compatibility::CCompatibilityController::GetDriverBlockType: Found more than one match for the specified device.
2012-11-04 15:44:54, Error MIG COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
2012-11-04 15:46:12, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed 0x139f, bridge present = 0
2012-11-04 15:46:13, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6}, ThreadingModel=Apartment}. Error: 0x80070002
2012-11-04 15:46:13, Error Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,D:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
 


These log entries seem to be from an installation or migration process on a Windows system, indicating various errors encountered during the operation. Here's a breakdown of some of the key errors mentioned in the logs: 1. Error 0x1 in BRIDGEMIG: This error indicates that a function related to migration failed for some reason with error code 0x1. 2. Multiple matches found for a device in CONX: The entries starting with "Error CONX" mention that multiple matches were found for a specified device. This can lead to conflicts and issues during compatibility checks or driver installations. 3. Failed to create CSearchManager instance: This error occurred while trying to add a path to the Search Indexer. The specific error code 0x80070422 suggests a problem with the Search Manager creation. 4. Query bridge presence key failed: Another error in the BRIDGEMIG plugin where a query regarding the presence of a bridge failed with error code 0x139f. 5. Failure while calling ApplySuccess for Microsoft-Windows-DirectoryServices-ADAM-Client: This error occurred during a post-apply operation related to the Active Directory Application Mode (ADAM) client. The error code 0x80070002 indicates a file not found issue. 6. Error READ 0x00000002: This error seems to be related to reading an object during the process and encountering an issue with a specific action related to Microsoft-Windows-DirectoryServices-ADAM-Client. Each of these errors points to specific issues during the installation or migration process, which might require troubleshooting to address. It could involve checking driver compatibility, resolving file not found errors, or investigating issues with certain migration plugins. If you need further assistance in troubleshooting these errors or need guidance on resolving them, feel free to provide more details about the specific context or setup where these errors occurred.
 


Back
Top