Easy2Patch v3.0
  • Infrastructure Documents
  • Overview
    • What is Easy2Patch
    • FAQs
    • Road Map
    • Licensing
  • Planning
    • Supported Configurations
    • Windows Operating System Requirements
    • Other Requirements
    • Network Considerations
    • Design
      • Update & Application & Intune (Server Deployment)
      • Standalone WSUS Deployment
      • Standalone Intune Deployment
  • Deployment
    • Installing WSUS Console
    • Installing SCCM Admin Console
    • Configuring Intune Application Registration
    • Getting Code-Signing Certificate
    • Installing Easy2Patch
    • Licensing
  • Configuring
    • Configuring SSL WSUS for 3rd Party Update
    • Configuring ConfigMgr for 3rd Party Updates
    • Easy2Patch Settings
      • General
        • Certificate Management
        • General Settings
        • Application Deployment
        • Intune Deployment
        • Maintenance
      • Notification
        • E-Mail
        • Telegram
          • Creating a Telegram Bot
          • Telegram Chat ID
      • SCCM / WSUS / INTUNE
        • WSUS Settings
        • SCCM Settings
        • Database Settings
        • Intune Settings
      • Proxy
  • Managing Easy2Patch
    • Update
    • Application Deployment
    • Intune Update
    • Intune Application
    • License Management
  • Troubleshooting
    • Schema files not found!
    • Failed to sign package; error was: 2147954402/2147954429
Powered by GitBook
On this page
  1. Troubleshooting

Failed to sign package; error was: 2147954402/2147954429

This error is usually caused by no or long communication with the timestamp server. In order to overcome this error, it would be useful to change the Time Stamp server URL address on the Settings\Certificate Management screen. The following steps are applied to change the address.

  1. The Settings\Certificate Management screen opens,

  2. Click the (...) button in the Time Stamp server URL field,

  3. Another address can be selected from the predefined address list that opens, or a new address can be defined with the New button,

  4. Click Yes to use the selected address,

  5. Press the ping button to make sure the address is accessible, under normal conditions, a timestamp address that responds quickly is expected to respond in about 1-2 seconds. If it takes longer than that, make sure the address is accessible or check if it causes a timeout while passing through security systems for example firewall, proxy or any other security systems. Timestamp URL addresses broadcast from TCP 80 or 443 addresses. However, most timestamp server do not host a web page at these addresses. They provide this URL as a service. Therefore, it is important to test it with the ping button.

PreviousSchema files not found!

Last updated 1 year ago