ESB Configuration Tool Error

Question

I'm getting an error when I run the ESB Configuration Tool. I'm trying to enable the Exception Management Database: I specify my local server as the SQL server, change the BizTalk Admin Group and BizTalk App Group to match my two domain security groups, and click Apply Configuration.

The config runs for a few seconds, then I get an error that reads: "Exception calling "Create" with "0" argument(s): "Create failed for Login 'MyDomain\BizTalk Server Administrators'."

I'm using the latest version of the BizTalk ESB toolkit 2.0. on SQL server 2008, Windows Server 2008, and BizTalk Server 2009.

Answer 1

Can you try putting the domain logins in the ESBconfigurationtool.exe.config file(under c:/program Files/Microsoft BizTalk ESB Toolkit 2.0/bin ) directly and then run the config tool?

Answer 2

I used the compiled source to create the web portal application for me, then i just ran the scripts in powershell to enable all of the ESBExceptionDb stuff. I think there was a couple of create sql scripts i ran as well. aslo make sure you set the web app to 32 bit mode (before compiling and int he IIS app pool after ppublishing) Also i had to remove the all.exceptions send port and a couple of generic error orchestrations afterwards.

so i really didnt even use the ESB configuration tool as i had similar problems however once i installe dthe ESB portal, Operations and set the IIS app pool (also i did change the configuration in the exe.config file) the ESB configuration tool works now. Not sure if it was the running of the exception handling powershell scripts

Answer 3

I'm getting similar errors with the configuration tool while enabling the Exception Services: "Exception retrieving member "Create". The system cannot find the path specified.

---

Jimit Ndiaye

Answer 4

Have you checked to see if the BizTalk Administrators group has access in SQL? I got the same error, but for the Isolated Host group and I fixed it by adding the Isolated Host group as a login user to the SQL server with public access. I was obviously installing the ESB Toolkit to a different SQL Instance than my BizTalk SQL Instance. -Elizabeth

Answer 5

good call graham, but of course you are an indy biztalker so what else would i expect, i think my powershell scripts failed during sql db creations as well, if you try run the msi's or try to run the powershell scripts outright and you dont have sql or web project types in visual studio installed (just biztalk and cs projects) then if you watch the powershell scripts that actually build and deploy each project you will find that they dont run (because you cant even open let alone build the database/web projects). but the sql scripts are there and easy enough to run in sql studio. but again, check your sql database permissions and security access (sql trace will tell you identity you are using if you dont know) as well as checking that all the tables, sql users and stored procs were created.

Answer 6

Any further thoughts on this issue?  I am attempting to install ESB on a x64 server (2003), while my SQL Server instance is clustered on a set of Server 2008 boxes hosting SQL Server 2008.

Haven't been able to get past the Exception calling "Create" error... 

I have verified that all users in the BizTalk Server Administrators group have full access to SQL Server (gave all SysAdmin role, just to be sure)

Have also edited the config file to add Domain information / accounts there.  No joy.

Any help / insight would be *greatly* appreciated.

Full text of error from log file:


Object:  Role [ESBPortal]    Script Date: 10/28/2007 11:54:56 ******/
CREATE ROLE [ESBPortal]

ESBConfigurationTool.exe Information: 0 : Exception calling "Create" with "0" argument(s): "Create failed for Login '<mydomain>\BizTalk Server Administrators'. "
ESBConfigurationTool.exe Error: 0 : An error has occurred:
Exception calling "Create" with "0" argument(s): "Create failed for Login '<mydomain>\BizTalk Server Administrators'. "
Create failed for Login '<mydomain>\BizTalk Server Administrators'.
An exception occurred while executing a Transact-SQL statement or batch.
The server principal '<mydomain>\BizTalk Server Administrators' already exists.

Answer 7

In the event another stumbles upon this problem...

The answer is, as stated earlier:  "Can you try putting the domain logins in the ESBconfigurationtool.exe.config file(under c:/program Files/Microsoft BizTalk ESB Toolkit 2.0/bin ) directly and then run the config tool?"

The thing to remember, or to look for, is case.  Example:  In my SQL Server instance, the group had been configured as "domain\groupname"  But everywhere else on my domain, it is listed as "DOMAIN\groupname"  Manually entering "DOMAIN\groupname" did not work, though "domain\groupname" absolutely did the trick.


Hope that helps the next person to come across this "feature" :-)

Answer 8

None of these suggestion seem to work for me. Can anyone just provide the .sql file so I can be done with this! Otherwise what else can I try?

Small update.. I tried BizTalk Operators for the App Group name and it installed successfully. I deleted the database and then tried again with BizTalk Application users and it failed again. I checked active directory and the only difference between the two was Application users was a member of Domain Users. I removed it from that and it still failed for App users.

Next I will look at SQL settings.

Answer 9

I am at a loss for the SQL settings, I just adding in App Users manually via Sql studio. Now EsbException service does not crash.

Answer 10

I just tried to install ESB Toolkit 2.1 and ran into similar issue. So, based on previous posts, I realized that it could be an issue with the way Logins are created in SQL Server. So here are the steps:

1. Get the "BizTalkAdminGroup" and "BizTalkAppGroup" details from SQL Server Logins -- get the exact "Login name"

2. Update the "C:\Program Files\Microsoft BizTalk ESB Toolkit 2.1\Bin\EsbConfigurationTool.exe.Config"

For e.g.:

   <add key="BizTalkAdminGroup" value="BizTalk Server administrators" />
    <add key="BizTalkAppGroup" value="BizTalk Server Application users" />

3. Save the file and run the configuration tool

The same steps worked for me... of course, I ran into similar issue again when I tried to setup Web Services, but the same steps worked for that as well. So the catch is, the logins (group in this case) defined in SQL Server are case sensitive and configuration tool doesn't recognize it.

I hope this help.