5 Replies Latest reply: Nov 10, 2016 2:47 AM by Lakshmikandh Karthikeyan RSS

    QlikSenseServer problem after upgrade to 3.0

    Urs Blapp

      Hello,

      After upgrading the QlikSense from 2.0.2 to 3.0 on a Windows 2012 R2 server, login to QMC or hub is not possible anymore. Looking at netstat -an, I can see that ports 80 and 443 are not listed.

       

      The related services start up but with errors.

      Here is the error in System/ServiceRepository.log file:

       

      4    3.0.0.0    20160817T091708.954+0200    ERROR    qliksense3    8c17c186-d8b1-456d-bc0c-cdcccc08301d    Command=Start repository;Result=-2146232828;ResultText=Error: Exception has been thrown by the target of an invocation.    0    0    0    INTERNAL    System    0    Not available    Repository    Not available    Not available    Start repository    -2146232828    An error occurred while executing the command definition. See the inner exception for details.    8c17c186-d8b1-456d-bc0c-cdcccc08301d

       

      In the Trace/SystemRepository.txt following info can be found:

      56    20160817T091709.017+0200    ERROR    qliksense3    System.Repository.Repository.QRSMain    12    d8275323-bba6-4c35-9a73-7c1afd48b70f    NT AUTHORITY\SYSTEM    Fatal exception    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond↵↓Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.↵↓Server did not respond within the specified timeout interval.↵↓Server did not respond within the specified timeout interval.↵↓An error occurred while executing the command definition. See the inner exception for details.↵↓Exception has been thrown by the target of an invocation.   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)↵↓   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)↵↓   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)↵↓   at Devart.Common.au.a(Byte[] A_0, Int32 A_1, Int32 A_2)↵↓   at Devart.Common.au.a(Byte[] A_0, Int32 A_1, Int32 A_2)↵↓   at Devart.Common.j.c(Byte[] A_0, Int32 A_1, Int32 A_2)↵↓   at Devart.Common.z.d(Byte[] A_0, Int32 A_1, Int32 A_2)↵↓   at Devart.Data.PostgreSql.PgSqlDataReader.f(Int32 A_0)↵↓   at Devart.Data.PostgreSql.PgSqlCommand.InternalExecute(CommandBehavior behavior, IDisposable stmt, Int32 startRecord, Int32 maxRecords)↵↓   at Devart.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior, Boolean nonQuery)↵↓   at Devart.Data.PostgreSql.Entity.t.a(CommandBehavior A_0)↵↓   at Devart.Data.PostgreSql.Entity.t.b(CommandBehavior A_0)↵↓   at System.Data.Entity.Infrastructure.Interception.InternalDispatcher`1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func`3 operation, TInterceptionContext interceptionContext, Action`3 executing, Action`3 executed)↵↓   at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)↵↓   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)↵↓   at System.Data.Entity.Core.EntityClient.Internal.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior)↵↓   at System.Data.Entity.Core.Objects.Internal.ObjectQueryExecutionPlan.Execute[TResultType](ObjectContext context, ObjectParameterCollection parameterValues)↵↓   at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.<>c__DisplayClass7.<GetResults>b__5()↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption)↵↓   at System.Data.Entity.Core.Objects.ObjectQuery`1.<System.Collections.Generic.IEnumerable<T>.GetEnumerator>b__0()↵↓   at System.Data.Entity.Internal.LazyEnumerator`1.MoveNext()↵↓   at Repository.Core.Repository.Common.RepositoryEntityCache.AddToCache[T](IEnumerable`1 items, Boolean includeNavigational)↵↓   at Repository.Core.Core.<>c__DisplayClass75_1`1.<LoadEntityIntoCache>b__1(IEnumerable`1 items)↵↓   at Repository.Core.Repository.Common.ModelRepository`1.InitializeRepositoryCache(Boolean loadFromDatabase, Func`2 f)↵↓   at Qlik.Sense.Common.Ioc.WorkScope.Work[T](Action`1 action)↵↓   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)↵↓   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)↵↓   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)↵↓   at Repository.Core.Core.ReloadEntityCache()↵↓   at Repository.Core.Core.Setup_CentralNode()↵↓   at Repository.Core.Core.Setup()↵↓   at Repository.Core.Core.Inner(ManualResetEvent shutdownRequestedEvent)↵↓   at Repository.QRSMain.<Main>b__24_0(ICore core)↵↓   at Qlik.Sense.Common.Ioc.WorkScope.Work[T](Action`1 action)↵↓   at Repository.QRSMain.Main()   d8275323-bba6-4c35-9a73-7c1afd48b70f

       

      All services are running and I am also able to login into postgres.

      Has anyone had similar problems when upgrading to version 3.0? Any input is very much appreciate.

       

      Thanks

      Urs

        • Re: QlikSenseServer problem after upgrade to 3.0
          Andrew Donald

          I am seeing the same issue.

            • Re: QlikSenseServer problem after upgrade to 3.0
              alexander korsikov

              Did you do a database clenup before upgrading?

              --

              Perform a database cleaning before migrating to 3.0

               

              It is recommended that customers with large amount of users or applications performs a database cleaning before migrating from 2.0.x to 3.0.

               

              After performing an upgrade in a multi-node environment, it can take very long time for newly created database items (such as sheets, applications, bookmarks, or tags) to appear on all nodes. This is caused by long synchronization queues between the nodes, as a result of the upgrade. All new items will be at the end of these queues. From Sense 2.2 the repository database is stored in RAM to improve the performance, for users with very large databases the database can become larger than the available RAM on the server which results in an error during startup. If you are running a large installation (users or apps) we recommend that you perform the steps described below before performing the upgrade.

               

              Workaround: Synchronization queues will eventually finalize by themselves, but in very large environments this can take several hours. If you import a large Active Directory, it is recommended to do the following before upgrade to reduce upgrade synchronization queues:

               

               Make sure that you applied best practices for User Directory connectors: https://community.qlik.com/docs/DOC-14708

               

               If a large Active Directory has been imported without filters, do the following:

               

              1. Setup LDAP import filters, according to the best practice guide, to reduce size of imported user attributes.

               

              2. Remove users and perform a new import of the Active Directory.

               

              3. Run the Database Cleanup Script, provided by Qlik, to clean the repository database before upgrading. To acquire the Database Cleanup Script, log in to the Support Portal and search for article “17620”. The title of the article is “Qlik Sense Database Cleanup Script 2.2.x”.

               

              4. Restart the system and start the upgrade.

                • Re: QlikSenseServer problem after upgrade to 3.0
                  Syed Ismael Hamid

                  Hi Alexander,

                   

                  I am currently having some issues with the DB cleanup script. I am upgrading from qlik sense 2.0.1 to 3.0.0.

                  1)

                  psql:C:/Users/visorservice/Desktop/SenseCleanupScript_v1.2/SenseCleanupScript/CleanupSenseDb_2.0.sql:127:

                  ERROR:  update or delete on table "CompositeEvents" violates foreign key constraint "FK_CompositeEventTimeConstraints_CompositeEvents_ID" on table "CompositeEventTimeConstraints"

                  DETAIL:  Key (ID)=(328e73cd-5113-4c73-bfd2-5599fab94753) is still referenced from table "CompositeEventTimeConstraints".

                   

                  This is what i got from the error logs after running the dbcleanupscript

                   

                  After that i ran the qlik 3.0.0 installer and the qlik sense database service did not start automatically nor manually.

                  Restarted the server and same thing happened.

                  Did a repair via the installer.

                  The Qlik DB can run however i will still get an error to connect to QMC or HUB.

              • Re: QlikSenseServer problem after upgrade to 3.0
                Shraddha Gajare

                Have you tried disabling proxy server setting of Browser?

                Setting it to Automatic proxy server might help.

                • Re: QlikSenseServer problem after upgrade to 3.0
                  Lakshmikandh Karthikeyan

                  Did you restart the server after upgrade ?

                  can you try it once ?