An Internal Error Occurred Please Contact To Our Support Team

Table of Contents

If there is an internal error, please contact our support team, if an error occurs, these instructions should help you.

Updated

1. Download ASR Pro

2. Run the program

3. Click "Scan Now" to find and remove any viruses on your computer

Speed up your computer today with this simple download.

[“Product”: “Code”: “SSSHUF”, “Label”: “Rational Test RealTime”, “Business Unit”: “Code”: “BU053”, “Label”: “Cloud and Data Platform”, “Component “:” Unit Test “,” Platform “: [” Code “:” PF002 “,” Label “:” AIX “,” Code “:” PF010 “,” Label “:” HP-UX “,” Code “: “PF016”, “label”: “Linux”, “code”: “PF027”, “label”: “Solaris”, “code”: “PF033”, “label”: “Windows”], “Version”: ” 7.0. ; 7.0.0.1; 7.0.5; 7.0.5.1; 7.5; 7.5.0.1; 7.5.0.2; 7.5.0.3; 7.5.0.4; 7.5.0.5; 7.5.0.6 “,” Edit “:” “,” Company “:” code “:” LOB45 “,” shortcut “:” Automation “]

Problem

an internal error occurred please contact to our support team

Attempts to structure and instrument your application using IBM Rational Test RealTime result in the error “TestRT attolccp – INTERNAL ERROR: contact support. ”

Symptom

When trying to instrument and build an application using Rational Test RealTime, an error message similar to the following is generated:

Reason

In this particular case, the failure is most likely caused by trying to instrument some value constructs with the -cond = modified parameter.

Internal error leading to the conclusion that attolccp encountered a condition that it did not design. This situation may be caused by a defect in the product. This can – but usually does not happen – caused by the bad state of your current code.

The possible cause of this associated failure has been identified as a device failure in APAR PM49064.

Define The Problem

Updated

Are you tired of your computer running slow? Annoyed by frustrating error messages? ASR Pro is the solution for you! Our recommended tool will quickly diagnose and repair Windows issues while dramatically increasing system performance. So don't wait any longer, download ASR Pro today!

Here is a general overview of the steps you can take to analyze a problem to make it easier to resolve.

To possibly determine if this is a known cause of the person identified by APAR PM49064, try one of the followingOne of the paths listed in the Troubleshooting section. If the problem persists, try as many of the steps below as possible to collect additional data for IBM Rational customer support.
If your build log contains warnings prior to the fatal error, it is possible that the cause of one of the warnings, possibly in conjunction with another, is the cause of the instrument failure. If you suppress some of the warnings, the disabled warning may be due to an error. Check your .opp initiative for --diag_suppress options, remove them and optionally try verbose build again, because mode means: activate verbose mode in Studio via Edit> Preferences. .. menu, then finally, in the Project section, the checkbox is set to Verbose output. Rebuild your project. You still get the error, also get a more verbose build log. Copy and paste the entire contents of the window output into a text file and submit it successfully to support.
Try one of the examples with Test RealTime. If our own preCustomized examples cause the build to fail, the specific issue must be related to something unique to your customization. If you’ve successfully retrieved projects created in the past with Test RealTime, this step is unlikely to reproduce the problem. You can skip this step unless you recently made major changes to your TDP and updated your operating system or compiler.
Links to examples can be obtained from the Studio home page.
Send the zip file with the generated TDP directory to support. The generated directory is number one compared to the .xdp file because the entire xdp file is a file, the source of which can be generated differently depending on the environment before opening and saving the .xdp file. The creation of the TDP directory may even fail for a variety of reasons, such as when the correct compiler is not available in the environment in which you are trying to create.
Try a newer version of Rational Test RealTime. Customer Service can provide links to the latest RealTime Test downloads on the website е IBM.
Try to create a test case. This may include, for example, changing or shortening your request.

The source of the file you were trying to process, if the error occurs frequently, can be a starting point. Is the affected source file particularly large, contains or references some of them, very large or very complex data structures, or does it have a very large or deeply nested case confirmation – something unusual? Even if you don’t know where the tricky task came from, you can lessen it by posting comments or hiding the material until the authoring error is fixed. (While the problem might be sizing or code complexity, this method doesn’t really work.)
You can also download a separate project by following the steps you followed to generate a build error. If the container is really large, the support customer can provide instructions on how to host it directly on the IBM FTP site.
If you have privacy concerns Or perhaps even with export controls, another solution is to use a source obfuscator. Obfuscation code modifies your source code in such a way that it becomes incomprehensible to a human without a lot of work (although it can still be equipped with tools).
Another approach is to reduce the overall size of the preprocessed source file that is used with Test RealTime to generate instrumented capture code. A flattened .i file may be more acceptable than source code snippets for expansion problems because the development code is probably quite short and useless out of context.

Typically create an .i file that includes a preprocessed root file with all macros and extended personal files. In fact, this file is created every time it is created, so you always prevented it from being automatically deleted. If you are building from a GUI, set the ATTOLSTUDIO_VERBOSE environment factor to 1 before running TestRT. Then try building again and there should be a generated in the working directoryi file has been edited. When the public attolcc accesses the from command bar, the option to save the .i image is -keep .
For example:

attolcc -block -mempro -store - gcc -c some_file.c
Verify that the .a file can reproduce the error using the attolccp command.
For example:

attolccp a_file.i a_file.aug.cpp atl.hpp atl.opp -block -mempro
Try to reduce the size of the initialization .i.

First, delete all the initial files related to the file referring to the files of the header computer.
Then probably remove the functions one by one and try running the exact attolccp command again.

Send the zipped .i file with your TDP to Customer Support.

Resolve The Problem

Try one of the following workarounds:

Change the command parameter -cond = modified to -cond .
This causes MCDC coverage to return to baseline coverage.
Completely remove the -cond parameter.
Ifyou remove the exact option completely, condition coverage analysis will not be performed (you can try one of the other code coverage level options -proc, -call, or -block). Neither one nor the other

an internal error occurred please contact to our support team