1 2 3 Previous Next 30 Replies Latest reply on Nov 26, 2019 7:28 AM by Uwe Ryczek Go to original post
      • 15. Re: Invalid Smart Reporting Credentials
        Kobus Duminy

        If you do have access on the DB you can just reset it via SQLPLUS as sysdba. In my case it was a Oracle DB so the following worked: ALTER USER repadmin IDENTIFIED BY <password> ACCOUNT UNLOCK;

        (Using SQL*Plus to Unlock Accounts and Reset Passwords )

        If the above is not applicable to yourself you may want to check these posts:

        Reseting Smart Reporting Repository database password

        Remedy Smart Reporting - How To Reset Default Admin User "siadmin" Password To Fix The Error "You have exceeded the number of allowed login attempts."?

         

        Cheers

        • 16. Re: Invalid Smart Reporting Credentials
          McHarry Chito

          Hi Guys,

           

          Does anyone able to solve this?

           

          I am facing the same issue, I was able to login as siadmin on http://servername:8181/ but was not able to do onbarding because of the invalid credentials issue.

           

          Regards,

          Harry

          • 17. Re: Invalid Smart Reporting Credentials
            Ezra Wise

            I don't think that this would apply to the OP, but since the start of 2018 the OOTB Smart Reporting license has expired.  Need to apply the new one before this will work.  You can find the license attached to the following KA:

            https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA214000000gmiUCAQ-Solution

            1 of 1 people found this helpful
            • 18. Re: Invalid Smart Reporting Credentials
              Mohamed Atta

              Hello McHarry,

                   Did you find a solution of your issue? As i have same issue,

               

              I'm able to login as siadmin on http://servername:8181

               

               

               

              but when i try to login to Admin console i got incorrect user name or password

               

               

               

              when i check the logs i got the below error:

               

              com.hof.mi.web.service.WebserviceException

              at com.hof.mi.web.service.AdministrationService.remoteAdministrationCall(AdministrationService.java:371)

              at com.hof.mi.web.webservices.LegacyAdministrationService.remoteAdministrationCall(LegacyAdministrationService.java:20)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

              at java.lang.reflect.Method.invoke(Unknown Source)

              at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:250)

              at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:149)

              at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:88)

              at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:1063)

              at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:979)

              at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:950)

              at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:825)

              at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:380)

              at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:651)

              at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:264)

              at com.sun.xml.ws.transport.http.servlet.ServletAdapter.invokeAsync(ServletAdapter.java:218)

              at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:159)

              at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:194)

              at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:80)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)

              at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:230)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)

              at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)

              at com.bmc.servlet.ClickJackFilter.doFilter(ClickJackFilter.java:88)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)

              at com.bmc.servlet.HSTSFilter.doFilter(HSTSFilter.java:47)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)

              at com.hof.servlet.BrowserHeaderFilter.doFilter(BrowserHeaderFilter.java:43)

              at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:192)

              at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:165)

              at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:198)

              at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:108)

              at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)

              at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)

              at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)

              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)

              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349)

              at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784)

              at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)

              at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:802)

              at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)

              at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

              at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

              at java.lang.Thread.run(Unknown Source)

              1 of 1 people found this helpful
              • 19. Re: Invalid Smart Reporting Credentials
                paul horncastle

                Hi Ezra, I've seen many attempts of people to reset the siadmin password because they could not onboard all linking to the password reset KA - yours is the first to mention the expired license. After downloading the license and importing it, I tried the onboarding again and it worked! I thought something odd was going on because I could log into the admin sonole using the default siadmin/siadmin credentials but not onboard. Thanks again.

                 

                Paul

                • 20. Re: Invalid Smart Reporting Credentials
                  Ravian Nugraha

                  For people who used version 18.08, this is a known error SW00551642 .

                  Just patch the Smart Reporting to 18.08.001.

                   

                  • 21. Re: Invalid Smart Reporting Credentials
                    Ravi Reddi

                    Defect SW00551642 is applicable only when SmartReporting is deployed with external web application (Tomcat). Bundled tomcat should work flawlessly.

                     

                    Below steps are worth a try:

                     

                    Execute the below query in Smart Reporting Repository Database, and confirm if the record exists :

                     

                    select * from Configuration where ConfigCode = 'SIMPLE_AUTHENTICATION'

                     

                    If this does not exists , add this entry with insert query and restart the SR server and hit the admin console login.

                     

                    INSERT INTO Configuration values (1, 'SYSTEM', 'SIMPLE_AUTHENTICATION', 'TRUE')

                     

                    Regards,

                    Ravi Reddi

                    • 22. Re: Invalid Smart Reporting Credentials
                      Ravian Nugraha

                      Anyway Ravi,

                       

                      Since you are here and talking about external tomcat.

                      Any particular reason why BMC suggest to use Tomcat 8.0.35?

                      Or this suggestion is already obsolete?

                       

                      Thanks

                      • 23. Re: Invalid Smart Reporting Credentials
                        Ravi Reddi

                        Any particular reason why BMC suggest to use Tomcat 8.0.35?

                        For a very simple reason.... "BMC has tested and certified only 8.0.35 version for external Tomcat"

                         

                        Or this suggestion is already obsolete?

                        This is applicable only until 9.1.02 releases since later releases Tomcat 8.5.xx was offered as OOB.

                         

                        Regards,

                        Ravi Reddi

                        1 of 1 people found this helpful
                        • 24. Re: Invalid Smart Reporting Credentials
                          Ravian Nugraha

                          Thanks a lot Ravi

                          Good to know that we are not stuck with 8.0.35 even on newer version.

                          Literary have to update the docs (Preparing to install BMC Remedy Smart Reporting - Documentation for Remedy Deployment 19.02 - BMC Documentation )

                          • 25. Re: Invalid Smart Reporting Credentials
                            Ravi Reddi

                            Sure Ravian, I have seen your comment on the docs page. Will let the team make the necessary changes!

                             

                            Regards,

                            Ravi Reddi

                            • 26. Re: Invalid Smart Reporting Credentials
                              Ravi Reddi

                              Hi Ravian,

                               

                              The doc is updated now!

                               

                              Regards,

                              Ravi Reddi

                              • 27. Re: Invalid Smart Reporting Credentials
                                Thomas Hammer

                                We have the same issue with Smart-IT 19,02 (Yellowfin 8.0.1).

                                Login with siadmin to Reporting console is working fine <Smart-reporting-server>/SmartReporting/

                                Login to admin console doesn't work <smart-reporting-server>/AdminConsole/#/

                                 

                                Does anybody have a solution for this?

                                 

                                - License is valid

                                - password not expired

                                - reset of password for siadmin did work, but did not help

                                 

                                What we did: We switched from http to https and changed the reporting url

                                - We've modified the mid-tier configuration

                                - We've modified the entry in form SmartReportingServer_Info

                                - Server has an additional IP adress

                                - Tomcat server has been configured to use the additional ip adress

                                • 29. Re: Invalid Smart Reporting Credentials
                                  Thomas Hammer

                                  Yes, but it did not help