Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Good day,
I installed QlikSense on Windows Server 2012 R2. After the installation all the services started, however I could not open the management console. I then noticed this error in the Repository Service Log:
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.IRepositoryContentService)' on type 'EntityTransactionRepository'. ---> An exception was thrown while invoking the constructor 'Void .ctor()' on type 'DatabaseContext'. ---> Unable to determine the provider name for provider factory of type 'Devart.Data.PostgreSql.PgSqlProviderFactory'. Make sure that the ADO.NET provider is installed or registered in the application config. (See inner exception for details.) (See inner exception for details.) | 40b36f76-d5fc-457d-84c4-2bb04d7c0ad5 |
I checked the .Net version which is correct. The user account which I use is part of the administration group.
Any other ideas of what might be wrong ?
Kind regards
Edwin Anderson
Perhaps this blog post helps: http://bizxcel.com/blog-post/qlik-sense-repository-failure-start-after-windows-upgrade
is Any other services are runng on same machine?
lik skype? if yes do uninstall Skype and restrt ur machine and chk it nce
Perhaps this blog post helps: http://bizxcel.com/blog-post/qlik-sense-repository-failure-start-after-windows-upgrade
Hello Gysbert,
Thank you, this was indeed the case on the .Net config file, however in the Framework64 sub directory.
I did change this, restarted the server but still the repository does not want start successfully. I get the following error:
21 | 2.2.4.0 | 20160704T095922.107+0200 | INFO | NASHUA-DWUAT | a0c82df6-315e-4ac2-bf79-47edf96af36f | Command=Start repository;Result=0;ResultText=Success | 0 | 0 | 0 | INTERNAL | System | 0 | Not available | Repository | Not available | Not available | Start repository | 0 | Network Interface Card (NIC) number isatap.{7CCD1782-BC54-43F4-81FB-93AF5CF92556}: Properties: Id: {3317D256-EDE7-4E51-8B6A-51B9ECC55803}, Inbound only: False, Status: Down, Speed: 100000, Multicast: False, DNS enabled: False, DNS suffix: , Dynamic DNS: True | a0c82df6-315e-4ac2-bf79-47edf96af36f |
22 | 2.2.4.0 | 20160704T095922.107+0200 | INFO | NASHUA-DWUAT | 6bd1f912-ad26-4f6b-a322-82b8795939ab | Command=Load plugin;Result=0;ResultText=Success | 0 | 0 | 0 | INTERNAL | System | 0 | Not available | Repository | Not available | /qps/loadplugins | Load plugin | 0 | Loaded plugin Repository.UserDirectoryConnectors.ODBC.ODBC | 6bd1f912-ad26-4f6b-a322-82b8795939ab |
23 | 2.2.4.0 | 20160704T095922.107+0200 | INFO | NASHUA-DWUAT | 179f048d-92a8-42a4-bba5-2ecb9851a64c | Command=Load plugin;Result=0;ResultText=Success | 0 | 0 | 0 | INTERNAL | System | 0 | Not available | Repository | Not available | /qps/loadplugins | Load plugin | 0 | Loaded plugin Repository.UserDirectoryConnectors.ODBC.OdbcAccess | 179f048d-92a8-42a4-bba5-2ecb9851a64c |
24 | 2.2.4.0 | 20160704T095922.107+0200 | INFO | NASHUA-DWUAT | e7babe8c-dd1b-4923-96ba-52d7a00b1c9c | Command=Load plugin;Result=0;ResultText=Success | 0 | 0 | 0 | INTERNAL | System | 0 | Not available | Repository | Not available | /qps/loadplugins | Load plugin | 0 | Loaded plugin Repository.UserDirectoryConnectors.ODBC.OdbcExcel | e7babe8c-dd1b-4923-96ba-52d7a00b1c9c |
25 | 2.2.4.0 | 20160704T095922.107+0200 | INFO | NASHUA-DWUAT | e79a0811-641f-4183-ae2d-a735d89d5e45 | Command=Load plugin;Result=0;ResultText=Success | 0 | 0 | 0 | INTERNAL | System | 0 | Not available | Repository | Not available | /qps/loadplugins | Load plugin | 0 | Loaded plugin Repository.UserDirectoryConnectors.ODBC.OdbcSql | e79a0811-641f-4183-ae2d-a735d89d5e45 |
26 | 2.2.4.0 | 20160704T095922.107+0200 | INFO | NASHUA-DWUAT | c134dfa8-ce20-4fe6-beac-20a99062aaba | Command=Load plugin;Result=0;ResultText=Success | 0 | 0 | 0 | INTERNAL | System | 0 | Not available | Repository | Not available | /qps/loadplugins | Load plugin | 0 | Loaded 8 plugins | c134dfa8-ce20-4fe6-beac-20a99062aaba |
27 | 2.2.4.0 | 20160704T095937.044+0200 | WARN | NASHUA-DWUAT | df6285f4-f150-47af-bbc0-96bf5e036ca2 | Command=Check service status;Result=500;ResultText=Error: The remote server returned an error: (400) Bad Request. | 0 | 0 | 0 | INTERNAL | System | 43c885e1-6908-4799-9040-4d12a92db77e | Central | Repository | Not available | /qrs/servicestatusworker | Check service status | 500 | Method: 'SendServiceStatusRequest'. Failed to retrieve service status from 'https://172.16.0.210:4243/qps/'. Server host '172.16.0.210'. Error message: 'The remote server returned an error: (400) Bad Request.' | df6285f4-f150-47af-bbc0-96bf5e036ca2 |
28 | 2.2.4.0 | 20160704T095937.044+0200 | WARN | NASHUA-DWUAT | 90436117-602e-4cea-bddd-3fec47b5049e | Command=Check service status;Result=500;ResultText=Error: The remote server returned an error: (400) Bad Request. | 0 | 0 | 0 | INTERNAL | System | 43c885e1-6908-4799-9040-4d12a92db77e | Central | Repository | Not available | /qrs/servicestatusworker | Check service status | 500 | Method: 'SendServiceStatusRequest'. Failed to retrieve service status from 'https://172.16.0.210:5151/qss/'. Server host '172.16.0.210'. Error message: 'The remote server returned an error: (400) Bad Request.' | 90436117-602e-4cea-bddd-3fec47b5049e |
29 | 2.2.4.0 | 20160704T095937.044+0200 | WARN | NASHUA-DWUAT | 3c1e588c-4c14-467f-9017-3e3a8e1b14da | Command=Check service status;Result=500;ResultText=Error: The remote server returned an error: (400) Bad Request. | 0 | 0 | 0 | INTERNAL | System | 43c885e1-6908-4799-9040-4d12a92db77e | Central | Repository | Not available | /qrs/servicestatusworker | Check service status | 500 | Method: 'SendServiceStatusRequest'. Failed to retrieve service status from 'https://172.16.0.210:4899/printing/'. Server host '172.16.0.210'. Error message: 'The remote server returned an error: (400) Bad Request.' | 3c1e588c-4c14-467f-9017-3e3a8e1b14da |
Kind regards
Edwin
When I use localhost it works, so I will do some more investigation.
Thank you
Edwin
No idea, sorry. I suggest you contact Qlik Support to help troubleshoot this.
hi Edwin,
How did you manage to solve this issue? Or is it still not resolved?
Thanks,
Ajit