• Replies 5 replies
  • Subscribers 338 subscribers
  • Views 19 views
  • Users 0 members are here
Related

TPAHTS broken by Windows update

Ian Ferguson
$organization

Hi

When we upgraded to v11.0.3 on Tuesday, PAH stopped working. Took us a while to realise, but it was actually a Windows update that broke it, not the Tessitura upgrade. (thanks Caryl @ RAH!)

Error in the PAH log is System.Runtime.InteropServices.COMException (0xFFFFDF2B): Exception from
HRESULT: 0xFFFFDF2B

Does anyone know exactly which update it was? It takes ages uninstalling an update and we installed quite a lot of patches on Tuesday. Windows Server 2008.

Thanks!

Ian

  • Former Member
    Former Member $organization

    We do not yet know which Windows update (or updates) caused this problem, but it is one (or more) of the following updates.  These were applied by a US licensee this morning which caused the PAHT problem Ian notes; backing out these updates and rebooting the web server resolved the problem without needing to reinstall the PAHT service:

     

     

    If we are able to determine the exact update or combination of updates that led to the PAHT problem we will pass on this information.

     

    Bob

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ian Ferguson
    Sent: Wednesday, July 18, 2012 12:59 PM
    To: Robert Bell
    Subject: [Tessitura Technical Forum] TPAHTS broken by Windows update

     

    Hi

    When we upgraded to v11.0.3 on Tuesday, PAH stopped working. Took us a while to realise, but it was actually a Windows update that broke it, not the Tessitura upgrade. (thanks Caryl @ RAH!)

    Error in the PAH log is System.Runtime.InteropServices.COMException (0xFFFFDF2B): Exception from
    HRESULT: 0xFFFFDF2B

    Does anyone know exactly which update it was? It takes ages uninstalling an update and we installed quite a lot of patches on Tuesday. Windows Server 2008.

    Thanks!

    Ian




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

  • $organization in reply to Former Member

    Hi Bob

    Thanks - I can confirm that the update which stops it working (at least on our Windows 2008 server) is KB2698365.

    I see that it patches an exploit in Microsoft Data Access Components, so that makes sense.

    http://technet.microsoft.com/en-us/security/bulletin/ms12-045

  • $organization in reply to Ian Ferguson

    Hello,

    At Melbourne Recital Centre we have just started receiving alerts in our live environment with this same error message.  Error: 0xFFFFDF2B - COMException. We are currently restarting our PAHT service twice daily.

    We are looking into whether the same windows update has caused issues for us, but wanted to see if anyone else has any further thoughts as to why this may be occurring?

    BV

  • $organization in reply to Beau Vigushin (Past Member)

    Hi there,

    We too are getting a COMException error.  Is there an update as to which Windows update could cause this?

    thanks,

    frannie

  • Former Member
    Former Member $organization

    Frannie,

     

    If the specific error noted in the posting below from 2013 which is:

     

    Failed to print order.System.Runtime.InteropServices.COMException (0xFFFFDF2B): Exception from HRESULT: 0xFFFFDF2B.

     

    appears in the PAH log, it is indicative of a known Microsoft bug related to RDS-based applications. Check your Microsoft updates to see if KB2698365 has been installed. If so, this update should be uninstalled and the system restarted to resolve the error. Microsoft published a hotfix for this error in 2013 which can be obtained from: http://support.microsoft.com/kb/2734642.  Please note that security update 2698365 which initially caused the problem as well as the noted hotfix 2734642 are applicable to computers running Windows 7 SP1 or Windows Server 2008 R2 SP1.

     

    This COMException error:

     

    Failed to print order.System.Runtime.InteropServices.COMException (0xFFFFDF81): Exception from HRESULT: 0xFFFFDF81

     

    when seen in the PAH log can be resolved by restarting the PAH service.

     

    If you are seeing a different error than one of these 2 errors or if you have any questions about what is noted here please open a TASK ticket so that Support can assist you.

     

    Bob

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Frances O'Connell
    Sent: Monday, December 29, 2014 1:46 PM
    To: Robert Bell
    Subject: RE: [Tessitura Technical Forum] TPAHTS broken by Windows update

     

    Hi there,

    We too are getting a COMException error.  Is there an update as to which Windows update could cause this?

    thanks,

    frannie

    From: Beau Vigushin <bounce-beauvigushin8188@tessituranetwork.com>
    Sent: 12/15/2013 9:00:38 PM

    Hello,

    At Melbourne Recital Centre we have just started receiving alerts in our live environment with this same error message.  Error: 0xFFFFDF2B - COMException. We are currently restarting our PAHT service twice daily.

    We are looking into whether the same windows update has caused issues for us, but wanted to see if anyone else has any further thoughts as to why this may be occurring?

    BV




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!