I've installed the latest Firebird ADO.Net Provider (FirebirdSql.Data.FirebirdClient-4.5.1.0.msi) and the latest Firebird DDEX Provider (DDEXProvider-3.0.1.0.msi).
Both providers are registered in GAC.
FirebirdSql.VisualStudio.DataTools, Version=3.0.1.0, Culture=neutral, PublicKeyToken=bae6c78ccb0fcdb3, processorArchitecture=MSIL
FirebirdSql.Data.FirebirdClient, Version=4.5.1.0, Culture=neutral, PublicKeyToken=3750abcc3150b00c, processorArchitecture=MSIL
The Firebird ADO.Net Provider is also registered in the "DbProviderFactories" Node of the machine.config (for both x86 and x64).
<add name="FirebirdClient Data Provider" invariant="FirebirdSql.Data.FirebirdClient" description=".NET Framework Data Provider for Firebird" type="FirebirdSql.Data.FirebirdClient.FirebirdClientFactory, FirebirdSql.Data.FirebirdClient, Version=4.5.1.0, Culture=neutral, PublicKeyToken=3750abcc3150b00c"/>
I'm trying to create a new Database Connection using the DDEX Provider in VS2013 SP3, but it's not
working. When I change any values in the "Firebird Data Source" connection dialog, the dialog disappears.
I debugged VS2013 in background with a 2nd VS2013 Instance and got this Output messages, while the connection dialog disappears:
FbDataConnectionUIControl::LoadProperties()
Eine Ausnahme (erste Chance) des Typs "System.NullReferenceException" ist in FirebirdSql.VisualStudio.DataTools.dll aufgetreten.
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei FirebirdSql.VisualStudio.DataTools.FbDataConnectionUIControl.LoadProperties()
FbDataConnectionUIControl::LoadProperties()
Eine Ausnahme (erste Chance) des Typs "System.NullReferenceException" ist in FirebirdSql.VisualStudio.DataTools.dll aufgetreten.
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei FirebirdSql.VisualStudio.DataTools.FbDataConnectionUIControl.LoadProperties()
Eine Ausnahme (erste Chance) des Typs "System.NullReferenceException" ist in FirebirdSql.VisualStudio.DataTools.dll aufgetreten.
Any ideas how I can get the provider to run or where I can look for other prerequisites?
I had a similar problem and after a week of googling I think I have found a fix.
Download and install the following:
Visual Studio SDK
Firebird ADO.NET Data Provider
Firebird DDEX Provider
When installing the providers, make sure to click on the "Advanced" button. This is needed for installing the DDEX provider as it will give you a chance to choose which versions of Visual Studio it will get installed on. Installation on the GAC and registry should be taken care of by the DDEX installer.
HTH.
I had a similar problem. I removed the FirebirdSql.Data.FirebirdClient.dll from the GAC, uninstalled and reinstalled DDEX and registered the firebird client in C:\Program Files (x86)\FirebirdClient\FirebirdSql.Data.FirebirdClient.dll (which i downloaded as an msi installer from firebirdsql.org
Not sure if this will fix your problem but worth a try.
Related
I have a:
Windows 2019 server
IBM DB2: Version 11.5.0
"v11.5.7_ntx64_universal_fixpack"
I want to update the DB to Version 11.5.7 with this "v11.5.7_ntx64_universal_fixpack".
a.) I doublclick the "setup.exe"
b.) On the launchpad, I choose under "Install Product", working with an existing installation
c.) then I choose my Edition and click button to start
==> I get the message: "Error applying transforms. Verify that the specified transform paths are valid."
In the log I have the following text:
*DEBUG: Error 2254: Database: Transform: Cannot update row that doesn't exist. Table: Property
1: 2254 2: 3: Property
Error applying transforms. Verify that the specified transform paths are valid.
C:\Windows\Installer\2641882f.mst
MSI (c) (B4:44) [11:15:10:831]: Produkt: DB2 Server Edition -- Installation fehlgeschlagen.
MSI (c) (B4:44) [11:15:10:831]: Windows Installer installed the product. Product Name: DB2 Server Edition. Product Version: 11.5.7000.1973. Product Language: 1031. Manufacturer: IBM. Installation success or error status: 1624.*
I search for a solution some day but have found nothing. Has somebody an idea or an idea?
thank you
Regards
Tino
Now, I have found the solution myself:
https://www.ibm.com/support/pages/applying-db2-v115-fix-pack-windows-fails-error-applying-transforms-any-language-other-english
In my system, the path was another. I have found the correct path to the files with regedit, and now the update works perfectly.
(I am using a german Windows Server 2019, so bear with me. I try to translate everything to recognizable english ui equivalents)
The goal is to create a GPO to install a .msi file to client computers. Everytime I try to create the GPO, it says
Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct.
The Windows Event Log outputs a warning and then an error(translated by me).
Warning:
Warning: Event 119, Software Installation
While reading the msi file \\dc1\gpo\Install\AnyDesk_Client_v2.msi, an unexpected error occured. The error is not severe enough to cancel the operation. The following error occured: The operation was completed successfully
Original german text:
Beim Lesen der MSI-Datei \\dc1\gpo\Install\AnyDesk_Client_v2.msi ist ein unerwarteter Fehler aufgetreten. Der Fehler ist nicht schwerwiegend genug, um den Vorgang abzubrechen. Folgender Fehler ist aufgetreten: Der Vorgang wurde erfolgreich beendet.
Error:
Error: Event 103, Software Installation
The Software Installation could not deliver/prepare the package AnyDesk_Client_v2.msi. The following error occured: The directory name is invalid
Original german text:
Die Softwareinstallation konnte das Paket AnyDesk_Client_v2.msi nicht bereitstellen. Folgender Fehler ist aufgetreten: Der Verzeichnisname ist ungültig.
What I tried:
Using another msi. Used the standard Anydesk.msi (so no "_" in the filename). I tried the Teams x64 .msi from MS Teams MSI Download. I tried a Futuremark_SystemInfo.msi I had
lying around.
I put all the files in \dc1\NETLOGON and tried again. I put all the files in \dc1\SYSVOL and tried again. I checked that authenticated users had access to the share. I logged on directly on the Domain Controller as Domain Admin via RDP. I logged directly on the Domain Controller via VMRC (it's a virtual environment). I checked if I can access the shares I put the .msi's in (I can). I got a tip that says
Go to Default Domain Controllers Policy
Expand Computer Configuration\Windows Settings\Administrative Templates\System\Netlogon
Change the Netlogon and Sysvol Compatibility to enabled (2 seperate settings)
This does not work because there is no Computer Configuration\Windows Settings\Administrative Templates - it is Computer Configuration\Administrative Templates. But there is no setting to enable NETLOGON/SYSVOL Compatibility underComputer Configuration\Administrative Templates. I assume this is a tip relating to an older Windows Server version.
I recently tried to add more Reports to our Jasper Server to distribute them to those who need them.
This worked with the first Report I uploaded, but when trying to upload new ones, on trying to execute them through the Server I get an Error message.
The following is what I've extracted from the log:
2021-03-19T12:56:31,694 ERROR AsyncJasperPrintAccessor,pool-5-thread-9:321 - Error during report execution com.jaspersoft.jasperserver.api.JSSecurityException: Ein Fehler ist aufgetreten. Wenden Sie sich an Ihren Systemadministrator. (6632)
Arguments:
at com.jaspersoft.jasperserver.api.security.validators.Validator.newSecurityException(Validator.java:544)
at com.jaspersoft.jasperserver.api.security.validators.Validator.validateSQL(Validator.java:533)
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:148)
at net.sf.jasperreports.engine.fill.JRFillDataset.createQueryDatasource(JRFillDataset.java:1257)
at net.sf.jasperreports.engine.fill.JRFillDataset.initDatasource(JRFillDataset.java:726)
at net.sf.jasperreports.engine.fill.JRFillDatasetRun.evaluate(JRFillDatasetRun.java:249)
at net.sf.jasperreports.engine.fill.JRFillElementDataset.evaluateDatasetRun(JRFillElementDataset.java:259)
at net.sf.jasperreports.engine.fill.JRFillCrosstab.evaluate(JRFillCrosstab.java:678)
at net.sf.jasperreports.engine.fill.JRFillElementContainer.evaluate(JRFillElementContainer.java:383)
at net.sf.jasperreports.engine.fill.JRFillBand.evaluate(JRFillBand.java:548)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummaryNoLastFooterSamePage(JRVerticalFiller.java:1238)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillSummary(JRVerticalFiller.java:1189)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReportEnd(JRVerticalFiller.java:297)
at net.sf.jasperreports.engine.fill.JRVerticalFiller.fillReport(JRVerticalFiller.java:117)
at net.sf.jasperreports.engine.fill.JRBaseFiller.fill(JRBaseFiller.java:615)
at net.sf.jasperreports.engine.fill.BaseFillHandle$ReportFill.run(BaseFillHandle.java:135)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$SynchronousExecutor.execute(EngineServiceImpl.java:956)
at net.sf.jasperreports.engine.fill.BaseFillHandle.startFill(BaseFillHandle.java:181)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$AsynchronousReportFiller.fillReport(EngineServiceImpl.java:907)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl.fillReport(EngineServiceImpl.java:1842)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runWithDataSource(EngineServiceImpl.java:1159)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportFill.runReport(EngineServiceImpl.java:1100)
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$ReportRunnable.run(EngineServiceImpl.java:978)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
But since I am not using code to generate report I can't quite interpret the messages.
Can anybody tell me, why executing the report fails on the server, but is successful in the Jaspersoft Studio?
Both are running on the same Virtual Machine.
IT seems the developer handling this particular report started his queries with "which ..." which broke security rules set by Jaspersoft server by default, this has been changed, and reports do now properly generate when executed via the server
In Dynamics CRM 2016 on-premise, I need to read in a plugin some information from another Dynamics CRM 2016 on-premise.
I am trying to use use Microsoft.Xrm.Tooling.Connector to get a CrmServiceClient object for getting information from the remote Dynamics CRM.
I can register the plugin but when the step of the plugin is triggered I receive an error message:
Business Process Error
Impossible de charger le fichier ou l'assembly 'Microsoft.Xrm.Tooling.Connector, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ou une de ses dépendances. Le fichier spécifié est introuvable.
I want to know if this is the right way to get information from another CRM in the context of a plugin, and how can I resolve the above error.
Thank you
Radu
The Microsoft.Xrm.Tooling.Connector.dll is not available on the CRM Server, because it is a client-side library.
You need to make it available on the server by adding it (and any dependencies) to the GAC (on each CRM server) or including it with the assembly using ILMerge.
We are trying to deploy our unmanaged solution from our development system as a managed solution to our production system, as we do regularly.
We are now getting a deployment failure: the deployment rolls back. I download the deployment report: It shows that all entities and diagrams are deployed and that the dashboards (next item on the list) were not started. No issue is shown.
Then I run a trace on the server. It shows a "duplicate key" exception: "inserted element already exists". But there is no real indication which record is causing the conflict.
Crm Exception: Message: Import failed, ErrorCode: -2147188706, InnerException: System.ArgumentException: Ein Element mit dem gleichen Schlüssel wurde bereits hinzugefügt.
bei System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
bei Microsoft.Crm.Tools.ImportExportPublish.IgnoreCustomizedReportsTreeInNonOverwriteMode.FindExistingRelations(XmlNodeList reports, Guid solutionId)
bei Microsoft.Crm.Tools.ImportExportPublish.IgnoreCustomizedReportsTreeInNonOverwriteMode.Execute(IXPathNavigable reportsRoot, ExecutionContext context)
bei Microsoft.Crm.Tools.ImportExportPublish.ReportPreImportHandler.ExecutePreImportSteps(XmlNode reportsNode, ExecutionContext context)
bei Microsoft.Crm.Tools.ImportExportPublish.ImportReportsHandler.ImportItem()
bei Microsoft.Crm.Tools.ImportExportPublish.ImportHandler.Import()
bei Microsoft.Crm.Tools.ImportExportPublish.RootImportHandler.ImportAndUpdateProgress(ImportHandler ih)
bei Microsoft.Crm.Tools.ImportExportPublish.RootImportHandler.ProcessMetadataHandlers(String[] ImportEntities, Hashtable ht, String& curPath, ImportHandler& ihForCurrentPath, CounterList listCounters)
bei Microsoft.Crm.Tools.ImportExportPublish.RootImportHandler.RunImport(String[] ImportEntities)
Question: How do other programmers hunt this kind of issue?
It is an on-premise installation.
We solved the issue. For an unknown reason we had all Dynamics standard reports twice in our solution. They are also now present twice on the development system. Since those are managed reports, we can't delete them from the development system. But we removed them from the solution. Now deployment is working again.
There are still some open questions:
a) Why are the reports present twice on the dev system and in the solution?
b) Why is it a problem to import the reports twice to the prod system when they obviously coexist in the dev system.