Wednesday, February 13, 2013

Specified RunAs Account is Invalid

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:

EnvironmentLogged In AccountRunAs AccountSupport
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".

4 comments:

  1. I log, on my windows7 workstation, with a domain account (that is also in the local administrator group) and I try to create my Farm with the self user id. As you say I'm in the context of the first line in your table combinations. And I still have the "account is invalid" message.
    Any idea?

    ReplyDelete
  2. If you're using Windows Authentication, does that user also have SysAdmin privileges on the SQL server?

    If you're logged in with a domain account you created (not built-in) which has local administrator privileges and access to the SQL server then I can't think of any reason why it shouldn't let you configure a new farm.

    Please feel free to email me whatever information/screenshots you feel might help troubleshoot the problem and I'll do my best to assist.

    ReplyDelete
  3. I find the origin of my problem. The origin is in the Active Directory configuration. The user profiles of my AD are defined under a OU node (not the default CN Users). In this case the WellKnowObjects attribute of the DC node must be set to the OU users node. The SB installer probably uses the user WellKnowObjects to check the user under the service will run.

    ReplyDelete
  4. See tsca answer here:
    http://social.msdn.microsoft.com/Forums/en-US/servbus/thread/3d803e15-606a-4f06-96fe-97c23ad3c01a/

    ReplyDelete