Windows Server

Dana · Guest

Event Type: Error
Event Source: HIP Service
Event ID: 810
Description:
(810) A Transaction Integrator HIP Application could not create the
server application program.
HIP Application: TestHIPApp

ProgID: UpcaseHIP.Server

HRESULT: 80040154

EXPLANATION
A Transaction Integrator HIP Application, listed above, received a
failure indication when calling CoCreateInstance for the ProgID listed
above.

This started after I recompiled my TI project. What did I do wrong?

Rob Beardsworth [MSFT] · Guest

Well, the error is Class not Registered. You say you recompiled your TI
project, did you make any changes to it (some changes make us generate new
CLSIDs)? Have you regsvr32-ed your implementing DLL ? Go look for
"UpcaseHIP.Server" under HKLM\Classes and see if the CLSID mentioned in
there is defined under HKLM\CLSID.

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------
From: Dana <a@b>
Subject: (810) A Transaction Integrator HIP Application could not create
the server application program
Date: Tue, 23 Nov 2004 09:20:14 -0800
Organization: .
Message-ID: <75s6q05ns0s1tukda8me1koks0tcp0e75j@4ax.com>
X-Newsreader: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: ip68-4-148-188.oc.oc.cox.net 68.4.148.188
Lines: 1
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14
.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4457
X-Tomcat-NG: microsoft.public.hiserver.general

Event Type: Error
Event Source: HIP Service
Event ID: 810
Description:
(810) A Transaction Integrator HIP Application could not create the
server application program.
HIP Application: TestHIPApp

ProgID: UpcaseHIP.Server

HRESULT: 80040154

EXPLANATION
A Transaction Integrator HIP Application, listed above, received a
failure indication when calling CoCreateInstance for the ProgID listed
above.

This started after I recompiled my TI project. What did I do wrong?

Dana · Guest

It was dumb mistake. When this experiment was first written, C# was
used, but later abandoned in favor of VB 6.0 because I could not get
it to work. Hence the same Prog ID from two projects, one that works
and one that does not (the C# one registered for COM Interop). The
TIM file is defined in the C# solution. Finally found the VB 6.0
project and compiled it and... it is working again.

I've been trying to develop a "best practice" for our development
staff while evaluating the HIS 2004 capabilities. Unfortunately this
is a background task and ... the matrix of options is pretty large.

The documentation is rather sparse, so alot of experimenting led to
this. Some questions.

Does HIP support variable size final field? When I set this property
it seems to be ignored.
Does HIP support in, out or only in/out parameters?
Can I use COMTI context (which looks useful) with HIP?
Can I use Meta Data (full) with HIP - if so how does it work?
If I don't use Meta Data (full) how do server errors get reported to
the Host (client) application?

- Dana

Rob Beardsworth [MSFT] wrote:

Terry Bullington [MSFT] · Guest

HIP does support variable final field but there are some restrictions such
as the final field has to be either a string or an array.

Parameters can be in, in/out or output.

Context for HIP is currently not implemented (we do include the optional
context array but currently have no way to populate it). In the future we
will architect a method for clients to pass context.

You can use full meta data (Include All Information) it is the only way to
get error information returned to the client program. It uses a little
more than 400 bytes of data, it can be significant if you are using a link
programming model where you are limited to 32K of user data. If you create
a project and select "Include All Information" and then export the COBOL
you will see the generated meta data. On input the method name can be used
as resolution data (i.e. as a means to map the call to a particular method
in a windows application program), on output the error code (SERRORCODE)
and error description (BSTRHELPSTRING) are useful for error reporting (the
others are of dubious value for HIP).
--------------------
From: Dana <a@b>
Subject: Re: (810) A Transaction Integrator HIP Application could not
create the server application program
Date: Wed, 24 Nov 2004 18:08:30 -0800
Organization: .
Message-ID: <aidaq0558t97mdtr88qvq41i80igo3sjvo@4ax.com>
References: <75s6q05ns0s1tukda8me1koks0tcp0e75j@4ax.com>
<tgRlncl0EHA.3440@cpmsftngxa10.phx.gbl>
X-Newsreader: Forte Agent 1.8/32.548
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: microsoft.public.hiserver.general
NNTP-Posting-Host: ip68-4-148-188.oc.oc.cox.net 68.4.148.188
Lines: 1
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09
phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.hiserver.general:4462
X-Tomcat-NG: microsoft.public.hiserver.general

It was dumb mistake. When this experiment was first written, C# was
used, but later abandoned in favor of VB 6.0 because I could not get
it to work. Hence the same Prog ID from two projects, one that works
and one that does not (the C# one registered for COM Interop). The
TIM file is defined in the C# solution. Finally found the VB 6.0
project and compiled it and... it is working again.

I've been trying to develop a "best practice" for our development
staff while evaluating the HIS 2004 capabilities. Unfortunately this
is a background task and ... the matrix of options is pretty large.

The documentation is rather sparse, so alot of experimenting led to
this. Some questions.

Does HIP support variable size final field? When I set this property
it seems to be ignored.
Does HIP support in, out or only in/out parameters?
Can I use COMTI context (which looks useful) with HIP?
Can I use Meta Data (full) with HIP - if so how does it work?
If I don't use Meta Data (full) how do server errors get reported to
the Host (client) application?

- Dana

Rob Beardsworth [MSFT] wrote:

Dana · Guest

Thanks Terry.

In the topic "Connecting HIP Components to Visual Basic Applications"
it states:

All parameters defined to type library methods must be Input\Output.
The Implements keyword does not support parameters defined as either
input or output. All parameters must be defined as input or output.

Does this apply only to VB 6.0 ?? Or VB.NET as well? C#? Do you have
to use the Implements keyword?

- Dana

Terry Bullington [MSFT] wrote:

HIP does support variable final field but there are some restrictions
such
as the final field has to be either a string or an array.

Parameters can be in, in/out or output.

Context for HIP is currently not implemented (we do include the
optional
context array but currently have no way to populate it). In the
future we
will architect a method for clients to pass context.

You can use full meta data (Include All Information) it is the only
way to
get error information returned to the client program. It uses a
little
more than 400 bytes of data, it can be significant if you are using a
link
programming model where you are limited to 32K of user data. If you
create
a project and select "Include All Information" and then export the
COBOL
you will see the generated meta data. On input the method name can be
used
as resolution data (i.e. as a means to map the call to a particular
method
in a windows application program), on output the error code
(SERRORCODE)
and error description (BSTRHELPSTRING) are useful for error reporting
(the
others are of dubious value for HIP).
--------------------

Rob Beardsworth [MSFT] · Guest

HI Dana,
as you can see from our sample C# server, all you do is make your class
inherit from the appropriate thing (basically equivalent to the
Implements). There is no restriction on C# parameter directions. In VB.NET,
you still use the Implements keyword, but the direction of parameters seems
to be freely choosable.

Rob Beardsworth
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
--------------------

Thanks Terry.

In the topic "Connecting HIP Components to Visual Basic Applications"
it states:

All parameters defined to type library methods must be Input\Output.
The Implements keyword does not support parameters defined as either
input or output. All parameters must be defined as input or output.

Does this apply only to VB 6.0 ?? Or VB.NET as well? C#? Do you have
to use the Implements keyword?

- Dana

Terry Bullington [MSFT] wrote:

HIP does support variable final field but there are some restrictions
such
as the final field has to be either a string or an array.

Parameters can be in, in/out or output.

Context for HIP is currently not implemented (we do include the
optional
context array but currently have no way to populate it). In the
future we
will architect a method for clients to pass context.

You can use full meta data (Include All Information) it is the only
way to
get error information returned to the client program. It uses a
little
more than 400 bytes of data, it can be significant if you are using a
link
programming model where you are limited to 32K of user data. If you
create
a project and select "Include All Information" and then export the
COBOL
you will see the generated meta data. On input the method name can be
used
as resolution data (i.e. as a means to map the call to a particular
method
in a windows application program), on output the error code
(SERRORCODE)
and error description (BSTRHELPSTRING) are useful for error reporting
(the
others are of dubious value for HIP).
--------------------

(810) A Transaction Integrator HIP Application could not cre

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1