|
Home > Archive > BizTalk Server > July 2005 > Error 1067 when starting BizTalk Server 2002
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 |
Error 1067 when starting BizTalk Server 2002
|
|
| Chris Cichocki 2005-07-11, 5:51 pm |
| I recently received a new PC running Windows XP sp2 and when I try to start
the BizTalk Messaging Service I receive the following error:
Could not start the BizTalk Messaging Service service on Local Computer.
Error 1067: The process terminated unexpectedly.
There are no messages in the Application, System or Security logs related to
this error.
Any ideas on where to start looking?
Thanks,
Chris
| |
| WenJun Zhang[msft] 2005-07-12, 7:55 am |
| Hi Chris,
Looks like the main service process crashes during startup. Do you
see any MSDTC or COM+ errors in the event log?
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
| Chris Cichocki 2005-07-12, 5:51 pm |
| This error is placed in the Application event log when I sign in:
TransactionManager->GetWhereabouts failed. If Distributed Transaction
Coordinator is configured to use remote host to coordinate transactions, it
is likely that remote host cannot be contacted. You can configure MSDTC to
use local coordinator by clicking MSDTC toolbar button in Component Services
MMC snap-in. Since further execution is impossible at this time, server
process has been terminated.
Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}
Server Application Instance ID:
{5B891F43-C558-477D-8098-6FD742A8FB23}
Server Application Name: System Application
Error Code = 0x8004d01b : The Transaction Manager is not available.
COM+ Services Internals Information:
File: d:\qxp_slp\com\com1x\src\comsvcs\txprop\
dtcinfo.cpp, Line: 164
Comsvcs.dll file version: ENU 2001.12.4414.258 shp
I checked the setting for MSDTC and verified that it is set to local. I'm
not sure why I didn't see it before, but the System event log is loaded with
occurances of this DCOM error:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10021
Date: 7/11/2005
Time: 8:21:55 PM
User: N/A
Computer: LOC3B026
Description:
The launch and activation security descriptor for the COM Server application
with CLSID
{2A6D72F1-6E7E-4702-B99C-E40D3DED33C3}
is invalid. It contains Access Control Entries with permissions that are
invalid. The requested action was therefore not performed. This security
permission can be corrected using the Component Services administrative tool.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Also, when I go into the Component Services snapin and select "Component
Services\My Computer\COM+ Applications", I get the following error:
An error occurred while processing the last operation. Error code 80080005
- Server execution failed. The event log may contain additional
troubleshooting information.
Sounds like things are pretty messed up... what is the likelyhood that this
can be resolved, or is the best path to reload Windows?
Thanks,
Chris Cichocki
""WenJun Zhang[msft]"" wrote:
> Hi Chris,
>
> Looks like the main service process crashes during startup. Do you
> see any MSDTC or COM+ errors in the event log?
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
| |
| Chris Cichocki 2005-07-12, 5:51 pm |
| The DCOM errors are related to McAfee's antivirus program running on my PC.
Apparently we need to get a patch from them to fix those errors.
"Chris Cichocki" wrote:
[vbcol=seagreen]
> This error is placed in the Application event log when I sign in:
>
> TransactionManager->GetWhereabouts failed. If Distributed Transaction
> Coordinator is configured to use remote host to coordinate transactions, it
> is likely that remote host cannot be contacted. You can configure MSDTC to
> use local coordinator by clicking MSDTC toolbar button in Component Services
> MMC snap-in. Since further execution is impossible at this time, server
> process has been terminated.
> Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}
> Server Application Instance ID:
> {5B891F43-C558-477D-8098-6FD742A8FB23}
> Server Application Name: System Application
> Error Code = 0x8004d01b : The Transaction Manager is not available.
> COM+ Services Internals Information:
> File: d:\qxp_slp\com\com1x\src\comsvcs\txprop\
dtcinfo.cpp, Line: 164
> Comsvcs.dll file version: ENU 2001.12.4414.258 shp
>
> I checked the setting for MSDTC and verified that it is set to local. I'm
> not sure why I didn't see it before, but the System event log is loaded with
> occurances of this DCOM error:
>
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10021
> Date: 7/11/2005
> Time: 8:21:55 PM
> User: N/A
> Computer: LOC3B026
> Description:
> The launch and activation security descriptor for the COM Server application
> with CLSID
> {2A6D72F1-6E7E-4702-B99C-E40D3DED33C3}
> is invalid. It contains Access Control Entries with permissions that are
> invalid. The requested action was therefore not performed. This security
> permission can be corrected using the Component Services administrative tool.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Also, when I go into the Component Services snapin and select "Component
> Services\My Computer\COM+ Applications", I get the following error:
>
> An error occurred while processing the last operation. Error code 80080005
> - Server execution failed. The event log may contain additional
> troubleshooting information.
>
> Sounds like things are pretty messed up... what is the likelyhood that this
> can be resolved, or is the best path to reload Windows?
>
> Thanks,
> Chris Cichocki
>
>
>
> ""WenJun Zhang[msft]"" wrote:
>
| |
| WenJun Zhang[msft] 2005-07-13, 7:54 am |
| Hi Chris,
I think you have to remove any consumer anti-virus softwares on the
server to test. They usually break Biztalk service due to the
features like file receive function.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|