I have moved an application from one machine to another.  It worked on the
previous machine.  The orchestration consumes several Web Services from
another server.

Each machine has a dedicated local BizTalk user configured identically
including password.

If I use the Deployment wizard and a deployment script, deployment works.

If I undeploy using BizTalk Explorer and try to redeploy using the VS.NET
IDE from the project, it builds but it fails to deploy.

The TaskList shows the following:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.

I do not understand why there should be a difference as the same user should
be involved in both cases with the same set of permissions.

What am i missing?

cheers
--
PeterW

[ Post a follow-up to this message ]

Peter,

>I have moved an application from one machine to another.  It worked on the
> previous machine.  The orchestration consumes several Web Services from
> another server.
>
> Each machine has a dedicated local BizTalk user configured identically
> including password.
>
> If I use the Deployment wizard and a deployment script, deployment works.
>
> If I undeploy using BizTalk Explorer and try to redeploy using the VS.NET
> IDE from the project, it builds but it fails to deploy.
>
> The TaskList shows the following:
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
>
> I do not understand why there should be a difference as the same user
> should
> be involved in both cases with the same set of permissions.

Check your project properties, in the "Deployment" section. Usually, the
name of the database server (where the BizTalkMgmt db is) to deploy to is
saved there, and it probably is still pointing to your previous environment.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Yes, looks like the problem is SQL database hasn't been changed in the
project property. You can check this and I assume the issue should go away.

Have a nice day.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.

[ Post a follow-up to this message ]

Exactly right.

Thanks for the help
--
PeterW


""WenJun Zhang[msft]"" wrote:

> Yes, looks like the problem is SQL database hasn't been changed in the
> project property. You can check this and I assume the issue should go away
.
>
> Have a nice day.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>
>
>

[ Post a follow-up to this message ]