Debugging is also an attitude and an attitude.

Debugging is also an attitude and an attitude.

Today, when debugging the Excel report display, there was a big error because I didn't know what it was at the beginning? It was a little because I had been entangled with it for half a day and suddenly realized it. Next, let's record the path of this exploration.

I. Error body

There is a yellow warning in the bottom right corner of the browser, and then the interface is "yellow. Click to display the following error:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2 ;. net clr 2.0.50727 ;. NET CLR3.5.30729 ;. net clr 3.0.30729; Media Center PC 6.0; InfoPath.3 ;. NET4.0C ;. NET4.0E)

Timestamp: Mon, 1 Dec 2014 09:33:45 UTC

Error parsing:

1. The application version "Mozilla/4.0" indicates that you use the IE8 kernel in the Maxthon 2.0 Browser;

2. Version ID "MSIE7.0"

3. "Windows NT6.1" indicates "Windows 7 OS"

4. Trident kernel version "Trident/4.0", a browser kernel, and a WebKit Kernel

Ii. Exploration track solution 1:

At the beginning, I didn't think much about it, so I stuck the error body to Baidu. Most of the solutions are summarized as follows:

(1) register the browser version kernel in the Registry

1. Open your computer and Select Start> run in the lower left corner of the screen ".

2. Enter regsvr32 jscript. dll and select "OK"

3. Enter regsvr32 vbscript. dll again and select "OK"

4. A message indicating successful registration is displayed for the preceding two inputs. Indicates that you have successfully repaired your IE component. Clear IE and open the webpage.

Finally, click the Internet option tool on the IE browser page, delete cookies, and click Delete files. Remember to check all offline files.

(2) Upgrade the browser

If the above method does not work, upgrade the browser and restart the computer.

Sadly, both methods have been tried, but the results still do not work. But it is better that there is no yellow warning, but no data is displayed. Looking at the browser is really scratching your mind, thinking this is also an attitude!

Next, we can only find another method. This message indicates that the data has been transmitted from the underlying layer, but it cannot be displayed normally. Is there a problem with the data found? So I added a few breakpoints at the underlying layer for a little tracking, and the actual problem finally surfaced. I took this problem to find a second solution. As follows:

Cannot resolve the collationconflict between "Chinese_PRC_CI_AS" and "SQL _Latin1_General_CP1_CI_AS" in the equal to operation.

Solution 2:

This error occurs when the SQL statement is left connected or when the stored procedure is written. The cause of this error is that each table has its own sorting rules, when you connect them to a partition, a sorting rule conflict occurs. In this case, you need to unify the rules. As follows:

Join database_default.

    LEFT JOIN @table1 cpt on o.Part = cpt.ProductId COLLATEdatabase_default          select a1,a2 COLLATEdatabase_default from Call_id          union all          select a1,a2 COLLATEdatabase_default from Call_Detail

Iii. Summary

In this error, I realized my biggest blind zone:

First, you should have an attitude in your future work, and find a solution to the problem.

Second, when solving the problem, you should find a solution based on the cause of the problem. Do not check the problem on the Internet immediately. This may give you half the effort, so you must learn the right remedy, instead of doctors.