Error Code in T_Application_Errors

Hello,

I have just done a check up on our T_Application_Errors and I have just noticed that we have a recurring error in there. 

Has anyone ever come across the err_text 'PBReleaseDC Failed'?

What does this mean?

Many Thanks,

Scott

  • We’ve been getting them forever (counts below) so I haven’t paid them any attention.  They’re always err_line 91, err_object uo_vw_map_container on our system.

     

    version_no         year       entries

    7.0.0.2                   2007       50

    7.0.0.2                   2008       105

    7.5.0.1                   2008       541

    8.0.0.1                   2008       108

    8.0.0.1                   2009       370

    8.0.0.3                   2009       935

    9.0.0.2                   2009       438

    9.0.0.2                   2010       1551

    9.0.0.2                   2011       334

    10.0.0.1                2011       966

     

    Hope they weren’t something important….

     

    Moira

    _______________________________________________________________________

     

    Moira Mannas

    Information Manager

    + Southbank Centre, Belvedere Road, London, SE1 8XX

     

     


    www.southbankcentre.co.uk

    Ticket Office: 0844 847 9910

    Southbank Centre is a Registered Charity No. 298909

    ______________________________________________________________________

    This message (and files transmitted with it) may contain confidential or copyright information. If you receive it in error, please notify the sender and delete it from your computer.

    _______________________________________________________________________
  • We have quite a few, just wondered about the significance of them.

    I know its nothing of major importance (I think!) as no one has reported anything to us.

     

  • Former Member
    Former Member $organization in reply to Scott Whitehouse

    Thanks for reporting this; this error is indeed harmless and can be ignored. So much so, in fact, that we will be removing the logging of this error in version 11.

  • Thanks for the confirmation Steven!

     

    Scott