Windows Service Bus Configuration requires a "RunAs" service account which seems like it should be a fairly simple requirement. Unfortunately, if the configuration does not like the user you've entered it displays the generic error message, "Specified RunAs account is invalid." without providing any indication of the problem.
In my case, the service account was fine. The problem was that I logged in with a local administrator account and was trying to use a domain service account, which is not supported. Once I figured out the issue and logged in with a domain account the error went away.
Below are the supported combinations:
Hopefully this article will save someone else the headache of wondering why their service account is considered "invalid".
In my case, the service account was fine. The problem was that I logged in with a local administrator account and was trying to use a domain service account, which is not supported. Once I figured out the issue and logged in with a domain account the error went away.Below are the supported combinations:
| Environment | Logged In Account | RunAs Account | Support |
|---|---|---|---|
Domain
|
Domain
|
Domain
|
Supported
|
Domain
|
Domain
|
Local
|
Not supported.
|
Domain
|
Local
|
Domain
|
Not supported.
|
Domain
|
Local
|
Local
|
Either in development environment (1-box) or by using SQL Authentication.
|
Workgroup
|
Domain
|
Domain
|
Not supported.
|
Workgroup
|
Domain
|
Local
|
Not supported.
Not possible.
|
Workgroup
|
Local
|
Domain
|
Not supported.
Not possible.
|
Workgroup
|
Local
|
Local
|
Either in development environment (1-box) or by using SQL Authentication.
|
Hopefully this article will save someone else the headache of wondering why their service account is considered "invalid".
