Upgraded and now ERR_CONNECTION_REFUSED

Anonymous — Mon, 09 Apr 2018 08:54:52 GMT

Hi,

I've tried to update from Qlik Sense June 2017 to the latest Feburary 2018 release.

All of the process went smoothly, and I had a message "Qlik upgrade has been successful" or similar message, but now when I try to access HUB/QMC I get the error "ERR_CONNECTION_REFUSED" as in it seems those sites are not live.

I will paste my log below which I believe contains the relevant error, but I'm not smart enough to troubleshoot this, has anyone came across this before?

N.B. When I was running the installer, I did have some troubles with user accounts so that could be related to the issue.

Please let me know if I can provide any more information

Thanks,

James.

Log is below:

Sequence# ProductVersion Timestamp Severity Hostname Id Description ProxySessionId ProxyPackageId RequestSequenceId UserDirectory UserId ObjectId ObjectName Service Origin Context Command Result Message Id2

1 18.5.2.0 20180406T163734.468+0100 INFO GR2LCYMQKSV01 2e31ecfd-aafb-4739-93c5-7597f5ba7f3d Command=Start repository;Result=0;ResultText=Success 0 0 0 INTERNAL System 0 Not available Repository Not available Not available Start repository 0 Validating certificates. 2e31ecfd-aafb-4739-93c5-7597f5ba7f3d

2 18.5.2.0 20180406T163814.373+0100 ERROR GR2LCYMQKSV01 bc16aef7-7946-45c0-996e-273ec3b3e30f Command=Start repository;Result=-2146233088;ResultText=Error: 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.ILifetimeScopeEntityCache, Repository.Core.Repository.Common.IEntityFrameworkExtendedWrapper)' on type 'EntityTransactionRepository'. ---> An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> Failed to remove soft deleted records (See inner exception for details.) (See inner exception for details.) (See inner exception for details.) 0 0 0 INTERNAL System 0 Not available Repository Not available Not available Start repository -2146233088 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.ILifetimeScopeEntityCache, Repository.Core.Repository.Common.IEntityFrameworkExtendedWrapper)' on type 'EntityTransactionRepository'. ---> An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> Failed to remove soft deleted records (See inner exception for details.) (See inner exception for details.) bc16aef7-7946-45c0-996e-273ec3b3e30f

3 18.5.2.0 20180406T165334.484+0100 INFO GR2LCYMQKSV01 7ff7bcce-2f6e-410f-b810-cd7ee1674b21 Command=Stop repository;Result=0;ResultText=Success 0 0 0 INTERNAL System 0 Not available Repository Not available Not available Stop repository 0 Stopping Repository and calling shutdown events, due to: stopped by Windows service manager 7ff7bcce-2f6e-410f-b810-cd7ee1674b21

Re: Upgraded and now ERR_CONNECTION_REFUSED

davidgabisonia — Thu, 16 May 2019 14:48:11 GMT

Hi,

Could you solved this case?

topic Upgraded and now ERR_CONNECTION_REFUSED in Management & Governance

Upgraded and now ERR_CONNECTION_REFUSED

Re: Upgraded and now ERR_CONNECTION_REFUSED