|
Home > Archive > BizTalk Server General > May 2004 > debugging client is not a biztalk server administrator
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 |
debugging client is not a biztalk server administrator
|
|
|
| Any clue about what this means? I am getting this error even though all the
security groups look correct.
I have BizTalk04 on server A with the database setup on server B. I am
using domain accounts to run the BizTalk host and everything else. The
accounts are on both server A and server B. Everything runs fine, files
will even go through the orchestration with no errors.
However, when I try to debug (specifically the attach command in the
orchestration debugger) it gives me the error.
Is it possible to debug an orchestration when you have a server setup like
this?
Thanks,
Josh
| |
| Matt Milner 2004-05-12, 1:18 pm |
| Are you logged in as a biztalk server administrator? (make sure you log out
and back in after adding yourself to the group)
Matt
"Josh" <josh[athome]iowaheart.com> wrote in message
news:OOd2t0DOEHA.1644@TK2MSFTNGP09.phx.gbl...
> Any clue about what this means? I am getting this error even though all
the
> security groups look correct.
>
> I have BizTalk04 on server A with the database setup on server B. I am
> using domain accounts to run the BizTalk host and everything else. The
> accounts are on both server A and server B. Everything runs fine, files
> will even go through the orchestration with no errors.
>
> However, when I try to debug (specifically the attach command in the
> orchestration debugger) it gives me the error.
>
> Is it possible to debug an orchestration when you have a server setup like
> this?
>
> Thanks,
> Josh
>
>
| |
|
| Yes, I'm logged in as BizTalk Server Administrator. I have logged out and
back in. I was in the BizTalk Server Admin group all along, but I just
haven't been able to attach to debug the orchestration.
Josh
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:%23iO7o3DOEHA.904@TK2MSFTNGP12.phx.gbl...
> Are you logged in as a biztalk server administrator? (make sure you log
out
> and back in after adding yourself to the group)
>
> Matt
>
>
> "Josh" <josh[athome]iowaheart.com> wrote in message
> news:OOd2t0DOEHA.1644@TK2MSFTNGP09.phx.gbl...
> the
like[vbcol=seagreen]
>
>
| |
| Matt Milner 2004-05-12, 5:26 pm |
| Are you on the same box as your orchestration, or are you running HAT from a
remote box?
Matt
"Josh" <josh[athome]iowaheart.com> wrote in message
news:uiSpNuFOEHA.3420@TK2MSFTNGP11.phx.gbl...
> Yes, I'm logged in as BizTalk Server Administrator. I have logged out and
> back in. I was in the BizTalk Server Admin group all along, but I just
> haven't been able to attach to debug the orchestration.
>
> Josh
>
>
> "Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
> news:%23iO7o3DOEHA.904@TK2MSFTNGP12.phx.gbl...
> out
all[vbcol=seagreen]
am[vbcol=seagreen]
The[vbcol=seagreen]
files[vbcol=seagreen]
> like
>
>
| |
| Niklas E 2004-05-23, 11:33 pm |
| Make sure you have the right rights (Administrators, BizTalk*, SSO*,
Debugger Users, EDI Subsystem Users and VS Developers groups)
Sometimes it can be hard to debug BizTalk 2004 projects. Many people have
asked me how-to do this. Here are some tips. One common error is that it
doesn't work if your .pdb files are not the same version as the compiled (in
use) .dlls. Another one is that older dlls are still in use when installed
into BizTalk.
Try this which works for me when I have trouble debugging:
- Shut down BizTalk 2004 service and Visual Studio
- Make sure you have the right rights (Administrators, BizTalk*, SSO*,
Debugger Users, EDI Subsystem Users and VS Developers groups)
- UnGAC your .NET assemblies (if you have them in the GAC) and uninstall you
BizTalk assemblies (do not unGAC you BizTalk assemblies yourself)
- Remove/Move ALL your .dlls that you want to debug (Even other copies that
might be in the "wrong" place. At least the obvious obj, bin and where you
run you dlls)
- Open Visual Studio and rebuild all your files that you want to debug (with
..pdb, debug symbols. You can check this in project properties even for
Release builds to be sure to have latest version of the .pdbs)
- ReGAC the recompiled .net assemblies and Install the recompiled BizTalk
assemblies
- Start BizTalk 2004 service
- Start Visual Studio with the project you want to debug and insert
break-points
- Attach the BTS process and check the CLR checkbox
- Now it should work
You can open two Visual Studios as well and debug mappings by attaching the
other Visual Studio as well. Then you don't need to re-install your BizTalk
assemblies every time.
Best regards
Niklas Engfelt
"Josh" <josh[athome]iowaheart.com> wrote in message
news:uiSpNuFOEHA.3420@TK2MSFTNGP11.phx.gbl...
> Yes, I'm logged in as BizTalk Server Administrator. I have logged out and
> back in. I was in the BizTalk Server Admin group all along, but I just
> haven't been able to attach to debug the orchestration.
>
> Josh
>
>
> "Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
> news:%23iO7o3DOEHA.904@TK2MSFTNGP12.phx.gbl...
> out
all[vbcol=seagreen]
am[vbcol=seagreen]
The[vbcol=seagreen]
files[vbcol=seagreen]
> like
>
>
|
|
|
|
|