If you're experiencing issues with your AWS services, then please refer to the AWS Health Dashboard. You can find the overall status of ongoing outages, the health of AWS services, and the latest updates from AWS engineers.
AWS Transform job stuck after approval – assessment shows 1 of 2 .NET solutions failed
Hello,
I am encountering an issue while running a .NET modernization job using AWS Transform where the job is not progressing to the transformation phase even after the approval step.
Repository used: https://gitlab.com/sakshideore/dotnet_modernization.git
This repository is based on the following AWS sample: https://github.com/aws-samples/net-modernization
Steps performed:
- Cloned the repository from GitHub.
- Pushed the repository to GitLab.
- Uploaded the source code to an Amazon S3 bucket.
- Created the required repository connection in AWS Transform.
- AWS Transform successfully discovered the repository.
- The code assessment phase completed and generated the assessment report.
- Proceeded to the Review and start transformation step.
- Reviewed the job summary and selected Send for approval.
- The approval request was submitted.
However, the job does not proceed to the Transform phase and remains in Awaiting user input / AWAITING_HUMAN_INPUT state.
Assessment summary visible in the console:
Projects detected: 2 Lines of code: 1,081 Repositories selected: 1 Dependent repositories: 0 Private NuGet packages: 0
According to the assessment results:
1 solution was successfully assessed 1 solution failed with an internal processing error
The worklogs contain the following message:
"Assessment failed due to internal processing error"
Additionally, the failing solution appears as 'None', which makes it unclear which solution or project in the repository caused the issue.
Due to this partial assessment failure, the job does not proceed to the Transform stage even after the approval request has been submitted.
Questions:
Why does the assessment report display the failing solution as 'None' instead of the actual solution name? Could this behavior be related to the repository structure or solution configuration? Are there specific requirements for the .NET solution structure when running AWS Transform modernization jobs? What steps should be taken to identify and resolve the solution that failed during assessment?
Screenshots of the job plan, assessment summary, and transformation review step will be attached for additional context.
Any guidance would be appreciated.
Thank you.
- Newest
- Most votes
- Most comments
Based on the symptoms you're describing, where your AWS Transform job is stuck after approval with one solution failing during assessment, here are the key troubleshooting steps and considerations:
Understanding the Assessment Failure:
When a solution shows as 'None' in the assessment report with an "internal processing error," this typically indicates that AWS Transform encountered an issue while analyzing that particular solution file. This could be due to several factors related to the solution structure, project types, or dependencies.
Supported Project Types:
AWS Transform can only transform specific .NET project types including MVC, Web, WCF, Console, class library, UI framework (Razor pages), and unit test packages. If your repository contains unsupported project types or configurations, they may cause assessment failures.
Steps to Diagnose and Resolve:
-
Review Transformation Logs: Check the detailed transformation logs for specific error messages that might indicate what caused the assessment failure. These logs will provide more context than the generic "internal processing error" message.
-
Verify Solution Structure: Ensure that both solutions in your repository follow standard .NET solution structures and contain only supported project types. Mixed or non-standard configurations can cause processing issues.
-
Check Dependencies: Review any NuGet package dependencies and ensure they are properly configured. If you're using private NuGet feeds, verify they are correctly configured in AWS Transform.
-
Examine Build Configuration: Verify that both solutions can build successfully in their current environment. Build issues in the source code can prevent proper assessment.
-
Review the Transformation Detail Report: Download the detailed report for the repository to get more granular information about what was detected and what failed during assessment.
Why the Job Remains Stuck:
The job is likely remaining in the "AWAITING_HUMAN_INPUT" state because the assessment phase didn't complete successfully for all solutions. AWS Transform requires a complete assessment before proceeding to the transformation phase, even after approval.
Recommended Next Steps:
- Contact AWS Support with your transformation job ID, AWS account ID, region, and any error messages or screenshots from the logs
- Verify that the failing solution can be built independently outside of AWS Transform
- Consider removing or fixing the problematic solution and rerunning the assessment
- If one solution is critical and the other is optional, you might consider running separate transformation jobs for each solution
The fact that one solution assessed successfully suggests the issue is specific to the configuration or content of the second solution rather than a broader connectivity or permissions problem.
Sources
Best practices and troubleshooting - AWS Transform
Reviewing your plan to prepare for transformation - AWS Transform
Transformation Reports - AWS Transform
Relevant content
- asked 3 months ago
- asked 7 months ago
- AWS OFFICIALUpdated a year ago
