| Nick Malik 2004-02-08, 8:42 am |
| Is this a Biztalk question or a SQL Server Question? It isn't clear. From
your message, it appears that this is a SQL Server question.
In your SQL Job, you specify the account that you want to run your job
under. If it is the local system account, you will have to use SQL
permissions to open the connection, because local system accounts do not get
domain credentials. Also consider the possibility that the local system
account may not be able to write to a specific output location. Look at the
identity you are running your job under and make sure it is an account that
has access to the data and any other resources that your job requires.
On the other hand, if you are having problems getting data to Biztalk...
I'm sure that _you_ have permission to see the database, but does _Biztalk_
have permission? Check the services to see what account the Biztalk and
XLANG services use. If it is local system account, then you may not be able
to access SQL Server. Change to a domain account. Open Component Services
and make sure that the components used by Biztalk are also running under
domain accounts.
HTH,
--- Nick
Biztalk Bum
"Anunay" <anonymous@discussions.microsoft.com> wrote in message
news:c60e01c3ed79$e7856290$a501280a@phx.gbl...
> I've created a job in SQL Server to fetch all the columns
> from a table [POLL54]. When I start the job I get
> following error in the event log.
> ----------------------
> Event Type: Error
> Event Source: RFSQL
> Event Category: None
> Event ID: 10
> Date: 2/7/2004
> Time: 6:14:59 PM
> User: N/A
> Computer: BLRKEC24331D
> Description:
> A worker thread reported a failure: Access is denied.
>
> The error code is shown in the data area below.
> The operation was: CoCreateInstance(CLSID_SQLWorker)
> The worker thread was working on:
> Job Name: poll54
> SQL Script: SELECT *
> FROM [master].[dbo].[POLL54] for xml auto
> ----------------------
>
> I have granted full permissions on POLL54 table. I'm able
> to execute above query in Enterprise manager. I also tried
> the above query without/with [master] and [dbo], but I get
> the same error.
|