topic Re: Problems after upgrading 3.1.4 to 3.2.1 in Management & Governance

Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Tue, 07 Mar 2017 22:36:26 GMT

I've performed a Qlik Sense Enterprise upgrade from 3.1.4 to 3.2.1. The upgrade wizard indicated that the upgrade completed successfully. Now I cannot access either QMC or the Hub. The services appear to be running, but I see the following error in the System_Repository logs:

20170307T223709.030+0200

INFO

SERVERNAME

System.Repository.Repository.QRSMain

90d49e3a-2d0e-4a2d-ab36-5ae8031ca08c

NT AUTHORITY\SYSTEM

Entering main startup phase..

90d49e3a-2d0e-4a2d-ab36-5ae8031ca08c

20170307T223710.301+0200

INFO

SERVERNAME

System.Repository.Repository.Core.Migrations.Support.MigrationMonitor

518ed2ad-fde2-49f7-84f7-020cd191e411

NT AUTHORITY\SYSTEM

Database migration triggered..

518ed2ad-fde2-49f7-84f7-020cd191e411

20170307T223710.392+0200

ERROR

SERVERNAME

System.Repository.Repository.QRSMain

fdd36f35-8d92-4e7c-987d-219a0524df26

NT AUTHORITY\SYSTEM

Fatal exception

password authentication failed for user "qliksenserepository"↵↓The provider did not return a ProviderManifestToken string.↵↓An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure.↵↓An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure. (See inner exception for details.)↵↓An exception was thrown while invoking the constructor 'Void .ctor(Qlik.Sense.Common.ITypeResolver, System.Func`1[Repository.Core.Repository.Database.Common.IDatabaseContext], Autofac.ILifetimeScope, Repository.Core.Repository.Common.ITransactionUtility, Repository.Core.Repository.Common.IRepositoryEntityCache, Repository.Core.INodeStaticInfo, Qlik.Sense.Logging.IQSLogManager, Repository.Core.Repository.Common.IRepositoryContentService, Repository.Core.Repository.Common.ILifetimeScopeEntityCache)' on type 'EntityTransactionRepository'. ---> An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure. (See inner exception for details.) (See inner exception for details.)↵↓An exception was thrown while invoking the constructor 'Void .ctor(Qlik.Sense.Logging.IQSLogManager, Repository.Core.INodeStaticInfo, Qlik.Sense.Communication.Security.ICertSetup, Qlik.Sense.Common.Communication.REST.Server.IRESTEngineFactory, Repository.Core.ISystemInformation, Repository.Core.Certificates.ICertificatePasswordVerificationWebService, Qlik.Sense.Common.Logging.ILogMaster)' on type 'SetupService'. ---> An exception was thrown while invoking the constructor 'Void .ctor(Qlik.Sense.Common.ITypeResolver, System.Func`1[Repository.Core.Repository.Database.Common.IDatabaseContext], Autofac.ILifetimeScope, Repository.Core.Repository.Common.ITransactionUtility, Repository.Core.Repository.Common.IRepositoryEntityCache, Repository.Core.INodeStaticInfo, Qlik.Sense.Logging.IQSLogManager, Repository.Core.Repository.Common.IRepositoryContentService, Repository.Core.Repository.Common.ILifetimeScopeEntityCache)' on type 'EntityTransactionRepository'. ---> An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file. See http://go.microsoft.com/fwlink/?LinkId=386386 for information on DbContext and connections. See the inner exception for details of the failure. (See inner exception for details.) (See inner exception for details.) (See inner exception for details.)

at Devart.Data.PostgreSql.w.x()↵↓ at Devart.Data.PostgreSql.w..ctor(PgSqlConnectionOptions A_0)↵↓ at Devart.Data.PostgreSql.b.a(t A_0, Object A_1, DbConnectionBase A_2)↵↓ at Devart.Common.DbConnectionFactory.a(DbConnectionPool A_0, t A_1, DbConnectionBase A_2)↵↓ at Devart.Common.DbConnectionPool.a(DbConnectionBase A_0)↵↓ at Devart.Common.DbConnectionPool.GetObject(DbConnectionBase owningConnection)↵↓ at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)↵↓ at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)↵↓ at Devart.Common.DbConnectionBase.Open()↵↓ at Devart.Data.PostgreSql.PgSqlConnection.Open()↵↓ at Devart.Data.PostgreSql.Entity.y.a(DbConnection A_0, b& A_1)↵↓ at Devart.Data.PostgreSql.Entity.PgSqlEntityProviderServices.GetDbProviderManifestToken(DbConnection connection)↵↓ at System.Data.Entity.Core.Common.DbProviderServices.GetProviderManifestToken(DbConnection connection)↵↓ at System.Data.Entity.Core.Common.DbProviderServices.GetProviderManifestToken(DbConnection connection)↵↓ at System.Data.Entity.Utilities.DbProviderServicesExtensions.GetProviderManifestTokenChecked(DbProviderServices providerServices, DbConnection connection)↵↓ at System.Data.Entity.Utilities.DbProviderServicesExtensions.GetProviderManifestTokenChecked(DbProviderServices providerServices, DbConnection connection)↵↓ at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)↵↓ at System.Data.Entity.Utilities.DbConnectionExtensions.GetProviderInfo(DbConnection connection, DbProviderManifest& providerManifest)↵↓ at System.Data.Entity.DbModelBuilder.Build(DbConnection providerConnection)↵↓ at System.Data.Entity.Internal.LazyInternalContext.CreateModel(LazyInternalContext internalContext)↵↓ at System.Data.Entity.Internal.RetryLazy`2.GetValue(TInput input)↵↓ at System.Data.Entity.Internal.LazyInternalContext.InitializeContext()↵↓ at Repository.Core.Repository.Database.Common.AbstractDatabaseContext..ctor()↵↓ at lambda_method(Closure , Object[] )↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓ at Autofac.Core.Lifetime.LifetimeScope.GetOrCreateAndShare(Guid id, Func`1 creator)↵↓ at Autofac.Core.Resolving.InstanceLookup.Execute()↵↓ at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at lambda_method(Closure )↵↓ at Repository.Core.Repository.Common.EntityTransactionRepository..ctor(ITypeResolver typeResolver, Func`1 databaseContextProvider, ILifetimeScope containingScope, ITransactionUtility transactionUtility, IRepositoryEntityCache repositoryEntityCache, INodeStaticInfo nodeInfo, IQSLogManager logManager, IRepositoryContentService repositoryContentService, ILifetimeScopeEntityCache lifetimeScopeEntityCache)↵↓ at lambda_method(Closure , Object[] )↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Execute()↵↓ at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Execute()↵↓ at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)↵↓ at Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable`1 parameters)↵↓ at Autofac.ResolutionExtensions.Resolve[TService](IComponentContext context, IEnumerable`1 parameters)↵↓ at Repository.Core.Repository.Common.SecurityAwareRepository.<>c__DisplayClass51_0`1.<GetAllWithoutSecurity>b__0()↵↓ at Repository.Core.Repository.Common.SecurityAwareRepository.RunWithoutSecurity[TResult](Func`1 func)↵↓ at Repository.Core.Settings.LocalConfigStash.GetFromRepository(LocalConfigKey key, ISecurityAwareRepository repository)↵↓ at Qlik.Sense.Common.Ioc.WorkScope.Work[T,TResult](Func`2 func)↵↓ at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)↵↓ at Repository.Core.Settings.LocalConfigStash.TryGet(LocalConfigKey key, LocalConfigCachePolicy cachePolicy, ISecurityAwareRepository repository, LocalConfig& localConfig)↵↓ at Repository.Core.Settings.LocalConfigStash.Get(LocalConfigKey key, LocalConfigCachePolicy cachePolicy)↵↓ at Repository.Core.Settings.LocalConfigStash.Get(LocalConfigKey key, T defaultValue, LocalConfigCachePolicy cachePolicy)↵↓ at Repository.Core.SystemInformation.<get_LocalNode>b__23_0(ISecurityAwareRepository repository)↵↓ at Qlik.Sense.Common.Ioc.WorkScope.Work(Action`1 action)↵↓ at Repository.Core.SystemInformation.get_LocalNode()↵↓ at Repository.Core.SystemInformation.GetTemporaryFolder()↵↓ at Repository.Core.Services.SetupService..ctor(IQSLogManager logManager, INodeStaticInfo nodeInfo, ICertSetup certSetup, IRESTEngineFactory restEngineFactory, ISystemInformation systemInformation, ICertificatePasswordVerificationWebService certificatePwdWebService, ILogMaster logMaster)↵↓ at lambda_method(Closure , Object[] )↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Execute()↵↓ at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()↵↓ at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.InstanceLookup.Execute()↵↓ at Autofac.Core.Resolving.ResolveOperation.GetOrCreateInstance(ISharingLifetimeScope currentOperationScope, IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.Core.Resolving.ResolveOperation.Execute(IComponentRegistration registration, IEnumerable`1 parameters)↵↓ at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)↵↓ at Autofac.ResolutionExtensions.ResolveService(IComponentContext context, Service service, IEnumerable`1 parameters)↵↓ at Autofac.ResolutionExtensions.Resolve[TService](IComponentContext context, IEnumerable`1 parameters)↵↓ at Qlik.Sense.Common.Ioc.WorkScope.Work(Action`1 action)↵↓ at Repository.QRSMain.Main()

fdd36f35-8d92-4e7c-987d-219a0524df26

20170307T223710.405+0200

INFO

SERVERNAME

System.Repository.Repository.QRSMain

fe254572-e107-4301-b7b6-4d8787344094

NT AUTHORITY\SYSTEM

Shutdown completed. Signing off..

fe254572-e107-4301-b7b6-4d8787344094

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Tue, 07 Mar 2017 23:33:19 GMT

Figured it out. Used the ConnectionStringEditor to look up the password for the qliksenserepository user, then went to pgAdmin to reset it to the expected value. Everything seems to be ok now.

Re: Problems after upgrading 3.1.4 to 3.2.1

jaisoni_trp — Tue, 21 Mar 2017 14:44:32 GMT

Alex, during the upgrade did it prompt for repository database password? I just executed the installer and it just asked for service user password.

Also can i ask if you are facing any major issue in 3.2.1 in terms of overall functionality?

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Tue, 21 Mar 2017 14:47:36 GMT

Jai,

I think it did ask for the superuser password.

We haven't run into other issues since the upgrade.

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Tue, 21 Mar 2017 15:43:46 GMT

Actually, I was just reading the releases notes for 3.2.2 and remembered that we were experiencing one issue that is now fixed:

Jira issue ID: QLIK-73023
Description: When opening an app in the mashup editor or single
configurator, sometimes sheets, objects and master objects are not listed
in the Dev hub objects panel.

Re: Problems after upgrading 3.1.4 to 3.2.1

db_qliksense — Wed, 03 May 2017 08:01:18 GMT

Hi Alex,

Could you please elaborate on - " ConnectionStringEditor to look up the password for the qliksenserepository user"? I am struggling here- is this a tool or command line utility?

My problem is that after I entered the service account password ( I used, run as administrator), it did not prompt me for database password during the upgrade. The upgrade was fine, services were running. But, HUB/QMC are not accessible.

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Wed, 03 May 2017 08:44:49 GMT

Hi,

it's a tool located in your Qlik installation directory, by default in C:\Program Files\Qlik\Sense\Repository\Util\ConnectionStringEditor.

Re: Problems after upgrading 3.1.4 to 3.2.1

db_qliksense — Wed, 03 May 2017 09:27:24 GMT

Many thanks.

May I ask about its encryption and decryption?

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Wed, 03 May 2017 10:27:57 GMT

Sure, you may want to check this document too: https://community.qlik.com/servlet/JiveServlet/download/1172359-256508/Qlik_Sense_Shared_Persistence_31_SR2.pdf

Re: Problems after upgrading 3.1.4 to 3.2.1

ansarikashif2017 — Tue, 22 Aug 2017 10:44:44 GMT

Hey Alex,

I am unable to find the ConnectionStringEditor in my QlikSense 3.0.0 installation.

There is only RepositorySnapshotManager folder in the Util folder :-

Qlik\Sense\Repository\Util\

I can't see ConnectionStringEditor. A blanket search on the server also didn't return any ConnectionStringEditor.

Can you please send the file from your installation?

Regards,

Kashif

Re: Problems after upgrading 3.1.4 to 3.2.1

Anonymous — Tue, 22 Aug 2017 14:58:41 GMT

Hi Kashif - ConnectionStringEditor could be part of a newer version of Qlik Sense than what you currently have installed in your environment.

Pranav

Re: Problems after upgrading 3.1.4 to 3.2.1

ansarikashif2017 — Tue, 22 Aug 2017 15:01:59 GMT

Hey Thanks Pranav. Thats what I was thinking. We decided lets upgrade to 3.2.4 (with synchronized persistence) and see if the Utility appears in the folder.

Thanks for confirming.

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Tue, 22 Aug 2017 15:05:16 GMT

Kashif,

here is mine just in case, I think it might work even with 3.0.0.

Dropbox - ConnectionStringEditor.exe

Re: Problems after upgrading 3.1.4 to 3.2.1

alextimofeyev — Tue, 22 Aug 2017 15:06:28 GMT

And here is the readme file:

Qlik Sense Connection String Editor 0.0.0

=========================

The Connection String Editor (CSE) helps to edit the Qlik Sense database connection string that is encrypted. This is the database connection string that Qlik Sense Repository Service uses to connect towards the PostgreSQL database.

Usage:

1. Specify where Repository.exe is located (default: C:\Program Files\Qlik\Sense\Repository\Repository.exe)

2. Press "Read" to read the encrypted string

3. Modify the connection string

4. Press "Save" to encrypt the connection string

Propeties for connection string:

User ID - The username that Repository Service will use to authenticate against the database (default: qliksenserepository)

Password - The password for the user in "User ID" field that will be used for authentication

Port - Port number to connect to PostgreSQL database (default: 4432)

Host - Hostname of the machine serving the PostgreSQL database (default: localhost)

Database - Name of the database that will be used (default: QSR)

Max pool size - Max number of concurrent connections against PostgreSQL database (default: 90). Note that increase of this number require that PostgreSQL configuration also can accept same amount of connections.

Note: All property and values are closed with ";" example: "myPropertyName=myValue;"

Re: Problems after upgrading 3.1.4 to 3.2.1

Anonymous — Tue, 22 Aug 2017 15:06:42 GMT

Why not Shared Persistence? Synchronized persistence is no longer supported as of June Release 2017.

Re: Problems after upgrading 3.1.4 to 3.2.1

ansarikashif2017 — Tue, 22 Aug 2017 15:07:33 GMT

Thanks Alex.

Re: Problems after upgrading 3.1.4 to 3.2.1

ansarikashif2017 — Tue, 22 Aug 2017 15:10:21 GMT

Yes from 3.2.4 to June 2017, we will go to Shared Persistence.

Re: Problems after upgrading 3.1.4 to 3.2.1

Anonymous — Tue, 22 Aug 2017 15:31:25 GMT

What is the page size set to? We have our's set to 500.