Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se describen los errores comunes de inicialización y entrega de apps en
App Engine, y los métodos para solucionarlos.
Error de permiso cuando se crea una app con la cuenta de servicio predeterminada
Cuando creas una app después de habilitar la
API de App Engine por primera vez, es posible que falle con los siguientes errores:
gcloud CLI
An internal error occurred while calling service consumer manager for service account.
Creating App Engine application in projectPROJECT and REGION....failed. DEBUG: (gcloud.app.create) Error Response: [13] an internal error has occurred
Solicita registros.
Service account creation is not allowed on this project.
Para resolver este problema, debes quitar de forma temporal la restricción constraints/iam.disableServiceAccountCreation de la política de la organización para permitir la creación y la implementación de la cuenta de servicio predeterminada de App Engine. La cuenta
de servicio predeterminada es necesaria para crear la app y no se puede omitir. Esto también se
aplica cuando usas una cuenta de servicio por versión.
La cuenta de servicio predeterminada de App Engine se puede borrar o reemplazar
por una cuenta de servicio que crees después de una implementación realizada de forma correcta.
Si usas una cuenta de servicio que creaste, revisa la Descripción general de las recomendaciones de roles para comprender cómo aplicar la restricción de permisos, como proporcionar una función de creador de tokens en la cuenta de servicio que creas para el agente de servicio.
Errores de seguridad cuando se usan servicios agrupados en paquetes heredados para Python
Si usas una API de servicios agrupados en paquetes heredados cuando se inicia una app de Python 3,
es posible que veas el siguiente mensaje de error:
Attempted RPC call without active security ticket
Este error puede ocurrir en situaciones como la lectura de ciertos valores de Memcache cuando tu app comienza a configurar una conexión de base de datos o establecer una variable global.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-01 (UTC)"],[[["\u003cp\u003eThis page details common errors encountered during App Engine app initialization and serving, along with their troubleshooting methods.\u003c/p\u003e\n"],["\u003cp\u003eA permission error can occur when creating an App Engine app due to the organization policy constraint \u003ccode\u003econstraints/iam.disableServiceAccountCreation\u003c/code\u003e, which prevents the creation of the default service account.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve the default service account creation error, temporarily remove the \u003ccode\u003econstraints/iam.disableServiceAccountCreation\u003c/code\u003e policy to allow for its provisioning, as it is required during app creation.\u003c/p\u003e\n"],["\u003cp\u003eWhen using legacy bundled services with Python 3 apps, a security error ("Attempted RPC call without active security ticket") may arise, particularly when accessing services like Memcache during startup.\u003c/p\u003e\n"],["\u003cp\u003eTo fix the security errors when using legacy bundled services, move the logic that causes the error to a warmup request.\u003c/p\u003e\n"]]],[],null,["# Troubleshoot serving issues in App Engine\n\n\u003cbr /\u003e\n\n\u003cbr /\u003e\n\n\nThis page describes common app initialization and serving errors in\nApp Engine and methods to troubleshoot them.\n\n### Permission error when creating an app with the default service account\n\nWhen you create an app after enabling the\nApp Engine API for the first time, it might fail with the following errors: \n\n### gcloud CLI\n\n An internal error occurred while calling service consumer manager for service account.\n Creating App Engine application in project\u003cvar translate=\"no\"\u003ePROJECT\u003c/var\u003e and \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e....failed. DEBUG: (gcloud.app.create) Error Response: [13] an internal error has occurred\n\n### Request logs\n\n Service account creation is not allowed on this project.\n\n### Console\n\n Error while initialising App Engine.\n\nThis error might occur due to the enforcement of the organization policy constraint [`constraints/iam.disableServiceAccountCreation`](/resource-manager/docs/organization-policy/restricting-service-accounts#disable_service_account_creation) when creating your\napp. This policy prevents the provisioning of the [App Engine default service account](/appengine/docs/standard/configure-service-accounts) `PROJECT_ID@appspot.gserviceaccount.com`.\n\nTo resolve this issue, you must temporarily remove the organization policy\nconstraint `constraints/iam.disableServiceAccountCreation` to allow for the\ncreation and deployment of the App Engine default service account. The default\nservice account is necessary for app creation and can't be skipped. This is also\napplicable when you use a per-version service account.\nThe App Engine default service account can be deleted or replaced\nwith a service account that you create after successful deployment.\n\nIf you are using a service account that you created, review the [Overview of role recommendations](/policy-intelligence/docs/role-recommendations-overview)\nto understand how to enforce restricting permissions, such as providing a\ntoken creator role on the service account you create for the service agent.\n\n### Security errors when using legacy bundled services for Python\n\nIf you use a legacy bundled services API when a Python 3 app is starting up,\nyou might see the following error message: \n\n Attempted RPC call without active security ticket\n\nThis error might occur in scenarios such as, reading certain values from\n[Memcache](/appengine/docs/standard/services/memcache) when your app is starting\nto configure a database connection or set a global variable.\n\nTo resolve this issue, you could try moving such logic into a\n[warmup request](/appengine/docs/standard/configuring-warmup-requests)."]]
