Author Archives: Robins

Ansoft installation error_ ansys.exe ERROR:Error3221227010

Ansoft installation error_ ansys.exe ERROR:Error3221227010

Problem description solution

Problem description

The original Maxwell software cannot be opened after the window is updated

Due to the installation of several latest security patches for windows, Maxwell can not be opened and the problem can not be solved after the re installation, and the error has been reported all the time

resolvent

There is only one solution: uninstall the latest security updates, generally the package starting with kb457 *
Win + R Enter to view the update record & gt; uninstall update = = & gt; find the relevant update package and uninstall it.

Maven of springboot project pom.xml Unknown error in the first line of the file

Reason: the plug-in version of Maven is not compatible with IDE

Solution: add & lt; Maven jar to POM- plugin.version&gt ;3.1.1</maven-jar- plugin.version&gt That’s all

    <properties>
        < java.version&gt ;1.8         <spring- cloud.version&gt ; Greenwich.SR1&lt ;/spring- cloud.version&gt ;
        <maven-jar- plugin.version&gt ;3.1.1</maven-jar- plugin.version&gt ;
    </properties>

Android studio error Error:Could not Determine java version from ‘9.0.4’

The beginning of the matter is to export an APK with signature package and report an error Error:Execution failed for task ‘: app:compileReleaseJava ‘& gt; cannot find sys

At that time, my default setting location did not point to the correct JDK path, so an error was reported. Since I haven’t found my previous JDK for a long time, I went to the next version of JDK (9.0.4). Please pay attention to the latest version.

Then I try to export again and report an error: Error:Could not Determine java version from ‘9.0.4’

Then try again and continue to report errors Error:Gradle version 2.2 is required. Current version is 4.6. If using the gradle wrapper, try editing the distributionUrl in /Users//Desktop/gradle/wrapper/gradle- wrapper.properties to gradle-2.2- all.zip … because of the error caused by the inconsistency between the gradle version and the gradle version of as, modifying the gradle configuration file (there are many detailed solutions on the Internet) is of no use to me… Because after the change, an error is reported: could not initialize class com.android.repository . api.RepoManager Well, I gave up.

I began to think about why I encountered this series of problems at the beginning, right! Because of the latest version of JDK! So, I went to download a 1.8.0 JDK (download address), download and install it, change the JDK location of Android studio (Figure), and then gradle changed back to the old version, APK signature package export, success!!

So why should I download the latest JDK?:)

[development experience] solution to unexpected syntax error: unexpected identifier in JSON parsing

The solution of unexpected syntax error: unexpected identifier

Analysis of the causes of the solutions to errors

Error phenomenon

As shown in the title, this error occurs when the foreground parses the JSON object passed in the background. Other code is very simple, as follows:

$.getJSON("Index_ToDoList", { type: "GetBacklog" }, function (data) {
                   var rowData = eval('(' + data + ')');
                   alert(rowData[0].RiskNumber);
               }
        })

Results no matter how to test and modify, always report the above error. Online Baidu also many times, are saying less or more a “comma”, but tested the background, JSON format is no problem.

resolvent

One hour later, when I couldn’t figure out the solution, I suddenly found that in other code, the parsing was done by another method. I quickly tested the code as follows:

    $.ajax({
               url: 'Index_ToDoList?random=' + Math.random(),
               data: { "type": "GetBacklog" },
               success: function (data) {
                   var rowData = eval('(' + data + ')');
                   alert(rowData[0].RiskNumber);
               }
        })

It’s OK! The data is also parsed out!

Cause analysis

The most likely reason is that there is a problem with the version of jQuery quoted in this framework, or some code has been changed by others (I don’t have the ability to look up the code), so this writing method is feasible in this framework. It can be seen that maintaining the code left behind by others is such a pitfall, but sometimes, if you can’t rewrite the code, you have to be more careful!

Fatal error in launcher:

It’s wrong to build a virtual environment today, but why not

I tried the PIP command and found that it was the same error

I feel like it needs to be updated, and then I enter the update PIP command

python -m pip install –upgrade pip

Sure enough,

Pip is OK, but virtualenv still reports an error

So I updated virtualenv. Now it’s OK. The command is as follows

python -m pip install –upgrade virtualenv

 

Error in project operation org.springframework.beans . factory.BeanCreationException : error creating bean with name can be configured by

I encountered this problem because the JDK memory and Tomcat I configured were not large enough, so the project ran with an error. I solved this problem through configuration.

JDK configuration memory size

-Xms500m -Xmx1024m -XX:NewSize=800m -XX:MaxPermSize=800m

Run eclipse normally, open window preferences Java, and the page window will pop up

 

 

Tomcat configuration is divided into two steps

The first step is to configure in eclipse

-Xms500m -Xmx1024m -XX:NewSize=256m -XX:MaxPermSize=512m

 

Find the path to configure and install tomcat, enter the bin file, and install Tomcat 7 by myself

-Xms500m
-Xmx1024m
-XX:PermSize=64M
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=48m
– Duser.timezone=GMT +08

 

After the configuration is completed, there is no error in running the project! Problem solving

 

 

Eclipse reported an error: an error has occurred

Eclipse reported an error: an error has occurred

When installing maven, the JDK was updated from jdk9 to jdk11. However, when opening eclipse, after selecting workspace, the loading process stopped suddenly, and then the box: an error has occurred
It’s obviously a problem with the version of JDK, so I didn’t return to jdk9, but returned to the relatively stable jdk8.

Jdk8 official download link: https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

Sublime error: error while loading pyv8 binary:exit code three

The error information is:

The solution is: (Reference: https://blog.csdn.net/revitalizing/article/details/50086495 But slightly different)

1. Check the version of sublime

2. Access https://github.com/emmetio/pyv8-binaries Download the file according to the sublime version

3. Click “browse plug-in directory” to find the package directory

4. Unzip the compressed package to pyv8 directory

———————Successful solution, over————–

Error creating bean with name ‘sqlsessionfactory’ defined in ServletContext resource)

Error creating bean with name ‘sqlsessionfactory’ defined in ServletContext resource)

The general error report is as follows

error creating bean with name 'aaaService'......
error creating bean with name 'aaaMapper'......
error creating bean with name 'sqlSessionFactory'defined in ServletContext resource [XXXXXXXX.AAA.class]

From the Internet search a lot of solutions, are not my type. Finally, the problem has been solved;
solution:
reconfigure maven, download the relevant jar package, and then view the project’s pom.xml Whether there are redundant or missing dependencies in. (mine is in pom.xml There is one more dependency in. After deleting, the project will start normally.)

IntelliJ idea error: error: Java does not support release 5

Recommended solution: thanks to another blogger in the comments area, Fu moon, for his solution: https://blog.csdn.net/qq_ 42583206/article/details/108375173   

If the problem is solved in the above way, it can be ignored below.    

—————————————————————————————————————————————————————————————————————————————–

A new Maven project is created in IntelliJ idea. The running error is as follows: error: Java does not support release 5

Jdk9 is used for local operation. When testing Java stream operation, the error should be that the Java version used in the project compilation configuration is wrong. You need to check the Java compilation version configuration used in the project and environment.

Click “file” – & gt; “project structure” in IntelliJ to see if the Java version in “project” and “module” columns is consistent with the local version

 

If not, change to the local java version.

Click “Settings” – & gt; “bulid, execution, deployment” – & gt; “java compiler”, and set the target bytecode version to the local java version. (you can configure project bytecode version to local java version once and for all in default settings)

Default Settings:

After the above two steps have been configured, the above error will not be reported after re running.

 

Once and for all reform through labor:

Thanks to another blogger in the comments area, fumion, for his proposal: https://blog.csdn.net/qq_ 42583206/article/details/108375173