- Remove From My Forums
-
Question
-
Hi,
Just came across this scenario: program deployed, but user logs off during installation. Program fails with exit code 1073807364 and does not rerun, although it’s scheduled to rerun if previously failed. Program has to run with user interaction and it’s
deployed to run when user is logged on. Any thoughts would be much appreciated.
All replies
-
1073807364 = 40010004 (hex) — This means the system cannot open the file»
4001 is the facility code. Please check the actual setup log which should be in the temp folder of the system.
Also check the application log under the Windows log of the Event Viewer for more detail.
Raman Katoch TechNet Clean Energy
-
Edited by
Tuesday, December 8, 2015 1:06 PM
-
Proposed as answer by
Raman Katoch
Tuesday, December 8, 2015 1:14 PM
-
Edited by
-
-
Edited by
KP_Mirshad
Tuesday, December 8, 2015 12:29 PM
-
Edited by
-
«although it’s scheduled to rerun if previously failed»
That is not correct. The «Rerun if failed» is not a scheduling mechanism, its a check to see whether or not a program will rerun if it is scheduled to run again. If there are no additional schedules, then this setting is meaningless. Only if there
are additional manually created schedules or a recurring schedule set on the deployment will this setting have any effect.
Jason | http://blog.configmgrftw.com | @jasonsandys
-
Hi Raman,
Many thanks, should have provided more details. Basically, I have a script that prompts the user to postpone or start the installation of an application and used a vbs script to do this. For all the failed installations I can see that the program
started, but when the user logged off, it fails with exit code 1073807364 .execmgr.log
MTC task with id {46FABF43-9B7D-45F8-A1F7-2BDD5B3A91E5}, changed state from 4 to 5 execmgr 07/12/2015 18:15:31 6716 (0x1A3C)
Program exit code 1073807364 execmgr 07/12/2015 18:38:57 7132 (0x1BDC)
Looking for MIF file to get program status execmgr 07/12/2015 18:38:57 7132 (0x1BDC)
Script for Package:U0100097, Program: Install failed with exit code 1073807364 execmgr 07/12/2015 18:38:57 7132 (0x1BDC)
Raising event:
[SMS_CodePage(850), SMS_LocaleID(1036)]
instance of SoftDistProgramErrorEvent
execmgr 07/12/2015 18:38:57 7132 (0x1BDC)
Raised Program Error Event for Ad:U0120363, Package:U0100097, Program: Install execmgr 07/12/2015 18:38:57 7132 (0x1BDC)
Execution is complete for program Install. The exit code is 1073807364, the execution status is FailureNonRetry execmgr 07/12/2015 18:38:57 7136 (0x1BE0)
Requesting MTC to delete task with id: {46FABF43-9B7D-45F8-A1F7-2BDD5B3A91E5} execmgr 07/12/2015 18:38:57 7136 (0x1BE0)
MTC task with id: {46FABF43-9B7D-45F8-A1F7-2BDD5B3A91E5} deleted successfully. execmgr 07/12/2015 18:38:57 7136 (0x1BE0)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»U0100097″,ProgramID=»Install», actionType 10l, value Result:FALSE, user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 07/12/2015 18:38:57 7136
(0x1BE0)
Requesting MTC to delete task with id: {46FABF43-9B7D-45F8-A1F7-2BDD5B3A91E5} execmgr 07/12/2015 18:38:57 7136 (0x1BE0)
This execution request does not have a corresponding task in MTC. execmgr 07/12/2015 18:38:57 7136 (0x1BE0)
Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID=»U0100097″,ProgramID=»Install», actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 07/12/2015 18:38:57 7136
(0x1BE0)
The user has logged off. execmgr 07/12/2015 18:39:07 7132 (0x1BDC)This is very easy to reproduce, create a dummy vbs script, WScript.Sleep(120000), deploy it as a program in SCCM (to run asap, while the user is logged on), check taskmgr for wscript.exe and log off while it’s executing.
I was wondering what’s the best approach for this scenario.
Many thanks
PS: I have specific requirements for this deployment and have to run it while the user is logged, allow user the interaction, scheduled to run as soon as possible.
I’ve built a RCP-based application, and one of my users running on Windows XP, Sun JVM 1.6.0_12 had a full application crash. After the app was running for two days (and this is not a new version or anything), he got the nice gray JVM force exit box, with exit code=1073807364.
He was away from the machine at the time, and the only thing I can find near that time in the application logs was some communication with the database (SQL Server by way of Hibernate). There’s no hs_ files or anything similar as far as I can tell. Web searching found a bunch of crash reports with that exit code in a variety of applications, but I didn’t see any fundamental explanation of what causes it.
Can anyone tell me what causes it? Is there additional information likely to have been dumped that could prove useful?
asked Feb 1, 2010 at 0:50
1
From what I can tell, this error code (0x40010004) arises in all sorts of situations, with (as you noted) no obvious common thread.
However this page says «0x40010004» means «the task is running»! So, I would surmise that the correct way to interpret it is as saying «this tasked has exited in a way that prevented it setting a proper exit code».
I don’t know if this will help, but I would try looking in the Windows Event logs to see if the problem is being reported there.
answered Feb 1, 2010 at 3:01
Stephen CStephen C
694k94 gold badges798 silver badges1210 bronze badges
1
I am using STS, jdk 1.6. It was working fine until now. I am getting this STS pop-up when I start it.
Java was started but returned exit code=1073807364
C:/jdk1.6.0_18/bin/javaw.exe
-Dosgi.requiredJavaVersion=1.5
...
... /15 more lines of stack on the pop-up window.
Any idea?
Brock Adams
90.1k22 gold badges229 silver badges292 bronze badges
asked Jan 27, 2011 at 14:22
Some Java GuySome Java Guy
4,93219 gold badges70 silver badges107 bronze badges
4
Found this; Looks like there is no one problem, that error code can come from a variety of events.
From what I can tell, this error code (0x40010004) arises in all sorts of situations, with (as you noted) no obvious common thread.
However this page says «0x40010004» means «the task is running»! So, I would surmise that the correct way to interpret it is as saying «this tasked has exited in a way that prevented it setting a proper exit code».
I don’t know if this will help, but I would try looking in the Windows Event logs to see if the problem is being reported there.
found here: What is the cause of JVM exit code 1073807364?
answered Jan 27, 2011 at 14:27
0
From my experience, that error (described as «task is running») occurs when there is a thread in blocking mode, and the thread cannot be terminated by being interrupted (per the rules) so it lingers, causing the program to hang, and requiring a kill shot. I have experienced that error as recently as today (Sept 5, 2012), and that was the cause (because I did it deliberately).
There may be other causes, but that is one distinct possibility.
answered Sep 5, 2012 at 20:53
All I can suggest is updating your JDK to the latest release (1.6.0_23) and STS to the latest version (2.5.2) and seeing if the problem still persists.
answered Jan 27, 2011 at 16:12
PowerlordPowerlord
87.2k17 gold badges125 silver badges174 bronze badges
1
Нашел это; Похоже, что нет одной проблемы, этот код ошибки может происходить из различных событий.
Из того, что я могу сказать, этот код ошибки (0x40010004) возникает в самых разных ситуациях, и, как вы заметили, нет очевидного общего потока.
Однако на этой странице написано «0x40010004» означает «задача выполняется»! Таким образом, я бы предположил, что правильный способ интерпретации — это сказать: «это задание завершилось таким образом, что помешало ему установить правильный код выхода».
Я не знаю, поможет ли это, но я попытался бы просмотреть журналы событий Windows, чтобы увидеть, не сообщается ли о проблеме там.
нашел здесь: В чем причина кода выхода JVM 1073807364?
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
drastiK91 opened this issue
Apr 13, 2023
· 2 comments
Assignees
Labels
info-needed
Issue requires more information from poster
Comments
Type: Bug
The terminal process «C:WINDOWSSystem32WindowsPowerShellv1.0powershell.exe» terminated with exit code: 1073807364.
VS Code version: Code 1.77.1 (b7886d7, 2023-04-04T23:21:11.906Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 x 3792) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off |
| Load (avg) | undefined |
| Memory (System) | 31.91GB (6.74GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Extensions (76)
| Extension | Author (truncated) | Version |
|---|---|---|
| vscode-openapi | 42C | 4.16.6 |
| vscode-color | ans | 0.4.5 |
| swagger-viewer | Arj | 3.1.2 |
| atlascode | atl | 3.0.3 |
| vsc-sort-react | avr | 1.4.2 |
| generator-from-swagger | Bar | 1.1.39 |
| git-temporal-vscode | bee | 1.0.0 |
| vscode-yarn-script | car | 0.0.1 |
| hide-node-modules | chr | 1.1.7 |
| npm-intellisense | chr | 1.4.4 |
| path-intellisense | chr | 2.8.4 |
| vscode-markdownlint | Dav | 0.49.0 |
| vscode-eslint | dba | 2.4.0 |
| python-environment-manager | don | 1.0.4 |
| python-extension-pack | don | 1.7.0 |
| vscode-generate-getter-setter | DSK | 0.5.0 |
| gitlens | eam | 13.5.0 |
| swagger-panel | els | 1.0.2 |
| prettier-vscode | esb | 9.10.4 |
| vscode-yarn | gam | 2.1.0 |
| todo-tree | Gru | 0.0.226 |
| vscode-mocha-test-adapter | hbe | 2.14.1 |
| vscode-test-explorer | hbe | 2.21.1 |
| vue-snippets | hol | 1.0.4 |
| search-node-modules | jas | 1.3.0 |
| react-vscode-extension-pack | jaw | 1.0.0 |
| code-eol | jef | 1.0.12 |
| nbpreviewer | jit | 1.2.2 |
| svg | joc | 1.5.2 |
| vsc-python-indent | Kev | 1.18.0 |
| vscode-codemetrics | kis | 1.26.1 |
| vscode-python-test-adapter | lit | 0.7.1 |
| git-graph | mhu | 1.30.0 |
| gitignore | mic | 1.0.1 |
| autoflake-extension | mik | 1.0.4 |
| vscode-docker | ms- | 1.24.0 |
| vscode-language-pack-it | MS- | 1.77.2023041209 |
| vscode-kubernetes-tools | ms- | 1.3.11 |
| isort | ms- | 2022.8.0 |
| python | ms- | 2023.6.0 |
| remote-wsl | ms- | 0.77.0 |
| test-adapter-converter | ms- | 0.1.7 |
| vscode-react-native | msj | 1.10.2 |
| sqltools | mtx | 0.27.1 |
| sqltools-driver-mysql | mtx | 0.5.1 |
| sqltools-driver-pg | mtx | 0.5.1 |
| color-highlight | nau | 2.5.0 |
| autodocstring | njp | 0.6.1 |
| stats-bar | njz | 0.5.2 |
| vscode-extension-auto-import | Nuc | 1.4.3 |
| vetur | oct | 0.37.3 |
| react-proptypes-intellisense | OfH | 1.0.3 |
| docthis | oou | 0.8.2 |
| vscode-react-native-storybooks | Ort | 2.7.1 |
| openapi-designer | phi | 0.3.0 |
| prisma | Pri | 4.12.0 |
| python-fastapi-snippets | pyt | 1.0.8 |
| vscode-yaml | red | 1.12.2 |
| comment-ts | sal | 1.0.21 |
| markdown-preview-enhanced | shd | 0.6.8 |
| vscode-react-scripts-test-adapter | sma | 0.1.2 |
| swdc-vscode | sof | 2.7.0 |
| vscode-taskexplorer | spm | 2.13.2 |
| autoimport | ste | 1.5.4 |
| react-proptypes-generate | sum | 1.7.6 |
| tabnine-vscode | Tab | 3.6.44 |
| python-tox | the | 1.0.0 |
| python-extended-snippets | tus | 0.0.1 |
| volar | Vue | 1.2.0 |
| vscode-todo-highlight | way | 1.0.5 |
| jinja | who | 0.0.8 |
| vscode-import-cost | wix | 3.3.0 |
| eno | Wsc | 2.3.53 |
| qf | Wsc | 6.8.122 |
| JavaScriptSnippets | xab | 1.8.0 |
| ReactSnippets | xab | 2.4.0 |
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.77.3. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!
Labels
info-needed
Issue requires more information from poster