Re: ComTI UDTs return empty in com 3.0

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Microsoft wrote:
"Sinna" <news4sinna_NOSPAM@xxxxxxxxxx> wrote in message news:u0S4AK$2GHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
Microsoft wrote:
"Sinna" <news4sinna_NOSPAM@xxxxxxxxxx> wrote in message news:OXIC%23J72GHA.5032@xxxxxxxxxxxxxxxxxxxxxxx
Microsoft wrote:
Some of the User Defined Types return empty when a call is made to our
Mainframe. Any ComTI components created on an old 2000 machine and
installed on 2003 servers work fine. But if we create new duplicate
components with UDTs in them on 2003 servers and attempt to use them then no
data is returned.

We thought at first that this was due to a marshalling issue with VS2005
vb.net, but we resorted to VB6 and tested the method and the UDTs returned
blank also. However is we call one of the components that was originally
created on a 2000 server and also calls the same program on our mainframe it
works like a charm.

Anyone have any suggestions as to why the UDTs are coming back blank for
components made using 2003 server.
Just guessing...
Are you dealing with possible errors correctly?
I know (out of experience) that when compiling a component using COM+, it links to another default interface depending on the OS. On Win2K it links to COM+ 1.0, while om WinXP on COM+ 1.5. When running the component built on WinXP on a Win2K machine, it fails because it can't find the default interface. On the contrary, when running the component build on Win2K on a WinXP machine, everything works like a charm.

That's why every programmer should build the application on the oldest platform that has to be supported: in your case: W2K.

Sinna
Actually, the problem is that the components were built around the year 2002. At the time we had Windows 2000. Since no changes have been made to the components, we use the install created from those servers. Now we are developing new applications and we dont wish to mingle ComTI Components between more than one program so we are making new ones. The method in the new component doesnt work even though the method we are recreating is an exact structural copy of the original method.
I don't think I get you right, but isn't it possible to build the new ComTI components on a Win2K OS? This should solve your problem (for as far as I can see).

Sinna

We no longer have any Win2K servers. All of our production servers and development servers are Win2003 servers and have been since Win2003 was released. We are now developing on only the Win2003 servers and only have access to the Component Builder on a Win2003 server.

Even if we did have a Win2K server running around here, it still wouldnt answer why the Components created on a Win2003 Server do not function properly.


You didn't read my comments or don't understand them.

Win2K comes with COM+ 1.0 as default interface
WinXP comes with COM+ 1.5 as default interface

When building a component against COM+, it depends on the OS what interface will be supported by default.
Win2K doesn't support COM+ 1.5, so it will fail, while WinXP does support COM+ 1.0.

Perhaps I'm mixed up with your subject. What do you mean with 'com 3.0'?
If it doesn't mean COM+ my comments don't make any sense at all.

Sinna
.

Relevant Pages

  • MAD.exe domain controllers not responding.
    ... DC1 is win2k sp3 and runs FSMO roles RID, scheme, domain name, GC. ... DC3 is win2k sp4 and runs FSMO role PCD em and is also a GC. ... My exchange servers both report Event id 2102 errors stating that the DC's ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: Moving NT4 based PDC and BDC to Win2k
    ... The "easiest" way to move to AD is to just upgrade your pdc. ... > We are totally Win2k with the exception of our PDC and BDC ... We are planning on retiring these servers ...
    (microsoft.public.win2000.active_directory)
  • Re: _msdcs. - Help Pls
    ... replication scope anywhere. ... Let me give a brief scenario about the ROOT1 and ROOT2 servers (These are ... Win2K SP4 servers). ... Zone Transfer - To any server (which was the previous settings in our Win2K ...
    (microsoft.public.windows.server.dns)
  • Re: Securing a Win2k DNS server outside firewall...
    ... Securing a Win2k DNS server outside firewall... ... I have 2 Windows 2000 DNS servers sitting on the outside of our firewall. ... When running a port scan against these servers, ...
    (Security-Basics)
  • ipsec and encryption in mixed environment
    ... We use windows 2000 servers but our desktops are mixed ... between win2k, win95, and winxp. ... the Win2k Pro with Client - Respond Only using Group ...
    (microsoft.public.win2000.security)