SQL Server does not exist or access denied : 08001 when deploying Microsoft.BizTalk.ESB.BAM.Exceptions.xml

When deploying the Microsoft.BizTalk.ESB.BAM.Exceptions.xml BAM activity (as part of the Core ESB Toolkit install) we ran into this error:

---

OLE DB error: OLE DB or ODBC error: DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied : 08001

Errors in the high-level relational engine.  A connection could not be made to the data source with the DataSourceID of ‘bam_ExcByApplication’, Name of ‘bamExcByApplication’

---

The issue was that we used a SQL Server Alias while configuring BizTalk to point to our backend SQL servers.  This apparently led to the alias name being embedded into the Analysis Services artifact generation when we tried to deployed the BAM Activity.  We had the SQL Server Alias on the two BizTalk application servers.  We did not have it on the two Analysis Services cluster nodes.  Once we added it to the SSAS nodes we were able to successfully deploy the activity.

  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
Print | posted on Posted On Thursday, February 25, 2010 2:34 PM | Feedback (0)

ESB Toolkit 2.0 Portal 401 Exception

I had this exception in the Application Event Log after trying to bring up the portal in IE (after a newly installed and configured BizTalk & ESB platform):

---

Exception information:
    Exception type: WebException
    Exception message: The remote server returned an error: (401) Unauthorized.

---

I was working in a two (application) server BizTalk environment but I only had this exception on one server.  The portal came up fine on the other server.

I looked at IIS log files and found a 401 for /ESB.Exceptions.Service/ExceptionService.svc/GetUserSettings

I browsed to the /ESB.Exceptions.Service/ExceptionService.svc in IE and saw this in the Application Event Log:

---

Exception information:

Exception type: NotSupportedException

Exception message: Security settings for this service require Windows Authentication but it is not enabled for the IIS application that hosts this service.

---

Uhh... I did have that configured: Windows Integrated was turned on and Anonymous was turned off.

The issue was that I did not run the set command for NTAuthenticationProviders (specified in this KB: http://support.microsoft.com/kb/215383) on that server.  I had previously ran the set command on the other server in my environment before running the Microsoft.Practices.ESB.UDDIPublisher.exe

  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
Print | posted on Posted On Thursday, February 25, 2010 12:57 PM | Feedback (0)
Copyright © Andy Morrison