04-27-04 06:36 PM
There is a section in the documentation called Enabling Biztalk webservices
which talks about different option you have.
In short, if you are on Win2K3 (IIS 6.0) then you should create a seperate
Application Pool for your published webservices and run the Application
pool under a identity which is part of the Biztalk Isolated Host Users
group. If the BiztalkMgmt DB is remote then the Application Pool Identity
must be added to the Biztalk Isolated Host Users group of that machine.
If you are on WinXP or Win2K then if BiztalkMgmt DB is local then you
should add ASPNET user to Biztalk Isolated Host Users group of your local
machine.
If BiztalkMgmt DB is remote then you should change the process model
identity in machine.config to preferebly a domain identity and add that
idenity to Biztalk Isolated Host Users group of the remote server. Other
options are also given in the documentation.
Hope this helps.
| >>Hi,
| >>
| >>Check the event log for a message about not having access to
| >>BizTalkMgmtDb.. I think you are probably running into a common issue
| >>that is caused by web services being published under the Share Point
| >>Admin Pool, which runs as an identity that doesn't have access to the
| >>database.
| >>
| >>I haven't seen a solution to this problem that I'm happy with yet, so
| >>please post yours if you get it working!
| >>
| >>EZB
| >>
| >>"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in
message news:<Ow1lpihKEHA.2260@TK2MSFTNGP09.phx.gbl>...
| >>> Any eventlog messages?
| >>>
| >>> "Sedat Cankaya" <sedat.cankaya@ceng.metu.edu.tr> wrote in message
| >>> news:%23kIxdiWKEHA.2756@TK2MSFTNGP10.phx.gbl...
| >>> > We debugged the web service and saw that the message comes but we
think
| >>> that
| >>> > it could not be written to the SQL Server database. We are
submitting the
| >>> > document from another computer and it is trying to connect to the
SQL
| >>> > Server installed on the other
| >>> > machine with a IUSR account. However SQL Server is using the
Administrator
| >>> > account. So the message comes but it cannot be written to the
database and
| >>> > the orchestration suspends. Actually this is what we think. We
would be
| >>> glad
| >>> > to hear your solution suggestions. Thanks in advance...
| >>> >
| >>> >
| >>> > "Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote
in
| >>> > message news:e%23XZF3VKEHA.1764@TK2MSFTNGP12.phx.gbl...
| >>> > > What does the eventlog tell you?
| >>> > > The fact that the schema does not appear in the find message view
means
| >>> that
| >>> > > BizTalk never saw a message before that was recognised as being an
| >>> instance
| >>> > > of that particular schema!
| >>> > >
| >>> > > Regards,
| >>> > > Christof
| >>> > >
| >>> > > "Sedat Cankaya" <sedat.cankaya@ceng.metu.edu.tr> wrote in message
| >>> > > news:OEKY9tUKEHA.3016@tk2msftngp13.phx.gbl...
| >>> > > > I could not find the schema of my message in the find message
query.
| >>> Why?
| >>> I
| >>> > > > still could not solve the problem. Whay I could not receive the
xml
| >>> file
| >>> > > > sent through infopath?
| >>> > > >
| >>> > > >
| >>> > >
| >>> > >
| >>> >
| >>> >
| >>
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
[ Post a follow-up to this message ]
| 
