Contact US
Thanks. We have received your request and will respond promptly.
Come Join Us!
- Talk With Other Members
- Be Notified Of Responses
To Your Posts - Keyword Search
- One-Click Access To Your
Favorite Forums - Automated Signatures
On Your Posts - Best Of All, It’s Free!
Posting Guidelines
Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Related Projects
aborted with system error code 1073741819
aborted with system error code 1073741819
aborted with system error code 1073741819
I was trying to simulate a wear problem with mesh motion subroutine. the job ran for 1 increment after which it aborted with an error. I refined mesh with coarse size but still showing error. please help me to rectify this issue.
The executable standard.exe aborted with system error code 1073741819. Please check the .dat, .msg, and .sta files for error messages if the files exist. If there are no error messages and you cannot resolve the problem, please run the command «abaqus job=support information=support» to report and save your system information. Use the same command to run Abaqus that you used when the problem occurred. Please contact your local Abaqus support office and send them the input file, the file support.log which you just created, the executable name, and the error code. 
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
Unfortunately these files don’t indicate the actual reason of the error.
Try running this model without subroutine. If you still get this error, disable adaptive meshing. If this doesn’t help, there’s probably an issue with features such as contact and constraints (ties, couplings).
RE: aborted with system error code 1073741819
When I disable subroutine it runs fine. Even when adaptive mesh is turned on .
In this problem i have two solid blocks in relative motion.
I am giving adaptive mesh to the lower body and for the same body iam specifying displacement in z direction using periodic boundary condition and arresting x and y dofs(rotation and displacement) , (rotation in z direction also). For top body iam giving pressure load only by restricting displacement in x and z direction. All boundary conditions and loads are specified using boundary condition manager.
Is there any mistake in specifying my boundary conditions?
There are no ties or coupling in this problem. It is held together by pressure load and friction contact is specified by defining master and slave.
RE: aborted with system error code 1073741819
If these boundary conditions/loads are assigned to the top surface of the upper block and bottom surface of the lower block then it seems correct.
Apparently there’s a problem with your subroutine code.
Check the article «Material removal analysis for compliant polishing tool using adaptive meshing technique and Archard wear model» by A.P.S. Arunachalam et al. It may be helpful.
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
its showing excessive distortion even after switching automatic stabilization.
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
Yes, the boundary conditions should look like in your picture.
Slave surface should be the one with finer mesh. And you may have to increase the mesh density for the whole model, especially for the region with adaptive meshing assigned. I would apply this feature only to the layer of elements close to the interface.
RE: aborted with system error code 1073741819
Mesh density was modified. slave surface was given highest mesh density.
I tried with the above boundary conditions. But it didn’t worked . Always job is getting aborted even without ALE. But if I specify motion to the entire lower body and constraining other dofs of bottom surface of lower body, it will move in the periodic manner as specified.
I tried in different ways to avoid giving motion to entire body but it didn’t worked. Even tried to give motion to upper body (along with pressure) alone by encastring bottom surface of lower body.but it also failed.
Iam specifying user defined adaptive mesh constrain only to top surface of lower body. Is it the correct way?
RE: aborted with system error code 1073741819
I modified Model-2 in the database that you shared here:
— turned off the remeshing rule
— applied boundary conditions to faces instead of entire blocks
— switched surfaces in contact definition
— changed initial increment size to 0.1
And it works now. However the mesh should be refined anyway.
Yes, apply this constraint only to the surface nodes.
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
I made these changes in newer version of Abaqus than yours so you wouldn’t be able to open my cae file. But I can share the input file if you want.
Yes, I used the option named «Switch surfaces». It turns the master surface into slave surface and vice versa.
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
RE: aborted with system error code 1073741819
Red Flag Submitted
Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Eng-Tips forums is a member-only feature.
Click Here to join Eng-Tips and talk with other members! Already a Member? Login
Abaqus system error code
Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
System error when compiling a quite complex subroutine
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Several months ago I had successfully developed a user subroutine in FORTRAN for a particular commercial finite element software (ABAQUS). I decided several days ago to extend this subroutine and the resulting subroutine is quite complex, big, and involves several big matrices/arrays (over 10 thousand lines) that are exchanged among subroutines with COMMON BLOCKS.
The thing is that the subroutine does not compile and I get the following error:
Abaqus Error: The executable standard.exe aborted with system error code 1073741819.
There is no other information in any other file. It is important to note that this kind of error could be due to many reasons and is different than the error that appears as a consequence of poor programming. However, I thought that maybe I had define wrongly some of the variables of the code: I thoroughly checked all the code and tried to locate the error. My surprise came when I saw that, reducing the number of lines of the big matrices/arrays mentioned before, the subroutine works. Those matrices/arrays are all of them initialized (the suppressed lines only contain 0s) and I have checked that its dimensions agree through all the code. Searching on the internet I see that some people with similar problems say that it could be due to memory problems. Could it be? What could I do to solve it?
I know that usually, in the 95% of the cases, when subroutines don’t work this is due to poor programming. However, in this case there are several circumstances that make me think that it could be to other reasons. Among them, if I add to the subroutine the following statement WRITE, the above mentioned error appears again, independently of the variable (A or other).
WRITE(7,*) ‘A equals:’, A
(Note that in this statement the number 7 indicates that the message is written to a particular file of the FE software).
Searching on the internet I have also found this nice post by Steve Lionel:
I wonder if it is my case and if I can do anything to solve the problem, since I use quite a lot of static code but unfortunately I am not able to reduce it due to the limitations of not having access to the main code.
Русские Блоги
Abaqus ERROR in job messaging system: Error in connection to analysis error code 1073740791
Недавно оборудованный компьютер в лаборатории использует процессор i3-6100. После установки abaqus6.13-1 вы можете открыть интерфейс и модель CAE, но после отправки анализа он появится
Это все еще так после переустановки, и при установке 2016CAE он застревает на 1174 Мб, что действительно душераздирающе. После нескольких подбрасываний я повторно исследовал ошибку и обнаружил, что это не то, что решатель не может подключиться, а то, что система сообщений не может подключиться к информационной системе. В следующей строке я увидел код ошибки 1073740791. Я поискал код в Baidu и получил следующеессылка на сайт, Хотя последние несколько цифр кода ошибки отличаются, я очень рад успешно решить проблему, изменив ее в соответствии с ее методом.
Таким образом, основная причина проблемы заключается в том, что некоторая библиотека динамической компоновки не может использоваться в обычном режиме из-за процессора новой платформы. Кроме того, после возникновения проблемы вы должны как можно скорее проверить код ошибки, вместо того, чтобы бесцельно переустанавливать его, и целенаправленно организовать действия.
Интеллектуальная рекомендация
Функция epoll
Эта функция генерирует файловый дескриптор, посвященный epoll. параметр: size: максимальное количество дескрипторов, которым может следовать epoll. Используется для управления событием файлового.
шаблон проектирования java шаблон_команды шаблон
Командный режим (Command): 1. Концепция:Инкапсулируйте «запрос» (команду / пароль) в объект, чтобы его можно было параметризовать с помощью различных запросов, очередей или журналов. Коман.
Идея нажмите RUN, чтобы запустить ошибку: Неисправная конфигурация из-за недоступного плагина или неверных данных конфигурации .
Сегодня я открыл идею, как обычно, и внезапно обнаружил, что была проблема с предыдущей конфигурацией запуска, а затем сообщил об ошибке: Run Configuration Error: Broken configuration due to unavailab.
Меч относится к 76-м серии предложение: субструктура дерева
Тема Описание Введите два бифурия A, B и определите, что B — подстройка A. Это на самом деле применение бинарного дерева запасного алгоритма. Чтобы найти определенное дерево курса в исходном двоичном .
MBG конфигурационный файл шаблона + конфигурации Объяснение + способ использования
Профиль письменность В целях повышения эффективности работы, мы часто используемMybatisGeneratorОбратный инжиниринг генерирует соответствующий класс сущностей для таблицы базы данных.DAOинтерфейс,Mapp.
Debugging of ABAQUS errors
For sure, whoever has worked with computers, heard the words “Bug” or “Debugging.” Ordinary people may have heard these words in gaming, common software such as Microsoft Office, google chrome, etc. If we want to introduce a synonym for the Bug, we could say “Error.” Here we will tell you what the “Bug” and “Debugging in the ABAQUS” mean. Also, we will introduce some techniques to handle the ABAQUS errors or, as we would like to call them, bugs.
1 Bug and convergence in the ABAQUS
As it defines itself, Bug means anything annoyance that causes your problem not to be solved or without accurate results. Debugging means any actions that need to be done to solve a problem correctly, without any errors, and obtain accurate results.
Convergence is a term to say our problems equations and matrices are solved properly to have our job completed even without any warnings. But, are the results accurate and according to the actual model? If not, then you have to start debugging. You could say that convergence is a subset of the debugging process.
Now, let’s debug the ABAQUS errors with some techniques.
2 Debugging techniques
Here, we introduce some techniques and procedures for debugging ABAQUS errors. Some of them are preprocessing, and some are post-processing:
- System of units check
- Making a test model
- Output check
- Syntax check
- Data check
- Boundary conditions and loadings
- Materials check
- Constraints check
- Elements check
- Interference fits check
- Contact check
- Over Constraints and initial rigid body motion check
- Static stabilization
- Dynamics check
2.1 System of units check
In the first step of debugging process, you should check the units of your input data to see if they are consistent or not. After that, you should review the boundary conditions and loading to ensure there aren’t any issues. For more information about the system of units, click here.
2.2 Making a test model
A large model may take a long time to be analyzed, so making a test model speed up the debugging process is highly recommended. The test model is simplified and miniaturized from the original model created for speeding up the debugging process. It should be only used for debugging and testing.
2.3 Output check
Having more information about your problem before or after submitting a job is always useful. However, for debugging purposes, request more results through the “Field Output” and “History Output” in the Step module (see figures 1 and 2) to debug the analysis afterward. Obviously, it will take more computational time, but it is worth it because these requests will help you debug the system and find the convergence issues.
Figure 1 Field Output requests
Figure 2 History Output requests
2.4 Syntax check
When you want to check your input file to see any flaws in your script, you should use the syntax check command. It checks your input file line by line, and finds and shows any flaws that may exist in the file’s script. After a syntax check, check the “.log” file, and if there are no flaws, you will see the lines as shown in figure 3. To do a syntax check, type the command line “abq6142 syntaxcheck j=your input file’s name” in a command prompt window. For more information, click here.
Figure 3 The input file without flaws
2.5 Data Check
The data check is the same as the syntax check with one difference; the data check runs the file to ensure that the model has all the required options. It checks the model consistency as well. You could say the syntax check is the subset of the data check.
The procedure to execute a data check is the same as the syntax check, with only a slight difference in the command line:
abq6142 datacheck j=your input file’s name
The log file message is different (see figure 4). Also, you could use the data check through the GUI (see figure 5).
Figure 4 The log file without error
Figure 5 Data check through the GUI
2.6 Boundary conditions and loading
After a syntax and data check, you can correctly run the model’s input data into the ABAQUS. Moreover, you can ensure that appropriate settings are applied according to the model specifications. After that, check the boundary conditions and loading. You must monitor them to ensure that the applied boundaries and load cases have appropriate settings with proper ABAQUS features.
2.7 Materials check
Check the material properties. You must check them to ensure that the model’s structural responses present proper behavior under the boundary conditions and loading. Also, apply physical behavior law and material data’s complexity function to the model.
2.8 Constraints check
If you have to use constraints (see figure 6), make sure to use the right one according to your problem. For example, when you need to couple the motion of a surface or a group of nodes to a reference node, you must use “Couple constraint.” There are two based methods for the Couple: Kinematic and distributing. You must choose the proper method according to the problem. 
Figure 6 Constraint option
2.9 Elements check
Sometimes the elements cause numerical difficulties in the model, such as: selecting the wrong element type, improper meshing, hourglass control, not using Hybrid elements in the incompressible models, etc. Therefore, you must check the elements to debug your model.
2.10 Interference fits check
This part is about using contact to solve interference problems by focusing on interference fits. The interference means excessive overclosure between surfaces. An interference fit (press fit, friction fit) is a method to fasten two parts by pushing them together with normal force, and they get stuck together by friction rather than any means of fastening. A typical example is shaft press-fitting into bearings. You can resolve the interference problems in surface-to-surface contact for the ABAQUS/Standard. Select the desired step and use the interference fit option (see figures 7 and 8).
Figure 7 The interference fits option through the GUI
Figure 8 The interference fits option through the input file
2.11 Contact check
It is relatively easy to define contact interactions. However, adding local contact stiffness can cause instability problems in the global stiffness matrix and make the matrix nonsymmetric. So, several numerical difficulties may occur. One of the good methods to prevent these issues is to select the master and slave surface correctly. The master surface should be rigid or with a higher Young’s module. Also, the master surface should have a coarser mesh than the slave surface.
2.12 Over Constraints and initial rigid body motion check
In an analysis, one reason for convergence issues is inadequate or improper boundary conditions. Also, a model can be under or over-constrained, leading to convergence issues. If you do not use enough boundary conditions, your model may move as a rigid body in any direction (rigid body motion). The rigid body motion causes the stiffness matrix to become singular. As a result, the ABAQUS will show “zero pivot” warning messages. Although the software tries to solve the issue, it’s not always working. Therefore, you have to check the warnings and fix the constraints and boundary conditions.
2.13 Static stabilization check
The ABAQUS finite element software uses this main equation to solve a problem:
“K” is the stiffness matrix, “x” is the displacement matrix, and “F” is the Force matrix. Whenever a static problem becomes unstable, the equation cannot solve the problem because of the numerical difficulties caused by instability in the model. So, a damping force component will be added to the equation so that the problem can be solved:
“D” is the damping coefficient that stabilizes the problem and makes a quasi-static solution. Therefore, the “D” value must be controlled to get as nearly static a solution as possible. To do so, compare the ALLSD and ALLIE energies levels. For more information, click here .
2.14 Dynamics check
In static analysis, there is no effect of damping or mass (inertia). The applied load acts fully immediately on the model instead of with time increment because it has no physical sense. On the other hand, the dynamic analysis has a physical sense regarding applied load versus time. Moreover, the effect of mass and damping are included as well. The static analysis uses an Implicit solver. The dynamic analysis can use the Explicit solver or the Implicit. When you have a dynamic problem, you need to check which solver is appropriate for the analysis, Implicit or Explicit. Learn .
Keep in mind that in this article, we just introduced each technique. To resolve any ABAQUS errors and know more about the techniques, make sure to get our products and read incoming articles.