I have a small orchestration with a map that uses a database lookup functoid
.
When I test the map, the lookup retreives data from the server correctly.
When I deploy the orchestration and run it, I receive the following message:

Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.

From what I've found in the newsgroups so far,  it's my understanding that
the credentials being used during the test are the currently logged in user,
which explains why it works there.

I have tried various changes to the connection string, but it seems to
ignore any sql logon parameters used. The biztalk development environment is
running on a single machine using local accounts. The sql database is on a
different machine.

I'm at a loss as to how to get the sql logon to work for this map. Any ideas
would be appreciated.

[ Post a follow-up to this message ]

I believe the database lookup functoid uses standard ADO.NET calls to create
a connection to your database. The connection string you input as your
second input parameter in the functoid should be a standard ADO.NET
connection string and if you use "Provider=SQLOLEDB.1;Initial Catalog=your
db name;Data Source=your server name;Integrated Security=SSPI" then the
account that the Orchestration is running under must have access to the
database.

--
Jeff Lynch
"A BizTalk Enthusiast"
http://dotnetjunkies.com/WebLog/jlynch/



"JeffP" <JeffP@discussions.microsoft.com> wrote in message
news:9902B02C-BA8F-406E-BB44-45BE27EF75E1@microsoft.com...
> I have a small orchestration with a map that uses a database lookup
functoid.
> When I test the map, the lookup retreives data from the server correctly.
> When I deploy the orchestration and run it, I receive the following
message:
>
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
>
> From what I've found in the newsgroups so far,  it's my understanding that
> the credentials being used during the test are the currently logged in
user,
> which explains why it works there.
>
> I have tried various changes to the connection string, but it seems to
> ignore any sql logon parameters used. The biztalk development environment
is
> running on a single machine using local accounts. The sql database is on a
> different machine.
>
> I'm at a loss as to how to get the sql logon to work for this map. Any
ideas
> would be appreciated.

[ Post a follow-up to this message ]

Seems the problem was with the user accounts. The dev box being used was set
up with local accounts. Once it was reconfigured to use domain accounts the
lookup worked fine.



"Jeff Lynch" wrote:

> I believe the database lookup functoid uses standard ADO.NET calls to crea
te
> a connection to your database. The connection string you input as your
> second input parameter in the functoid should be a standard ADO.NET
> connection string and if you use "Provider=SQLOLEDB.1;Initial Catalog=your
> db name;Data Source=your server name;Integrated Security=SSPI" then the
> account that the Orchestration is running under must have access to the
> database.
>
> --
> Jeff Lynch
> "A BizTalk Enthusiast"
> http://dotnetjunkies.com/WebLog/jlynch/
>
>
>
> "JeffP" <JeffP@discussions.microsoft.com> wrote in message
> news:9902B02C-BA8F-406E-BB44-45BE27EF75E1@microsoft.com... 
> functoid. 
> message: 
> user, 
> is 
> ideas 
>
>
>

[ Post a follow-up to this message ]