# UNIMPLEMENTED: grpc: service not implemented in server: mypackage.MyService

- **ID:** `grpc/grpc-unimplemented-service`
- **Domain:** grpc
- **Category:** config_error
- **Error Code:** `ESVC`
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

The gRPC server does not register or implement the requested service, often due to missing stub registration or proto mismatch.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| gRPC v1.61.0 | active | — | — |
| gRPC v1.58.0 | active | — | — |
| gRPC v1.54.0 | active | — | — |
| Node.js gRPC v1.24.0 | active | — | — |

## Workarounds

1. **Register the service implementation on the server, e.g., in Python: `server.add_insecure_port('[::]:50051'); server.start()` after adding `add_MyServiceServicer_to_server(MyServiceServicer(), server)`.** (90% success)
   ```
   Register the service implementation on the server, e.g., in Python: `server.add_insecure_port('[::]:50051'); server.start()` after adding `add_MyServiceServicer_to_server(MyServiceServicer(), server)`.
   ```
2. **Verify that the client and server use the exact same proto file version; regenerate stubs if mismatched.** (80% success)
   ```
   Verify that the client and server use the exact same proto file version; regenerate stubs if mismatched.
   ```

## Dead Ends

- **Restarting the server without recompiling the service** — The service registration is missing in the code; restart doesn't add it. (95% fail)
- **Adding the service proto file to the client only** — The server must implement the service; client-side proto doesn't help. (90% fail)