|
Home > Archive > BizTalk Server General > November 2004 > BizTalk MSI applications exit codes?
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 MSI applications exit codes?
|
|
| Lars W. Andersen 2004-11-09, 5:49 pm |
| Hi,
every time I install or uninstall an MSI package I get an "exit code error"
in my eventlog, with the event id = 0
I suspect this is the btsicustomaction.dll that writes this, but I can't
find any documentation about what it means. I know Iknow .. I should always
read the report files in the installation folder to find out what went
wrong, but even if I do not get any errors in the reports, I still get an
exit code error in the application log.
So - whoever from microsoft wrote the damn .dll please tell us what the exit
codes mean!!! 
regards
Lars
| |
|
| Why don't you find out what the dll is doing by decompiling the sucker! (its
only a suggestion I wouldn't do it...)
or...
Instead of using damn.dll msi files use NANT there's an example in scotts
trace of thought trust me MSI are painful, again its only a suggestion...
"Lars W. Andersen" wrote:
> Hi,
>
> every time I install or uninstall an MSI package I get an "exit code error"
> in my eventlog, with the event id = 0
>
> I suspect this is the btsicustomaction.dll that writes this, but I can't
> find any documentation about what it means. I know Iknow .. I should always
> read the report files in the installation folder to find out what went
> wrong, but even if I do not get any errors in the reports, I still get an
> exit code error in the application log.
>
> So - whoever from microsoft wrote the damn .dll please tell us what the exit
> codes mean!!!
>
> regards
> Lars
>
>
>
| |
| Lars W. Andersen 2004-11-09, 5:49 pm |
| debugging it could be a fun excercise .. hehe .. If I only knew how ,, and
had the time :-/
I need to give our the operations ppl of our customer something they can
install, on several servers. Can I do that with NANT, across domains etc?
The next thing im gonna look at when I get the time is using SDC as we are a
microsoft shop and that is going to be the preferred way of building things
(down the line). So I havent spend much time playing with NANT...
regards
Lars
"John" <John@discussions.microsoft.com> wrote in message
news:68571454-2BE1-4C1E-946C-06D4A8EDA5EA@microsoft.com...
> Why don't you find out what the dll is doing by decompiling the sucker!
(its[vbcol=seagreen]
> only a suggestion I wouldn't do it...)
>
> or...
>
> Instead of using damn.dll msi files use NANT there's an example in scotts
> trace of thought trust me MSI are painful, again its only a suggestion...
>
> "Lars W. Andersen" wrote:
>
error"[vbcol=seagreen]
always[vbcol=seagreen]
an[vbcol=seagreen]
exit[vbcol=seagreen]
| |
|
| Hi,
It could be possible to debug it if you had the pdb file then attached to
MSI process.
Yes MSBuild probably would be the solution but I haven't used it yet as its
very beta. NANT is the best way at the moment to do BTS deployment and can
be used to deploy to mulitple environments (MSBuild in my opinion is a
Microsoft rip off of this product, don't quote me on that)
Heres a link
http://www.traceofthought.net/Perma...1dfb1af51e.aspx
John
"Lars W. Andersen" wrote:
> debugging it could be a fun excercise .. hehe .. If I only knew how ,, and
> had the time :-/
>
> I need to give our the operations ppl of our customer something they can
> install, on several servers. Can I do that with NANT, across domains etc?
>
> The next thing im gonna look at when I get the time is using SDC as we are a
> microsoft shop and that is going to be the preferred way of building things
> (down the line). So I havent spend much time playing with NANT...
>
> regards
> Lars
>
> "John" <John@discussions.microsoft.com> wrote in message
> news:68571454-2BE1-4C1E-946C-06D4A8EDA5EA@microsoft.com...
> (its
> error"
> always
> an
> exit
>
>
>
|
|
|
|
|