Partilhar via

Service Bus EAI and EDI Labs – A ‘living’ blog post of issues you might encounter while using Service Bus EAI and EDI Labs

  • Artigo

Through this blog post, I am making an effort to collate some of the most common issues (and provide troubleshooting information) for issues one could face while using Service Bus EAI and EDI Labs bits. I call this a ‘living’ post because I am going to update this post with any issue I come across.

If you encountered an issue and came here looking for it and didn’t fit it, sorry about that. Do let me know of that issue, and I’ll include it here. If you know the solution, please share that as well. Even if you don’t know, no issues, I’ll find out and include it. Thanks.

 

 

Error Installing Service Bus Connect Feature

You might encounter an error stating the following

Error -2147467259: failed to create SQL database: SBConnect, error detail: unknown error

Resolution: You might want to retry the wizard run and when you specify the details for the SQL Server that would contain the configuration store, you might want to give the actual computer name or a dot (.) instead of specifying localhost. That should fix the problem.

Authorization Error While Creating an LOB Target

You might encounter an authorization error (401) while creating an LOB target using the Server Explorer in Service Bus EAI/EDI Labs. To fix this, verify that you started Visual Studio as an administrator. You need to do that to create an LOB target.

Authorization Error While Sending a Message to an LOB

You just finished creating your LOB target in Server Explorer using Service Bus EAI/EDI Labs. The target shows as enabled through that green arrow button. You have an end-to-end message flow set up, where a message comes in through a bridge and gets routed to the LOB server for which you created a target. However, when you send a message to test this solution, you get an authorization error, like the following:

Win32Exception:Logon failure: unknown user name or bad password

To troubleshoot this issue, right-click your LOB target, and select Properties.

image

In the Properties window, select the RuntimeSecurity property, and then the ellipsis button against that property.

image

In the Edit Security dialog box that opens up, select the appropriate option to specify user credentials and the enter the appropriate values. For example, because Service Bus Connect supports Windows Authentication for connecting to SQL Server, for a SQL Server LOB target you could select Fixed Windows Credential, and then enter your username, password, and domain.

image

Enter OK and try sending the message again.

Comments

  • Anonymous
    August 23, 2012
    Regarding "Authorization Error While Sending a Message to an LOB". I get a very similar error saying "The user has not been granted the requested logon type at this computer". Did you every encounter the same problem and know how to fix that? I can see the failed logon in the Windows NT/Security logs, but that information doesn't help me very much. Maybe anyone else? Log entry:

Date 24.08.2012 11:04:36 Log Windows NT (Security) Source Microsoft-Windows-Security-Auditing Category (12544) Event 4625 Computer VM-XY-WinServer.xy.mydomain.de Message An account failed to log on. Subject: Security ID: S-1-5-18 Account Name: VM-XY-WINSERVER$ Account Domain: PL Logon ID: 0x3e7 Logon Type: 2 Account For Which Logon Failed: Security ID: S-1-0-0 Account Name: svcEAI Account Domain: PL Failure Information: Failure Reason: %%2308 Status: 0xc000015b Sub Status: 0x0 Process Information: Caller Process ID: 0xd58 Caller Process Name: C:WindowsSystem32inetsrvw3wp.exe Network Information: Workstation Name: VM-XY-WINSERVER Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi   Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

Regards