Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for DataSphere
    • Resolving project startup errors in DataSphere
    • Resolving the `Failed to deserialize variable` error
    • `Table of Contents` extension is missing in the JupyterLab extension catalog
    • Getting access to GPU g1.1 and higher configurations in DataSphere
    • Resolving issues with long code execution within DataSphere project cells
    • Resolving the `Servant not allocated` error when running code within DataSphere project cells
    • Resolving the `TestsFailure` error
    • Resolving the `Token authentication is enabled` error
    • Resolving errors with project access or login
    • Resolving the `KernelNotResponding The kernel died unexpectedly` error
    • Fixing the `ConnectTimeoutError` error when installing packages through pip
    • Resolving the `Device or resource busy` error

In this article:

  • Issue description
  • Solution
  1. DataSphere
  2. Resolving errors with project access or login

Resolving errors with project access or login

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution

Issue descriptionIssue description

When running a project, you encounter errors associated with changes in its computing configurations.

Error examples:

  • Execute error: Servant g2.1 not allocated: Internal Error
  • Execute error: Failed to allocate servant c1.4: internal error. Please try again

SolutionSolution

Log in to the project once again by selecting File → Stop IDE Execution in the menu.

Was the article helpful?

Previous
Resolving the `Token authentication is enabled` error
Next
Resolving the `KernelNotResponding The kernel died unexpectedly` error
© 2025 Direct Cursus Technology L.L.C.