I was able to install npgsql successfull. I have also verified by looking at control-panel and i see the npgsql 4.0.10. However, when I run the "factoryclasses" command in PowerShell, I am not able to see the npgsql connector. I am doing the installation on the AWS server and i am using 4.0.10 version as that's the version which is recommended by the Microsoft team to connect with Power-Bi.
[System.Data.Common.DbProviderFactories]::GetFactoryClasses()
When i run the factoryclasses command, I expect to see npgsql.
Related
I already had SQL Server 2019. After upgrading my Windows 10 to latest October Update, I found my SQL Server does not have latest service packs.
I downloaded latest service pack CU8 from Microsoft and ran it. After initializing set up, I get error
Attempted to perform an unauthorized operation
Many research and no luck even in SO.
Please advise.
https://www.microsoft.com/en-us/edge/business/download
Please get the offline installer for latest Microsoft Edge (Chromium) on above link.
Once you have it, run Edge installer and then try to run SQL Update again.
This worked. I ran the latest Edge standalone install and it unblocked the MSSQL patch.
I also confirm that it works. Thanks
https://www.microsoft.com/en-us/edge/business/download
I can confirm this fixes the issue when trying to install SQL 2014 Express Advanced on Windows 10 with H2 update installed.
I had the same error, and installing the standalone Microsoft Edge fixes the error.
After reviewing the logs and digging into windows registry and security, I found the problem was "Microsoft Edge" registry key. Somehow it is read-only for administrator and I figured it out I need to use SYSTEM account to apply the service pack.
Finally I found I can do that using an executable in SysInternals package which is famous for doing weird things in Windows.
This is what I did to apply the service pack.
Run Cmd or PowerShell as Administrator
Go to SysInternals and make sure you have the PsExec64.exe there
Run below command:
.\PsExec64.exe -sid "D:\Downloads\SQLServer2019-KB4577194-x64.exe"
This way you will execute the service pack using SYSTEM account which has highest privilege.
Service pack installed successfully!
I'm running SSIS w/ Kingswaysoft on latest version of VS2017. I have created a package that executes successfully on my local computer and I have also successfully deployed the project deployment file via Integration Services Deployment Wizard to a SQL 2014 server (from the command prompt with ISDeploymentWizard.exe).
Before deploying, I checked that "TargetServerVersion" was indeed "SQL Server 2014".
After the successfull deploy, when I manually execute the package on the target server I got the following exception:
Data Flow Task:Error:
Microsoft.SqlServer.Dts.Pipeline.ComponentVersionMism atchException:
The version of Dynamics CRM Source is not compatible with this version
of the DataFlow. [[The version or pipeline version or both for the
specified component is higher than the current version. This package
was probably created on a new version of DTS or the component than is
installed on the current PC.]] at
Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHos
t.HostCheckAndPerformUpgrade (IDTSManagedComponentWrapper100 wrapper,
Int32 lPipelineVersion)
Anyone have a clue how to solve this one?
It is likely you have a later version of our software on your development environment then the server you are deploying to. You will want to make sure both environments are using the same version of our software.
https://www.kingswaysoft.com/products/ssis-integration-toolkit-for-microsoft-dynamics-365/download
Please let us know if you still have trouble.
I'm trying to get data from a PostgreSQL database into PowerBI Desktop but it doesn't seem to work. I think the problem is with the installation with npgsql. When trying to setup a new database connection in PowerBI I type in the database and server, and this is the error message I get:
"Unable to connect
Details: "PostgreSQL: We were unable to find a database provider with invariant name 'Npgsql'.
This error could've been the result of provider-specific client software being required, but missing on this computer. To download client software for this provider, visit the following site and choose the 64-bit (x64) version of, at minimum, 'Npgsql version 2.0.12': https://go.microsoft.com/fwlink/?LinkID=282716""
I've tried going npgsql website and install the required components but I can't seem to get it working. I'm not a developer so this is a bit complicated for me. Does anyone know how to get these components installed? I very much appreciate your help!
I'm using Windows 10 on a Surface Pro 3 if this helps. And I do have Visual Studio Community installed as well.
Best,
Bruno.
I have downloaded and tried it with version 3.6.6
Install npgsql
During the installation stage, enabled "Npgsql GAC Installation" as GAC requires Npgsql.
Restart the PC.
It should work now.
The solution from this page helped me: https://community.powerbi.com/t5/Community-Blog/Configuring-Power-BI-Connectivity-to-PostgreSQL-Database/ba-p/12567
Select the option to install to the GAC during install of the program npgsql v3.x.x downloaded from this page https://github.com/npgsql/Npgsql/releases
It worked for me (although I do not know why:-)
When you install Npgsql you should enable installation into the GAC.
Otherwise component will not be automatically detectable to other programs.
I did some research on this. Everywhere I have seen that, this is coming as package.
Weblogic/Eclipse IDE/OSB.
How can I use the Eclipse as client and connect to OSB server, deploy to server for testing.
i don't want to install any services.
Also I have installed Jdeveloper, that is not supporting OSB.
The Eclipse distribution you need to use is OEPE (Oracle Enterprise Pack for Eclipse).
There is a guide on how to get a development environment set up on the Oracle Middleware blog.
Do make sure you get compatible versions, though, even minor version differences can be a problem:
To ensure the Eclipse version is compatible with your OSB version I recommend using the Eclipse that comes with the supported WLS server, e.g. OSB 11.1.1.4 you would install WLS 10.3.4+oepe.
I'm not sure exactly what you mean when you say "I don't want to install any services".
If you mean you don't want to install OSB as a windows service, then don't. You will be able to start and stop the server with the startWeblogic.cmd file after installation.
If you mean you don't want to install OSB separately, then you won't be able to deploy to anything. OEPE just provides tools to work with OSB or Weblogic, it doesn't have a server as part of the software. If you are concerned about installing OSB, all of the configuration is stored in the "Oracle Home" directory, which you will specify yourself.
Does anybody here have positive experience of working with MS SQL Server 2005 from Rails 2.x?
Our developers use Mac OS X, and our production runs on Linux. For legacy reasons we should use MS SQL Server 2005.
We're using ruby-odbc and are running into various problems, too depressing to list here. I get an impression that we're doing something wrong.
I'm talking about the no-compromise usage, that is, with migrations and all.
Thank you,
Have you considered using JRuby? Microsoft has a JDBC driver for SQL Server that can be run on UNIX variants (it's pure Java AFAIK). I was able to get the 2.0 technology preview working with JRuby and Rails 2.1 today. I haven't tried migrations yet, but so far the driver seems to be working quite well.
Here's a rough sketch of how to get it working:
Make sure Java 6 is installed
Install JRuby using the instructions on the JRuby website
Install Rails using gem (jruby -S gem install rails)
Download the UNIX package of Microsoft's SQL Server JDBC driver (Version 2.0)
Unpack Microsoft's SQL Server driver
Find sqljdbc4.jar and copy it to JRuby's lib directory
jruby -S gem install activerecord-jdbcmssql-adapter
Create a rails project (jruby -S rails hello)
Put the proper settings in database.yml (example below)
You're all set! Try running jruby script/console and creating a model.
development:
host: localhost
adapter: jdbc
username: sa
password: kitteh
driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
url: jdbc:sqlserver://localhost;databaseName=mydb
timeout: 5000
Note: I'm not sure you can use Windows Authentication with the JDBC driver. You may need to use SQL Server Authentication.
Best of luck to you!
Ben
Instead of running your production server on Linux have you considered to run rails on Windows? I am currently developing an application using SQL Server and until know it seems to run fine.
These are the steps to access a SQL Server database from a Rails 2.0 application running on Windows.
The SQL Server adapter is not included by default in Rails 2. It is necessary to download and install it using the following command.
gem install activerecord-sqlserver-adapter
--source=http://gems.rubyonrails.org
Download the latest version of ruby-dbi from
http://rubyforge.org/projects/ruby-dbi/
and then extract the file from ruby-dbi\lib\dbd\ADO.rb
to C:\ruby\lib\ruby\site_ruby\1.8\DBD\ADO\ADO.rb.
Warning, the folder ADO does not exist, so you have to create it in advance.
It is not possible to preconfigure rails for SQL Server using the --database option, just create your application as usual and then modify config\database.yml in your application folder as follows:
development:
adapter: sqlserver
database: your_database_name
host: your_sqlserver_host
username: your_sqlserver_user
password: your_sqlserver_password
Run rake db:migrate to check your installation. If everything is fine you should not receive any error message.
I would strongly suggest you weigh up migrating from the legacy database. You'll probably find yourself in a world of pain pretty quickly. From experience, Rails and legacy schemas don't go too well together either.
I don't think there's a "nice solution" to this one, I'm afraid.
Our developers use Mac OS X, and our production runs on Linux. For legacy reasons we should use MS SQL Server 2005.
We are developing on Ubuntu 8.04, but our production servers are running Linux (Centos) and we are also using SqlServer 2005.
From our experiences the initial setup and config was quite painful - it took a couple of weeks to get everything to play nicely together. However, it's all seemless now, and I find SqlServer works perfectly well.
We use the FreeTDS ODBC drivers which once configured are fine.
DO NOT run productions Rails apps on Windows - you're asking for trouble. It's fine for development but nothing more. Rails doesn't scale well on Windows platforms.
Hope that helps.