Revit Design Automation fails with -1073740791 error - autodesk-forge

I ran a new job on design automation and it failed with -1073740791 error code. The job id is:
"Id":"3991468c840243a39ad95903f94a58b6"
The full error report is:
[06/13/2022 09:23:22] End Revit Core Engine standard output dump.
[06/13/2022 09:23:22] Error: Application revitcoreconsole.exe exits with code -1073740791 which indicates an error.
[06/13/2022 09:23:22] End script phase.
[06/13/2022 09:23:22] Error: An unexpected error happened during phase CoreEngineExecution of job.
[06/13/2022 09:23:22] Job finished with result FailedExecution
[06/13/2022 09:23:22] Job Status:
What does -1073740791 error code mean specifically?

Related

Revit Design Automation failedExecution with code -536852669

I was running a workitem on Design Automation for Revit, and it crashed with code 536852669. Looking at the log, it seems like it had almost finished the job when it crashed:
[06/08/2022 20:55:21] End Revit Core Engine standard output dump.
[06/08/2022 20:55:21] Error: Application revitcoreconsole.exe exits with code -536852669 which indicates an error.
[06/08/2022 20:55:21] End script phase.
[06/08/2022 20:55:21] Error: An unexpected error happened during phase CoreEngineExecution of job.
[06/08/2022 20:55:21] Job finished with result FailedExecution
The addon is a custom exporter (based on IExportContext) and was processing a relatively large model (7GB of Revit files). Any idea what may have caused the crash?

Tf-PGP descryption - The Execute method on the task returned error code 0x80131509 (No encryption methods specified)

When i am trying descrpting the encrypted files with TF- PGP task in SSIS.I am getting below message with SQL agent job Source: TF PGP Task Description: The Execute method on the task returned error code 0x80131509 (No encryption methods specified). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:08:55 PM Finished: 1:09:02 PM Elapsed: 6.609 seconds. The package execution failed. The step failed.
When i am trying the same execute from SSIS package i am getting below error message.

SSIS Workflow issue when run by Task Scheduler

I have a SSIS Workflow that is a little unreliable.
The Normal procedure should be as follows: Task Scheduler Job starts batch File. Batch File starts SSIS Job.
This process produces this error:
Error: 2020-12-08 07:10:43.95
Code: 0xC02090F5
Source: Data Flow Task Connect to Impala [2132]
Description: The component "Connect to Impala" (2132) was unable to process the data. ERROR [08S01] [Cloudera][ImpalaODBC] (120) Error while retrieving data from in Impala: [08S01] : SSL_read: error code: 0
End Error
Error: 2020-12-08 07:10:43.95
Code: 0xC0047038
Source: Data Flow Task SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "Connect to Impala" (2132) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
But when I start the Batch File, the SSIS Job is executed successfully. Even when I start the Job within MS Visual Studio there are no issues.
Google makes a hint that there could be an issue with the ODBC connection. I am using an 32 Bit ODBC Driver for Impala (User DSN). Also tried it with 64 Bit but doesn't work either.
I appreciate every answer.
Thanks
Problem solved
Please see this solution: https://community.cloudera.com/t5/Support-Questions/ERROR-SSL-read-error-code-0-with-IMPALA-from-R-programming/td-p/280561
It is about timeout parameters.

An unexpected error happened during phase Publishing of job

I am trying to use the ForgeApp with Revit. For the same I am trying to execute the workitem from Postman. During the execution I am getting below error.
An unexpected error happened during phase Publishing of job.
The parts of the actual report (after removing some of the sensitive info) is as follows:
[10/15/2020 05:45:24] Finished running. Process will return: Success
[10/15/2020 05:45:24] ====== Revit finished running: revitcoreconsole ======
[10/15/2020 05:45:25] End Revit Core Engine standard output dump.
[10/15/2020 05:45:25] End script phase.
[10/15/2020 05:45:25] Start upload phase.
[10/15/2020 05:45:25] Error: Non-optional output [result.json] is missing.
[10/15/2020 05:45:25] Error: An unexpected error happened during phase Publishing of job.
[10/15/2020 05:45:25] Job finished with result FailedMissingOutput
[10/15/2020 05:45:25] Job Status:
From the error it is clear that the Plugin has failed in processing but it gives give much idea as to why it has failed . After receiving this error, I tried to debug locally by following https://forge.autodesk.com/blog/design-automation-debug-revit-plugin-locally
But during debugging it is failing with below error while Executing the Plugin itself. It executes the Onstartup without any issues but after that it is not going in HandleDesignAutomationReadyEvent.
Managed Debugging Assistant 'FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0xdb9b8a8d, on thread 0x3784*
So I am not sure what to ahead to resolve this. If I can get this working somehow in the Local with Debugger or through Postman then it would help.
Further update - I have now found the root cause. Even though it was complaining about the missing output file leading me to believe the code was not running properly, the actual root cause was that it was not finding the model from the inputFile parameter. This became clear once I tried putting Console.Write in the Plugin code and then debugging became easy. I wasn't sure Console would be printed in the output at first and hence turned the debug logs off at first . But as I didn't have any other means to have the verbose logging , I put in lots of Console write and now got to know the root cause. Thanks

SSIS Package Failing when called through DTExec - fine through VS

I have an SSIS package that is running fine when I press the "Start" button in VS, but when I run it via DTExec, it's bombing part way through with the following errors.
Error: 2020-06-10 13:47:20.22
Code: 0xC0047038
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on JCMAST - WA returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
Error: 2020-06-10 13:47:20.49
Code: 0xC0047022
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Co, Job Yesterday Sort" (47) failed with error code 0xC0047020 while processing input "Sort Input" (50). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
End Error
I can see that the package is called properly, as I can see all of the different validation and pre-execution steps. These are the only errors that come up in the entire run.
Everything that I've Googled so far with these errors typically come with some sort of additional error. Not the case here.
What's so confusing to me is why it would run manually, but not through cmd.
EDIT: Full error output
Started: 2:55:09 PM
Error: 2020-06-10 14:55:14.35
Code: 0xC0047038
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on JCMAST - WA returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
Error: 2020-06-10 14:55:14.64
Code: 0xC0047022
Source: JCMAST to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Co, Job Yesterday Sort" (47) failed with error code 0xC0047020 while processing input "Sort Input" (50). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
End Error
Error: 2020-06-10 14:55:20.67
Code: 0xC0047038
Source: EMP Files to SQL SSIS.Pipeline
Description: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on PREMP - WA returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 2:55:09 PM
Finished: 2:55:34 PM
Elapsed: 24.343 seconds
SSIS package "D:\SafetyServicesProjects\WebAppsTest2\WebAppsTest2\Package.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x4004300C at Data Flow Task, SSIS.Pipeline: Execute phase is beginning.
Error: 0xC0047038 at Data Flow Task, SSIS.Pipeline: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on ODBC Source returned error code 0x80004005. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Information: 0x40043008 at Data Flow Task, SSIS.Pipeline: Post Execute phase is beginning.
Information: 0x4004300B at Data Flow Task, SSIS.Pipeline: "OLE DB Destination" wrote 0 rows.
Information: 0x40043009 at Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Data Flow Task
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "D:\SafetyServicesProjects\WebAppsTest2\WebAppsTest2\Package.dtsx" finished: Failure.
Well. Figured it out.
Turns out it all came down to versioning. I was using a version of IBM iAccess ODBC that had issues with Windows 10. Upgraded to the latest version and it worked.