500 Internal Server Error
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator,
[no address given] and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.
More information about this error may be available
in the server error log.升级adt插件后，eclipse突然出现Unable to build: the file dx.jar was not loaded from the SDK folder 错误Unknown error: Unable to build: the file dx.jar was not loaded from the SDK folder!&升级adt插件后，eclipse突然出现上面错误，无法运行android项目。网上搜索了很多方法试过了都不行，clean，换workspace目录，把tools下的dx.jar拷贝到对应platform下面也不行，重启eclipse，更新sdk都不行。最终在stackoverflow上搜索到一个方法试了以后才可以platform-tools\lib folder was missing after upgrade (my eclipse was open). close eclipse, using sdk manager uninstall and install "Android SDK platform-tools".即先关闭eclipse，打开sdk安装目录下的SDK Manager.exe 顶部Tools 下面的两个勾选上以后点击下面的 Install packages 按钮更新，更新完成后启动eclipse就可以了注：后来在另外一台电脑发现，如果sdk没有更新到最新版Tools下面的两个包是安装不了的，所以必须先更新sdk然后再更新Tools才行。&-----------------------------------------------------------------------另：升级adt的原因是eclipse突然无法生成R.java文件， 网上搜索了很多方法最终升级adt后可以生成R.java了但又出现了上面无法运行的情况。根本原因就是最终android sdk升级了，必须都升级到最新的才能正常使用。&详细请看另外一篇博客&&&
阅读(...) 评论()From Wikibooks, open books for an open world
Getting Started
Common Elements
Errors and Warnings
Technical Texts
Special Pages
Special Documents
Creating Graphics
Programming
Miscellaneous
Help and Recommendations
Appendices
LaTeX describes what it is typesetting while it does it. If it encounters something it doesn't understand or can't do, it will display a message saying what is wrong. It may also display warnings for less serious conditions.
Don't panic if you see error messages: it is very common to mistype or misspell commands, forget curly braces, type a forward slash instead of a backslash, or use a special character by mistake. Errors are easily spotted and easily corrected in your editor, and you can then run LaTeX again to check you have fixed everything. Some of the most common errors are described in next sections.
The format of an error message is always the same. Error messages begin with an exclamation mark at the start of the line, and give a description of the error, followed by another line starting with the number, which refers to the line-number in your document file which LaTeX was processing when the error was spotted. Here's an example, showing that the user mistyped the \tableofcontents command:
! Undefined control sequence.
l.6 \tableofcotnetns
When LaTeX finds an error like this, it displays the error message and pauses. You must type one of the following letters to continue:
Stop immediately and exit the program.
Carry on quietly as best you can and don't bother me with any more error messages.
Stop the program but re-position the text in my editor at the point where you found the error (This only works if you're using an editor which LaTeX can communicate with).
Try to give me more help.
(followed by a correction) means input the correction in place of the error and carry on (This is only a temporary fix to get the file processed. You still have to make that correction in the editor).
run in non-stop mode. Plow through any errors, unless too many pile up and it fails (100 errors).
Some systems (Emacs is one example) run LaTeX with a "nonstop" switch turned on, so it will always process through to the end of the file, regardless of errors, or until a limit is reached.
Warnings don't begin with an exclamation mark: they are just comments by LaTeX about things you might want to look into, such as overlong or underrun lines (often caused by unusual hyphenations, for example), pages running short or long, and other typographical niceties (most of which you can ignore until later). Unlike other systems, which try to hide unevennesses in the text (usually unsuccessfully) by interfering with the letter spacing, LaTeX takes the view that the author or editor should be able to contribute. While it is certainly possible to set LaTeX's parameters so that the spacing is sufficiently sloppy that you will almost never get a warning about badly-fitting lines or pages, you will almost certainly just be delaying matters until you start to get complaints from your readers or publishers.
Only a few common error messages are given here: those most likely to be encountered by beginners. If you find another error message not shown here, and it's not clear what you should do, ask for help.
Most error messages are self-explanatory, but be aware that the place where LaTeX spots and reports an error may be later in the file than the place where it actually occurred. For example if you forget to close a curly brace which encloses, say, italics, LaTeX won't report this until something else occurs which can't happen until the curly brace is encountered (e.g. the end of the document!) Some errors can only be righted by humans who can read and understand what the document is supposed to mean or look like.
Newcomers should remember to check the list of special characters: a very large number of errors when you are learning LaTeX are due to accidentally typing a special character when you didn't mean to. This disappears after a few days as you get used to them.
! Too many }'s.
l.6 \date December 2004}
The reason LaTeX thinks there are too many }'s here is that the opening curly brace is missing after the \date control sequence and before the word December, so the closing curly brace is seen as one too many (which it is!). In fact, there are other things which can follow the \date command apart from a date in curly braces, so LaTeX cannot possibly guess that you've missed out the opening curly brace until it finds a closing one!
! Undefined control sequence.
{December 2004}
In this example, LaTeX is complaining that it has no such command ("control sequence") as \dtae. Obviously it's been mistyped, but only a human can detect that fact: all LaTeX knows is that \dtae is not a command it knows about: it's undefined. Mistypings are the most common source of errors. Some editors allow common commands and environments to be inserted using drop-down menus or icons, which may be used to avoid these errors.
! Missing $ inserted
A character that can only be used in the mathematics was inserted in normal text. If you intended to use mathematics mode, then use $...$ or \begin{math}...\end{math} or use the 'quick math mode': \ensuremath{...}. If you did not intend to use mathematics mode, then perhaps you are trying to use a
that needs to be entere for example _ will be interpreted as a subscript operator in mathematics mode, and you need \_ to get an underscore character.
This can also happen if you use the wrong character encoding, for example using utf8 without "\usepackage[utf8]{inputenc}" or using iso8859-1 without "\usepackage[latin1]{inputenc}", there are several character encoding formats, make sure to pick the right one.
Runaway argument?
{December 2004 \maketitle
! Paragraph ended before \date was complete.
&to be read again&
In this error, the closing curly brace has been omitted from the date. It's the opposite of the error of too many }'s, and it results in \maketitle trying to format the title page while LaTeX is still expecting more text for the date! As \maketitle creates new paragraphs on the title page, this is detected and LaTeX complains that the previous paragraph has ended but \date is not yet finished.
Underfull \hbox (badness 1394) in paragraph
at lines 28--30
[][]\LY1/brm/b/n/10 Bull, RJ: \LY1/brm/m/n/10
Ac-count-ing in Busi-
This is a warning that LaTeX cannot stretch the line wide enough to fit, without making the spacing bigger than its currently permitted maximum. The badness (0-10,000) indicates how severe this is (here you can probably ignore a badness of 1394). It says what lines of your file it was typesetting when it found this, and the number in square brackets is the number of the page onto which the offending line was printed. The codes separated by slashes are the typeface and font style and size used in the line. Ignore them for the moment.
This comes up if you force a linebreak, e.g., \\, and have a return before it. Normally TeX ignores linebreaks, providing full paragraphs to ragged text. In this case it is necessary to pull the linebreak up one line to the end of the previous sentence.
This warning may also appear when inserting images. It can be avoided by using the \textwidth or possibly \linewidth options, e.g. \includegraphics[width=\textwidth]{image_name}
Overfull \hbox (9.11617pt too wide) in paragraph
at lines 860--861
[]\LY1/brm/m/n/10 Windows, \LY1/brm/m/it/10 see
\LY1/brm/m/n/10 X Win-
An overfull \hbox means that there is a hyphenation or justification problem: moving the last word on the line to the next line would make the spaces in the line wider th keeping the word on the line would make the spaces smaller than the current limit, so the word is left on the line, but with the minimum allowed space between words, and which makes the line go over the edge.
The warning is given so that you can find the line in the code that originates the problem (in this case: 860-861) and fix it. The line on this example is too long by a shade over 9pt. The chosen hyphenation point which minimizes the error is shown at the end of the line (Win-). Line numbers and page numbers are given as before. In this case, 9pt is too much to ignore (over 3mm), and a manual correction needs making (such as a change to the hyphenation), or the flexibility settings need changing.
If the "overfull" word includes a forward slash, such as "input/output", this should be properly typeset as "input\slash output". The use of \slash has the same effect as using the "/" character, except that it can form the end of a line (with the following words appearing at the start of the next line). The "/" character is typically used in units, such as "mm/year" character, which should not be broken over multiple lines.
The warning can also be issued when the \end{document} tag was not included or was deleted.
To easily find the location of overfull hbox in your document, you can make latex add a black bar where a line is too wide:
\overfullrule=2cm
! LaTeX Error: File `paralisy.sty' not found.
Type X to quit or &RETURN& to proceed,
or enter new name. (Default extension: sty)
Enter file name:
When you use the \usepackage command to request LaTeX to use a certain package, it will look for a file with the specified name and the filetype .sty. In this case the user has mistyped the name of the paralist package, so it's easy to fix. However, if you get the name right, but the package is not installed on your machine, you will need to download and install it before continuing. If you don't want to affect the global installation of the machine, you can simply download from Internet the necessary .sty file and put it in the same folder of the document you are compiling.
Although this is a warning from the Babel package and not from LaTeX, this error is very common and (can) give some strange hyphenation (word breaking) problems in your document. Wrong hyphenation rules can decrease the neatness of your document.
Package babel Warning: No hyphenation patterns were loaded for
the language `Latin'
I will use the patterns loaded for \language=0 instead.
This can happen after the usage of: (see )
\usepackage[latin]{babel}
The solution is not difficult, just install the used language in your .
If you previously set the X language, and then decided to switch to Y, you will get this error. This may seem awkward, as there is obviously no error in your code if you did not change anything. The answer lies in the .aux file, where babel defined your language. If you try the compilation a second time, it should work. If not, delete the .aux file, then everything will work as usual.
A reader requests expansion of this section to include more material.
You can help by
() or ask for assistance in the .
One common cause of (pdf)LaTeX getting stuck is forgetting to include \end{document}
There are several programs capable of checking LaTeX source, with the aim of finding errors or highlighting bad practice, and providing more help to (particularly novice) users than the built-in error messages.
nag () is a LaTeX package designed to indicate the use of obsolete commands.
lacheck () is a consistency checker intended to spot mistakes in code. It is available as source code or compiled for Windows and OS/2
chktex () is a LaTeX semantic checker available as source code for Unix-like systems.
: Hidden category:Cisco Unified Communications Manager Administration Guide, Release 7.1(2) - License File Upload
[Cisco Unified Communications Manager (CallManager)] - Cisco
Cisco Unified Communications Manager Administration Guide, Release 7.1(2)
Book Contents
Book Contents
Cisco Unified Communications Manager
System Configuration
Call Routing Configuration
Media Resource Configuration
Voice Mail Configuration
Device Configuration
Application Configuration
User Management Configuration
Cisco Unified Communications Manager Bulk Administration
Appendixes
Download Options
Book Title
Cisco Unified Communications Manager Administration Guide, Release 7.1(2)
Chapter Title
License File Upload
View with Adobe Reader on a variety of devices
Chapter: License File Upload
Chapter Contents
License File Upload
License files contain the information that is needed to enforce licenses for Cisco Unified Communications Manager. This chapter contains the following topics on uploading license files:
The Cisco Unified Communications Manager server where the license file is loaded assumes the functionality of a license manager. (The license file gets loaded on the first node only.) For information on license files, refer to the .
The license manager serves as the logical component that keeps track of the licenses that get purchased and used. It refers to the processes that control the checkin and checkout of the licenses. It keeps track of the number of license units that are required for each phone and application type. The license manager has responsibility for issuing and reclaiming licenses and for detecting whether an overdraft of licenses occurs.
Start the license manager service by using Cisco Unified Serviceability. This section describes the procedures to start, stop, or restart the service.
Note Because license manager is a network service, it automatically starts and runs after the Cisco Unified Communications Manager installation.
Step&1 In Cisco Unified Serviceability, choose Tools&& Control Center - Network Services.
The Control Center-Network Services window displays.
Step&2 Choose the Cisco Unified Communications Manager server from the Servers drop-down list box.
Step&3 Click the radio button for Cisco License Manager.
Step&4 If you want to start the License Manager service, click Start.
Step&5 If you want to stop the License Manager service, click Stop.
Step&6 If you want to restart the License Manager, click Restart.
Additional Information
Licensing helps manage Cisco Unified Communications Manager licenses and enforces the licenses for Cisco Unified Communications Manager applications and the number of devices. This section provides information on obtaining licenses for new Cisco Unified Communications Manager systems and/or device installations as well as for Cisco Unified Communications Manager nodes that have been upgraded from various releases.
Note You do not need to obtain new licenses if you are upgrading within a software release train, such as Cisco Unified Communications Manager 6.0(1) to 6.1(1).
To obtain a license, see the section that applies to your situation:
oIf you are installing new Cisco Unified Communications Manager or devices that require additional device license units, see the .
oIf you are upgrading from Cisco Unified CallManager 4.x, obtain a software feature license as described in
and then upgrade the product licenses as described in the .
oIf you are upgrading from supported versions of Cisco Unified Communications Manager 5.x or 6.x, see the .
Use the following procedure to obtain a node license file for new Cisco Unified Communications Manager nodes (servers) and to obtain device licenses for new devices that require additional device license units.
Each node in your cluster requires one node license unit. Each device type requires a fixed number of licenses units, depending on the type. For example, Cisco Unified IP Phone 7920 requires four license units, and Cisco Unified IP Phone 7970 requires five units. If you want licenses for four Cisco Unified IP Phones 7920 and four Cisco Unified IP Phones 7970 phones, you require 36 phone license units.
Cisco Unified Communications Manager contains a starter licenses that you can use to begin new installations of Cisco Unified Communications Manager. The system overwrites the starter license when you obtain and upload your permanent licenses. For more information on starter licenses, see the
section in the Cisco Unified Communications Manager System Guide.
You use the Product Authorization Key (PAK) that came with your product to obtain the necessary permanent licenses, as described in the following procedure.
Step&1 Enter the Product Authorization Key (PAK) that you received with your Cisco Unified Communications Manager or phone order in the License Registration web tool at .
Step&2 Click Submit.
Step&3 Follow the system prompts. You must enter the MAC address of the Ethernet 0 NIC of the first node of the Cisco Unified Communications Manager cluster. You must enter a valid e-mail address as well as the number of nodes and device license units for which you want licenses.
Note For information on calculating the number of device license units that are required for the devices in your system, refer to the .
The system sends the license file(s) to you via e-mail by using the E-mail ID that you provided. The format of a license file specifies CCM&timestamp&.lic. If you retain the&.lic extension, you can rename the license file. You cannot use the license if you edit the contents of the file in any way.
Note One license file may apply to more than one node in your cluster. For information on how to interpret the license file, see the .
Step&4 You must upload the license file to the server with the matching MAC address that you provided in . See the . This server then takes on the functionality of the license manager.
Note You can use the licenses that are specified in the license file only within the cluster on which the license file is uploaded.
Additional Information
A software feature license activates features on your system for the specified license version. To use previous device license versions with this version of Cisco Unified Communications Manager, make sure that you obtain the software feature license for the Cisco Unified Communications Manager version that is running on your system.
Use this procedure to obtain a software feature license:
Step&1 Navigate to the License Registration web tool at .
Step&2 Enter the Product Authorization Key (PAK) that you received with your Cisco Unified Communications Manager upgrade.
Step&3 Click Submit.
Step&4 Follow the system prompts. You must enter the MAC address of the Ethernet 0 NIC of the first node of the Cisco Unified Communications Manager cluster. You must also enter a valid e-mail address.
The system sends the license file to you via e-mail by using the e-mail address that you provided. To view the contents of a software feature license, refer to
in the Cisco Unified Communications Manager System Guide.
Step&5 You must upload the software license file to the server with the matching MAC address that you provided in . See the .
Step&6 If you are upgrading from Cisco Unified CallManager 4.x, perform the procedure that is described in the .
Additional Information
When you upgrade from supported Cisco Unified CallManager 4.x releases, the system calculates the licenses that are required for existing devices and existing nodes and generates an intermediate file (XML file) that contains this information. You use this file to obtain license files that you can import into Cisco Unified Communications Manager Administration. (Refer to .) Alternately, you can use the license file that Data Migration Assistant (DMA) generates. (Refer to .)
You receive these licenses free of cost because you are already using these phones for a Cisco Unified CallManager 4.x release.
Use either
to obtain licenses for Cisco Unified Communications Manager when you upgrade from supported 4.x releases.
Procedure 1
Step&1 When you use Data Migration Assistant to migrate your data, choose the Export & Storage Location & Destination Option for License File tool to specify a local directory destination for the license file licupgrade.lic
Note Do not specify a mapped network directory for the Local Directory. If you do, be aware that DMA may not be able to create the destination folder.
Step&2 Run DMA according to instructions in the Data Migration Assistant User Guide.
Step&3 Upgrade the Cisco Unified Communications Manager servers according to instructions in the document Upgrading Cisco Unified Communications Manager Release 7.1(2) from Cisco Unified Communications Manager 4.x Releases.
Step&4 Upload the license file to the server with the matching MAC address of the Ethernet 0 NIC of the first node of the Cisco Unified Communications Manager cluster.
Step&5 If your system requires additional device license units, you can obtain licenses for new devices that you are adding to the upgraded system. For detailed instructions, see the .
Procedure 2
Step&1 After you complete the Cisco Unified Communications Manager Administration upgrade process, as described in Upgrading Cisco Unified Communications Manager, navigate to Cisco Unified Communications Manager Administration and choose System&& Licensing&& License File Upload.
The License File Upload window displays.
Step&2 Choose the licugrade_&upgrade version&.lic file from the Existing Files drop-down list and click View File. The window refreshes and displays the license information for existing devices and nodes. Copy this information. To copy the contents on this window, you can use Ctrl-A (Select All) and Ctrl-C (Copy).
Step&3 Navigate to the License Registration web tool at .
Step&4 Enter the MAC address of the Ethernet 0 NIC of the first node of the Cisco Unified Communications Manager in the cluster.
Step&5 In the text box that is provided, paste the license file contents that you copied in
by using the appropriate keyboard shortcuts, such as Ctrl-V.
Step&6 Enter a valid e-mail address and click Continue. A license file generates.
The system sends the license file to you through e-mail by using the e-mail address that you provided.
Step&7 You must upload the license file to the server with the matching MAC address that you provided in . See the .
Step&8 You can obtain licenses for new devices that you are adding to the upgraded system, if your system requires additional device license units. For detailed instructions, see the .
Additional Information
Use the following procedure to upload a license file to the Cisco Unified Communications Manager server with the matching MAC address that is provided when a license file is requested. For information about obtaining a license file, see the . The Cisco Unified Communications Manager server where the license file is loaded takes on the functionality of the license manager.
The License File Upload window may display a message that uploading the license file removes the starter (demo) licenses for the feature.
After you upgrade to Cisco Unified Communications Manager 7.1 from a compatible Cisco Unified&CM 5.X or 6.X release, the Cisco CallManager service does not automatically run, even though Cisco Unified Serviceability shows that the Cisco CallManager service is activated. Immediately after you complete the upgrade to Cisco Unified Communications Manager 7.1, upload the software feature license that is required for Cisco Unified Communications Manager 7.1 in Cisco Unified Communications Manager Administration and restart the Cisco CallManager service in Cisco Unified Serviceability. Until you perform these tasks, devices fail to register with Cisco Unified Communications Manager 7.1.
Note Upload the license file only on the first node of Cisco Unified Communications Manager cluster.
Step&1 Choose System&& Licensing&& License File Upload.
The License File Upload window displays.
Step&2 The Existing License Files drop-down list box displays the license files that are already uploaded to the server.
Note To view the file content of any existing files, choose the file from the drop-down list box and click View File.
Step&3 To choose a new license file to upload, click Upload License File.
The Upload File pop-up window displays.
Step&4 To upload to the server, click Browse to choose a license file.
Note The format of the license file that you receive specifies CCM&timestamp&.lic. If you retain the&.lic extension, you can rename the license file. You cannot use the license if you edit the contents of the file in any way.
Step&5 Click Upload.
After the upload process completes, the Upload Result file displays.
Step&6 Click Close.
Step&7 In the License File Upload window, the status of the uploaded file displays. In Cisco Unified Serviceability, restart the Cisco CallManager service.
Note The system uploads the license file into the database only if the version that is specified in the license file is greater than or equal to the Cisco Unified Communications Manager version that is running in the cluster. If the version check fails, an alarm gets generated, and you should get a new license file with the correct version. The system bases the version check only on major releases.
Additional Information
You cannot delete a license file name through Cisco Unified Communications Manager Administration. For information on how to delete a license file name, refer to the Command Line Interface Reference Guide for Cisco Unified Solutions.
o, Cisco Unified Communications Manager System Guide
oCommand Line Interface Reference Guide for Cisco Unified Solutions
Was this Document Helpful?
Let Us Help
(Requires a )
Related Support Community Discussions}