Hi, I have two orchestrations published as webservices. (Biztalk 2004 on XP
SP2) One is typed and the other untyped. The untyped one works fine when
called from another orchestration and from an NUnit test.

The typed one however always throws a weird error message saying " Server
was unable to process request. --> File or assembly name FileName .dll, or
one of its dependencies, was not found." . I have looked at the support
article for the same at http://support.microsoft.com/?kbid=910295 but to no
avail. I gave all possible users permissions on all temp folders, but the
same message appears.

I tried adding some code to the asmx.cs to write custom statements to the
event log but that didnt work either. Im totally stuck now .

Does anyone have an idea of what might be going wrong ?

Thanks in advance,
Benjy

[ Post a follow-up to this message ]

As a followup,
(1) i changed the second orchestration to use an untyped message but that
didnt solve the problem
(2) i found an article which said that proxy names more than 61 characters
have problems,. I changed mine but still no solution
(3) the webservices are running under anonymous user and the aspnet user and
the isolated host user both have permissions to the temp folders and the
databases. I even ran the ASP.NET user as SYSTEM (i know its dangerous, but
only temporarily, but that didnt work either)

The thing is the other orch has exactly the same kind of functionality and
design and it works perfectly ...i cant understand why this one alone wont
work.

I have enabled detailed error tracing, but it doesnt create the
BiztalkWebServices folder under
 \docsandsettings\machinename\aspnet\loca
lsettings\temp for the problematic
service. it does this for the other working service correctly. Im wondering
if the entire webservice is somehow invalid. (But the code compiles correctl
y)

Still waiting for a response from anyone out there

:-)

Benjy

"BizTalk Benjamin" wrote:

> Hi, I have two orchestrations published as webservices. (Biztalk 2004 on X
P
> SP2) One is typed and the other untyped. The untyped one works fine when
> called from another orchestration and from an NUnit test.
>
> The typed one however always throws a weird error message saying " Server
> was unable to process request. --> File or assembly name FileName .dll, or
> one of its dependencies, was not found." . I have looked at the support
> article for the same at http://support.microsoft.com/?kbid=910295 but to n
o
> avail. I gave all possible users permissions on all temp folders, but the
> same message appears.
>
> I tried adding some code to the asmx.cs to write custom statements to the
> event log but that didnt work either. Im totally stuck now .
>
> Does anyone have an idea of what might be going wrong ?
>
> Thanks in advance,
> Benjy

[ Post a follow-up to this message ]

Okay, the problem is solved. It does not like TYPED messages. When i changed
the input to xmlDocument, it actually went into the orchestration but then
the stack trace said something of an exception in some method with the word
'response' in it (cant remember the exact name). So now we made the response
message as untyped too and the damn thing works.

Why the heck cant BTS WebServices handle typed messages? I though that
strong typing was the norm and that an untyped message was an unusual case.
Can anyone from MSFT help? i can send the message schemas if you want ..

Hope this can help someone,
cheers
benjy


"BizTalk Benjamin" wrote:
[vbcol=seagreen]
> As a followup,
> (1) i changed the second orchestration to use an untyped message but that
> didnt solve the problem
> (2) i found an article which said that proxy names more than 61 characters
> have problems,. I changed mine but still no solution
> (3) the webservices are running under anonymous user and the aspnet user a
nd
> the isolated host user both have permissions to the temp folders and the
> databases. I even ran the ASP.NET user as SYSTEM (i know its dangerous, bu
t
> only temporarily, but that didnt work either)
>
> The thing is the other orch has exactly the same kind of functionality and
> design and it works perfectly ...i cant understand why this one alone wont
> work.
>
> I have enabled detailed error tracing, but it doesnt create the
> BiztalkWebServices folder under
>  \docsandsettings\machinename\aspnet\loca
lsettings\temp for the problematic
> service. it does this for the other working service correctly. Im wonderin
g
> if the entire webservice is somehow invalid. (But the code compiles correc
tly)
>
> Still waiting for a response from anyone out there
>
> :-)
>
> Benjy
>
> "BizTalk Benjamin" wrote:
> 

[ Post a follow-up to this message ]

Hey Ben,

You can definitely expose BizTalk orchestrations as web services using
typed messages.

I've run into that error message a couple of times in the past when
I've tried to run the wizard against a DLL containing an orchestration
that exposed messages whose types were defined in a different assembly
that was not deployed on the BizTalk server. Are your types in a
different assembly to your orchestrations? Sure it's not a deployment
issue?

Keith


BizTalk Benjamin wrote:[vbcol=seagreen]
> Okay, the problem is solved. It does not like TYPED messages. When i chang
ed
> the input to xmlDocument, it actually went into the orchestration but then
> the stack trace said something of an exception in some method with the wor
d
> 'response' in it (cant remember the exact name). So now we made the respon
se
> message as untyped too and the damn thing works.
>
> Why the heck cant BTS WebServices handle typed messages? I though that
> strong typing was the norm and that an untyped message was an unusual case
.
> Can anyone from MSFT help? i can send the message schemas if you want ..
>
> Hope this can help someone,
> cheers
> benjy
>
>
> "BizTalk Benjamin" wrote:
> 

[ Post a follow-up to this message ]

Hi Keith,
Yes, the schemas are in a different DLL to the orchestration. But im quite
sure i deployed them because i made sure that i deployed the orchestration
first before even publishing it as a webservice and the orch deploy wouldnt
have worked without the schema DLL being deployed first. I will check this u
p
again though cos i dont want to leave it as is without getting to the bottom
of the issue.

Thanks for the response, I'll post here when i get a few minutes to re-test
the scenario.

cheers,
benjy


"Keith  Knight" wrote:

> Hey Ben,
>
> You can definitely expose BizTalk orchestrations as web services using
> typed messages.
>
> I've run into that error message a couple of times in the past when
> I've tried to run the wizard against a DLL containing an orchestration
> that exposed messages whose types were defined in a different assembly
> that was not deployed on the BizTalk server. Are your types in a
> different assembly to your orchestrations? Sure it's not a deployment
> issue?
>
> Keith
>
>
> BizTalk Benjamin wrote: 
>
>

[ Post a follow-up to this message ]