Report Builder Invalid Company Logon | Community
Skip to main content
julie_huynh-1
julie_huynh-1
October 16, 2015
Solved

Report Builder Invalid Company Logon

  • October 16, 2015
  • 14 replies
  • 7268 views

I'm unable to open Report Builder in my Excel files using my usual company logo.  I'm able to access the web app just fine with the same credentials. I have uninstalled the old report builder, and reinstalled the latest but still receive the same error. Any ideas on what's going on at this point? See error attached.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by warrensander

    unfortunately when this happened to me I had to uninstall/reinstall report builder. But that did fix the problem. 

    it also made excel faster (at least to startup report builder)

    14 replies

    Show previous replies
    B
    bephco
    October 16, 2015

    Many companies use proxy servers. This may be the case for you. If so:

    1. enter your credentials as you already have
    2. check the 'Use a proxy server' box. This opens additional credentials fields.
    3. enter the User Name and Pwd you would use on your internal network. Then Sign In.
      devinderbanga
      devinderbanga
      Level 6
      October 16, 2015

      Hi

      Please verify your access from Report and Analytics UI ,

      If you can see reportbuilder download link that mean you have the access otherwise you need to contact your admin for access permissions.

       

      Regards

      Devinder

      dkatz1
      dkatz1
      Level 2
      January 3, 2016

      I have the same issue of the unable to find company message.  I have reinstalled 64 bit Excel and plugin several times and this does not work.  The credentials are correct. It looks like it never even tries to make a remote connection and provides the message right away.  Any other thoughts on what to try?

      P
      psvlin
      Level 4
      March 12, 2016

      Just fixed it on my Mac running VMWare. The culprit was the Windows firewall. Make sure to allow RB through. 

      Terms & ConditionsAccessibility statement

      Loading footer...