Quantcast
Channel: Service Bus forum
Viewing all articles
Browse latest Browse all 1916

Service Bus for Windows Server throws exception on farm configuration (wizard and Powershell)

$
0
0

I am having issues with installing the latest Service Bus for Windows bits.  The configuration wizard continually crashes on the New Farm Configuration page as soon as it tries to validate the service account user and password with the following crash information:

Problem signature:
  Problem Event Name:CLR20r3
  Problem Signature 01:M5IL4IUBOFXDMX4GN4CG3WKPQFC0FQYW
  Problem Signature 02:2.0.20922.0
  Problem Signature 03:505e1b54
  Problem Signature 04:System.DirectoryServices
  Problem Signature 05:4.0.30319.17929
  Problem Signature 06:4ffa5bdb
  Problem Signature 07:8e
  Problem Signature 08:18
  Problem Signature 09:PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX
  OS Version:6.1.7601.2.1.0.274.10
  Locale ID:1033
  Additional Information 1:b35a
  Additional Information 2:b35a3a62e109cdf932d08dbd19f168e5
  Additional Information 3:a28a
  Additional Information 4:a28a81bcedc49de2300ad0e7e13de03e

Configuration through PowerShell also fails with the following error:

PS C:\Program Files\Service Bus\1.0> New-SBFarm -SBFarmDBConnectionString "data
source=localhost\sqlexpress;integrated security=true" -CertificateAutoGeneration
Key $mycert -verbose
New-SBFarm : The specified directory service attribute or value does not exist.
At line:1 char:1
+ New-SBFarm -SBFarmDBConnectionString "data
source=localhost\sqlexpress;integrate ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : NotSpecified: (:) [New-SBFarm], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Micr
   osoft.ServiceBus.Commands.NewSBFarm

Stack Trace from event log:

System.Runtime.InteropServices.COMException (0x8007200A): The specified directory service attribute or value does not exist.

   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()
   at System.DirectoryServices.AccountManagement.ADStoreCtx.IsContainer(DirectoryEntry de)
   at System.DirectoryServices.AccountManagement.ADStoreCtx..ctor(DirectoryEntry ctxBase, Boolean ownCtxBase, String username, String password, ContextOptions options)
   at System.DirectoryServices.AccountManagement.PrincipalContext.CreateContextFromDirectoryEntry(DirectoryEntry entry)
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer()
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit()
   at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()
   at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()
   at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable`1 identityType, String identityValue, DateTime refDate)
   at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithType(PrincipalContext context, Type principalType, IdentityType identityType, String identityValue)
   at System.DirectoryServices.AccountManagement.UserPrincipal.FindByIdentity(PrincipalContext context, IdentityType identityType, String identityValue)
   at System.DirectoryServices.AccountManagement.UserPrincipal.get_Current()
   at Microsoft.ServiceBus.Commands.NewSBFarmBase.ProcessRecordImplementation()
   at Microsoft.ServiceBus.Commands.ServiceBusBaseCmdlet.ProcessRecord()

I believe this may have something to do with permissions when accessing ActiveDirectory.  I am running the install and configuration as a local admin on the server but it's likely that I don't have whatever AD permissions the installer needs.

I found the exact issue on StackOverflow @ stackoverflow.com/questions/12352484/service-bus-1-0-beta-new-sbfarm-the-specified-directory-service-attribute-or-v but there was not a solution there and he just ended up going to RabbitMQ.

I have a sinking suspicion that this may be the root cause: http://blogs.msdn.com/b/dsadsi/archive/2009/08/28/getting-an-exception-the-specified-directory-service-attribute-or-value-does-not-exist-when-you-try-to-search-a-user-in-an-ad-container-using-system-directoryservices-accountmanagement-userprincipal-findbyidentity.aspx

Does anybody have any ideas? Is a fix needed in the installer and PowerShell commands?


Viewing all articles
Browse latest Browse all 1916

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>