cancel
Showing results for 
Search instead for 
Did you mean: 
Machine Learning
Dive into the world of machine learning on the Databricks platform. Explore discussions on algorithms, model training, deployment, and more. Connect with ML enthusiasts and experts.
cancel
Showing results for 
Search instead for 
Did you mean: 

Error starting or creating custom model serving endpoints - 'For input string: ""'

Deep_Blue_Whale
New Contributor

Hi Databricks Community,

I'm having issues starting or creating custom model serving endpoints. When going into Serving endpoints > Selecting the endpoint > Start, I get the error message 'For input string:'

Deep_Blue_Whale_1-1771333391364.png

This endpoint had worked correctly yesterday - and the configuration of the endpoint, and the model itself has not changed. I've tried to create a new endpoint using the same model and other custom models (originally from HuggingFace), but get the same error:

Deep_Blue_Whale_2-1771333570626.png

This issue occurs on a workspace with cross-geo enabled. I'm not sure what might have changed otherwise to cause this error message today, whereas everything had worked correctly yesterday. I also don't understand what 'For input string: "" ' refers to.

Are there any ideas as to how this can be resolved? Apologies if I've missed someone else with the same issue elsewhere.

Thanks.

1 REPLY 1

emma_s
Databricks Employee
Databricks Employee

Hi, sorry you're having the issue. You mentioned you've tried to recreate the endpoint with this model and other custom models but still having the same issue. Have you tried serving one of the foundation models and seeing if that works or a really simple ml model? That way you'll narrow down the scope to whether something has changed in your environment for these custom models or not. A couple of things that could cause this would be some kind of permissions change, invalid token etc. Have you checked you still have access to all the model artifacts? If this isn't obvious you could try re-registering the model from scratch and try to serve it again. A lot of internal documentation recommends trying to check the error logs in the model serving UI, to see if there are any surfaced errors. But my guess is you can't get to this screen. I hope this helps to point you in the right direction.