TI Live Exchange 2021

Dear to whom this may concern,

When attempting to register for the 2021 TI Live Exchange, I receive the following error:

"Error:

An unknown error has occurred. Please try to launch the show again."

https://www.ti.com/about-ti/events/ti-live-tech-exchange.html?HQS=corp-event-null-te21-bhp-pp-register-wwe

What is the best way to resolve this and register?  I've contacted TI through chat and submitted a support ticket 9 days ago with no response.

Thanks!

David Subert

  • Hello David, 

    Apologies for the difficulties in getting this issue resolved.  However, E2E is for technical/engineering design issues. 

    Please provide the support ticket info you received and I will look into how this can be resolved.  

    Regards,

    ~Leonard 

  • Ticket number CS0684407

    Thanks for the help.  With the conference starting Monday, I would have expected TI to receive more requests like this.

  • Ticket number CS0684407

    Thanks for the help.  With the conference starting Monday, I would have expected TI to receive more requests like this.

  • Thanks David, I will look into this.  

    Also, curious as to why you posted the Reply two times? 

    And, please verify that you had to Sign-In to your myTI account prior to submitting the registration request.  If not, please Sign-In to myTI, then check the registration process. 

    Thanks,

    ~Leonard  

  • Hi David,

      The department that runs the conference says they receive many similar requests, and the main reason for an error such as you received is that the user is not Sign-In to myTI. 

      So as previously suggested, please verify a valid Sign-In to myTI.  Also, recommend to clear the browser cache and cookies prior to SIgn-In.

    Let me know the results.  

    Regards,

    ~Leonard  

  • Thanks for help.

    I resolved the issues by creating a new TI account.  The existing TI account I had was roughly 15yrs old.  This account would allow complete TI site access, but not access to the TI Live Session.  Creating a new profile/account with a work email address (instead of personal) resolved the issue.