|
Home > Archive > BizTalk Server Applications Integration > June 2004 > Problem running BizTalk Adaptor for SQL Server
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problem running BizTalk Adaptor for SQL Server
|
|
| Campbell McNeill 2004-06-20, 11:09 pm |
| Hi,
I've currently got SQL Server Adapter for BizTalk 2002
installed but am having problems executing a stored
procedure.
I installed the Adapter as the local administrator. I am
using a UDL file to link to my SQL server on a different
machine and the UDL tests out OK.
The error event comes from the "RFSQL" source and has the
following contents:
A worker thread reported a failure: The server process
could not be started because the configured identity is
incorrect. Check the username and password.
The error code is shown in the data area below.
The operation was: CoCreateInstance(CLSID_SQLWorker)
The worker thread was working on:
Job Name: BENEFITS RECIEVE
SQL Script: Exec [sp_BENEFITS_RECIEVE]
I've tried running the package / service under both the
local admin account, and a domain account that has admin
access on both this machine and the sql server.
I also tried re-installing the Adapter from the console of
the BizTalk server.
Any help would be greatly appreciated.
| |
| Andres Felipe Arguello 2004-06-20, 11:09 pm |
| I has the same problem in enviroment with sql and biztalk in different
machines, try to use the user of the application, that can access the
domain, and this user is in the local admin group of both machines. This
user is db_owner of the db that has the SP and use this user to start the
service SQL Adaptader for Biztalk, and Biztalk too.
Maybe this would help
Andres Felipe Arguello
"Campbell McNeill" <anonymous@discussions.microsoft.com> wrote in message
news:1d84401c4547b$473f7c30$a601280a@phx
.gbl...
> Hi,
>
> I've currently got SQL Server Adapter for BizTalk 2002
> installed but am having problems executing a stored
> procedure.
>
> I installed the Adapter as the local administrator. I am
> using a UDL file to link to my SQL server on a different
> machine and the UDL tests out OK.
>
> The error event comes from the "RFSQL" source and has the
> following contents:
>
> A worker thread reported a failure: The server process
> could not be started because the configured identity is
> incorrect. Check the username and password.
>
> The error code is shown in the data area below.
> The operation was: CoCreateInstance(CLSID_SQLWorker)
> The worker thread was working on:
> Job Name: BENEFITS RECIEVE
> SQL Script: Exec [sp_BENEFITS_RECIEVE]
>
>
> I've tried running the package / service under both the
> local admin account, and a domain account that has admin
> access on both this machine and the sql server.
>
> I also tried re-installing the Adapter from the console of
> the BizTalk server.
>
> Any help would be greatly appreciated.
| |
|
| Hi,
I gave this a go, but to no avail.
On further scrutiny, it looks like this is a COM+ error
with the error Id : 8000401a.
I have verified that the account the COM+ package is
running under is valid, this also happens to be the same
account that BizTalk is running under.
I don't think its the SQL Server, I think its more to do
with it trying to access the BizTalk clients that the
service is writing to.
Any other suggestions would be greatly appreciated, I dont
want to have to re-install the BizTalk server as its in a
production environment.
Campbell.
>-----Original Message-----
>I has the same problem in enviroment with sql and biztalk
in different
>machines, try to use the user of the application, that
can access the
>domain, and this user is in the local admin group of both
machines. This
>user is db_owner of the db that has the SP and use this
user to start the
>service SQL Adaptader for Biztalk, and Biztalk too.
>Maybe this would help
>Andres Felipe Arguello
>"Campbell McNeill" <anonymous@discussions.microsoft.com>
wrote in message
> news:1d84401c4547b$473f7c30$a601280a@phx
.gbl...
the[vbcol=seagreen]
of[vbcol=seagreen]
>
>
>.
>
| |
| Jan Eliasen 2004-06-26, 10:53 am |
| I had a similar problem once. The solution, as I recall it was to open
the "Compoennt Services" mmc, open the com+-application part and right
click on the BizTalk Adapter for SQL Server com+-application. Choose
properties, and deselect the "Enforce accesschecks" checkbox.
Jan Eliasen
On Mon, 21 Jun 2004 02:46:26 -0700,
<anonymous@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Hi,
>
>I gave this a go, but to no avail.
>
>On further scrutiny, it looks like this is a COM+ error
>with the error Id : 8000401a.
>
>I have verified that the account the COM+ package is
>running under is valid, this also happens to be the same
>account that BizTalk is running under.
>
>I don't think its the SQL Server, I think its more to do
>with it trying to access the BizTalk clients that the
>service is writing to.
>
>Any other suggestions would be greatly appreciated, I dont
>want to have to re-install the BizTalk server as its in a
>production environment.
>
>Campbell.
>
>in different
>can access the
>machines. This
>user to start the
>wrote in message
>the
>of
--
Jan Eliasen, representing himself and not the company he works for.
| |
| Campbell McNeill 2004-06-26, 10:53 am |
| Got it sorted.
It turned out that if I started the adapter service from the console then
all worked fine.
The wierd thing is that once I had started it once on the console, I could
mess about with it as much as I liked using a terminal.
Cheers for the help guys.
C.
"Jan Eliasen" <spam@eliasen.dk> wrote in message
news:l5jdd0pp2p6ifge0ov1hqepls0vuu9no4u@
4ax.com...
>I had a similar problem once. The solution, as I recall it was to open
> the "Compoennt Services" mmc, open the com+-application part and right
> click on the BizTalk Adapter for SQL Server com+-application. Choose
> properties, and deselect the "Enforce accesschecks" checkbox.
>
> Jan Eliasen
>
> On Mon, 21 Jun 2004 02:46:26 -0700,
> <anonymous@discussions.microsoft.com> wrote:
>
>
> --
> Jan Eliasen, representing himself and not the company he works for.
|
|
|
|
|