Category Archives: How to Fix

This application failed to start because it could not find or load the Qt platform plugin “windows”.

When running the file, prompt:
This Application failed to start because it could not find or load the Qt Platform plugin “Windows”.
Reinstalling the application may fix this problem.

solution:
1. Comment out the code related to matplotlib and find that the above error disappears, indicating that there is a problem with the package matplotlib, re-install
2 in conda environment. This Application failed to start because it could not find or load the Qtplatform Plugin… The version is too low, Upgrade pytorch
enter the anaconda prompt
activate environment conda activate pytorch
to upgrade PIP install --upgrade pytorch torchvision
to wait for installation conda install pytorch torchvision-c pytorch

Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: no furthe

Phenomenon:
When starting the project today, this project used Elasticsearch service. This error was found in the background:
Under Caused by: io.net ty. Channel. AbstractChannel $AnnotatedConnectException: Connection refused: no further information:/127.0.0.1:9300
The error message prompts as follows:

The reason:
This project USES Elasticsearch search service. In the error message, elasticSearch.transport and other key information are shown. In fact, this error is caused by Elasticsearch service which failed to launch successfully.
Solutions:
Restart the Elasticsearch service (if it doesn’t work at one time, try shutting it down and restarting it again).

I rebooted it several times before It worked. Don’t lose heart

The Excel connection manager is not supported in the 64-bit version of SSIS [Switch]

Microsoft SQL Server 2008 R2 — & GT; SQL SERVER Business Intelligence Development Studio
Using the EXCEL data source or target reported the following error
Start the SSIS Package “package.dTSx”.
message: 0x4004300A, located in data flow task, ssis. Pipeline: validation phase is beginning.
error: 0xC00F9304, located in the Package, connection manager “Excel connection manager 1” : SSIS error code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: because there is no OLEDB access interface available, Excel connection manager is not supported in the 64-bit version of SSIS.
error: 0 xc020801c, located in the data flow task, Excel source [89] : SSIS DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER error code. The AcquireConnection method call to connection manager “Excel Connection Manager 1” failed with error code 0xC00F9304. An error message may have been sent prior to this, providing detailed information about why the AcquireConnection method call failed.
error: 0xC0047017, located in data flow task, ssis. Pipeline: component “Excel source” (89) fails validation, returns error code 0xC020801C.
error: 0xC004700C, on data flow task, ssis. Pipeline: one or more components fail validation.
error: 0xC0024107, error occurs during data flow task: task validation.
SSIS Package “package.dtsx” completed: failed.
Solution: Select the item, right-click the properties shown in the figure, and change Run64BitRuntime to FALSE
[Excel Destination [31]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager “Excel Connection Manager” failed with error code 0xC00F9304. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available.

 

Reproduced in: https://www.cnblogs.com/qiangshu/p/5238161.html

VUEJS Failed to execute ‘removeChild’ on ‘Node’: The node to be removed is not a child of

Failed to execute ‘removeChild’ on ‘Node’ : The Node to be removed is not a child of this Node.

in my previous post
VUEJS project practice 5 Dialog pop-up box MessageBox (very nice bootstrap style)
has introduced a MesageBox style combined with bootstrap style
Then in the previous post
VUEJS project practice 4 custom keyboard instructions (keystrokes to get focus)
introduced a way for keystrokes to automatically get focus and trigger events.
Now when MessageBox binds Enter, an error
messagebox.vue?Cb02 :80 Uncaught DOMException: Failed to execute ‘removeChild’ on ‘Node’ : The Node to be removed is not a child of this Node.

First post the message.vue file

<template>
  <div v-key-bind-listen>
      <div class="msgBox" v-show="isShowMessageBox">
        <div class="msgBox_header">
          <div class="msgBox_title">
            <h3>{{ title }}</h3>
          </div>
        </div>

        <div class="msgBox_content">
          <p>{{ content }}</p>
        </div>

        <div class="msgBox_btns">
          <button type="button" class="btn btn-lime btn-lg" id="confirmBtn" @click="confirm"  bind_key="ENTER">确定</button>
          <button type="button" class="btn btn-dark btn-lg" id="cancelBtn" @click="cancel"  bind_key="ESC">取消</button>

        </div>

      </div>
  </div>
</template>

<script>
  export default {
    name: 'messageBox',
    data(){
      return {
        title: '',
        content: '',
        isShowMessageBox: false,
        resolve: '',
        reject: '',
        promise: '' // 保存promise对象
      }
    },
    methods: {
      close(state){
        this.model.show = false;
        if(this.model.callback){
          this.model.callback(state);
        }
      },
    // 确定,将promise断定为resolve状态
    confirm: function () {
      this.isShowMessageBox = false;
      this.resolve('confirm');
      this.remove();
    },
    // 取消,将promise断定为reject状态
    cancel: function () {
      this.isShowMessageBox = false;
      this.reject('cancel');
      this.remove();
    },
    // 弹出messageBox,并创建promise对象
    showMsgBox: function () {
      this.isShowMessageBox = true;
      this.promise = new Promise((resolve, reject) => {
        this.resolve = resolve;
        this.reject = reject;
      });
      // 返回promise对象
      return this.promise;
    },
    remove: function () {
      setTimeout(() => {
        this.destroy();
      }, 300);
    },
    destroy: function () {
      this.$destroy();
      document.body.removeChild(this.$el);
    }
  }
  }
</script>

<style scoped>
  .msgBox {
    position: fixed;
    z-index: 4;
    left: 50%;
    top: 35%;
    transform: translateX(-50%);
    width: 420px;
    background-color: black;
    opacity: 0.55;
  }

  .msgBox_header {
    padding: 20px 20px 0;
  }

  .msgBox_title {
    padding-left: 0;
    margin-bottom: 0;
    font-size: 26px;
    font-weight: 800;
    height: 18px;
    color: #fff;
  }

  .msgBox_content {
    padding: 30px 20px;
    color: #fff;
    font-size: 18px;
    font-weight: 200;
  }

  .msgBox_btns {
    padding: 10px 20px 15px;
    text-align: right;
    overflow: hidden;
  }

  @keyframes show-messageBox {
    from {
      opacity: 0;
    }
    to {
      opacity: 1;

    }
  }

  @keyframes bounce-in {
    from {
      opacity: 0;
    }
    to {
      opacity: 1;

    }
  }


</style>

The V-key-bind-listen instruction defined here is used for key listening. For details, please refer to the previous blog. It would be boring to write it again.
VUEJS project practice four custom keyboard commands (keys to get focus)
When you press ESC to cancel, there is no problem
when you press ENTER to confirm, the error will appear in the newspaper
messagebox.vue?Cb02:80 Uncaught DOMException: Failed to execute ‘removeChild’ on ‘Node’ : The Node to be removed is not a child of this Node.
Error is located via console.

>
add a line of logs in the destroy method. The console prints this.$el.

console.log(this.$el)

Add a line of logs to determine if this.$el is a child of the body

console.log(document.body.contains(this.$el))

1716438 – Error :” Failed to load database information Details: The Database connector crdb_bwquery.

symptom (of an illness)

Error: “Failed to load database information details: database connector crdb_bwquery.dll could not be loaded” in Crystal Reports 2011 with old report. The newly created report works fine using the “SAP BW MDX Query Driver”.

 

environment

Crystal Reports 2011 SAP BW 7.x

Copy this question

Start Crystal Reports 2011 Designer and connect to SAP BW system, the report is saved in step 2 Refresh the report. i Display the error message “Failed to load database information details: database connector crdb_bwquery.dll could not be loaded”.

result in

crdb_bwquery. dll is used by the legacy SAP BW query drivers that are no longer available from Crystal Reports 2011. They were provided in CR 2008 so that already created reports using the legacy drivers can still be used, and the reports can be recreated using the new drivers. “SAP BW MDX Query Driver”

resolutions

    1. Open the report in the Crystal Reports 2008 or 2011 designer. Browse Database -> Set the data source location. Create a new connection using the “SAP BW MDX Query Driver”. Under the newly created connection, browse to the query used in the current reportClick update. If there are variables in the query, they will be prompted. Map the required fields that are handled or fetched differently by the new driver. Execute the report. </ ol>
    Note: Mapping fields can be complicated because the two drivers treat back-end objects like hierarchies differently, and in some cases, re-creating the report is the only option. In some cases, field names and types also change, so some formulas may need to be type-converted before the report can fetch data.

keywords

crdb_bwquery. crdb_bwquery. cr2011 database error, sap bw mdx query driver, sap bw query driver

symptom (of an illness)

Error: “Failed to load database information details: database connector crdb_bwquery.dll could not be loaded” in Crystal Reports 2011 with old report. The newly created report works fine using the “SAP BW MDX Query Driver”.

environment

Crystal Reports 2011 SAP BW 7.x

Copy this question

Start Crystal Reports 2011 Designer and connect to SAP BW system, the report is saved in step 2 Refresh the report. i Display the error message “Failed to load database information details: database connector crdb_bwquery.dll could not be loaded”.

result in

crdb_bwquery. dll is used by the legacy SAP BW query drivers that are no longer available from Crystal Reports 2011. They were provided in CR 2008 so that already created reports using the legacy drivers can still be used, and the reports can be recreated using the new drivers. “SAP BW MDX Query Driver”

resolutions

    1. Open the report in the Crystal Reports 2008 or 2011 designer. Browse Database -> Set the data source location. Create a new connection using the “SAP BW MDX Query Driver”. Under the newly created connection, browse to the query used in the current reportClick update. If there are variables in the query, they will be prompted. Map the required fields that are handled or fetched differently by the new driver. Execute the report.
    Note: Mapping fields can be complicated because the two drivers treat back-end objects like hierarchies differently, and in some cases, re-creating the report is the only option. In some cases, field names and types also change, so some formulas may need to be type-converted before the report can fetch data.

keywords

crdb_bwquery. crdb_bwquery. cr2011 database error, sap bw mdx query driver, sap bw query driver

Modify samba configuration, restart service failed

Service restart samba dl@lx100: ~ $$
= = = verify org.freedesktop.systemd1.manage-units = = = =
Authentication is required to restart “samba.service”.
Authentication is: root
Password:
=== Authentication complete ===
Restart samba failed. Service:unit samba. the service is masked.

dll @lx100:~$ sudo systemctl restart smbd service

Start tomcat server error Context initialization failed

Severe: Context initialization failed
org. Springframework. Beans. Factory. BeanCreationException: Error creating bean with name ‘org.springframework.context.annotation.internalAsyncAnnotationProcessor’ defined in org.springframework.scheduling.annotation.ProxyAsyncConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.scheduling.annotation.AsyncAnnotationBeanPostProcessor]: Factory method ‘asyncAdvisor’ threw exception; nested exception is java.lang.IllegalArgumentException: @EnableAsync annotation metadata was not injected
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1123)
At…
Solution: In springMVC.xml configuration file will < context:component-scan base-package=”*”/>
Change the path of your own project class files to: < context:component-scan base-package=”com.srpingmvc.*”>
— — — — — — — — — — — — — — — — — — — — to interpret the following — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
Now let’s take a look at the SpringMVC.xml file to see why this is happening
< ?The XML version = “1.0” encoding = “utf-8”?>
< beans xmlns=”http://www.springframework.org/schema/beans”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xmlns:context=”http://www.springframework.org/schema/context”
xsi:schemaLocation=”http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-4.3.xsd “& gt;
 
< ! — Configure @Controller @service –>
< context:component-scan base-package=”com.springmvc.*”> < /context:component-scan>
< ! — View parser logical View, physical view –& GT;
< bean class= “org.springframework.web.servlet.view.InternalResourceViewResolver”>
< property name=”prefix” value=”/”> < /property>
< property name=”suffix” value= “.jsp”> < /property>
< /bean>
 
< /beans>
In the configuration file, base-package=”com.srpingmvc.*” means that all files under the com.springMVC folder will be scanned for the purpose of scanning
Register classes with specific annotations such as @Controller @Component # Repository and so on as beans in the Spring container.
The following is reproduced from: http://blog.csdn.net/zzjjiandan/article/details/22922847
The Spring configuration file is the “drawing” for directing the Spring factory to Bean production, dependency injection (assembly), and Bean instance distribution.
Java EE programmers must learn and flexibly apply this “drawing” to accurately express their “production intentions”.
The Spring configuration file is one or more standard XML documents. Applicationcontext.xml is the default configuration file for Spring.
When the container starts and cannot find the specified configuration document, an attempt is made to load the default configuration file.
The following is a relatively complete configuration file template. The basic purpose of each XML tag node in the document is also explained in detail.
These XML tag nodes will be used in the following knowledge points. After mastering the purpose of these XML nodes and attributes,
It provides a solid foundation for us to start writing configuration files.

 
 

Solve the error of dual system installation: the grub-efi-amd64-signed package failed to install into /target/.

When Windows 10 installed Ubuntu16.04 and dual systems, the grub-amd64- package could not be loaded into target. There were three steps to solve the problem.
1, choose to boot from the storage disk and is legacy only.
2, the startup disk will have two options in the startup TAB, one with the UEFI option, the other without, select no UEFI startup.
3, when assigning the boot location, do not assign the /boot option, for reasons shown here.
solve!

Error: Failed to synchronize cache for repo ‘fedora’

When executing DNF Update, you encountered the following problem:

[zhangz@zwfedora23 ~]$ sudo dnf update
[sudo] password for zhangz:
    Error: Failed to synchronize cache for repo 'fedora'
[zhangz@zwfedora23 ~]$

Later, it was found that the agent problem was set before:

  1 [main]
  2 gpgcheck=1
  3 installonly_limit=3
  4 clean_requirements_on_remove=True
  5
  6 #proxy=http://10.0.13.109:808
~
~
~
~
~
~
~
~
~
~
~
/etc/dnf/dnf.conf [TYPE=] [POS=0006,0001][100%] [LEN=6]
"/etc/dnf/dnf.conf" [readonly] 6L, 103C

Just comment out the proxy line above.
all the existing proxy line, because I need a proxy in the company, otherwise when I connect to the external network, direct dial-up Internet at home there is no proxy problem, the 10 network segment of the LAN address does not exist, so the use of DNF will prompt an error.

GoogleIO 2013 Android fast networking framework Volley introduction

Recently, I investigated the Android development framework, looked at XUtils, KjFramework and other frameworks of HTTP modules, I think it is too simple, but simply encapsulate HttpUrlConnenction and Handler, added a callback function, I feel it is better than to write a little bit. Later I found Volley, a relatively reliable Android network request framework, and used it.
Volley is the network communication library on the Android platform, making network communication faster, simpler, and more robust.
is the origin of Volley’s name: a burst or emission of many things or a large amount at once
in Google IO’s speech, the picture is a picture of firing arrows, which is similar to meteor.

in fact, from this picture, we can also see that Volley is particularly suitable for scenarios with small amounts of data but heavy communication.

GoogleIO2013 Android Quick Networking Framework Volley

 Features offered by Volley

Asynchronous download of JSON, images, etc..
Sorting of network requests (scheduling)
Prioritization of network requests
cache
Multi-level cancellation requests
Linkage to Activity and Lifecycle (simultaneous cancellation of all network requests at the end of Activity)