|
Home > Archive > BizTalk Server General > June 2005 > BizTalk Deployment error while exporting to binding file
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 |
BizTalk Deployment error while exporting to binding file
|
|
| Marijn M. 2005-05-27, 7:56 am |
| Hello,
yesterday, we try to export the binding information from an assembly to
an xml file using the BizTalk Deployment Wizard. The export stops
processing (40% of the progress bar is blue) and the
deploymentwizard-screen disappears.
The following error is writen to the eventlog:
------------------------------------------------------------------------------
A condition has occurred that indicates this COM+ application is in an
unstable state or is not functioning correctly. Assertion Failure:
!m_punk
Server Application ID: {122DF2F2-293A-4F2E-BC11-DA48375A3D27}
Server Application Instance ID:
{9FE0C1E9-D068-429E-AA58-2BDCD986A123}
Server Application Name: Microsoft.Biztalk.Deployment
The serious nature of this error has caused the process to terminate.
COM+ Services Internals Information:
File: d:\nt_qxp\com\com1x\src\comsvcs\jit\jit.cpp, Line: 858
Comsvcs.dll file version: ENU 2001.12.4414.53 shp
------------------------------------------------------------------------------
Earlier we had succesfully made several binding files using this
machine.
This morning, the same problem occurs on another machine. On a third
machine, the wizard works correctly, producing an xml file.
Any help would greatly appreciated,
Marijn Moerman
| |
| Tomas Restrepo \(MVP\) 2005-05-28, 5:48 pm |
| Marijn,
> yesterday, we try to export the binding information from an assembly to
> an xml file using the BizTalk Deployment Wizard. The export stops
> processing (40% of the progress bar is blue) and the
> deploymentwizard-screen disappears.
>
> The following error is writen to the eventlog:
>
> ------------------------------------------------------------------------------
> A condition has occurred that indicates this COM+ application is in an
> unstable state or is not functioning correctly. Assertion Failure:
> !m_punk
>
> Server Application ID: {122DF2F2-293A-4F2E-BC11-DA48375A3D27}
> Server Application Instance ID:
> {9FE0C1E9-D068-429E-AA58-2BDCD986A123}
> Server Application Name: Microsoft.Biztalk.Deployment
> The serious nature of this error has caused the process to terminate.
> COM+ Services Internals Information:
> File: d:\nt_qxp\com\com1x\src\comsvcs\jit\jit.cpp, Line: 858
> Comsvcs.dll file version: ENU 2001.12.4414.53 shp
> ------------------------------------------------------------------------------
What OS is this? XP? 2003?
This sounds like you might be running, maybe, on a COM+ bug... have you
checked to see if the machine in question has the latest COM+ rollup package
installed?
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| ahrnolt 2005-05-29, 5:52 pm |
| In article <urL#jm9YFHA.1412@TK2MSFTNGP12.phx.gbl>, "Tomas Restrepo
\(MVP\)" <tomasr@mvps.org> says...
> Marijn,
>
> What OS is this? XP? 2003?
>
> This sounds like you might be running, maybe, on a COM+ bug... have you
> checked to see if the machine in question has the latest COM+ rollup package
> installed?
>
Tomas,
the machine in question happens to be my machine, running XP SP1. We
installed the rollup as mentioned in KB837119. The problem now also
occurs on other biztalk machines. Before last week, everything worked
fine on all machines. So we have more or less no idea where or what to
look for to solve this thingy.
grt,
Arnold Riet
| |
| Tomas Restrepo \(MVP\) 2005-05-29, 5:52 pm |
| Arnold,
>
> Tomas,
>
> the machine in question happens to be my machine, running XP SP1. We
> installed the rollup as mentioned in KB837119. The problem now also
> occurs on other biztalk machines. Before last week, everything worked
> fine on all machines. So we have more or less no idea where or what to
> look for to solve this thingy.
Sounds like a recent update installed in the machines in question might be
the culprit. Have you checked which hotfixes have been installed recently on
the machines?
Also, I'd certainly consider giving SP2 a try to see if that improves the
situation...
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
| Marijn M. 2005-06-03, 2:47 am |
| Windows XP
|
|
|
|
|