|
Home > Archive > BizTalk Server General > November 2004 > Service instance could not be terminated
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 |
Service instance could not be terminated
|
|
| HÃ¥kan Thornqvist 2004-10-15, 9:11 pm |
| I have alot of messages in Health and Activity Tracking that I cannot
terminate.
I get the following error message when trying to 'Terminate Service':
"One or more service instances could not be terminated. It is possible that
the instance(s) has already completed or terminated. or it may have a pending
control message"
Any suggestions?
Details of the message:
Message type: empty
Message Status: Delivered, not consumed
Service Class: Isolated adapter
Retry Count: 0
Timestamp: [datetime]
Submitter: [workstation]\ASPNET
MsgBox Server: empty
MsgBox DB: empty
Host: BizTalkServerIsolatedHost
OriginatorSID: [workstation]\ASPNET
OriginatorPID: s-1-5-7
Inbound Adapter: SOAP
Inbound URL: [URL]
Outbound Adapter: empty
Outbound URL: empty
Message ID: [MessageID]
Service Instance details:
Service Name: <Isolated Adapter>
Assembly name: empty
Service Class: Isolated Adapter
Message Count: 18
Status: Active
Pending action: Terminate
Pending job action submit time: 2004-10-11 12:32:50
Service instance ID: [ID]
Host: BizTalkServerIsolatedHost
Activation time 2004-10-08 09:08:05
// HÃ¥kan Thornqvist
| |
| Stephen W. Thomas 2004-10-15, 9:11 pm |
| You might want to try stopping the host, Terminate them again, then start the
Host.
In the past, that has worked for me.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"HÃ¥kan Thornqvist" wrote:
> I have alot of messages in Health and Activity Tracking that I cannot
> terminate.
> I get the following error message when trying to 'Terminate Service':
> "One or more service instances could not be terminated. It is possible that
> the instance(s) has already completed or terminated. or it may have a pending
> control message"
>
> Any suggestions?
>
> Details of the message:
> Message type: empty
> Message Status: Delivered, not consumed
> Service Class: Isolated adapter
> Retry Count: 0
> Timestamp: [datetime]
> Submitter: [workstation]\ASPNET
> MsgBox Server: empty
> MsgBox DB: empty
> Host: BizTalkServerIsolatedHost
> OriginatorSID: [workstation]\ASPNET
> OriginatorPID: s-1-5-7
> Inbound Adapter: SOAP
> Inbound URL: [URL]
> Outbound Adapter: empty
> Outbound URL: empty
> Message ID: [MessageID]
>
> Service Instance details:
> Service Name: <Isolated Adapter>
> Assembly name: empty
> Service Class: Isolated Adapter
> Message Count: 18
> Status: Active
> Pending action: Terminate
> Pending job action submit time: 2004-10-11 12:32:50
> Service instance ID: [ID]
> Host: BizTalkServerIsolatedHost
> Activation time 2004-10-08 09:08:05
>
> // HÃ¥kan Thornqvist
| |
| Matt Milner 2004-10-15, 9:11 pm |
| In this case, the host is probably your IIS service and restarting it should
get rid of these messages. Likely you have web service calls that timed out
or did not get a resonse but messages were posted back to the isolated
adapter anyway. These will hang out until you stop that host. Biztalk does
not have control over the host process (IIS) so it can't terminate these in
the same way it can with its own host.
Matt
"Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
message news:A3C252E9-74B8-4E66-95AD-CAF08ECBB48F@microsoft.com...[vbcol=seagreen]
> You might want to try stopping the host, Terminate them again, then start
> the
> Host.
>
> In the past, that has worked for me.
>
> Stephen W. Thomas
> http://www.geekswithblogs.net/sthomas
>
>
> "Håkan Thornqvist" wrote:
>
| |
| HÃ¥kan Thornqvist 2004-10-15, 9:11 pm |
| Thanks, stopping IIS did the trick.
"Matt Milner" wrote:
> In this case, the host is probably your IIS service and restarting it should
> get rid of these messages. Likely you have web service calls that timed out
> or did not get a resonse but messages were posted back to the isolated
> adapter anyway. These will hang out until you stop that host. Biztalk does
> not have control over the host process (IIS) so it can't terminate these in
> the same way it can with its own host.
>
> Matt
>
>
> "Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
> message news:A3C252E9-74B8-4E66-95AD-CAF08ECBB48F@microsoft.com...
>
>
>
| |
| Gary Michael 2004-10-15, 9:11 pm |
| I have had the same problem at work. I am at home right now so I cannot try
the stated solution, but I would have thought that re-booting the PC would
certainly cleared out the messages from HAT since effectively I am stopping
and starting the IIS service. Is this correct?
I cannot get rid of any message that is sent to HAT. This just started a
day ago so I am not sure what happened. I have tried recreating the
configuration and also repairing both SQLServer and BizTalk. Still get the
same error when I try to terminate the messages. I am about ready to go
through the painful process of reinstalling the entire BizTalk server.
Any other ideas, or do you believe I still need to stop and start IIS in
order to clear these messages? Also, will that stop the next message that
gets to HAT from having the same problem?
I don't think it will solve my problem but I am willing to give it a try
anyway.
Any suggestions before I reinstall BizTalk would be appreciated.
"HÃ¥kan Thornqvist" wrote:
[vbcol=seagreen]
> Thanks, stopping IIS did the trick.
>
> "Matt Milner" wrote:
>
| |
| HÃ¥kan Thornqvist 2004-10-16, 5:52 pm |
| As Stephen said, stop the host (IIS), then terminate the service instance and
start IIS again. It worked for me.
Actually, if the pending action _is_ 'terminate', just an 'iisreset' should
do it (?).
// HÃ¥kan Thornqvist
"Gary Michael" wrote:
[vbcol=seagreen]
> I have had the same problem at work. I am at home right now so I cannot try
> the stated solution, but I would have thought that re-booting the PC would
> certainly cleared out the messages from HAT since effectively I am stopping
> and starting the IIS service. Is this correct?
>
> I cannot get rid of any message that is sent to HAT. This just started a
> day ago so I am not sure what happened. I have tried recreating the
> configuration and also repairing both SQLServer and BizTalk. Still get the
> same error when I try to terminate the messages. I am about ready to go
> through the painful process of reinstalling the entire BizTalk server.
>
> Any other ideas, or do you believe I still need to stop and start IIS in
> order to clear these messages? Also, will that stop the next message that
> gets to HAT from having the same problem?
>
> I don't think it will solve my problem but I am willing to give it a try
> anyway.
>
> Any suggestions before I reinstall BizTalk would be appreciated.
>
> "HÃ¥kan Thornqvist" wrote:
>
| |
| Paul Lloyd 2004-10-27, 7:46 am |
| I have the same problem. I have messages in HAT that have a Service Pending
Job of Terminate, and so I can't Terminate them again. I can stop IIS,
teminate them, restart it, reboot the machine, stop all the hosts, and many
other permutations whatever.. and they still won't go. Worse, I can't
undeploy - there are still instances of the Orchestration (I know ! I can't
get rid of them).
So basically it's broken.
Any ideas - before I throw away all the databases and start again. Actually,
this is the second installation that has done this to me - I must be lucky.
| |
| Paul Lloyd 2004-10-27, 7:46 am |
| I had one last go.. it is a two server group so would involve me in a lot of
messing about. Stopped every web site I could, every host on each server,
basically stopped everything and they magically now delete. - Just after I
ask for help - typical !
cheers
Paul
"Paul Lloyd" wrote:
> I have the same problem. I have messages in HAT that have a Service Pending
> Job of Terminate, and so I can't Terminate them again. I can stop IIS,
> teminate them, restart it, reboot the machine, stop all the hosts, and many
> other permutations whatever.. and they still won't go. Worse, I can't
> undeploy - there are still instances of the Orchestration (I know ! I can't
> get rid of them).
>
> So basically it's broken.
> Any ideas - before I throw away all the databases and start again. Actually,
> this is the second installation that has done this to me - I must be lucky.
>
| |
|
| FYI... I have this happen as well. I find most often the 'only' quick
solution is to stop BTS altogether, Terminate the message instance, and
restart BTS.
"Paul Lloyd" wrote:
[vbcol=seagreen]
> I had one last go.. it is a two server group so would involve me in a lot of
> messing about. Stopped every web site I could, every host on each server,
> basically stopped everything and they magically now delete. - Just after I
> ask for help - typical !
> cheers
> Paul
>
> "Paul Lloyd" wrote:
>
|
|
|
|
|