Software Updates Error Oracle Id 3104046

If you’re managing software updates in a Windows environment and suddenly see an error labeled “software updates error oracle id 3104046,” it can be confusing. Many believe it has something to do with Oracle, but that’s not true. 

This ID actually refers to a Microsoft Office update error that often appears in SCCM (System Center Configuration Manager) or WSUS (Windows Server Update Services). The error can result in failed downloads or blocked updates due to certificate issues, outdated metadata, or mismatched language files. This article will guide you step-by-step in understanding and fixing it.

What Is Software Updates Error Oracle ID 3104046?

Despite the name, this error is not connected to Oracle software. Instead, it refers to Microsoft KB3104046, a security update for Office 365 or Office 2016. The “oracle id” part likely appears due to naming confusion in update logs or package details. 

This update may fail to install when your system cannot validate its digital signature or when WSUS/SCCM experiences synchronization issues. Often, administrators notice this problem when ADR (Automatic Deployment Rules) fail to push updates properly or when downloads pause at 50%, leading to incomplete patching cycles.

Causes of the Error:

Invalid Digital Certificate Signature:

One of the most common reasons for this error is a missing or untrusted certificate. When WSUS or SCCM tries to verify the update’s certificate and cannot confirm its legitimacy, it blocks the download. This is usually due to an outdated or missing WSUS signing certificate or the root certificate authority (CA) not being installed on the client or server.

Catalog Synchronization Issues:

If your WSUS catalog is outdated or out of sync, SCCM may try to push updates that no longer exist or are incorrectly signed. Manual syncs often resolve this temporarily, but recurring sync issues can lead to failed deployments and repeated error messages.

CAB File Download Stuck or Mismatched:

Another cause of this error is when the update package expects a certain CAB file (for example, “a640_exp.cab”), but it isn’t available or is named incorrectly. This mismatch often causes updates to pause around 50%, failing to complete the installation process.

Language or Locale Conflict:

Office updates are language-specific. If the ADR is set to “English (United States)” but the update downloaded is “German (Germany),” the system won’t install it. This mismatch between the expected and received files leads to download errors or package rejection.

TLS (Transport Layer Security) Configuration Problem:

SCCM and WSUS rely on secure communication protocols like TLS 1.2. If these protocols are disabled or misconfigured on the server or client, secure certificate verification will fail, triggering this error.

How to Fix Software Updates Error Oracle ID 3104046?

Step 1 – Resync WSUS and SCCM

Start by forcing a full synchronization of your WSUS and SCCM catalogs. Make sure all necessary classifications and product updates (like Office 365) are selected in the WSUS options. Once resynced, rerun your ADR manually to ensure updates are being pulled correctly.

Step 2 – Verify Certificate Validity

On your update server, locate the CAB file associated with KB3104046. Right-click it, go to “Properties,” then open the “Digital Signatures” tab. If it’s not signed or the signature is invalid, export and import the trusted publisher certificate into the Trusted Root Certification Authorities and Trusted Publishers stores.

Step 3 – Confirm TLS and Port Settings

Ensure that both TLS 1.2 is enabled and configured correctly in your server registry. Also verify that your update server is using the right ports (8530 for HTTP, 8531 for HTTPS) and that firewall rules allow these ports.

Step 4 – Match Language Settings

Go to your SCCM ADR rule settings and check what languages are selected. Ensure that your devices are also set to these languages. If needed, adjust the update filters to match only the languages deployed in your organization.

Step 5 – Clear and Rebuild Update Packages

Delete any failed or incomplete deployment packages related to KB3104046. Recreate the package with the correct CAB files and ensure metadata is correctly matched. Then redistribute it to your Distribution Points.

Best Practices to Avoid the Error in the Future:

Keep Systems Up to Date:

Update your SCCM, WSUS, and Windows servers regularly. Microsoft frequently releases hotfixes that patch catalog bugs, certificate errors, and deployment engine improvements.

Automate Certificate Management:

Set up a Group Policy or PowerShell script that automatically installs or updates root CA certificates and WSUS signing certificates across your network.

Monitor Logs Regularly:

Check SCCM logs like DataTransferService.log, ContentTransferManager.log, and UpdatesDeployment.log. These can give early signs of problems like missing CABs, failed downloads, or verification errors.

Clean Up Superseded Updates:

Remove older or expired Office updates that have been replaced by newer ones. This avoids duplication and reduces the chance of mismatched packages being downloaded.

Quick Troubleshooting Overview:

ProblemLikely CauseFix Summary
Invalid certificate signatureMissing or outdated certificateImport signing certificate to trusted stores
Download stuck at 50%CAB file mismatch or missingReplace CAB or adjust ADR to pull correct files
ADR fails but manual worksCatalog sync or outdated metadataRerun ADR after full WSUS synchronization
Language mismatch errorADR language differs from systemAlign ADR language with target devices
TLS/Communication errorDisabled TLS or wrong portEnable TLS 1.2 and validate port configurations

FAQs:

What is Oracle ID 3104046?

Oracle ID 3104046 is not related to Oracle software. It’s actually a Microsoft Knowledge Base (KB) update ID for a security patch, usually for Office 365 or Office 2016. The name can be confusing, but the issue comes from Microsoft updates failing to install correctly, especially in WSUS or SCCM environments.

Why does SCCM report an invalid certificate for this update?

SCCM may show an invalid certificate error if the update’s digital signature can’t be verified. This often happens when the WSUS signing certificate has expired, is missing, or isn’t trusted on the client or server. Updating the certificate or importing it into the trusted certificate store usually resolves the problem easily.

Can I ignore the error if other updates are installing fine?

No, ignoring this error is risky. Even if other updates install correctly, a failed Office update like KB3104046 can leave systems unprotected. Patching gaps may lead to software bugs or security vulnerabilities. It’s important to resolve the issue to keep all software up to date and systems running smoothly.

Why does my ADR fail while manual sync works?

If your ADR fails but manual sync works, it’s likely due to outdated metadata or expired updates being referenced. The ADR might be trying to deploy updates no longer in the catalog. Resyncing WSUS, cleaning up expired rules, or recreating the ADR with fresh settings usually fixes the issue.

Do I need to reinstall WSUS or SCCM to fix this?

In most cases, you do not need to reinstall WSUS or SCCM. Reinstallation should be your last resort. Errors like this can usually be resolved by updating certificates, syncing catalogs, checking language settings, or adjusting your ADR rules. These steps are easier and safer than starting over with a new setup.

Conclusion:

The “software updates error oracle ID 3104046” may sound like an Oracle-related issue, but it is actually linked to Microsoft Office update KB3104046. This error commonly appears in WSUS or SCCM setups and is often caused by certificate mismatches, catalog sync failures, or language mismatches. 

Understanding the root causes is key to resolving the problem quickly and preventing future update failures. By regularly updating your systems, managing certificates, and monitoring logs, you can maintain a healthy and error-free update environment that ensures all patches are deployed properly across your network.

Related post:

Leave a Reply

Your email address will not be published. Required fields are marked *