|
Home > Archive > BizTalk Server Orchestration > April 2006 > deploy in IDE fails but with wizard succeeds
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 |
deploy in IDE fails but with wizard succeeds
|
|
| PeterW 2006-04-18, 12:46 am |
| 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
| |
| Tomas Restrepo \(MVP\) 2006-04-18, 12:46 am |
| 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/
| |
| WenJun Zhang[msft] 2006-04-18, 12:46 am |
| 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.
| |
| PeterW 2006-04-27, 7:25 am |
| 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.
>
>
>
>
|
|
|
|
|