Код ошибки 3762504530

I’m just a lowly developer, but a scheduled (2:00 am) VB.Net console app job I inherited is intermittently not running to completion. About half the time, it just doesn’t run to completion, logging and event:
Task Scheduler successfully completed task «[appname]» , instance «{3f00cbd6-b40e-4e74-a0da-4def71b4d7db}» , action «D:\Scheduled Tasks[foldername][appname.exe]» with return code 3762504530.

I found one other mention of that return code on the web, and the guy included the description of some settings; below are our analagous settings with answers provided by our Networking guy.

I’d be pathetically grateful for any advice or direction… thanks in advance.

Does the job «run whether user is logged in or not»? — YES

Is the job «run with highest privileges» — YES

What’s the server OS? — Window 2008 R2 Standard

Is it true that «the only conditions set is to wake computer to run»?
It is not set to wake the computer to run the task. However, it is not going to sleep and the task is running. It’s just exiting abnormally.

Are the «settings are allow task to be run on demand / stop task if running more than 3 days / if task does not end when requested force it to stop»?
YES, it can be run on demand;
YES, it will stop the task if it runs longer than 4 hours;
YES, it will force it to stop if it doesn’t end as requested.

Источник

I found one other mention of that return code on the web, and the guy included the description of some settings; below are our analagous settings with answers provided by our Networking guy.

I’d be pathetically grateful for any advice or direction… thanks in advance.

Does the job «run whether user is logged in or not»? — YES

Is the job «run with highest privileges» — YES

What’s the server OS? — Window 2008 R2 Standard

Источник

Windows Terminal version

1.14.196.3.0

Windows build number

1?.?.22518.1000

Other Software

At least any windowed app with a console in any relevant prompt except the powershell hotfix for this, when restarting for example after the app updated. Look at steps to reproduce for similar software having this issue.

Steps to reproduce

The program I’m using is unofficial, but Similar issues are #4981 and #6287.

Expected Behavior

I expected to application to continue and restart. I also expected terminal to be fixed and not powershell.

Actual Behavior

It showed me my system specifications like supposed, but gave me the following error:
[process exited with code 3762504530 (0xe0434352)]

msftbot
bot

added

Needs-Triage

It’s a new issue that the core contributor team needs to triage at the next triage meeting

Needs-Tag-Fix

Doesn’t match tag requirements

labels

Aug 13, 2022

I mean, it just kinda sounds like whatever application you’re running is returning a non-zero exit code. Refer to:

Why am I seeing [process exited with code ...]?

I’d file an issue upstream with whatever software you’re using. If the application should be exiting cleanly, it should be returning 0. The Terminal displays that message by default so that when an application does return an error, you can view its output.

i got the same problem tryng to run my c# app 😢

[proceso terminado con el código 3762504530 (0xe0434352)]

aparently is when i write something in the console.readline()

This error code means that your C# application is crashing with a «COM+» error. Terminal has displayed it so that you know what is going on!

But only happens when i runned on windows terminal

@zadjii-msft < Someone already did, but it’s lazy to say all the app makers fix it individually, while it’s clearly a terminal issue, like @Mrgaton stated.
Did u even look into the powershell issue?
However, still thanks for giving insight, we could all use some of that.

Of course it only happens on the Windows Terminal, conhost (the vintage console) never had any code to handle anything like this. If an app crashed running in conhost, it’d just disappear itself, which doesn’t provide any useful information. Providing an error code is certainly useful — best practice has always been to return 0 if your process exits cleanly, and I’d want to know if my app wasn’t for whatever reason.

You can always tell the terminal to just ignore this by settings closeOnExit: always.

I haven’t looked more into the root of this, because there were no minimal repro steps in the OP 😉

I only know that’s the program crashes on the console.readlline() I tested out

I encountered it while obfuscating the dlls via a post build script. It looks like .exe was invoked before the obfuscation was completed. But the .exe is working well after that. So I just ignored it.

Источник

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

Comments

Application error

System


Platform	win32 10.0.19042
Architecture	x64
Application Version	1.4.14
Process	renderer

Message

Installer process quit unexpectedly (Code 3762504530)

Title

Installation failed

Details

Name: Error

Context

Resuming "LSC body and face-29722-3-5.rar" = nxm://fallout4/mods/29722/files/122441?key=TGGjQoFpNrg8VV6hHcq2xw&expires=1625679831&user_id=77830068,gamemode = Fallout 4,Resuming "VtawWardrobe1-39599-1-1-1561227958.7z" = nxm://fallout4/mods/39599/files/160375?key=8Tv3jp_UxqRt_bVj8CWMvg&expires=1625680063&user_id=77830068,Resuming "Vtaw Wardrobe 4-42145-1-0-1574017475.7z" = nxm://fallout4/mods/42145/files/171068?key=JZnaAAMT8Lzdnzh-ZlFHiQ&expires=1625680031&user_id=77830068,Resuming "Wardrobe6 Main-46628-1-0-1596281201.7z" = nxm://fallout4/mods/46628/files/188133?key=EHHNvO1TkA7xnkwCq3qyhA&expires=1625680048&user_id=77830068,Installing = Caliente's Beautiful Bodies Enhancer - v2.6.3-15-2-6-3-1587299180

Stack

Error: Installer process quit unexpectedly (Code 3762504530)
    at ConnectionIPC.<anonymous> (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5954:83)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5923:174)
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)

Reported from:
Error
    at Object.showError (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:381:195)
    at InstallContext.mShowError (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5865:66)
    at InstallContext.reportError (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5882:56)
    at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:1761:133
    at tryCatcher (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:729:18)
    at _drainQueueStep (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

External file: tmp-22160aDXF3ZWRV9Zv.7z

Reported by: ShoeMuckBootDirt

Hey there, error code 3762504530 translates to 0xe0434352 — the majority of the reasons for this error is having a faulty .NET Framework, another reason is because of some corrupted files or old drivers that are contradicting with Windows. This is unfortunately an issue with your environment not Vortex.

2 participants

Источник

Это корректно для SEO. Поисковые системы обновят свою базу данных, которую старый URL изменил на новый URL. Необходимо оставить это активным как этот в течение по крайней мере нескольких месяцев, они все получают шанс обновить, и посетители могут все еще использовать старый URL.

задан
3 October 2012 в 17:04

Ссылка

5 ответов

Я считаю, что код возврата — это общий код сбоя консольного приложения .NET . Эта проблема не возникает из-за способа настройки задания в планировщике заданий.

Проверьте журнал событий приложений на сервере на наличие ошибок, которые произошли примерно в то время, когда задание было «завершено». Эти события должны дать вам больше информации о том, почему задание завершилось аварийно, чтобы вы имели представление, с чего начать устранение неполадок.