ILNumerics® Support Services
Having a problem? Can't figure out some special solution? Ask an expert! We provide free support tickets for technical support directly from the creators of ILNumerics for users under Maintenance Subscription. Additional tickets can be purchased.
In this section:
- How to properly ask for help
- What is covered by a support ticket?
- Common installation problems
- Common licensing problems
- Other places of help
Help us to help you! We want to provide you with the rights answers and solutions as quickly as possible. You can support us in doing so. Give us the information we need in order to identify your problem. This is what your problem report should contain:
- English or German: Please send your question in one of these languages.
- Your license key. The key was sent to you by email / is found in your invoice.
- Information about version and edition of ILNumerics.
- Information about version and edition of your IDE.
- System information. You can obtain these information via "Run" - "msinfo32.exe". Make a screenshot or printout or simply provide at least the following data:
- Operating System Name and Version
- Processor Type
- RAM size installed
- System Type (32 / 64 bit)
- ALL display adapters installed: Name and Description (from the 'Component' / 'Display' Section, for problems related to visualization only)
- Version of .NET CLR used (the target selected for your application)
- If you encounter any problems during the execution of your program / ILNumerics, attach the complete application trace log. When run in Visual Studio you can obtain a printout of the trace log generated by ILNumerics very easily: The log is written in the Output tool window. Alternatively you can add a trace listener to your code and let the trace info get written into a text file:
- If you have problems installing ILNumerics, follow the guidelines below and attach the install log obtained.
- For licensing problems provide a complete build log of your assembly:
- Select "Detailed" log verbosity level (Visual Studio: Tools -> Options -> Projects and Solutions -> Build & Run). Make sure to select the level for the Output window log.
- Make sure the build log originates from an actual compiling build! Rebuild your assembly or touch some code file before triggering the build. Otherwise the project might be considered 'up to-date', the compilation could be skipped and the log would be empty.
- The build log can be copied from the Visual Studio Output window, Build tab.
- Finally, describe the problem. Be as specific and exact as possible! Start by describing the intention, desired result and describe the result obtained. Include any further information which might be related to the problem. Note the scope of a single support ticket.
- If possible, provide a running example in order for us to reproduce the problem. Include all relevant parts you have created already. But try to make the code as short as you can! Leave out any parts which are not needed for reproducing / demonstrating the problem.
- Send all these information by email to: email@example.com
We'll get back to you as soon as possible!
The scope of a support ticket orients towards the common conditions offered by Microsoft and others: A ticket constitutes a single “issue”. This typically relates to a single question or a single problem which can be described and answered in a reasonable simple context.
Examples for common tickets:
- How can I control my surface X and Y axis range data?
- I want my plots to have dark background. How?
- I get an error after deploying my application when trying to run the svd() function. …
- However, a question like: “I want to display the values of my data when hovering with the mouse over a line plot and the line data should update when clicking on the annotation.” Is likely to constitute two tickets.
Note, that we do not:
- Write, debug or fix your code.
- Install third party products (except in certain special situations).
- Give specific architectural advice. (general hints are fine though, as long as it relates to ILNumerics)
Naturally, the scope is not hard fixed. And the term "reasonable simple context" is sometimes not easy to define. Therefore, you can ask us to agree upon the scope of a ticket in advance. Otherwise we will delimit too demanding questions in a reasonable manner.
Since your ticket numbers are limited, consider using the common documentation places first before wasting a support ticket for a too easy solution. It might pay off to save 1..2 tickets for more demanding situations. Visit, at least the online documentation, use the search function on the site and look up the object in question in the apidoc.
The installer refuses to install and/or terminates with an error message
This sounds like a corrupted installation is left over from an incompleted / failed install attempt. There are several ways to resolve this. Try to apply the following methods, one by one, retry to install the trial after each:
* manually uninstall any previous version of ILNumerics. This step is obligatory up from version 5. Go to "Progams & Features" in the Windows control panel and uninstall any package found there. If there is an older trial version left over, just deinstall that, too.
* make sure the file was downloaded successfully. We don't provide checksums but usually the size of the downloaded *.exe file gives a good indicator of the successfull download. ILNumerics installers are roughly 170 MB in size. If your file is smaller than that, retry to download the file.
* open every instance of Visual Studio installed and go to Tools -> Extensions. Make sure no ILNumerics extension was left over. In case an older extension still exist in the list, uninstall it manually from here, make sure to close Visual Studio afterwards. Another way of making sure to have the extension deinstalled from all Visual Studio instances is to open the developer command prompt associated with the Visual Studio instance with the highest version number and run the following command:
If the above options did not help and still the trial version cannot be installed, aquire a verbose installation log and send it to us. In order to have the installer writing the log, open a command prompt and enter the following command:
Replace "D:\log.txt" with a writable path on you harddrive. Replace [PATH-TO-msi] with the full path to the installer downloaded from our website. After the installer was finished the log.txt file will contain more information helpful to locate and fix the problem. Please send this file to us!
Please refer to the Licensing FAQs.
Still using Starter Editions? Stuck at the old Community Edition? Still fetching nuget packages?
Be part of the community! Ask your questions on stackoverflow: our community is constantly growing. Simply use the tag 'ilnumerics' when posting your question. Please be nice, descriptive, explicit and follow the stackoverflow rules! Once you have learned something upvote and mark the answers. Help other users out if you can – they will be grateful too!
Found a bug? Or a feature request? Report the issue to our bugtracker!