Other features or issues related to Microsoft Partner Center
Store Developer onboarding fails with HTTP 500 INTERNAL_ERROR (OneVet initiation failed after 5 attempts)
Hello Microsoft Team,
I am unable to complete the Microsoft Store Developer onboarding process because of an internal server error.
The current status of my account is:
• Email verification: Completed successfully
• Business verification: Completed successfully
However, when I reach the Contact Details step, the onboarding process always fails with an HTTP 500 Internal Server Error.
The browser Network response shows:
HTTP 500 INTERNAL_ERROR
Error:
"OneVet initiation failed after 5 attempts. 1S API call skipped."
I have reproduced the issue multiple times and have already tried:
• Google Chrome and Microsoft Edge
• Incognito/InPrivate mode
• Different computers
• Different internet connections
• Restarting the onboarding process several times
The result is always the same.
Since both my email verification and business verification have already been approved successfully, this does not appear to be a business verification issue. The failure only occurs during the Store Developer onboarding workflow.
I previously contacted Microsoft Support and opened a Partner Center support request. Unfortunately, the request was routed to the Business Verification team and then closed because they determined that the issue was not related to business verification.
Based on the HTTP 500 response and the "OneVet initiation failed after 5 attempts" error, this appears to be an internal backend issue within the Microsoft Store Developer onboarding service.
I have attached screenshots showing:
- The HTTP 500 Internal Server Error.
- The browser Network response containing: "OneVet initiation failed after 5 attempts."
- Successful Business Verification.
- The onboarding failure at the Contact Details step.
Could you please investigate this backend issue or forward my case to the Microsoft Store Developer onboarding engineering team?
If required, I can also provide the Correlation ID and additional browser logs.
I would appreciate it if this issue could be reviewed by the Microsoft Store Developer onboarding engineering team, as it appears to be a backend service issue rather than a business verification issue.
Thank you for your assistance.