RE: Very odd behaviour of our receivehost (bts2006 R2)
- From: isabelledc <isabelledc@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 7 Jul 2009 23:57:01 -0700
I know biztalk heavily relies on AD...
It's not the isolated receive host , it's the 'normal' receive host that is
used for file/sql/msmq/ax2009 adapter and mqsc receiving.
This odd behaviour not only happens after AD-reboots but ALSO if f.e. the
axapta AOS is down (when there's a code-release f.e.) or after an IPL of the
mainframe.
In both cases of course you get error-messages because the receive-location
can not find the AOS or for mqsc can not reach the mainframe.
But after all is normal (aos is back or mf is back up) and you don't see
errors in the eventlog anymore , receivehost is still running!!! , still
nothing gets picked up.
We know when mf is ipl-ed( kind of a reboot) , so we stop/start the
receivehost after that and still this sometimes doesn't help, it has happened
that we have to do a stop/start of the receivehost again. (then it always
works)
We have MOM in place but if everything is normal again what can you do?
No errors , service running but nothing happens....
It's my impression that the adapters I installed (AX2009 biztalk adapter
and MQSC adapter) don't react well if they receive communication errors.
If you have problems with sql-server f.e. the sql-adapter will kind of reset
itself after x errors (you can see this in the eventlog)
I'm thinking about creating separate hosts for the mqsc and ax-adapter to
check if my hunch is right.
Is there someone using those adapters that has the same problem?
Isabelle
"Mark" wrote:
It is normal for BizTalk to error badly when AD goes down because AD is.
relied on for external and internal (eg BizTalk SSO) authentication. BizTalk
has a hard and constant dependancy on AD. if it goes down, BizTalk goes down.
The eventlog is the normal place for find error information like this. You
should have a monitoring solution in place that monitors the eventlog
actively and alerts admin personnel.
As for why that recievehost doesn't come back up, that might take more
troubleshooting. Is it an isolated receivehost?
"isabelledc" wrote:
After rebooting an AD-server we saw the following errors in biztalk-eventlog
1/error
Event ID: 6913
An attempt to connect to "BizTalkMgmtDb" SQL Server database on server "sql"
failed.
Error: "Login failed for user ''. The user is not associated with a trusted
SQL Server connection."
2/ warning
Event ID: 5773
All receive locations are being temporarily disabled because either the
MessageBox or Configuration database is not available. When these databases
become available, the receive locations will be automatically enabled.
3/Warning
Event ID: 5410
An error occurred that requires the BizTalk service to terminate. The most
common causes are the following:
1) An unexpected out of memory error.
OR
2) An inability to connect or a loss of connectivity to one of the BizTalk
databases.
The service will shutdown and auto-restart in 1 minute. If the problematic
database remains unavailable, this cycle will repeat.
Error message: Login failed for user ''. The user is not associated with a
trusted SQL Server connection.
Error source:
BizTalk host name: ReceiveHost
Windows service name: BTSSvc$ReceiveHost
We find this last one for every host I defined.
After a little while we see the restarting of all hosts except the
receivehost!
(setup looks exactly the same as the send,processing and trackinghost I have)
Odd thing is that after receiving a call that there was no communication , I
looked at the admin-console and all hosts were running!!!
Someone else looked at the services and they were also all running!
After stopping and starting the receive (and sendhost) everything worked
fine again.
After the facts the only thing we could find that something wasn't right was
by looking in the eventlog and there we saw that the all hostinstances were
restarted , but the receivehost was not there, when I stopped the receive and
sendhost from admin-console , we only see the stop of the sendhost .
Restart by me of send and receive , receive and send host show up in the
eventlog.
It's not only after AD-reboot that we have this , this also happens
sometimes after the connection to another application has given to many
errors (my impression)
We use MQSC and Dynamics AX 2009 adapter as extra installed adapters that
can sometimes cause lots of errors (for instance if mainframe is unavailable
or if axapta AOS is unavailable)
Has anyone come across something like this?
Or now where we could look for something to react on so we know it's going
wrong.
(preferrably before the business calls us that something's wrong)
Thank you for your reply
Isabelle
- References:
- Prev by Date: Problem mapping looping elements into a flat structure
- Next by Date: Web service/API/mash-up search strategies
- Previous by thread: RE: Very odd behaviour of our receivehost (bts2006 R2)
- Next by thread: Problem mapping looping elements into a flat structure
- Index(es):
Relevant Pages
|
Loading
