Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > ORM Profiler Section > Bugs & Issues> PostgreSQL won't execute on result set
 

Pages: 1
Bugs & Issues
PostgreSQL won't execute on result set
Page:1/1 

  Print all messages in this thread  
Poster Message
Mihies
User



Location:
Nova Gorica, Slovenia
Joined on:
08-Oct-2012 18:35:02
Posted:
20 posts
# Posted on: 25-Mar-2016 14:01:51.  
When trying to execute a sql command on PostgerSQL on same machine I get this guy

Quote:
Exception message:
-------------------------------
Exception type: ArgumentException
Unable to find the requested .Net Framework Data Provider. It may not be installed.


Is this by design and I have to configure PostgreSQL in profiler.config, or is this an error?

Update: I'm working with latest LLBLGenPro 5.0 beta framework
Miha Markic [MVP C#, INETA Country Leader for Slovenia, LLBLGenPro Partner, DXSquad, Friend of Red Gate]
Blog:http://blog.rthand.com/
Righthand .net consulting and software development
http://www.rthand.com/
 
Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
611 posts
# Posted on: 25-Mar-2016 14:43:11.  
please post code and stacktrace.

Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
Mihies
User



Location:
Nova Gorica, Slovenia
Joined on:
08-Oct-2012 18:35:02
Posted:
20 posts
# Posted on: 25-Mar-2016 14:49:24.  
Call stack
Quote:

Exception information.
=============================================================
ORM Profiler version: v1.5. Build: July 15th, 2015

Exception details:
=====================
Message: Unable to find the requested .Net Framework Data Provider. It may not be installed.
Source: System.Data
Stack trace:
at System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName)
at SD.Tools.OrmProfiler.Client.Core.CommandExecutorBase.GetFactory() in c:\Myprojects\VS.NET Projects\OrmProfilerv1.5_hg\SD.Tools.OrmProfiler.Client.Core\CommandExecutorBase.cs:line 244
at SD.Tools.OrmProfiler.Client.Core.CommandExecutorBase.CreateConnection() in c:\Myprojects\VS.NET Projects\OrmProfilerv1.5_hg\SD.Tools.OrmProfiler.Client.Core\CommandExecutorBase.cs:line 90
at SD.Tools.OrmProfiler.Client.Core.ResultsetRetriever.RetrieveResultset(Int32 limit) in c:\Myprojects\VS.NET Projects\OrmProfilerv1.5_hg\SD.Tools.OrmProfiler.Client.Core\ResultsetRetriever.cs:line 48
at SD.Tools.OrmProfiler.Client.Controls.ResultsetViewer._queryExecutorBW_DoWork(Object sender, DoWorkEventArgs e) in c:\Myprojects\VS.NET Projects\OrmProfilerv1.5_hg\SD.Tools.OrmProfiler.Client\Controls\ResultsetViewer.cs:line 210
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

Inner exception: <null>


Code isn't aynthing special, just a (any) select with couple of conditions, i.e.:

Code:
ctx.User.Where(e => e.Username == username && e.IsActive).SingleOrDefaultAsync(ctoken)


which results in this SQL in profiler

Code:
SELECT "LPA_L1"."id"             AS "Id",
     "LPA_L1"."user_role_id" AS "UserRoleId",
     "LPA_L1"."username"     AS "Username",
     "LPA_L1"."is_active"     AS "IsActive",
     "LPA_L1"."name"         AS "Name",
     "LPA_L1"."surname"        AS "Surname",
     "LPA_L1"."password"     AS "Password",
     "LPA_L1"."last_logged_in" AS "LastLoggedIn"
FROM "public"."user" "LPA_L1"
WHERE (((("LPA_L1"."username" = :p1)
     AND ("LPA_L1"."is_active" = :p2))))



Miha Markic [MVP C#, INETA Country Leader for Slovenia, LLBLGenPro Partner, DXSquad, Friend of Red Gate]
Blog:http://blog.rthand.com/
Righthand .net consulting and software development
http://www.rthand.com/
 
Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
611 posts
# Posted on: 25-Mar-2016 14:54:34.  
ah! Regular Smiley I was confused with the fact your query ran in code but it's of course inside the profiler client.

OK, this is easy to solve:

- either make sure the npgsql factory is installed in machine.config, so the factory is found by all apps. This is done through the msi installer on npgsql's releases page. It might be though that this goes wrong if the installer isn't installing the npgsql factory in the 32bit machine.config file. The ORM profiler client is a 32bit client by design so will request the factory from the 32bit .NET machine.config.
- or in ormprofiler.exe.config uncomment the npgsql section and correct the values for the npgsql version you're using Regular Smiley


Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
Mihies
User



Location:
Nova Gorica, Slovenia
Joined on:
08-Oct-2012 18:35:02
Posted:
20 posts
# Posted on: 25-Mar-2016 14:58:52.  
Ah, thanks.
I thought that profiler could get that data from client.
Miha Markic [MVP C#, INETA Country Leader for Slovenia, LLBLGenPro Partner, DXSquad, Friend of Red Gate]
Blog:http://blog.rthand.com/
Righthand .net consulting and software development
http://www.rthand.com/
 
Top
Otis
ORM Profiler Team



Location:
The Hague, The Netherlands
Joined on:
22-Aug-2011 10:26:38
Posted:
611 posts
# Posted on: 25-Mar-2016 15:03:22.  
Mihies wrote:
Ah, thanks.
I thought that profiler could get that data from client.

It has to create the db provider factory, and to obtain the factory instance it asks .NET for the factory instance. As there's no factory known for 'npgsql' at runtime in your case, it fails.


Frans Bouma
ORM Profiler / LLBLGen Pro Lead Developer | Blog | Twitter
 
Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.09082011 Final.