Install License on Windows/Sql Server Cluster

I have just taken over the project, but the previous developers said that the PGNP license was failing to verify when installing on our Sql Server 2012 failover cluster. They believed that setup was reading the wrong computer name. I will be researching this but thought I would ask anyway, before I really have any details, to see if this is already a known problem. I saw in the product history that a bug was fixed related to licensing on a sql cluster in version 1.4.0.3132, and we just purchased version PGNP-Postgres-SE-1.4.0.3200. Any help will be much appreciated to give me a head start on this problem, as it is impacting production processing because ODBC is too slow. Thanks!

The PGNP Provider supports cluster environment. We have previously fixed bugs in reading VSN, and in activation on active/inactive nodes.

However, the current build (3206) still has a minor issue related to the access to the license file from SQL Server account (in some clusters). The workaround is to grant permission for the user account to the license file folder C:/ProgramData/Intellisoft/PGNP.

Thank you so much! I have reinstalled the driver on both nodes this morning and it accepted the key and I successfully run tests by moving data from our postgres data source into sql server instances on both (active/active) nodes. So I have had no problems with my test. Your answer may still save the day because I am an admin on everything, so perhaps the folder permission may come into play when the developers start testing it. I really appreciate your timely response!

I deployed the package to Integration Services Catalogs in Sql Server, and ran into the error our developers have. I opened up the folder as you mentioned to read access, then to full control, and still get the same error message.

pgnp_test:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "PGNP" Hresult: 0x80004005 Description: "Invalid License".

This is affecting our production processing since the ODBC driver as you can imagine is extremely slow. Any ideas please?

Executing through the 'Execute Package Utility' still works fine for me, executing through SSMS Integration Services Catalogs fails.

Yes, this issue is related to the permissions. Please find which user account is used for running the package. It could be Network Admin, or rather a dedicated SQL Server account.

There are many ways of determining the user account. One possibility is to use Process Explorer from sysinternals.com, and search for pgnp.dll/pgnp64.dll after the "invalid license" error occurred. The process that loaded the dll(s) is not having access to the C:\ProgramData\Intellisoft\PGNP folder.